Server logging - a thought...

[Bacon Surfboard 61]

So rather than crying about losing a firefight to a server hopper can we think of a rational way to fix this?

I know there are knockout timers etc and Rocket has mentioned that he will be patching this out in the future (if possible) but I was thinking about the situation we were in today and it does present some problems.

3 man team, vs 2 man team.

We are the three man team and two of us get downed by a DMR from range.

Our 3rd man counter snipes the DMR ranger and spots second target taking cover.

Whilst covering the exits after about 10 minutes my boy gets domed in the back of the head and it was definitely a server hop.

Thing is, even if there were a 10 minute rule lock out, in game we didn't much want to just up sticks and move as you can't be sure who is where in a fight.

The only conclusion I came up with was to lock people out of a server they disconnected from for ~20-30 minutes. Which isn't going to fly with new spawners on the coast at all and yeah even I think that's excessive, but how can you leave it long enough to get comfortably up the 500 yards cautiously to see where the player is if it is less than 15 minutes?

I feel that even as a relatively new player this issue is going to be "fixed" but not work in practice as 80% of the playerbase want nothing to do with these server hop restrictions, 10% are server hoppers and 10% are legit stay-in-til-the-end fire fighters...

Is it just a case of tough shit you gotta relocate inside 5 minutes and hope no one else is on overwatch or is there anything else that the community has suggested?

I don't particularly want to just log off and go to a different server but if the majority of firefights end up this way that's all my team are going to do unless we get confirmed rifle headshots from 600 yards+.

And inb4 tears, i'm not mad, re-rolling is re-rolling in DayZ it's gonna happen and I'm cool with that, just want to curb some cheese gaming.

[SystemiK 366]

I believe I saw Rocket mention somewhere recently that the most he could do technically the way the code is was ~5min possible it was ~2min not sure. (srry can't recall exactly where I saw it).

[Bacon Surfboard 61]

If that is the case then we'll just have to log off.

Target takes cover, logs in behind you, waits timer, kills you.

If you only have one overwatch player he cannot watch front and back in case he did/nt hop and the hop and penalty is less than 10 minutes, which is not really feasible to approach a hilltop inside 10 minutes unless you just sprint/crouch run directly up it in which case if he didn't hop you're going to die.

[SystemiK 366]

Yeah we are just gonna wait and see how it all shakes out. No doubt he will come up with something workable for everyone.