Jump to content

lumax

Member
  • Posts

    27
  • Joined

  • Last visited

Posts posted by lumax

  1. Haha cen. seems like you re-Uploaded the file after i pointed out that files where removed, such as the license file :P
    Also you still fail at rule 1.

    1. All redistributions must keep the original package intact.
    Its not the orginale package when you have repacked it :P

    But im not gonna bother with this anymore, i got all the latest files and its not really my job to police this.
    I'll use the orginale source if i need to redownload something. i can atleast be sure the files has not been tampered with.

    No offence cen. but im always skeptic to some random download link posted in any forum, not only this one.

    This was merly a classic example of how people dont understand license, copyright, ip-right these days.


    In case other are equal as skeptic as me when it comes to random download links. you can use the orginale source.

    Program.

    ibattle.org/Downloads/Bec.zip

     

    Plugins.

    ibattle.org/Downloads/Plugins/ConnectionLimiter.zip
    ibattle.org/Downloads/Plugins/Rss.zip
    ibattle.org/Downloads/Plugins/ScriptBan.zip
    ibattle.org/Downloads/Plugins/StaffNames.zip
    ibattle.org/Downloads/Plugins/WatchDog.zip
    ibattle.org/Downloads/Plugins/Ts3.zip
    ibattle.org/Downloads/Plugins/Plugin-dev-example.zip

  2. Why are you quoting the license to me. seems like you are the one who needs to read it.
    You failed at rule 1.

    Anyway enough about that.
    I suggest people use the orginale source  (ibattle.org) as long as its there.
     

  3. From your previouse posts it looks like youre the one complaning :P

    And where am i complaining ?

    I just pointing out that cen should not Re-Distribute Bec.
    And if you ever bothered to take a look at the Bec License file you can see this is not allowed.
    I also pointed out that the download of the Bec files can still be donwloaded from the orginale source.

    But people dosent give a crap about ip/cp etc etc rights anymore.

  4. So you get butthurt because you had to block ibattle in you host file and that he desided to quit because he did not want go along with Bis new policy.

    He has after all given us a free service for years now be gratefull for that.
    Atleast he has moral and dosent just sit by and whine about stuff.
    He does something. if something usefull comes out of this is another case.
    Bis ignores most in the community anyway.

  5. @cen the download directory on ibattle is not down.

    From my history i got this.

    Program
    ibattle.org/Downloads/Bec.zip

    Plugins.
    ibattle.org/Downloads/Plugins/ConnectionLimiter.zip
    ibattle.org/Downloads/Plugins/Rss.zip
    ibattle.org/Downloads/Plugins/ScriptBan.zip
    ibattle.org/Downloads/Plugins/StaffNames.zip
    ibattle.org/Downloads/Plugins/WatchDog.zip
    ibattle.org/Downloads/Plugins/Ts3.zip
    ibattle.org/Downloads/Plugins/Plugin-dev-example.zip
     

    You should not be distributing Bec, Just because the maker of Bec desiced to quit, it gives you no right to Re-Distribute Bec.
    More so edit the content of the package such as the license file removed..
    No wounder the maker desided to quit with the mentality people got these days.
     

  6. Not entierly true.. i got im my config file.

    BePath = C:\Program Files (x86)\Steam\SteamApps\common\Arma 3\servercfg\BattlEye
    

    And it works just fine.

    You can try to use double slashes.

    BePath = C:\\Path To\\My Directory\\Where I Got\\Battleye
    


     

  7. take a look at two last posts.



    Also if your not doing so already. you should start up Bec as admin or with admin permission.
    If you start up your server without admin rights it can cause some issues since Battleye wants to be run with admin permissions.
    so run Bec as admins so it has admin rights when starting up your bat file.

  8. That scheduler example will not help him if hes using a newer Bec version.
    The format of the scheduler.xml was changed in 1.58 or 1.59 i think.

    @ Antichrist. When you start up Bec. it should tell you if you have errors in your scheduler.
    if you do not have errors it will tell you how many jobs are set to be scheduled.

    you'll see this message once Bec has logged in.

  9. take a note that the current work dir of the restart script is where your bec is located.
    so if you want the current workdir for your bat script to be where its located. you need to set it in the bat script.
    from reading the scheduler faq file i saw this,


       4 - Keep in mind that the CWD (Current Work Directory) your bat|cmd script or program will have is the same as your Bec install.
           Let say the path you have your Bec installed is at (C:\Tools\Bec).
           This is and will be the CWD of your script even if its located in C:\Scripts\Myfile.bat or some other place.
           
           Depending on your script and what it does, you might need to set a new work-dir by editing your script with something like:
           ::--------------------
           set NewCWD="C:\Scripts\"
           cd /d %NewCWD%
           
           do stuff
           ::--------------------



    this might be confusing for some people, espesially if they edit the script and mix up rel paths with abs pats and dont know the current workdir.
    this might be a case where it would fail to run the restart script properly i belive.

  10. Question. How are you going to handle Bec updates in the future?
    I know the tool gets the newset Bec version when you run it.

    But lets say i already have configured my Bec with your tool.. then there is a new Version of Bec out.
    can there be some way to only download the Bec version without doing the hole setup again ?

    when i launch Bec it checks for a new version, it is possible that you can do the same ?
    or just have a update  Bec checkbox ?
     

  11. I tested your previouse version and had no problems with it.
    From my experiance when Bec will not connect its mostly caused by wrong Battleye path set in the config.

    Ofcource there could always be some other issue. i also always check if its something wrong with Bec or the battleye installation by using another Rcon tool to verify with. I know that if you can login with another Rcon tool,. "Ie, Epm Rcon or others".  there is 99% of the time wrong BePath set in Bec config.
     

  12.  

    Logan

    Installation went fine, except when I click the start it runs my server fine. But once it launches the BE window it says Waiting for Server Startup.

    To the developer.

    this can be a case of the name of the server has been renamed. IE. from Arma2oaserver.exe to somethign else.

    when this happens Bec will fail to startup unless you specify this in the config file or use --dsc.

    You should adapt the tool so it check the file info on the exe files in the dir, to ensure that it has set the ServerExeName in the config if this happens.

    http://stackoverflow.com/questions/11350008/how-to-get-exe-file-version-number-from-file-path

     

  13. If your Server exefile has been renamed from arma2oaserver.exe to something else. you need to specify this in the Bec config file in the Misc section.
    ServerExeName = somename.exe
    if that dosent work. you can try starting up Bec with the --dsc option. like Bec.exe -f myconfig.cfg --dsc

×
×
  • Create New...