Magotchi

Yeah. A guy just came into Teamspeak to let me know about it. I was about to go to sleep, but I guess it's time to go into investigation mode. A couple days ago somebody destroyed all the buildings in the Balota airfield (I think with airstrikes). The hacking in this game is nuts. Regarding it "happening to[o] often to not be admins", you're welcome to believe as you please I guess, but that's absolutely false. I quit about a half hour ago for the night, because all my friends that normally play are on Dota 2 right now. Anyway, I'm looking through the scripts log at the moment. Hopefully I'll find something useful. The scripters are often able to bypass BattlEye, which makes looking for things a lot more difficult. If I don't find anything tonight, I'll be on it tomorrow for sure. Update: Here's the full, unredacted scripts log, as of roughly 2:40am MDT (last server reboot and rotation of log was at 11:03 pm MDT): http://callear.org/m...-2-40AM-MDT.zip Feel free to peruse through it and let me know if you find anything.

The problem with that is that the first person to join the server is the person that gets to accept the mission. Either way, I also haven't had any issues with missing tents or vehicles since I started using the #shutdown command. In fact, the problems we do sometimes have (which I think are common) are that the tents sometimes reappear fully stocked, even after flattening, and the vehicles sometimes reappear in full condition, even after being destroyed.

I'm glad I could help.

I hope this "movement" thins out the herd. The community doesn't need this kind of nonsense, rulebreaking, and incivility.

It's a little confusing at first, but you just need to follow the instructions at the BattlEye Extended Controls website. To get you started, though, here's the contents of my Config.cfg for it: [Bec] Ip = 74.91.120.179 Port = 2302 BePath = ..\US303\BattlEye LogDir = US303 Admins = Admins.xml Commands = Commands.xml [Misc] KickLobbyIdlers = 300 Scheduler = Scheduler.xml Timeout = 60 My Scheduler.xml: <?xml version="1.0"?> <Scheduler> <job id="0"> <time>01:55</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 This server will restart in 5 minutes, as scheduled.</cmd> <cmdtype>0</cmdtype> </job> <job id="1"> <time>02:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>#shutdown</cmd> <cmdtype>0</cmdtype> </job> <job id="2"> <time>07:55</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 This server will restart in 5 minutes, as scheduled.</cmd> <cmdtype>0</cmdtype> </job> <job id="3"> <time>08:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>#shutdown</cmd> <cmdtype>0</cmdtype> </job> <job id="4"> <time>13:55</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 This server will restart in 5 minutes, as scheduled.</cmd> <cmdtype>0</cmdtype> </job> <job id="5"> <time>14:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>#shutdown</cmd> <cmdtype>0</cmdtype> </job> <job id="6"> <time>19:55</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 This server will restart in 5 minutes, as scheduled.</cmd> <cmdtype>0</cmdtype> </job> <job id="7"> <time>20:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>#shutdown</cmd> <cmdtype>0</cmdtype> </job> </Scheduler> I have the Bec directory inside the game's main directory. As Bec exits when the game shuts down, my monitoring script (a tweaked version of R4z0r49's) also kills it (to make sure it's closed) and starts it again at the same time it starts the server.

Yet another thread on basically the same topic... They didn't lock enough others for your tastes?

Are you killing the server's process, or are you issuing the #shutdown or #restart commands via RCon? I used to kill the process, and it seemed like I had more issues, but now I have BattlEye Extended Controls issue the #shutdown command on a schedule, and then my monitoring script notices the server is shut down, so it restarts it.

Many servers also have automatic kicking of lobby idlers. It may not have been an actual person kicking you.

Don't let the door hit you guys on the way out. Good riddance.

It's not a matter of blindly following Ander or the dev. team. It's a matter of keeping your agreement you made to do so when you signed up for a server. To not do so makes you a liar.

If the DayZ team made an agreement with some hosting providers that they only host rule-following servers, and a server operator in-turn agreed to their host's policy on the matter, I see no problem with DayZ notifying the host, and the host cancelling the server operator's service. That's been the case as I've so far seen it in the forums.

While I concede that the tense of the word "set" can be ambiguous, the way I used it every time above, I meant it in the indefinite (basically present) sense. I also believe that's the usage they intended in the welcome email (among other places):

Nobody is forcing anyone to operate DayZ servers, but to use the official DayZ hive and be listed on the official server list, server operators had to agree to follow the rules the DayZ team set.

AllDayZSimon: It doesn't seem like you understand the English/Latin idiom, "Don't look a gift horse in the mouth." What I mean is that I don't expect anything out of the DayZ team, as I've given them nothing in return for such an expectation. DayZ is 100% free, and nothing obligates me to operate a DayZ server. I did however agree to follow the rules they make if I'm to use their hive and listing services, as did all server operators.

YouTube evidence of the developer's not creating a solution to prevent people from DC-ing to avoid death? What are you talking about? (me playing Adron): I would insult you by [insults you in process of describing insult], but I'm better than that. Great logic.

I don't look gift horses in the mouth.

It doesn't. Server operators agreed to follow the rules the DayZ team set. They didn't agree to only follow the rules that existed at the time.

They are specifically recommending beta build 95054 (and by extension, not RC2 build 95054).

The email does say "recommended", so I doubt it's mandatory. Also, DayZ hasn't updated today, so it would be very difficult to pull off anyway.

I believe admins violating their agreement with the DayZ team, and making a worse overall experience for DayZ as a whole, is worse than players DC-ing to avoid death. However, DC-ing to avoid death is indeed a major problem, it needs to be resolved, the devs. have said they're working on it, and hopefully they'll have a solution soon.

Hello SeaFoam. There are only 2 people with admin access to US 303. I am one of them. I've haven't joined the server all day today (except via RCon), and I believe the other guy, Infinity, has been playing Dota 2 all day. Not only does being an admin not give me the ability to do the things you describe, but I wasn't even around to attempt them, and even if I had the ability, it's not my bag. I'm sorry you feel we've wronged you somehow, but please trust me that we haven't.

I don't understand your question. What are you implying I think is "more so" than what you're talking about, and in what regard?

As a server operator wanting to keep my server as up-to-date as possible, should I be running the latest Arma 2 beta build (beta build 95054 currently) or the latest release candidate build (RC2 build 95054 currently)? If I do run the RC2 build of 95054, will people installing the beta build of 95054 via the Arma 2 beta patch page still be able to play on my server, or will they too need to install the RC2 build? The server is already running/requiring beta build 95054, and it seems to be fine, but I'm wondering if I'm missing out on anything by not running the RC2 build. Thanks in advance for shedding any light on this.

The staff answered my question with their latest update email: "...please ensure your servers are updated to Beta build 95054." It then went on to link to ARMA2_OA_Build_95054.zip , which is the beta build, not the RC build.

IMO, more power to them if they want to use a private hive. That's a lot better than them negatively affecting the one I use.