This repository has been archived by the owner on Dec 7, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 47
Database should be toggleable #219
Labels
Comments
I am aware of the weaknesses of the "database." I am looking at possibly having settings/snowflake/other stats stored remotely and acquired when a player logs in. |
@twizmwazin like remote DB? |
@RubeGamerV perhaps |
Is this being worked on? |
@intenseoxygen more like the other way arround, database is now needed for ranks to work (in cardinal 1.9), moved all the data for who has what ranks to there, instead of the config-based saving that we had before |
@Pablete1234 nice keep it up |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The Database provided should really be off by default, and toggleable. That or other database options should be provided, by using an interface with many subclasses for different Database types. Storing player data in flat file will grow over time, and if the server is used a lot, it has the chance that the server may be slowed down by storing the large database document in RAM.
I can see that it is used for settings, and snowflakes, which personally I believe would be best stored in YAML, or in an actual Database, such as MongoDB or MySQL. Although ideally, for scrimmages, it should be off completely, unless of course you provide an open database for all Cardinal servers to use.
The text was updated successfully, but these errors were encountered: