Dupe problems on server restart

[SadBoy1981]

 If player before restart add crypto to bank, about 1 minute before restart, then, when he login, crypto stay with player and also he have it in bank!

Is there way tp prevent this, looks like database wont save player with some actions or there is some saving timer?

 

Edited August 27, 2015 by SadBoy1981

[Sp4rkY]

If this was so in earlier versions, then the problem is the saving time of the database...

Otherwise you should post this in the Feedback part of the forum, so Devs can take a look at this.

If this only happens since 0.3.2.0 you could write some temporary code to prevent players from using the Atm 5 or more minutes before restart..

cheers

[SadBoy1981]

If this was so in earlier versions, then the problem is the saving time of the database...

Otherwise you should post this in the Feedback part of the forum, so Devs can take a look at this.

If this only happens since 0.3.2.0 you could write some temporary code to prevent players from using the Atm 5 or more minutes before restart..

cheers

Maybe u know some way to do that?

[Brian Soanes]

Simple way to do this is to change redis.conf to save more often. It shouldn't add any overheads.

You can change one of the values or add your own to:-

save 30 1

This will save every 30 seconds as long as there is at least 1 change waiting to be saved.

[SadBoy1981]

Simple way to do this is to change redis.conf to save more often. It shouldn't add any overheads.

You can change one of the values or add your own to:-

save 30 1

This will save every 30 seconds as long as there is at least 1 change waiting to be saved.

Thanks, i will try!

[Halvhjearne]

 If player before restart add crypto to bank, about 1 minute before restart, then, when he login, crypto stay with player and also he have it in bank!

Is there way tp prevent this, looks like database wont save player with some actions or there is some saving timer?

 

are you restarting redis when you restart the server?

Simple way to do this is to change redis.conf to save more often. It shouldn't add any overheads.

You can change one of the values or add your own to:-

save 30 1

This will save every 30 seconds as long as there is at least 1 change waiting to be saved.

it wont help saving the database more often, if the keys was never changed.

most likely his server is overloaded with db requests for server restart, when the server shuts down redis for a restart.

if thats the case, the last keys changed will never made it through the queue.

Edited August 28, 2015 by Halvhjearne

[KPABATOK]

This is how duping always worked and works in DayZ SA too and they never even tried to fix it. For over a year. I guess this is exclusive Bugemia feature

[SadBoy1981]

are you restarting redis when you restart the server?

 

Server run on VertHosing, i dont have acces to database configs. Dont know how database work there.