Coast Spawning, Please Explain.

[Gustav Mahler 40]

At the moment, a whole lot of players are spawning on the coast randomly. Can we please get a response from the devs as to whether this is a new feature intended to dissuade server hoppers or an unintended bug?

1. If the answer is unintended bug. Alright, fair enough. Alpha is alpha.

2. If the answer is new feature, then please explain to us its mode of operation so that those of us who are experiencing problems with it can know how to play appropriately.

Thank you and good day,

[McLovinCR 29]

At the moment, a whole lot of players are spawning on the coast randomly. Can we please get a response from the devs as to whether this is a new feature intended to dissuade server hoppers or an unintended bug?

1. If the answer is unintended bug. Alright, fair enough. Alpha is alpha.

2. If the answer is new feature, then please explain to us its mode of operation so that those of us who are experiencing problems with it can know how to play appropriately.

Thank you and good day,

Seems the counter-measure implemented for server hoppers.

[Texas Red 8]

Are you talking about that sometimes when logging on, you get spawned on the coast, with all your stuff, instead of where you were? This happened to me once, at NWAF. I left the server a bit from the walls, in the woods. And I spawned back in, but was in Balota instead. Is this what you are talking about?

[daddydustin 93]

I think the problem is that the servers save points were reset during the patches, or the servers are not saving your log out point

[Gustav Mahler 40]

According to who?

[HMS 115]

This only happens to me when:

Stuck on perma-load, I quit. Usually 95417.

Join another server, successfully. Always 95883.

This does not happen when:

Join 95883 server. Quit just because it's time to quit.

"Server hop" to another 95883. I am right where I am supposed to be.

Based on that experience, this isn't a feature. (good)

[t3hnoob 9]

its a new feature, it "corrects" for spawning in debug plains/forest, instead of spawning there, you get respawned on the coast with all your stuff, take your pick, i pick coast, running 40km(3 times the lengh of the map) isnt fun....

[Dingus (DayZ) 429]

I was just playing fine on the new patch and 95883.

But hey, there's a dusty bug reporting board over there.

[Gustav Mahler 40]

I was just playing fine on the new patch and 95883.

But hey, there's a dusty bug reporting board over there.

Thats lovely, I'm glad you're having a fine time. Now as a member of the Forum Team, could you please answer my specific and direct question. Are the coast respawns an attempt to prevent server hopping or not? Thankyou.

[Dingus (DayZ) 429]

I'm a mod, sir. I'm not a developer. I wish I could tell you. I'm sure once it is known, and this thread is still floating around, I'll be sure to update it, like I did during the Battleye situation.

[HMS 115]

To OP: In my small test group, it is not random. It seems random, but there is a common thread.

I can make it happen with 100% certainty based on my other post in this thread.

That makes me think/hope it is not intended. But that of course is just conjecture until we hear something for sure.

[xzite 18]

Personally if it IS a 'fix' i'm probs not gonna stick around. It takes away from the emersion for me, knowing that all my hours of running will be for nothing. Plus the fact that shoreline snipers are gonna be absolutely loving life now, because the beach-goers that they're targetting will most likely be fairly well equipped.

[oshnatour1 14]

i dont know how it would be a sever hoping thing because every time i spawn in... (hours apart) its a new spawn so i dont know about you but i dont consider that a server hop

[sixlooter 1]

same here, everytime I log in I respawn somewhere along the coast. Deeply annoying.

[sostronk 334]

Its happened to me a couple of times, but usually I spawn where I finished last time.

[cwc_shadow 70]

Happened to me yesterday. I haven't played DayZ for 10 days and installed the latest release (1.7.2.5) from Dayz Commander and also the latest ArmA II Beta (95883). I was in a wood north of Cherno the last time, but when I logged back in I spawned at coast with all my stuff. I then walked to Stary to meet some of my friends who where playing on another server. After I was there, I switched to their server, but got stuck on "Loading" for ages. It took me a while to figure out that they all had been still running DayZ v1.7.2.4 and also was that server. I still had a backup of that version so I reverted to play with them. When logging into that Server again (now with the correct 'old' version), guess where I spawned again: in Cherno! Again with all of my stuff, but I had to take that stupid 5 km walk again...

I then said to myself "FU" and reverted back to 1.7.2.5 to keep playing on the other server, as I wasn't in the mood to run all that way again. When I logged back into the other server I was playing before, I still spawned on the coast in Cherno (d'oh!).

I sticked to the new version because I didn't want to risk my position getting reset with 1.7.2.5 again if I kept using v1.7.2.4. I guess the character position is not saved correctly in some cases after the update, that's the only explanation I have as I wasn't playing for several days before the update and just after the update I spawned at coast again. At least I didn't lose my gear. :P

€dit: It happened again... <_<

Edited August 12, 2012 by System98