Welcome, Guest. Please login or register.

Pages: [1]
Print
Author Topic: Game (State) Data  (Read 3007 times)
tZee
Community member

Posts: 190


View Profile Email
« on: June 16, 2009, 09:05:41 AM »

What is the plan for the game data, the state the game is currently in? Right now the PC will be reloaded on a map-change and there is no such thing as game state data.

I think there should be something like the GameState class which contains all the information, about the location of the hero (and his stats etc.) and about the progress in quests. (I also have an idea how to keep track of quest progress.)

What do you think about that?
Logged

maximinus
Community member

Posts: 694



View Profile Email
« Reply #1 on: June 16, 2009, 02:19:17 PM »

The entire game state should be stored in the Engine class, defined in /scripts/Engine.py.
Logged

Science is open-source religion
tZee
Community member

Posts: 190


View Profile Email
« Reply #2 on: June 16, 2009, 03:04:09 PM »

Wouldn't it get too crowded there if we don't abstract it?! It would be easier to serialize as well, if we put it in a separate class.
Logged

maximinus
Community member

Posts: 694



View Profile Email
« Reply #3 on: June 16, 2009, 03:10:23 PM »

Well you can sub class, or hold other classes. For example, we should really have a 'map' class to hold all the current map data, and so on. You're right that the individual class shouldn't be too big.
Logged

Science is open-source religion
Pages: [1]
Print
Jump to: