16.01.2015, 13:45
If you're certain every query works, you can skip saving everything again during OnPlayerDisconnect.
Whenever a variable changes, like money, save it in the database with a small query, preferably inside a small function that updates the money on the server, as well as sending a small query to change the money value in the database (like I showed previously using Player_Reward in the other thread).
If you have such a system for everything, you don't need another huge query to save everything when a player logs out, as all data has been saved already when he was playing the game.
Because after the last save, data didn't change anymore, so no reason to save it again.
Whenever I add a new query to my script, I run the server, open Navicat and display the data in my tables.
When I run the game and I edit the value of that new variable (say jailtime), I put myself in jail and check the database, when the game is still running.
If it updates everytime, it works and you can skip saving that when you logout as it has been updated properly.
Whenever a variable changes, like money, save it in the database with a small query, preferably inside a small function that updates the money on the server, as well as sending a small query to change the money value in the database (like I showed previously using Player_Reward in the other thread).
If you have such a system for everything, you don't need another huge query to save everything when a player logs out, as all data has been saved already when he was playing the game.
Because after the last save, data didn't change anymore, so no reason to save it again.
Whenever I add a new query to my script, I run the server, open Navicat and display the data in my tables.
When I run the game and I edit the value of that new variable (say jailtime), I put myself in jail and check the database, when the game is still running.
If it updates everytime, it works and you can skip saving that when you logout as it has been updated properly.