Make demo's data structure similar to the eventual database
Closed this issue · 5 comments
Currently, the demo runs beautifully, especially the beds. Those are awesome. However, on the inside, the random generation code creates a structure that isn't very much like what I think the database will look like later, and this could make the transition very difficult. I also think it makes adding new items to the temp data structure harder. For these reasons, we should probably switch soon to a single array of items which are themselves perhaps arrays or dictionaries of attributes.
Agreed. Please be sure to commit and push often so the versions of the file we're working on aren't vastly different game demos. :)
I made a commit which begins the process of making things more generic, and merged it with your player-targeted actions commit. It also looks like some code for working with the database was added?
I think we have some unignored compiled code in the repository now, I'm seeing pyc files that changed when I ran the program to test the merge. We should probably get that out of there.
So it seems the current room_demo.py has some discontinuity. Should we not touch it/care? Since there's a chance to abandon || require drastic changes?
Love what you did with the code, by the way.
We're pretty much there already. We'll continue to tweak it, though.