justchil
-
Content Count
7 -
Joined
-
Last visited
-
Medals
Posts posted by justchil
-
-
Cheers it works :D I have unable to get info from the arma process (don't use the reporter account but my give it a try) but I think I need to look back a few pages/posts for solution.
Good work!
-
I know mine is on 3333. My other server is all defaults so 2302.
If I start up server then BEC it's Waiting for server.
If I startup BEC then server it's Please Wait.
-
Sweet! Giving it a try now.
I'm super excited about the plug-in's :)
When I used #shutdown I didn't have anything in place that would kill arma2oa so that my monitor script (with start /wait) would trigger). It seemed like things ran a bit smoother when I used #shutdown and it worked properly... kind of like pulling a cord on a computer as opposed to a proper shutdown. I'm sure I can find something to work just right... this update should help my quest :D
Thanks!
---------- Post added at 15:13 ---------- Previous post was at 13:38 ----------
Same issue for me. I made my config as simple as possible... i started with all the new fresh files...
[bec]
Ip = 127.0.0.1 (I tried localhost,internet ip for fun)
Port = 3333
BePath = D:\DayZ\Arma2OA\dayz_1.chernarus\BattlEye (i had ..\BattlEye\) previously... neither help
Admins = Admins.xml
Commands = Commands.xml
LogDir = Server1
Server will not connect. This is a pretty simple server setup too... my server exe is default name... I really don't know what else to try to make it work. Reverted back for now.
-
Changelog says Removed: --dsc will no longer work?
Is it connecting to your server at least? I can't even get this far. I've tried it on 3 servers from full customized to fresh install lol...
-
Waiting on server.... server starts... Please wait... that's it. Never connects for me. Started over with default configs and same happens. Will keep trying I guess but this test machine is very very basic/simple setup.
-
Hello folks.
I've been using BEC for a couple months now and everything has been running pretty well. Recently I adapted my restart script / schedule.xml to utilize #shutdown instead of doing a kill /IM and or kill /F.
I've noticed several times #shutdown has failed to end the process of arma2oaserver.exe which left my server borked for hours while I was away... so I'm back to using kill.
What I'd like to do is to figure out how to call #shutdown from my .bat so that I can do something like this.
BEC runs restart.bat ever 3 hours...
somehow run #shutdown from my .bat << no clue on how to do this
if proc still exists run kill /IM arma2oaserver.exe << currently doing this
if proc still exists run kill /F arma2oaserver.exe << currently doing this
In short it seemed I had less small issues when using #shutdown... however if I can't depend on it working I can't use it... If this is possible and maybe someone could help me figure it out... I'd pretty much have a foolproof way of making sure the sever is shut down properly...and if not it will at least be shut down lol.
B.E.C. "Battleye Extended Controls" - Admin Tool
in ARMA 2 & OA - Servers & Administration
Posted
This is a bit OT from the update (working well for me ATM). I did see a few times the lobby kick said 15 seconds twice but no big deal there.
Could any explain a little further exactly what the #shutdown command does. It seems to work better for me than a task kill for some reason.
I've figured out how to do a #shutdown then and "if process exists" task kill it and continue my startup script. Hoping to gain a little bit of knowledge as to how it works and why it seems to work better for me :) Thanks!