Replies: 1 comment 7 replies
-
I think that we could do the following:
One important thing, I think that UDID should ONLY be used for the initial connection step, after that further communication with the client is done using the client short playerID. That will help prevent hackers from copying another players UDID. |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
So we're getting to the point at which we're thinking about potentially storing players' previous positions etc when they connect, and when the host saves.
This means we will need to find a way to persist/differentiate the different clients as they connect and disconnect.
There are several options/approaches we can take:
Plus other options such as running our own auth service, but that has all the same pros and cons as steam auth, apart from we can issue new IDs whenever, but them we become data controllers under GDPR (not fun) and have to run our own infra (also not fun).
Suggestions welcome.
Beta Was this translation helpful? Give feedback.
All reactions