Approaching Completion

[Noodels]

Now that the structure has taken shape and we are now ironing out the kinks, we need to get the world into a workable shape. We need to work out the final part of World.init that will be written to successfully initiate the world, and aquire an initial database to work with. Off the top of my head I can think of the following things, but everyone needs to confirm that this is correct or whether there needs to be any ammendments to account for anything else that needs loading.

World (starts empty) -> gets settings from metafile -> opens the database -> loads objects into the world -> ensure locations are set correctly -> perform exit destination IDs to pointers conversion

[MattWindsor91]

Seems ok. Will there be a separate flow for initialising a database from YAML? Does the database YAML go in a separate file or in the metafile?

[Noodels]

To load the database from yaml we have a seperate tool. Essentially, when the game runs, we must guarantee that there is a working database. So the dbgen.py file you wrote which is in test should work, and possibly be moved to the root directory.

[DinCahill]

What do I know, I'm just the metafile man!

[Noodels]

Very well, I will add those steps to the World.init function.

[Noodels]

I already realised I missed out removal of puppets from the world. Not a good start.

[Noodels]

Okay, I've written it all in, I need Matt to go into World.init and define the cursor value, which is an iterator that will return the ID of every object in the database. If need be, change appearances of "i" to "i[0]".

[Noodels]

Update: As I understand, Matt's doing some shuffling around somewhere in the world retrieval routine and elsewhere to load the whole database serially without need for the whole FOR id IN database GET id, values AND DO ... END cycle, and it'll be replaced with a FOR id, values IN database DO ... END cycle.