Closed Measurity closed 2 years ago
Doesnt this run into the issue of there being specific settings for the server that are pointless on the client? wouldnt it be best to separate the client and server data? Yes I can see where keeping them together is nice however it can cause certain issues to crop up in the long run especially when someone wants to put the server files on a separate drive from their client, Say in the event of someone having a specific drive they want their server to be on(Say for speed purposes) but they don't keep their games/programs on that drive.
We can use the same structure for both client and server with just some files/folders missing. This way we can have the same code for both client and server.
Will look into that after #1075
I'll take a look at it. Seems doable :)
Right now files are saved left and right. It would be nice to have them in one "nitrox data" folder.
Both client and server should store files into same directory if both are on the same PC/machine. Location of the profiles is likely best stored in App Data but if not, let me know.
The API is best implemented in the "NitroxModel" project so that it can be used anywhere.
Folder structure should be like
"Nitrox data"
Example API (doesn't need to work like this)