Mojo (DayZ)

No, Omar means the opposite. Another player was reporting similar problems, I'll just repaste my explanation to him: Simply put, ArmA 2 is hilariously poorly optimized. First, despite possessing the LargeAddressAware flag on the executable, the OA executable (and the ArmA2 executable) cannot, under any circumstances, use any more than 2 gigs of memory. Whether you have four gigs or eight or 16 won't make a difference. It's two gigs max, period. Second, at some point Bohemia Interactive decided that more people had bigger hard drive than lots of RAM, so instead of making the game RAM-intensive, they made it Hard Drive intensive. Watch your hard drive light next time to play. See it blinking like mad? You have no idea how much arma2oa loads and unloads from the HD. Third, that also tends to mean there's a big chunk of page file/virtual memory it likes to use. Which increases hard drive usage even more. Fun! Over all, the major performance limiter in the Real Virtuality engine is hard drive thrashing. Lastly, Operation Arrowhead is a pure 32-bit executable. That means that regardless of anything else, Windows XP 32-bit remains the best operating system to run it under. XP 64 is a little worse, and by the time you get to Vista/7, well, it sorta freaks out. So, what can you do to improve your performance? Your first option is to install a Solid State Drive. Putting my Arma2/OA installs on an SSD gave me a performance boost of anywhere from 10 (the horribly unoptimized frame-eater Elektrozavodsk) to 30 FPS. On average I see FPSs of about 30-60. Your second option is to install such a stupid amount of RAM that the executable runs off a RAM disk. This is even faster than an SSD. Between ArmA2 and OA, you're looking at about 16.5 gigs just for the space taken up. If you're selecting and very tweaky and control freak about what you put on your ramdisk, you can ramp that back quite a bit. As for operating it in a 32-bit mode, compatibility options will never be quite as good as a native 32-bit OS. However, if you put -winxp in the launch parameters of your DayZ shortcut, it does actually help quite a bit. Lastly, I'd recommend turning Anti-Aliasing off. For some reason it seems to cause OA to freak out. If you really hate jaggies and really like anti-aliasing, I'd recommend using FXAA on the beta clients of the Operation Arrowhead executable, which even at its highest settings gives me much (much, much) better frame rates than FSAA on lowest settings. In other words, do not upgrade your graphics card expecting leaps and bounds in improvement. It may help draw the geometry marginally faster, but remember that if Arma is delivering its streamed content slowly, no matter how fast that GPU can go, it is limited by how fast it gets the information. You can be the fastest portrait artist in the world, but if nobody ever visits your studio, you're going to draw exactly zero portraits. Things that will significantly improve your FPS: 1. Faster platter hard drives. 2. Solid state drives. 3. Striping platter drives. 4. Striping SSDs. 5. Running OA on a Ramdisk.

Simply put' date=' ArmA 2 is hilariously poorly optimized. First, despite possessing the LargeAddressAware flag on the executable, the OA executable (and the ArmA2 executable) cannot, under any circumstances, use any more than 2 gigs of memory. Whether you have four gigs or eight or 16 won't make a difference. It's two gigs max, period. Second, at some point Bohemia Interactive decided that more people had bigger hard drive than lots of RAM, so instead of making the game RAM-intensive, they made it Hard Drive intensive. Watch your hard drive light next time to play. See it blinking like mad? You have no idea how much arma2oa loads and unloads from the HD. Third, that also tends to mean there's a big chunk of page file/virtual memory it likes to use. Which increases hard drive usage even more. Fun! Over all, the major performance limiter in the Real Virtuality engine is hard drive thrashing. Lastly, Operation Arrowhead is a pure 32-bit executable. That means that regardless of anything else, Windows XP 32-bit remains [i']the best operating system to run it under. XP 64 is a little worse, and by the time you get to Vista/7, well, it sorta freaks out. So, what can you do to improve your performance? Your first option is to install a Solid State Drive. Putting my Arma2/OA installs on an SSD gave me a performance boost of anywhere from 10 (the horribly unoptimized frame-eater Elektrozavodsk) to 30 FPS. On average I see FPSs of about 30-60. Your second option is to install such a stupid amount of RAM that the executable runs off a RAM disk. This is even faster than an SSD. Between ArmA2 and OA, you're looking at about 16.5 gigs just for the space taken up. If you're selecting and very tweaky and control freak about what you put on your ramdisk, you can ramp that back quite a bit. As for operating it in a 32-bit mode, compatibility options will never be quite as good as a native 32-bit OS. However, if you put -winxp in the launch parameters of your DayZ shortcut, it does actually help quite a bit. Lastly, I'd recommend turning Anti-Aliasing off. For some reason it seems to cause OA to freak out. If you really hate jaggies and really like anti-aliasing, I'd recommend using FXAA on the beta clients of the Operation Arrowhead executable, which even at its highest settings gives me much (much, much) better frame rates than FSAA on lowest settings.

1. Increasing player cap is bad. It seriously cripples server frames. Don't do it. The community seems happy with an average cap of 50 players. 2. The problem you're likely having is creating a vanilla clone. As in' date=' you're changing the port, but not the actual config files. The reason you can't see it on the server list is probably because you're not fully creating another instance. If you need help with [b']ANY of this, please find me on TeamSpeak at ts3.MonolithServers.com. I'll take you through it step-by-step. Step-by-step: 1. GET A NEW MISSION FILE. This would be dayz_XX.Chernarus.pbo in your MPMissions folder in OA install directory. Very important. One instance will need one of these files, two instances will need two different mission files, three instances will need three, etc. 2. Look at your launch parameters for your DayZ server, which you will either find in a) your .bat server shortcut or b) Your services manager (ie: FireDaemon) start-up parameters. One of those parameters should read -config=[whatever].cfg 3. Go to where that .cfg file is located (it should be in your arma2oaroot/cfgdayz/ folder), find [whatever].cfg and make a copy of it. Now edit that copy. In particular, you are looking for this: hostname = "DayZ Zombie RPG - [Whatever you want the second server to be called] (v1.5.7) dayzmod.com - hosted by [whatever you want the host name to be]"; // The name of the server that shall be displayed in the public server list Change that to make sure it's a different name from your original server. Now find this: // MISSIONS CYCLE (see below) class Missions { class DayZ { template = dayz_XX.Chernarus; difficulty = "veteran"; }; }; And change the [XX] to the number of the mission file you just got. 4. Save the change you just made TO A DIFFERENT FILE NAME THAN THE ORIGINAL SERVER CONFIG. 5. Now either a) make a copy of your server .bat file or b) make a clone of your DayZ server service. 6. In the .bat copy/service clone, again look at your parameters (the same place you found the -config=[whatever].cfg) Now change that -config= to point at the second config you just saved. 7. Optional but highly recommended: Use the -port flag on both your instances to designate a port. This is so that if you use the RCon GUI (and you really should), you can save the connections to your server instances easily, without having to worry about typing in the port. 8. Also optional but highly recommended: Use -exThreads=1 and not -exThreads=Anything Else. The reason for this is that the server absolutely does not need to thread textures or geometry. However, it can use the File Operations on an additional thread, which may cause a performance increase. Not much, but it tends to be there. Loading with exThreads=[anything other than 1] can cause the server to pointlessly attempt to create additional threads that will only a) act inefficiently b) do nothing and c) create useless overhead usage. Don't bother. 9. Also optional, also highly recommended: Stop using the batch files. Use FireDaemon with defined parameters. It allows you to set Core Affinity without having to dictate that affinity at launch or pointlessly mess with elevated cmd start /c. Core Affinity can be set on a defined service and FireDaemon will automatically handle it for you. It has a lengthy trial period and a cheap licensing fee that's well worth it.

I posted a reply the other day saying that the forums were the closest thing to a Governmental Gazette or Paper of Record that we administrators had, and that got me thinking that I should create a thread where every administrator can post the rules for the servers they run in a single place, as a quick reference for players, and in an effort to do our due diligence. We obviously cannot personally call, email, and send out pamphlets to every person in the world in the off chance they might pick up DayZ. We must make due with what we can. I've posted the rules to my servers before, but this might allow a concise publication of server rules and regulations players can reference, and I've also had to make up a surprising amount of new regulations given that the ones I had in place before seem to be ones players generally follow. So, without further ado: ---------- For the Chicago 1 Series of servers, these currently being Chicago 1 Original and Chicago 1 Blues: In-game server rules (in no particular order): THE DO NOTS: 1. Do not spam microphone voice chat. People will bring this to your attention, and when they do, listen to them. Using in-game voice is acceptable only on the direct channel, which is why voice will never be disabled completely. I recommend that players go into options and unbind ALL VOIP/VON keybinds, then find the keybind that is specifically for Voice on Direct Channel. This way if you ever accidentally broadcast from your mic, it will only be to those around you. It will also switch you from whatever channel you're on (typically side) to the direct, and then automatically switch you back to your previously used channel when you release the mic key. Very handy. 2. Do not spam connections. Connection spamming is not repeatedly pressing enter or spacebar to get into the server. Connection spamming is not waiting 10 minutes or more and attempting to reconnect to this or another server to see if it's a persistent, global problem. Connection spamming is not reconnecting after you spawn in incorrectly, like in the debug forest or ocean. All of those are acceptable and understandable. Connection spamming refers only to repeatedly slamming one or more servers with multiple attempts to connect in a very short period of time. This puts strain on the servers, ranging from desync to outright crashing as the server freaks out. An extreme amount of players doing it can also cause the support apps to begin spitting out errors no matter how many times they're fail-safed and recovered. 3. Do not attempt to depopulate the server or instill "panic." Do not announce that on another server they're handing out free anti-materiel rifles, NVGs, and GPSs. Do not announce server restarts. Beyond anything else, doing this will most likely result in a permanent, irrevocable, unappealable ban. 4. Do not spread misinformation to other players. Players ask what server they're on because finding servers can often prove to be difficult, making it difficult to know which server they've joined. They either want to a) attempt to rejoin the same server or b) inform their friends they've found a working server and get a group organized. Misinforming them deliberately deprives them of their play experience. You aren't cute and clever when you tell them Chicago 1 Blues is eg. Dallas 1 or US 4. You are being a pain in the ass, and it's nothing against Dallas 1 or US 4 -- you're keeping these players from finding the assets that they've invested time in, such as tents and vehicles, or from playing with their friends. 5. Do not talk about what Internet cliques you belong to, or which stupid Internet clique is the best and how some other Internet clique is the worst. Do not talk about 4chan or Something Awful or reddit or Google+ or MySpace or GeoCities. First of all, "LOLOL U MUST BE FROM [stupid internet website]" isn't much of an insult. If they are active in that community, they aren't going to take it as an insult (otherwise they wouldn't be part of that community) and if they aren't a part of that community, they're just going to think you're stupid. So, knowing that, what have you accomplished? You've turned my chat into a stupid slapfight between two idiots flaming each other over shit only the person trying to sling "redditor" or "channer" as an insult would find insulting, and to the rest of us watching this stupid pissing match, you both sound equally idiotic. You also turn the entire chat box into a complete shitfest, and drown out legitimate game talk with your stupidity. The same goes for people raging about Call of Duty or whatever. Don't do it. You know what community you're all a part of? The DayZ community. Talk about that instead! 6. Do not attempt to override the rules of the administrator. If I tell somebody to stop spamming mic and you run in and go "NO YOU SHUT UP! YOU CAN JUST MUTE HIM!" I could count the amount of fucks I give on one hand and could still do so if I was an amputee. You have your solution to the problem, I have my solution to the problem, and I also have the server and the responsibility for administrating it. Guess which solution trumps the other? 7. No racism/sexism/other discrimination. People have been surprisingly good about following this. I've had to hand out about two warnings about it, and only one ban (to a guy who didn't understand the server was a "no racism server", which, you know, should really just be a general life guideline for you). 8. No pointlessly offensive behaviour. If your username is Idi Amin and you're requesting fire support under the codename Uganda Actual, this is kind of funny and I'll let it slide as long as you keep being entertaining and iconoclastic. If your username is Anders Breivik and you're otherwise just acting like you want attention through shock value, I will be glad to offend your ironically delicate sensibilities when you suddenly find yourself back at the lobby screen. Ask yourself the following question: "If I walked into a bar with a healthy cross-section of the average population wearing a t-shirt espousing the views or personages I'm espousing with my in-game behaviour, would I get punched in the face?" If you answered yes to that question, avoid engaging in the behaviour at all. Remember when your mother tried to explain the difference between a person laughing AT you and laughing WITH you? This is similar. If you make us laugh AT death and all the horrible things in the world, that is good. If you find yourself laughing WITH death and all the horrible things in the world, you are foul cunt and ought to be segregated from society. 9. Do not be a stupid Internet lawyer. "BUT MOJO, WHAT ABOUT FREE SPEECH?" you cry. Hang on. "Congress shall make no law..." Alright. Stop right there. My server is not Congress. The end. 10. No far-too-long flame wars. Tying in with the "your Internet clique pissing match turns everything stupid" rule is number ten. This is a game. Gloat and strut over your victories. That's fair. Blow off steam over your losses. That's also fair. Know when to stop. That's mandatory. I know peoples' tempers can get a little hot when you come out with the short end of the stick and the ones who ended up winning the Makarov showdown at the Cherno Corral can goad them on. If I intervene and tell you the argument is over, I am not telling you to continue the argument. I'm not telling you to continue the argument with me. I'm not telling you to continue the argument with other players who have asked you to stop your vaguely erotic verbal wrestling match. I am telling you that you have each said your piece and your argument is over. 11. ABSOLUTELY, UNDER NO CIRCUMSTANCES, EXPECT SPECIAL TREATMENT if you're from my gimmick clan, Monolith, or are a server donor. I don't care if you gave me money. This should be a disincentive to act like a complete idiot, not an arousal of your sense of entitlement. If you're misbehaving you'll be treated like everybody else. Not everybody has the fortune to have money to spend towards the servers they play on, nor does everybody have the extremely good fortune to have basked in my magnificent presence for several years. That does not mean you can deprive them of their play experience. You are all my little sunshines, no matter what you give or who you know. You will NOT get a reserved slot for knowing me. You will NOT get a reserved slot for donating. You will not be able to demand people be kicked or banned for petty offences. THE DOS: 1. Inform an administrator and other players if there's a problem with the server. If there's no loot spawning, or no zombies spawning, or hiveauth didn't properly initialize your tent or vehicles, let others know immediately. The more conscientiously people play, the better the server is run. While a single report is rarely enough to actually take action, it goes a long way to establishing a pattern of server behaviour that can be enough for an administrator to take the appropriate steps to correct it. If I happen not to be around at the time, another trusted admin you don't recognize might be. And barring that, other players become aware of it and become able to pass on the message when we do become available. 2. Inform an administrator and other players if there's a problem player on the server. Due to game glitches, odd behaviour, or me simply playing the game and not always monitoring chat, I can always see abusers of the rules. For example, I'll often see a lot of people telling a person to stop using their mic even though for me it appears they're not broadcasting at all. Your admins are neither omnipresent or omnipotent, we rely on you to bring problem players to our attention immediately. Tell us if you suspect a player is playing illegitimately. Ask us if a weapon is a real drop if you suspect it's hacked in. Let us know if a person disconnected during a gunfight to avoid being killed. Inform us if they then immediately reconnected in a new position to kill you. Again, like DO #1, a single report is rarely enough to take action unless it's serious. If you spent an hour stalking a guy and he logged out, know a few things. Crashes happen. They happen at times that are inconvenient, either to you or to other players. Know that other players' lives do not revolve around you and your desire to kill them. You can't expect another player to say "Sorry grandma, I can't take you to church right now, some guys in a video game want to kill me and I have to let them, I didn't even know they were there but they might have been stalking me for an hour or so." On the other hand, that excuse doesn't fly if they reconnect immediately in a new position to kill you. It's hard to argue that you had to stop playing if you keep playing. We, the admins, need to establish a pattern of bad behaviour. That pattern is either established very quickly (based on something like them spawning in jets or disconnect/repositioning) or not at all, whether or not what appeared to be bad behaviour inconvenienced you. Rest assured that when you make a report to me, I keep a notepad and pen in front of me at all times to write down what you say, who you're accusing of it, etc. I then go through the server logs, the RCon, I make notes of their GUID, when they disconnected, etc. When you inform me of illegitimate player behaviour, it is always taken seriously, even if I can't take action immediately. 3. Do be helpful to other players. This is a matter of saving the most important rule for last. Helpful does not mean 'helping'. It doesn't mean doing zero-PvP or roleplaying the Red Cross, giving blood transfusions to every player in the Cherno church. It means playing the game legitimately, as you wish to play it, but taking the time and effort to engage your fellow players' questions and concerns. If people ask how you force-save, and you know the answer, tell them. If they're trying to figure out keybindings or controls, and you know the answer, tell them. If you're ambiguous on what I mean by the difference between helping and being helpful, consider it like this: Tell a person that according to convention, white moves first. Then try to get them in checkmate. Explain that baseball has nine innings. Then try to hit a grandslam. Victories are sweeter when you win them on a level playing field, against competent opponents. Help new players become competent opponents -- or competent teammates. TeamSpeak server rules (in no particular order): THE DO NOTS: 1. Do not come into a channel just to "hang out" with me. A lot of players do this, and I can't tell you how annoying it is to be trying to actually play the game on the rare occassion I'll sit down with it, and have somebody that just wanders into the channel to make conversation. We're coordinating movements, strategizing, talking about where we keep our tents and vehicles; all things I do not want you to know. I get why you want to be friends with the admin and be on his good side. Doing that is the fastest way to get on my bad side. 2. Seguing from 1, do not metagame. Do not forcefully sit in a publicly accessible channel listening in on another group. The channels are available for group-organization on a first-come, first-serve basis. If you need an additional group channel created, contact an admin and one will be created for you. If you cannot contact an admin at the time, feel free to use one of the other servers' empty group channels until such a time as a new channel can be created for your group. For example, if you're in Chicago 1 Original and all the Group Subchannels for that server are filled, but there are empty group channels for Chicago 1 Blues, use one of the Blues channels. Under no circumstances will an excuse be tolerated for spying. You will gain at best a single minor victory at the cost of access to the TeamSpeak and most likely the game server. Note that this doesn't apply to doing something like using the group channels for their purpose, but for nefarious ends. Feel free to ingratiated yourself to a group of players, integrate into them, and then betray them. Do not simply follow them through TeamSpeak until they feel the need to quit TS to get away from you listening in on them. A group "owns" a channel they go into until they abandon it. A group is not a single person. If you have any trouble with understanding this and wish to argue it, see "Do Not Be An Internet Lawyer" above. THE DOS: 1. Do come into any channel I'm in or poke me or private message me to inform me of a problem immediately, even at the cost of interrupting my gameplay. The server, and consequently all players, take priority over my play experience. 2. Do come into any channel I'm or poke me or private message me if you need help running ArmA 2, getting DayZ up and running, or are experiencing other technical issues related to gameplay. I'm more than happy to sit with a player and adjust settings, set up launchers, or just generally troubleshoot any problem you have, from loading errors to crashes to desktop. I want all of my players to have a positive play experience both on my server and with DayZ in general. I've been dealing with Bohemia's quirks since OFP 11 years ago, and continue to do so now. After not playing in over a year, I've reoriented myself to things I thought would remain forgotten, and will happilly let you pick my brain. I don't care if I'm in the middle of something. I don't care what you need help with. I don't care if I need to give up my slot to get you in game to see if it works. I don't care if you're a donor or don't have a dime to spare. I will try anything within my power to get you playing. This is part of what the TeamSpeak is there for. 3. Do help other players on TeamSpeak if they are asking for help or advice. Beyond anything else, I appreciate the players who not only take the time to enjoy the game, but to help others enjoy it as well. Do you know the answer to their question? Please, give it to them. Take two minutes to help them out, and then (politely) ask them to excuse themselves from the channel if they're in your group channel.

The thread is meant to be a concise collection of rules (ie: one thread for all admins to post their rules rather than being spread out willy-nilly and inefficiently), not a collection of concise rules. And that distinction is why you sometimes need to go the extra step of explaining things with examples ;)

No. This, 100%, does NOT constitute connection spamming. Let's go over things that constitute connection spamming really quick: Things that are NOT connection spamming: 1. You have spawned incorrectly, in the debug forest or the ocean. Reconnecting to fix this, either to the server you're on or another server, is NOT connection spamming. 2. You have waited an inordinate amount of time on a single server. You attempt to disconnect and reconnect to the server once, or you disconnect to reconnect to another server to see if that alleviates the problem. This is NOT connection spamming. 3. Repeatedly hitting enter to try to get into a server. This is NOT connection spamming. Both of those qualify as TROUBLESHOOTING. You have encountered a problem and taken steps to see if it's a) reproducible or b) fixable. There is ABSOLUTELY NO FAULT WITH THIS, AT ALL, WHATSOEVER. Things that DO constitute connection spamming: 1. You have connected to one server, become impatient after a few minutes, and make repeated disconnects and reconnects to the server you are on. 2. You have connected to multiple servers, become impatient, and hop down servers constantly unable to spawn in. These both fall under violations of the common-sense definition of insanity: doing the same thing over and over again and expecting different results. In the first case, if it didn't work the last 20 or 30 times on the same server, what makes you think it'll work the 21st or 31st? If you do this, you're connection spamming. In the second case, if it didn't work the last 20 or 30 servers you tried, what makes you think it'll work the 21st or 31st? If you do this, you're connection spamming. The keyword here is spam.

Be warned, however, that this may cause server stability issues (not due to your server itself, but the limitations of arma2oa). If you pull it off, you will want to judiciously monitor your server FPS. FPS falloff can be a pretty steep curve over time.

No. In fact' date=' I know that the type of user who will repeatedly spam connections to a server is precisely the type of person who will not actively seek out solutions to their problem. All the same, as a responsible administrator, I feel it's necessary to do my due diligence and use the closest thing we have to a gazette or paper of record to clearly illustrate the problem and consequences for compounding that problem rather than slough my duty off on a Message of the Day. It's also caused bandwidth issues in ArmA 1 servers. I've been intimately familiar with the Real Virtuality engine's usage of bandwidth, which isn't the only problem. There's it's notoriously leaky memory, its absolute lack of garbage collection, the fact that the previous RC server executable is not as stable as the recent beta builds, and a whole slew of concerns that are, at least local to the hosting server, compounded by repeated disconnects and reconnects. Bandwidth itself isn't a problem -- that barely scratches what we have available. The same goes for memory, processor, and disk usage. What is a problem is that what we have available is irrelevant in terms of what the particular server instance itself considers sanitary. In other words, you can have a Ferrari, but if your grandma's behind the wheel, that thing won't break 20. And if you force her foot on the pedal, all you're going to get is a horrendous crash and a few dead pedestrians. Just to make that analogy perfectly clear, arma2oaserver.exe is grandma, our machine is the Ferrari, the impatient, freaking-out few are the ones jamming her foot on the gas, and the dead pedestrians are my other players. I won't permit 1/10th of my players to ruin the experience for the other 9/10ths of the players on my server, regardless of if its chat harassment, hacking/exploiting, or behaviour damaging to either the server or the server support applications. Period.

So, thanks for all the donations! All our regulars tell us we're the best, because they're giant suck-ups (not that there's anything wrong with that). Thanks to the donations we received, we were able to roll off another Chicago server. Confusingly, this server is also called Chicago 1. But why? Well, we lost the contiguous namespace. And that wasn't really acceptable to us. Why be Chicago 10 when we're the original Chicago? Pfft. The easiest thing to do was iteration namespace. Protect our brand. Protect our reputation. Let everybody know this new server is the genuine Chicago experience. L@@K!: Chicago 1 -- the original server -- is now called Chicago 1 Original. That makes it easy to tell! The second server is Chicago 1 Blues, in recognition of the fact that Chicago basically gave birth to rock'n'roll by turning Delta blues electric. And I like rock and roll. And you guys are, you know, pretty rock and roll for getting that second server up so fast. There were load balancing issues, and they've been fixed! Wow! The two servers will never, ever touch each other on the cores. Thanks to everybody who weathered the nasty storm of horrible Windows 2008 being horrible. I love you all, and admire your bravery.

There are two files you can look at on the server. You can find either file simply by searching for them. One, ban.txt, is the in-game #exec ban list, which bans by PID (shorter and strictly decimal, ie: comprised only of digits 0 through 9). ban.txt will be located in your oaserver.exe root directory. Two, bans.txt (note the s), is the Battleye/RCon ban list, which bans by GUID, (longer and hexadecimal, ie: comprised of digits 0 through 9 as well as letters a through f). bans.txt will be located in your Battleye working directory which, for me, is the %OASERVER ROOT%/cfgdayz/battleye/ Depending on the method used to ban him, you will need to look in either of these files. If you used the in-game chatbox command line, his ban will appear in ban.txt. If you used the RCon to ban him (whether the RCon GUI or the command line RCon) his ban will appear in bans.txt. He can easily give you his PID to check against ban.txt, but the GUID for bans.txt may be harder to check against. Assuming he was the last person you banned with Battleye RCon, he will be the last listed entry in bans.txt, and can be removed simply by deleting that line. edit: If, for any reason, you are unsure about which line to remove for a GUID ban (eg: you don't want to lift a legitimate ban), I'll happily make arrangements for him to connect to my server, verify his GUID, and then private message you the GUID you need to find and remove to lift the ban. edit 2: I see you already know his GUID. I'll let my previous overly-helpful-but-totally inattentive idiocy stand.

Lies' date=' damn lies and statistics from last week! We actually converted to veteran a couple of days ago after listening carefully to player feedback. Then I said "to hell with it," stripped [i']everything, including 3rd person, and explained to everybody how to turn off Headbob (it's in the gameplay options) and widen your FOV by double-tapping numpad minus. It's great to see the Chicago 1 Series get this much love, and I'd like to remind you all that with 1 admin and 99 other players between Chicago 1 Original and Chicago 1 Blues, you guys are 99% of the play experience for everybody else.

Admin confirm on that. I RDP'd in and force-crashed the server as fast as I could, unfortunately when it came back up we discovered it wasn't nearly fast enough.

Thank you' date=' thank you. I always look to entertain, whether it be by spectacle, joke, or sight gag. Hooray me! Mojo: Bad at administrating.

Long answer: It's true. The server is capped at 30 people. This is confusing for many of our players' date=' because they see x/50 in the server browser, and we [i']appear to have 50 people on at all times. Something I haven't told you guys is that Chicago 1 is haunted. There's 30 players and 20 ghosts on at any time. We had called a Catholic Priest and asked him to perform an exorcism on the VPS, but it turns out holy water is not dielectric (which also blows my plan of immersion-cooling my system with it and getting better pings because it's closer to God) and will, in fact, get the manager of the datacenter to personally call you up and tell you he's going to "kill you" and is "outside your house, right now" with a "gun" in his "car". Pfft, whatever that technobabble means, nerd. I just need you to TCP/IP into my USRobotics modem and make sure my JPEGs are being uploaded to Windows 3.1. Short answer: No.

FireDaemon + arma2oaserver.exe run as a service set to restart on a set interval would do the trick. I use FireDaemon to regularly restart hive and hiveauth, and automatically recover oaserver if it crashes. I dislike the idea of restarting automatically, because there's been many a time when arma2oaserver.exe has remained stable well beyond its sanity limit (~8hrs instance up-time, on average), and I watch my server pretty judiciously with VNC and RCon. If that's not an option, then FireDaemon's automatic restart system is probably worth it.