Page MenuHomeFeedback Tracker

Previous Steam user data when new Steam user logs into Steam and runs DayZ
Acknowledged, WishlistPublic


When trying to play DayZ on a PC of another DayZ player you will see his character and his character name on the start menu.

I had to change my name as it was stored locally

The character displayed at the start page was my friends last character.


Legacy ID
Have Not Tried
Steps To Reproduce

Log out from Steam and log in with another user credentials. Then play DayZ.

Additional Information

Won't be able to reproduce. It was a one time only action. I've been at friend's PC just to show him my own character and stuff.

Event Timeline

Rebeliant edited Additional Information. (Show Details)
Rebeliant set Category to Settings.
Rebeliant set Reproducibility to Have Not Tried.
Rebeliant set Severity to None.
Rebeliant set Resolution to Open.
Rebeliant set Legacy ID to 2092294449.May 8 2016, 11:55 PM
Rebeliant edited a custom field.
Rebeliant added a subscriber: Rebeliant.

After receiving a feedback from my friend I can confirm that the problem is repeatable.

when he wanted to log in into his account then my character name and character was visible on the start page but in Favorites there were my friend's servers added (as yesterday there were mine).

Should I test it more?

I think you could easily test it in your own environment so I won't have to ask my friend to test it more on his PC.

It seems that some files stored on the local HDD are common to any Steam account thus it may seem a simple case but instead it needs quite a big redesigning.

I can test whatever is needed, my friend lives like 100m away so the only thing we need is some beer/vodka to socialize so I can once again try to log in to Steam on his PC (and his PC is familiar to my account ATM).

Geez added a comment.Oct 20 2015, 9:33 AM

Hello Rebeliant.
We are going to test this internally, so you do not have to test this any more. In case we require more information I will post on here.

Geez added a comment.Oct 20 2015, 12:40 PM

The issue has been confirmed and scheduled for a fix.