Hello!
Currently my server is using yaml to store and read all the information of player, so there are many yaml read and write stuff pretty frequently..
I would like to (maybe) change that as yaml isn't the best solution to store data. First of all - I'm not going to store it just in variables, because they are hard to edit (with yaml I can just edit file..), can be corrupted etc. So I've came up with some ideas:
1. Still use yaml, but on player join write required data in varibles for future use (don't need to check files on every command operation..)
2. To use mysql database to store data, I could edit it at any time, on every operation server/script would check required data in the database
3. Use mysql, but on every player join write data from database to variables for future use.
Maybe there would be some other ways, I need the best for both efficiency (less server resource usage) and usage (possible to easely edit if needed).
Currently my server is using yaml to store and read all the information of player, so there are many yaml read and write stuff pretty frequently..
I would like to (maybe) change that as yaml isn't the best solution to store data. First of all - I'm not going to store it just in variables, because they are hard to edit (with yaml I can just edit file..), can be corrupted etc. So I've came up with some ideas:
1. Still use yaml, but on player join write required data in varibles for future use (don't need to check files on every command operation..)
2. To use mysql database to store data, I could edit it at any time, on every operation server/script would check required data in the database
3. Use mysql, but on every player join write data from database to variables for future use.
Maybe there would be some other ways, I need the best for both efficiency (less server resource usage) and usage (possible to easely edit if needed).