A long shot away but persistent save could be made of the character stats.
The character would then be able to be reloaded in a new game session (menu required), but he will start from the same room as a new character.
A small database table could be made, and then serialization and unserialization could take place via MySQL.
INSERT INTO characters WHERE ....
UPDATE characters SET .... WHERE character_name = ........
through a CharacterSavetoDb() or CharacterLoadFromDb() methods.
When you select 'Save' ingame via Shift-S or something, CharacterUpdatetoDb() can be called.
This is a light and raw scenario and it is a bit more complex.
Valid issue?
A long shot away but persistent save could be made of the character stats.
The character would then be able to be reloaded in a new game session (menu required), but he will start from the same room as a new character.
A small database table could be made, and then serialization and unserialization could take place via MySQL.
INSERT INTO characters WHERE .... UPDATE characters SET .... WHERE character_name = ........
through a CharacterSavetoDb() or CharacterLoadFromDb() methods. When you select 'Save' ingame via Shift-S or something, CharacterUpdatetoDb() can be called.
This is a light and raw scenario and it is a bit more complex. Valid issue?