i see that message a lot and its usually because the server restarts. once the server is back online i would just rejoin and my character was right where i left off with all my stuff.

at least you have the voip icon next to your name on ps4. i dont even have that showing up. have all the voice chat settings right too.

you will probably need to provide your server info. i have encountered this issue on all servers with persistence on since last weekend. some of those servers have become so unstable they refuse connections entirely. going through the support/abuse channels that BI actually tells us to use when reporting server issues ended up being a waste of time as the server company refused to accept my ticket because i did not have an account. i reported it here as well but no action has been taken. persistent servers are still an unstable mess and will probably not be fixed until the next changelog. good luck on your report though.

vilayer has replied and will not accept my support ticket because i need to have an account with them. i dont really understand this policy as it is contradictory to the process that BI tells us to use in their own blog posts.

i am including a link to my other report as it is basically an extension of this issue.

http://feedback.dayzgame.com/view.php?id=15947

10 days after reporting this and i have still not found a solution to why this is happening. this is mainly due to the fact that more and more servers are failing and i do not have time to check them all anymore.

no acknowledgement of the issue in the latest progress report other than, we will be wiping the servers once .49 goes to stable. i fail to see the reason why this would be considered a "solution".

i have included a screencap of all the servers that are seemingly dead. 0 populations and timers locked at xx:00.

if anyone has a link to information that i have missed regarding this issue please include it. honestly, i have reached my limits with this issue and this ticket process altogether and all i see happening once .49 hits stable is a repeat of these same issues because no fix was ever implemented.

upvoted for you chode...yes, what started out as
an item issue report has now become a widespread
server performance issue. i was going to change
the category but i do not think you can once you
report an issue...so it is stuck as items. no biggie.

current report as of sunday.

all persistent servers seems to be malfunctioning.
during yesterdays play time i did notice a
severe drop in server performance with restarts
taking 15-20 minutes when before it only took 1 minute.
all persistent servers are listed but with 0 pop and
refusing connection.

more information from my tests. i have copy pasted my post from the steam forums. my point about servers being "loot locked" for several days is what has me confused the most about persistence and if this is how it is intended to function.

*copy/paste*
well after a long night and morning of testing some ideas on the nature
of persistence here are my observations as of saturday morning.
*official servers with persistence on only*
loot does not despawn. seemingly ever. my stockpile has remained
safe and sound out in the forest since thursday morning. this is great
news for the survival players out there! but...this doesnt just mean the
loot you are stockpiling somewhere that seems to be safe from despawning
and server restarts. this seems to mean all loot. i tested my theory out
on a second server through 3 restarts yesterday and into the early morning
hours and noticed the same patterns. untouched loot is not despawning.
what this seems to indicate is if persistence is working as intended then
what we have here is a kind of "loot locked" server environment. in my
searches across 3 bases on 2 different servers the loot is not refreshing.
it is the same loot in the same spots as before after every restart.
if i notice any changes to loot in the areas that i patrol i will report it here.

i tried to report this months ago with no success. i reported again just a few days ago because i figured by now it would have been fixed. glad someone else noticed this as well.