[TheBigFive]

So it is a bad idea to update once changes are made? Hm that is very unfortunate. I wasn't thinking directly about OnPlayerUpdate. Was thinking e.g a person uses /buy and buys a cigarette. When he does that there'll be ran a query updating the database, telling him that he has a cigarette (bad example as I wouldn't save that, but you get it). Or a skin for example. You go to a clothing store and buy a new skin, it gets updated in the database immediately. Or if admin uses /setskin, a query will be ran. If everything that will be stored in the database is being ran immediately once a change like that has been done, then there will never be any rollbacks?


I have a master account system and a character system right now. Two different accounts.
If you have a master account, you can create a character. That character will have a "owner" field in the database including the master accounts unique ID. In other words they are connected in one way. You can only log onto the server using your character account.

However the master account has an admin field in the database, an integer. That shows what admin level you have, but I want the character to be admin ingame as well - if the master account has an admin rank. How should I do that in a best way possible? To retrieve that data, and make the character admin in-game.

if character is owned by a master account with an admin rank = character is admin