Wow. The feedback tracker is dead.
Guess nobody cares anymore, not even players.

what the hell do you mean with "The feedback tracker is dead"? look at yesterday how many stuff was closed.

BI was on holiday, give them a break!

Not BI, there are no comments from other players anymore.

So you downvoted a sensible bug report that can be used for duping because you were upset about my note, did you? Sad case, you are?!

can you reproduce it? i think not. they will fix the server crashes. no crash no "no message receive" no duplication bug

Actually you found a bug with an item. I too unstablized the server once. Cant do it again. Seemed to be the spray paint can I used. Did it 3 more times and ended up with 6 of the same bags.

Persistence errors they are working on. So until persistence is fixed, I agree anything reported with persistence doesn't mean much at this point. Dayz knows about persistence.

Even my server provider does, by the messages TuRN off persistence if no loot is spawning. Tents don't work correctly, teddy bears respawn at horrible rates.

The persistence is a mess.

I actually have reproduced it a few times by now, even if unwillingly. It has to do with a discrepancy between when the character is saved and the server loot is saved.

Problem is, you have to know precisely what second (+/- 2 seconds) the server will restart.

Meaning admins can exploit this to their advantage. It has nothing to do with server crashes, but restarts. Brain!

there is a popular duping method involving restarting the server.

Player 1, Player 2

1 drop backpack
2 pick up backpack and log out
1 restart server

or something like that

player 2 logged out and had his stuff saved
player 1 restarted the server before the server synced with the hive and kept his backpack.

There are/were ways to do this on any server involving handcuffs and killing.

@Franzuu
Yes, that sounds feesible.

damn, i hate admins doing such things with a server.

if a server has normal restart timers, no crashes and no bad admins.
can you reproduce it, too?

Hey ColonelBurton,
the FT is most definitely not dead and we keep track of every ticket.
The reason for no response here was simply the fact that we are aware of this problem and it has been scheduled for an eventual rework - which might take some time, as the whole situation is quite closely linked to the server restart and persistence systems in general.
Rest assured we are looking into ways of preventing this, but as I said, due to the complex nature of the problem, it might take time - please be patient.
I am going to close this ticket, as the issue has been reported before. I'll also make it private to prevent anyone who might not know about this from abusing it.
Thank you for your feedback and dedication.
Regards,
Andy