Loading/Saving

[Muirrum]

Implement a way for the game to be saved via SQLite/JSON, whichever is easier for you. Bonus points for making a way to swap between them (Maybe a SaveProvider base class and then SQLiteSaveProvider/JSONSaveProvider would be best)

[nurettn]

I will give a try with Json, can you assign me to this?

[Muirrum]

@nurettinabaci What's the progress on this?

[nurettn]

I couldn't spare time exactly, you can unassign me if you want

[JessieVela]

I have experience with SQLite but not with JSON. I can give it a try and see if I can do both.

[Muirrum]

Alright! Make sure to define a base SaveProvider class or similar so users can define their own.

[JessieVela]

When you say users, are you meaning the actual players?

[Muirrum]

I'm meaning the people using the library

[JessieVela]

What are the main things that will be saved? Currently, I see Person will be saved and possibly in the future Locations.

[Muirrum]

@JessieVela The Player object should be saved, as well as the state of any Mobiles in the game. That's all I can think of right now.

[JessieVela]

Currently, we are not creating Mobiles? its not implemented yet?

[Muirrum]

I mean, you can define new ones and add them to areas, but nothing displays them yet.

[JessieVela]

Thats what I meant nothing displays them yet. To prevent scope creep im going to only add the player into the database. In the future the save will just need to be expanded to accommodate mobiles added to the game. Also, if its okay I would like to do this in parts. One pull request for SQLite and then another for JSON.

[Muirrum]

That's fine, as long as there's a way to define new ones (base class)