'No Disconnect Zone'

[forester155 11]

The idea is simple. Some areas are a 'No Disconnect' zone, preventing players from server-swapping so easily. Similar to if you alt-f4 while tied, or DC while passed out, if in these zones your character will be killed on reconnect. Each NO-DC zone is warned with a status identifier in the pause menu, as should any other interruption to your disconnection (IE: If you're in a No-DC zone, it'll say in red text NO DISCONNECT ZONE when you open the menu. Same should happen if you open the menu and you're cuffed or passed out) to allow for fair warning before a player accidentally kills themselves. If a player is safe to disconnect, a green "OK TO GO" or something like that should be visible. (Or perhaps just nothing).

 

Where should the No DC zones be? That's up to rocket or the community. I'd suggest that most of the airfields are no-dc zones, as well as any other barracks and military loot zones. I think it should be the same for hospitals. Players should be free to DC on the street though, and also in houses with lower level loot. This helps to discourage server-hopping as it makes it a little bit more difficult. It also makes it more difficult to create 'bunny ambushes' where one server hops with a group in a set of barracks effectively teleporting in to take anybody at the location by surprise (HUGE ISSUE AT BALOTA!)
 

What do you guys think? Should rocket consider this, or a similar feature to this?

[atc86 46]

I only read the first paragraph but you sir have my beans!

They would need to make it so that if you d/c from connection problems, or from a server restart that this rule isn't applied.

Good idea though! :)

[fluxley 2228]

They would need to make it so that if you d/c from connection problems, or from a server restart that this rule isn't applied.

 

 

And there's the problem,

There's no way to tell if someone legitimately loses connection or manually shuts down their game.

[dsi24 227]

And there's the problem,

There's no way to tell if someone legitimately loses connection or manually shuts down their game.

But making it harder to do makes it less likely to happen. 

 

Really good idea OP, making it actual zones instead of some kind of rules based prevents any information gathering through it!

Edited December 25, 2013 by Dsi1

[Diggydug (DayZ) 331]

So if someone did disconnect or close the game, then what?

 

 

I misread. Killing them for potentially legitimate reasons, especially in Alpha is not the way to go. Don't punish the innocent in an attempt to punish the guilty.

Edited December 25, 2013 by Diggydug

[ClassifyLP 61]

This is impossible to achieve, since you cannot tell wether or not a disconnect or game crash was legitemate. Killing someone because his game crashes or he lost connection due to legitemate reasons is unfair.

Find a better solution.

[crazykid1297 51]

Instead of logging off in a "No-disconnect Zone" and having your character outright killed, it should respawn you at the coast or move you kilometers away. I like the idea though.

[Mind Killer 7]

honestly if you lose internet, tough luck imo, that doesnt happen often enough to be a legitimate problem, and if it does, its your own fault for choosing shitty internet. And the server restart thing is easy to counter, just have the no dc zone thing turn off a second before the server restarts.

[satly 2]

To be honest, its bad idea, i think the best thing to do is just have time till you can dc, like the mod had, give the player 20-30 secs untill he can disconnect, and if someone dc before that time (e.g. combat log) then the person who dc'ed stays is the place for about 20-30, and if it was a combat logger so the other person can just shoot him and take hs gear, that will fix the problem as if someone combat log and comes back right at the coast , that will make his first gear disspear.

[crazykid1297 51]

To be honest, its bad idea, i think the best thing to do is just have time till you can dc, like the mod had, give the player 20-30 secs untill he can disconnect, and if someone dc before that time (e.g. combat log) then the person who dc'ed stays is the place for about 20-30, and if it was a combat logger so the other person can just shoot him and take hs gear, that will fix the problem as if someone combat log and comes back right at the coast , that will make his first gear disspear.

 

It's a better idea than another I've heard, such as banning players temporarily who server hop. Sometimes with the current servers you server hop without malicious intent, such as to find a daylight / nighttime server.

[per2 9]

The idea is simple. Some areas are a 'No Disconnect' zone, preventing players from server-swapping so easily. Similar to if you alt-f4 while tied, or DC while passed out, if in these zones your character will be killed on reconnect. Each NO-DC zone is warned with a status identifier in the pause menu, as should any other interruption to your disconnection (IE: If you're in a No-DC zone, it'll say in red text NO DISCONNECT ZONE when you open the menu. Same should happen if you open the menu and you're cuffed or passed out) to allow for fair warning before a player accidentally kills themselves. If a player is safe to disconnect, a green "OK TO GO" or something like that should be visible. (Or perhaps just nothing).

 

Where should the No DC zones be? That's up to rocket or the community. I'd suggest that most of the airfields are no-dc zones, as well as any other barracks and military loot zones. I think it should be the same for hospitals. Players should be free to DC on the street though, and also in houses with lower level loot. This helps to discourage server-hopping as it makes it a little bit more difficult. It also makes it more difficult to create 'bunny ambushes' where one server hops with a group in a set of barracks effectively teleporting in to take anybody at the location by surprise (HUGE ISSUE AT BALOTA!)

 

.......

 

 

To be honest, its bad idea, i think the best thing to do is just have time till you can dc, like the mod had, give the player 20-30 secs untill he can disconnect, and if someone dc before that time (e.g. combat log) then the person who dc'ed stays is the place for about 20-30, and if it was a combat logger so the other person can just shoot him and take hs gear, that will fix the problem as if someone combat log and comes back right at the coast , that will make his first gear disspear.

 

 

i like both ideas and i would merge them .... i would make the 30 sec log-off timer everywhere(you have to be sitting and not moving - otherwise timer is interupted) + i would add the combat/no dc zone  where the log-off timer would be something like "x" minutes or so? if you lose connection there your char will stay there for "x" minutes and then logs off .. there is chance it survived (no bandits around/not chased by zeds at the moment of connection failure) ... question is where those zones would be (some distance from buildings?/all military zones?)

[applejaxc 2500]

The problems therein being:

 

How large are the disconnect zones? I don't want to be forced to keep running because I'm unknowingly within 300 meters of some part of the map I've never seen before.

 

If they're too small, what's to prevent players from running in, looting, running out and disconnecting? For some loot areas, enough running is required regardless that this won't do much to impact server hoppers.

[ryan__mc__@hotmail.co.uk 131]

no

[aug1186 0]

And there's the problem,

There's no way to tell if someone legitimately loses connection or manually shuts down their game.

 

Not necessarily.  I can't imagine it being tough to add in a 'behind-the-scenes' command to the Menu Exit button that says to the server "I am legitimately disconnecting from the server, is this okay?"  If you are in the No DC zone, the server responds with "are you sure, you're in the No DC Zone".  Should you choose to disregard the warning, there's where the consequences apply.  

I also imagine it's not hard to put in a check for pressing ALT+F4.  If they could introduce something like in WoW where you're 'In Combat' and you press ALT+F4, that would take care of that issue as well.  If you disconnect in some other way than ALT+F4 or using the Exit button, we can probably safely assume internet related issues.  Yea, you could probably alt+tab and kill the DayZ process with task manager and keep server hopping, but that's now starting to make someone work rather than just a quick disconnect and server swap.

[Hoj0 (DayZ) 31]

To be honest, its bad idea, i think the best thing to do is just have time till you can dc, like the mod had, give the player 20-30 secs untill he can disconnect, and if someone dc before that time (e.g. combat log) then the person who dc'ed stays is the place for about 20-30, and if it was a combat logger so the other person can just shoot him and take hs gear, that will fix the problem as if someone combat log and comes back right at the coast , that will make his first gear disspear.

 

 

good idea, you should be allowed to disconnect and whatnot, but if you kill your game or loose connection, legitimate or malicious, your character should remain in place for a period of some, giving someone the opportunity to kill you for combat logging.  Would probably have to have something in place to where you couldnt change servers for that same period when you disconnect.

[satly 2]

Guys, think about the fact that if there will be "no dc zone" then most of the people will be killed by spawning in the field, take for exemple the field behind NWAF, most of the people who want to dc and stay close will go there, probebly will be killed by someone who just connected or it can be the other way, someone connecting in the field, and someone want to dc, sees him and killing him.
 

i really think that the only option there is for this is not the no dc zone, but make more time dcing in some zones, not like 30 secs but for 5 mins , will make some people to run away and some to wait, kinda balanced.

with the other idea that i said before, with this thing will be awesome, will stop people from dcing and respawning causing their gear to dissapear and the person who wanted to kill him will get no gear at all even tho he almost killed him.

[Propulsion_Joe 97]

So what stops people from camping right outside the No DC zone, shooting people in the No DC zone, and then disconnecting once their position is compromised?

[combatcomm1 234]

YES PLEASE! I am so tired of this shit. This exploit is annoying and gets people killed after effectively clearing the building. The only people that dont like this kind of idea are people who love to use the exploit. We need to keep this one at the top so the devs can see.

 

All I see are people saying, "Honestly uhhh hurr durr its a bad idea..." and than not saying why its a bad idea. And don't use the internet cut out on you. Tough luck. 

Edited December 31, 2013 by VictorM

[methr1k2dop3 323]

I think we should just start with some sorta log out timer.

Some people will suffer with DC's but getting rid of the exploit would be worth it.

30 secs is to short,

i vote for 10 min timer to log out.

this means to log out safetly you would need to get to a truly safe spot.

Maybe a sleeping animation to go along with it.

 

IMO would be better than just specific spots you can logout.

Edited December 31, 2013 by methr1k2dop3

[Dchil 829]

Why not have the NO DC ZONE script only activate if the exit button is pressed and not if you crash/internet DCs.

 

It shouldn't be that hard, and who is going to bother to wait the 5mins (i'm just putting a random number on it here) it takes to restart the game and then the extra time to log into a new server, just to swap a server?

 

Should stop the problem, unless it doesn't work that way. I seriously doubt that it doesn't work that way.

 

EDIT: also 10mins for a disconnect timer is far, far too long. That sh*t would seriously cut into my possible game time (I could only play 50mins instead of 58-59 mins when i have only 1 hour to play) and what happens if someone comes in, i'm  pretty sure that you can't voice chat in the pause menu. That would sh*t people right off, possibly leading to more KOS for no reason other than the guy walked into a room he had no idea that someone was in.

Edited December 31, 2013 by Dchil

[ChangoSoup 0]

A simple 30 second timer over a logging players head would be easier, maybe even a chat notification for people close by "so and so is attempting to log". For people who alt f4 out make their character remain in the world for 1 min with an LD sign over their head. Very similar stuff to what MMOs do