Menu

#9 investigating required playerdata

Other
open
None
2023-09-10
2023-09-05
No

What data do we require to keep the data for a specific player.
(localuniqueUserID), (CurrentRiskNickname), (OldRiskNickname default NULL seperated with ", " when multiple renamings occured), (RiskFriendID), CurrentDiscordName), (OldDiscordnames default NULL seperated with ", " when multiple renamings occured), (DiscordID), (Discordservers seperated with ", " if the player is available via multiple servers {this is required for the bot to be able to send a private message}), (Date of being added), (Userspecified password default NULL and if NULL personal page can't be opened, we do need to add some salt at the registrationphase)

Am i missing any data we might need to identify a user, I personally don't want to include name / email other contactinfo since if we ever could get a databreach we don't want to have anything of use outside of this tournamentsetting registered for players.

Discussion

  • Johan-Retry-Games

    CREATE TABLE riscordbot.userdata (UserID INT NOT NULL AUTO_INCREMENT , CurrentRiskName TEXT NOT NULL , PreviousRiskNames TEXT NULL DEFAULT NULL , RiskFriendID VARCHAR NOT NULL , CurrentDiscordName TEXT NOT NULL , PreviousDiscordNames TEXT NULL DEFAULT NULL , DiscordUserID INT NOT NULL , DiscordServers TEXT NOT NULL , UserPassword VARCHAR NOT NULL , RegisterDate DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP , UNIQUE UniqueUserID (UserID)) ENGINE = InnoDB;

     
  • Johan-Retry-Games

    So while chatting, there should be a databasestructure linking userIDs in groups
    family
    irl friends
    people that play often

     

Log in to post a comment.

MongoDB Logo MongoDB