Search the Community

Hello , I'm sorry to hear about your trouble. I do want to remind you that the rules are NOT currently being enforced. As i've mentioned several times , the project will launch when more server options are released. For now you must treat the server as a casual one , until we launch the project , then stuff like KoS , ghosting , etc will be punished severely. Regards

I was looking for a post on this topic. Ghosting is my pet peeve. Three of us successfully defended a building in an AB inspite of the opposition logging in and out to see where we were in the unrendered (for them) building. They also continually clipped into outside walls and fired randomly hoping to hit us. They then ghosted into the upper floor room. We heard them in there getting ready to rush us and decided rather than playing along to take away thier pleasure by exiting. They exhibited pretty low class gameplay. I have two names that I look for now and I won't play on any server they are on. I know they can change names and perhaps part of the solution is to make names permanent. After awhile the community will identify the cheats and hackers and be able to ostracise them ourselves. Report suspisious relogging to server admins and perhaps they can confirm and take punitive action. Death messages might help further this process. Now I know I will get replies from trolls and those who exist only to compensate for low self esteem by ranting and rude comment. I would really like to hear some ideas on how we, the community can deal with exploiters, cheats and hackers.

I agree, as a player that it is top priority. But for dev of an alpha game this is left to be a finishing touch. As you see for Rocket the priority is to add a revolver and work on server interface, hacker and combat loging/ghosting will probably wait till late 2014.

It seems there is a large percentage of COD r-tards that play this game as I've seen about 40 or 50 different players so far use combat logging and ghosting (logging in to a different server to move - then rejoin the old server) like a bunch of pussies. Please make fixing this a priority because it's has a huge negative impact on the game.

Ghosts are the lowest form of life in DayZ with the possible exception of combat loggers. Its always been a problem with the single hive architecture though. When you can just hop through a dimensional portal and end up in the same place, there is very little point to actually utilizing the entiriety of the map to search for gear all you need to do is get to one place that has a good cross section of everything you'll need, like...Zelenogorosk in the SA, which has military, residential and industrial spawns all within about 100m of each other and you're all set. Hop through low pop servers to gear up and...well overall you're pretty much done with the game at least in the current state of the SA. Now that kinda sucks but the real problem with ghosting isn't the people cheaping it up by grubbing up all the good gear from server to server, eventually the real problem with ghosting means there is no actual place of semi-security that you can fall back to or use as a base that cannot be infiltrated and invaded by someone who will simply see that you're stacked up in say....the big industrial at Berezino, with a few friends covering the outside approach..and all they have to do is get close enough to see that, get an idea of where people are keeping watch, then they just hop to another server, enter the big industrial where there are no defenders whatsoever, hide under the staircase or something or in a good position on one of the floors where the defenders were last know to be, log in to the original server and immediately have the tactical advantage of surprise because no one was immediately expecting a threat from inside the building. Its the cheapest and easiest way to win a fight in a central hive experience when it comes to a building you know is defended. The only fix I've ever really considered for this problem is to timestamp a player record on connection and disconnection, and disallow fast reconnections to multiple servers. This removes a bit of freedom from the player but its the only way to keep people from just avoiding having to play the game as intended by simply abusing the "Long Earth" nature of Chernarus in a main hive multi-server environment. Effectively the only way to stop it is simply to disallow it by limiting server switching based by login/logout timestamping, and serverID checks. If someone is exceeding a certain amount of server swaps in a proscribed time frame. Then if a player is falling under the predefined login checks in regards to timestamp and serverID history on their record, a progressively longer login delay or logout timer should be applied to their character. In simple terms, if I log on to say, US 1, and spend less than 600 seconds on that server, log out, then I login to US 2 and again I spend less than 600 seconds on that server, these things should be recorded to the Hive (and they are, given the amount of data you are pulling from the hive already) and its a simple case to simply block server access right at the loading screen with a delay timer that displays right over the character that says you have to wait X amount of minutes to join another game. Since mostly everyone will only have one character, this cuts down heavily on people taking the easy and cheesy method of gearing up and/or outflanking known enemy defenders because all it takes is a few simple checks when the client queries player data from the hive, on launch, to determine the key data needed to know if the player is a server hopper or a legitimate player. The hive most definitely knows the last serverID you played on when you start the DayZ client, so effectively all you have to do is force everyone back to the menu screen after server logout, and run a hive data check every time. If the Timestamp data for login/logout/serverID/PlayerPosition over the last X minutes of play doesn't match up...then simply enforce a login delay on the character which deactivates both the Play and Server browser buttons. This all by itself curb checks peoples capability to constantly ghost through the network and avoid playing the game...cause its really what they're doing, they're avoiding playing the game at all but still "winning" as it were and they'll always have a direct advantage against people playing the game as intended because they gear faster and they're a constant threat to anyone playing the game as intended because they can appear at any time that someone playing the game legitimately is trying to get access to high value loot and simply overpower them based on their constant and direct access to key military hardware that the non-ghosting player cannot get their hands on because of the hoppers in the first place.

So the forum is pretty much full with topics regarding combatlogging. People complaining about it, people using it and people trying to fix it. For me combatlogging (and everything of the sort, ghosting, server hopping) are a major annoyance right now. I know rocket is working to fix it, and maybe even has a solution ready to be implemented. The goal of this thread is to maybe help him with a couple of ideas to make the solutions as failsafe as possible. I read a lot in the forums about the topic and I'm going to try and merge the best ideas I found together into one giant combatlogging fixing juggernaut ;). First we must define what combatlogging is. Here's what I think. Combatlogging is logging out of the game when your character is in danger of being detained, robbed, wounded or killed. Now in order to put a system in place which prevents players from combatlogging, we must determine when a player is actually at risk of becoming detained, robbed, wounded or killed (or in other words, is considered in combat) Number 1: Player is bleeding Number 2: Player is under attack either by 2.1) a zombie, which means he has alerted a zombie to his presence and said zombie is in pursuit or attacking the player. 2.2) another player, which means there was a hostile action towards the player (shots fired at or hit in a 100m radius around the player**), melee attack, the attempt to handcuff the player). Number 3: The player himself is attacking (again any kind of hostile action towards a zombie or another player like stated above) I think the "in combat state" should last 2 minutes. Meaning whenever one of the above 3 is true, there is a 2 minute timer for how long you are in combat. **There is one big problem with the "shots fired rule". How do you determine if the shots were meant for the player? You can either go by a given radius in which every shot fired would be considered a threat to the player, or by shots hit in the vicinity. In my opinion the first one is out of the question, because the radius would have to be to big (a sniper could in theory be shooting from 1km away). That leaves option 2, shots that hit or are shot in the vicinity of the player. I'd suggest a 100m radius. Now that we've determined when a player is considered in combat, the next thing would be how to handle logging out. There are 2 states. The normal logout: The player wants to quit, goes into the menu, gets a 15 second timer and then hits "Exit". This has been proven functional in many DayZ mods and is, in my opinion absolutely reasonable. After that, your character just normally disappears. And you can switch the server if you like. But after the switch you get a 1 minute delay, which gets multiplied by the factor 2, before you can switch again. Which would mean you can switch once without a delay but after that every server switch the timer would get multiplied by 2. Adding up to a total of 15 minutes. (Also gets reset every 30 minutes. Meaning if you play on a server for 30 minutes your timer gets reset) You can rejoin the last server as often as you like, as long as you didn't change the server in between. After that, you're banned from your last server for 15 minutes. (This is to prevent ghosting while still allowing you to take a break for what ever reason) OR The combatlog: The player is considered in combat and logs out, hits ALT+F4, pulls his network cable or what ever else he might think of. Now the player goes into a surrender position for 2 minutes where he just stands there with his hands up. Now the other party has 2 minutes to either shoot him or handcuff him (during this time the combatlogger is locked out from joining ANY server.This is to prevent him from coming back and shooting the other party while they are on the way over to handcuff him, and to prevent duplication of the items when he joins another server). If they handcuff him, they get a 5 minute time frame in which they can do what ever they want to him and the combatlogger gets logged back into the same server if he tries to join another server (this is so he can take back control of his character and continue playing it if he chooses). Like I said I combined many ideas I heard or read about in the last couple of days. And this is to be seen as a suggestion to the dev team as to how they can effectively prevent combatlogging, server hopping and ghosting. Some of it might seem a little harsh, like not being able to go to a different server for a total of 7 minutes after you combatlog. But you have to understand that combat and PvP is a big part of this game, and for many people the main reason to play. And because of this, there needs to be a punishment if you cheat other other players of the experience by just leaving the game. I hope you guys like it. Cheers! Edit: Added ghosting solution. Edit2: Added an idea Mr. Hyde had on Page 4 of this thread. I actually like solution B a lot, because it's very "simple". You want to log out? Fine by me, just run "here" and you can leave. It certainly would need some fine tuning, like give you a radius of X meters in which you can log out, so you can find a bush or something safe to log out. But in general a really great idea and it fixes a lot of problems. Thanks again for sharing Mr. Hye

Rocket launchee from quake! No but seriously, i would like to see more endgame goals, like base building if ghosting is solved. Like in the wasteland mod maybe, but with more base models. And maybe the ones that dont break the legs of everyone around you. And barbed wire that actually hurts you

Pretty similar to what I have been suggesting, so I am just going to add what I think. Step 1 Essentially, the biggest thing required is to carefully consider how to determine if a player is "in combat", having players nearby should not be considered in combat, as friends wouldn't be able to log out near each other, and can be exploited as mentioned. There is many ways of determining in combat status however: - If you're currently bleeding (you must bandage or you're considered in combat) - If there was someone "Attacking" within a certain radius of you (Melee/guns, pretty much any "hostile" action could count for this, that includes if you yourself did that action) - If you were dealt damage (or dealt damage, whether to a player or a zombie, or by a player or a zombie) - If a zombie is nearby (This is a big one, once zombie respawns are in, will basically count as being in combat unless you wipe out all the zombies nearby, usually would involve having to leave a town) - If shots were hitting nearby within the radius (So if a player is outside the "hostile action" radius, yet shooting at you, it will count as being in combat) That is about all I can think of right now, there might be other ways to determine if a player should be considered in combat or not, but for now that should hopefully give some ideas. Step 2 The next step is to determine how to handle combat logging, which is usually the focus of peoples discussions, so there's already plenty of ideas out there. The biggest issue is legit disconnections/crashes versus alt+f4ing/pulling your network cable out/etc. And also the fact the for some people, there are times where they simply must leave, this is not an excuse for combat logging, and impossible to determine if just combat logging or leaving because they have to. Because of that, I don't think there should be a required log out timer, if people really have to go, they should be able to, but suffer from the punishment for combat logging. So I believe there should be a set timer of say, 30 seconds if someone is considered in combat, when you hit the menu key, you can see the timer, if they click log out it will be considered combat logging, if however they wait for the timer to reach 0, they can log out just fine and are not considered combat logging. I can't imagine a better system for determining when someone determined as "in combat" from the first step, moves into the "combat logged" stage of the second step, remember though that "30 seconds" can be changed if needed. Step 3 Now for step three, the punishment. If you combat log, what is the punishment? At first I was going for a "your character dies" punishment, based on logging out while unconscious or handcuffed changes, this could still work, but the reason its needed for handcuffing is because the person who handcuffed them wont know if the player decided to log off if we try to go with some kind of "character remains logged in for X seconds/minutes", that is also why I didn't put handcuffing or unconsciousness in the list of ways to determine if in combat. Where as if you're still alive, you can still be killed, you're still vulnerable. So I think if "combat logged", the character should remain logged in for 2 minutes(again, amount can be adjusted). Step 4 Now here comes the final step, the character is in "Combat logged" mode, stuck on the server, but what could happen?: - Character gets handcuffed I know this is unlikely, but if someone handcuffs a combat logged character, when the timer expires, the character will get all the "log off" rules applied as if they just logged off, so the character dies, which leads to... - Character gets knocked unconscious More likely to happen, same deal as handcuffed, character dies - Player tries to join another server Should be locked out from joining any other server, this can help prevent ghosting and the like, but the real purpose is to prevent inconsistencies with the Hive, and loot duplication - Player tries to join the same server I really only seeing this happen if someone lost connection briefly, or the game crashed, they log back in to whatever the character state the "dummy" was in. So if they were handcuffed, they would be handcuffed when they log back in, if unconscious, they will log back in unconscious, if they then log off again, their character will die as per the other log off rules. That's my suggestions and thoughts on the topic anyway.

Since my first days in DayZ I hated Server hopping and ghosting, be it for looting reasons or even worse to get in someones back while PVPing so my normal approach is to KoS them as soon as I spot one logging in. Gladly DayZ SA offers now a second option... And there my story starts. Since I spawned a few days back I got myself fully equiped apart from an ACOC for my M4 so was hopeing to get one earlier today in the new tents at NWAF, I approached them carefully from the northeast corner with several breaks to see if anyone is already there, all was quiet, 22 people on the server. I started checking the 1st sandbagbunker outside the wall, nothing of use, 2nd bunker inside the wall the same as just when I was about to leave the bunker I hear the reload sound behind me, turn around and a Server Hopper loggs in, right in the corner of that bunker. Now I hope my plan goes well and I shot him in the leg, it brakes, goooood :D . I immidiatly yell over direct comms: "Sorry, sorry you just scared me to death, I will help you and heal, you just give me a second." I waited 5 to 10 seconds then Mr Hopper anwsers: "Ok, no problem, I´m just glad you didnt killed me." I got him and he didnt logged out, hurray. Then he told me that he was unconcious and I jumped up and down on my computer chair :D :D I asked him how long and he told me "looks like it will be for ages" and we agreed that I go and look for a saline bag ( which was already in my Backpack ) to get him back on the feet but 1st I bandaged him to secure his trust in me. While I searched the surrounding tents ( atleast thats what he thought I was doing ) we had some small talk over direct chat and he told me that this was his 4th server today he was jumping to. I came back to check the area from that bunker I told him and we talked some more while I started phase 2 of my cunning plan, put all his stuff out of his backpack in one that was laying beside him and got that away on my next run for the 2nd tent row on my search for saline :D So there he was, with his face in the grass, no gear left, no meds, no food, probably half dead and a still broken leg, poor him :( Time to confront him with with the reality! While I got my saline out that I "just found" I told him that I will handcuff him for my own security, he accepted after a short arguement and the offer by me to end him right now if he will not obey. The saline goes into his venes and there he is, awake and back on his knees, telling me that all is still greyish and that he is shakeing. So time to start phase 3 of my plan. Without any further notice I started forcefeeding him 3 pieces of rotten fruits I found earlier in his backpack. I guess he didnt know that you shouldnt eat them as he was not moaning and I coudnt hold on myself an started laughing over comms like a maniac and told him what an dumpass he is for server hopping and getting himself in such a situation. I wished him a slow painful death from the rotten fruits and went away with lots of name calling comming from him over comms that got lower and lower... Have a nice day fellow Server Hopper, I hope we meet again...

24h cycles actually break the immersion for me. It is possible to die of starvation/dehydration several times within one day/night cycle of a 24h server. Dont get me wrong, I dont want total "realism" where i could go without food for 3 weeks or without water for 3 days, that would entirely defeat the purpose of the survival mechanics (looting, cooking, resting) already in place providing a meaningful experience to the gameplay and we all have to face one fact: As much as rocket calls DayZ some kind of anti-game it is and always will be a game. I still think that the overall baseline time to starve/dehydration should at least somewhat be reflected in the actual passing of time. I also dont like that I am kind of "forced" to do one or the other. Playing at day or playing at night. I would actually like to experience both..and not by logging from a daylight server to a nighttime server but instead by the time actually passing in a somewhat simulated way that makes it possible to have that dynamic change of scenery gradually happen in a gameplay session. Especially for people with something similar to a 9-to-5-job this can get quite annoying, logging through servers until you can actually "do" something. I think nighttime play and especially the lighting engine need a rework. Right now Flashlights come in two flavors and both kind of taste like shit. Flavor one is the handheld flashlight..which is the single most useless object in dayz. Even more so than toiletpaper in the mod. Your flashlight barely helps you see anything and it gets worse (you see even less) the closer an object is to you. Trying to look for food in a rural home? Get fucked! Handling is clunky and weird, light doesnt work like that IRL and every enemy (currently: every player not on your steam friends list) in a 2km radius can see you lighting up the house like its an asian paper lamp. Oh yeah..and it gives away your location. You are an "idiot" if you dont try to exploit gamma like every bushcamping wannabe-bandit or selfrighteous wannabe hero already does. Another thing to note is that you are utterly defenseless thanks to the flashlights apparent weight of 20 pounds which forces your Survivor to wield it with both hands, unable to equip even a knife or pistol. Best usage for a flashlight at night while having a buddy around? Stay outside of the location you want to loot. Flick the switch and point the torch at the approximate location of the desired room, have your friend go inside and enjoy a house that is lit up like amsterdams redlight district. Because apparently houses in Chernarus are made of indestructable paper. The other one, the headtorch does at least shine where you want it to. Kind of. But dont you dare switch to a weapon and aim down sights. Btw same thing to do when skulking about the nights with a buddy, let him enter, hide in a bush flick the switch and just look at the house - easy loot for the bros. Something just has to be done, not "right naow" of course, because its alpha, but somewhere down the line some hard calls have to be made design-decision-wise, regarding what nighttime-gameplay should be like, same with the third/first person debate, combatlogging (and yes, if I tell you to drop your weapon, get on your knees and you just log out - that is combat logging), serverhopping, ghosting and so on.

This is a very good idea! Especially with public hive systems, just binding your account to a server for a few minutes would solve it quite elegantly: If you want to switch servers, you'll need to wait 5 minutes, while your character remains visible (and killable) on the last server you played on. Additionally you get a reasonable discouragement of ghosting and hopping.

Hello everyone! I'll start off by saying that regardless of the game's very, very early alpha status, it's amazing. The implemented mechanics and amount of potential it has are just overwhelming. Keep that up and you'll have the most amazing, immersing title in a decade. My... appeal for the community as a whole. People who come here and complain about the mod having this and that mechanic or just compare the "visible" exterior mechanics simply don't have a clue and i'm sad for them. Just give it time. This engine already has an impressive set of means for making an unique and wonderful gameplay. Ofcourse there's a ton of flaws and limitations and things i'd like to change myself but it would be pointless to bicker about those at this stage of development and most of those already have had a debate going on for a year atleast so... The antihack, combat timer etc. will be there i'm sure, as well as something to prevent ghosting, exploiting etc. So no need to endlessly scream about it, is there? I believe we as a community would do well to try keep these forums as constructive as possible if we really want our voices to be heard. No dev is gonna waste three days going through hundreds of pages of endless rants and flames about the obvious in hopes to catch that single constructive post with a great idea in it! There are indeed many here, lost among the pointless bickering. People posting about "how serious disappointment this is" are systematically either too ignorant, clueless or just simply unable to properly understand just what are they evaluating in the first place. Take a deep breath and consider if you actually have any relevant feedback or realistic solutions for those issues. If you don't, just don't post. If you aren't even trying to solve the problem, you are part of it. As stated a few times: Pre-Alpha(er). You got what you paid for. Regarding the weapon accuracy... There's really a huge debate about weapons. I'm all for realistic approach myself and having an excessive firearms training, having served in army as a platoon commander/drill instructor i certainly have my own view about how guns should work and what people should be able to accomplish with and without proper training/knowledge/excersize. My suggestion for the middleground is this: Introduce condition to the weapon itself. Make it play a big role: Bad condition gun/mags results in bad, unpredictable behaviour (bad accuracy, weapon jams, unintentional firing, feeding issues, etc.) Pristine weapon is accurate and reliable. Make weapons/materiel degrade over time/conditions and maintainable. No gun, especially western made complicated assault rifle, is able to fuction properly while running around, engaging enemies, crawling in forests etc. without proper maintenance. It should be an effort to keep ones weapon in good condition/prevent degrading. A normal soldier spends almost as much time/effort maintaining combat equipment as maintaining oneself in those conditions. Make bad quality equipment the stardard. Make ways to maintain or even slightly improve the materiel condition. A reliable, accurate rifle of any kind should be a really rare, prized possession be it mosin or whatever else. Hell, make it so that most weapons you find are pretty much useless until proper measures have been taken to restore functionality, much like vehicles in the mod. When you (after firing lots of rounds) leave the gun laying in the autumn woods, it sure as shit isn't going to work properly after a few weeks, let alone longer time. Other than the weapon condition, performance should be purely about skill/knowledge instead of some random dice roll. This would be completely doable with the excisting mechanics already implemented in the game. =) Oh... Such a huge post. I guess i got carried away a bit... None the less... Do not just complain people! Suggest, give ideas and solutions if you have issues! That way you can sill rant all you want but might actually contribute something while doing so! See you out there.

don't sue me if this is a retarded idea but here she goes. right now PVP is completely pointless thanks to combat logging, and there's not much else to do right now. - bound a player to his/her current server for at least 120 seconds. if the player leaves during combat, his character stays in game for (2minutes) as a dummy. making it pointless to log/alt+f4 during PVP, unless you want to give away your gear. - if a player logs out to go on another server (for escaping combat, loot farming, server hopping or ghosting) he gets the error "Your character is currently logged in. [servername]". Maybe it could show the remaining locked-time in the message as well. obviously i dont know much about the netcode but i hope/guess it wouldnt be too hard to implement this. current server for every player would be saved on the central server. you could argue that it doesnt matter if no one likes the alpha-test right now but more players also mean more bug-reports, more moneys for development etc

Once Alpha stages are over things will be opened up alot more and this will probably be a reality. As of right now they need everything public and centralized so they can track down and smash the bugs as fast as possible and it sux terribly that we have to wait (I too am sick of the hoppers mainly altho they can be a fun hunt) but that is the price you pay when you buy into a game that is in the works. There is the possiblity they will come up with some ingenious way to combat the ghosting/hopping before hand but I have no idea what the best cause of action would be, I just hope they won't let game ruining things run unchecked until late late phases.

When can I expect private servers with no server ghosting/jumping option? For now none take gameplay seriously beacause you can get best gear in 30 minutes jumping from server to server. You will say "ok, then don't jump and play legit way!". Ok! I'll play for hours and finally get my fire axe to then get killed by freshspawn with silenced m4 with ACOG. DayZ official servers were never playable, just saying. So again when will private servers start?

Servers popping up with only allowing a few players and such. Could this be people renting a server for their clans or what not and using them to gear up and then logging on to the busier servers. Only to do it all over again when or if they die? Obviously could be used for ghosting as well. Just wondering I have no proof of this nor will I attempt to obtain any cause I have no desire to waste my time on it. just thought I would bring this up and maybe could be something to watch out for.

Three words: Server locked Inventory Play on any server you want, but have the inventory saved only for that specific server. See. All of the listed problems have gone away. Okay, ghosting (not listed above) could still be an issue! And it won't do much for spawn campers. But if you log off in the middle of NWAF, can the head shot on spawn really be unexpected! I've never understood the idea of being able to jump between servers and take your inventory with you, and have never seen it used in anything other than exploitive ways.

Walking speed is way too fast as it is. Hell, sprinting at 24 km/h indefinately is so OTT. Crank those back, I say. Take a day to walk across the map. At least that's one day you're not dead! And you want cars! Next you'll want helicoptors and jets! And then it's only a small step to teleports between fat loot spawns! Might as well since WOW has them, right? ;-) The only major flaw in this game (and the mod as well) is the fact you can loot gear on one server and transport it to another to be used. Kill that and then we're all on the same battlefield with the server jumping, combat logging, ghosting, PvP sons of ... Opps. Sorry, almost headed into full rant mode there.

I really dont understand why are ppl constantly suggesting crazy ideas for fixing those things. For combat loggers, just do what mmos have been doing for a decade now(if not even more) You want to log out - you have to sit still for 20 seconds. If you dont want to wait or alt f4 your character just stays in the world defenseless for several minutes. For ghosting - when you switch servers you get a 5 minute cooldown until you can join the last one you were in. Server hopping - If you switch servers more than X times in X amount of time you get a global ban for Y amount of time until you can join any server. Am I missing something or is it just so easy?!

you mentioned ghosting, combatlogging and hacking. buying my own server and freefarming equip does not sound like any of those.

Well its an alpha so the net code isn't done being updated/worked on i'd assume. I've experinced some rubber banding/ghosting through walls(my buddy says I ran through the second floor of the ATC but on my screen I just left the room) and some stutters randomly but overall the lag isn't any worse then the mod

You did the right thing. It was a low pop server he was not their when you went up so the sound of a gun being loaded means he just spawned in. Most likely ghosting/server hoping for loot.

Rust has the best solution to each of these problems. When you log off your player stays in game but sleeps. Each server has its own saved player location so this eliminates ghosting or server hopping.

Let me just play the devil's advocate: Upon release: Private Hives should do whatever they damn please, as long as it doesn't affect other private hives and the public hive. There is a reason why implementing all these, in my opinion simply fascist, rules about how the game is 'supposed' to be played, will simply kill off more than it will preserve. They paid for their private server, let them mock around with it! You don't like that? Find a different one! Even in the darkness there is always a shard of light, good private hives which enforce their own rules, not limited by the developer. Heck, the more freedom you give people, the more chance they will maybe even produce something good! Don't limit something because it differs from your view of how it is supposed to be. You may be wrong... You don't like BS private hives? Play public! And please, don't complain that it shatters the community. It is shattered to begin with, with people wanting to play different settings and different variations. Private hives can provide this much faster and much better than the public ones, while also building a community to play with. I left public hive because it was full of hackers, combatloggers and ghosters, neither of which have even been remotely solved in the mod and which will not be solved by SA. Forgive me for being realistic. TL;DR version: (Good)Private hives: + No Ghosting + Quick response to hackers + Quicker problem solving(reverting versions, loot decisions and so on) + A regular, solid community + Tailored to what people like (Good)Public Hive: + Quick switching if you don't like the server + Ability to meet a lot of new people faster + Ability to gear up faster(server hopping, OMG!) - Ghosting - Combatlogging usually unpunished(switch servers, proceed) - Hackers usually unpunished(same as above) - One size does not fit all

Probably ghosting, did the right thing to kill the twat.