Not quite making it

drnlm on 2011/04/10 00:13 of skaapsteker

The uploaded version of the game has a a fair portion of the game playable, be we alas ran out of time before hooking up the final few bits. By poking at the debugging flags [1],  it's possible to see most stuff, but the game can't be completed.

The outstanding items will not actually take us long to add [2], but we are currently too wasted to do that now. We also have a bunch of packaging issues to sort out as well, which we will look at after sleeping.

We'll probably fix the outstanding issue tomorrow as well, since we are so close to having something completely playable and post a link to the completed version here for anyone interested.


[1] enabling DEBUG in constants.py and running with --all-tails (and maybe some other things)

[2] Estimates vary from 30 minutes to 2 hours, depending on how awake we are.

(log in to comment)

Comments

mauve on 2011/04/10 02:44:

I get this on getting back to the man once I have the fan.
 
Traceback (most recent call last):
  File "scripts/skaapsteker", line 9, in <module>
    skaapsteker.__main__.main()
  File "skaapsteker/__main__.py", line 72, in main
    engine.run()
  File "skaapsteker/engine.py", line 51, in run
    self._current_scene.dispatch(ev)
  File "skaapsteker/levelscene.py", line 368, in dispatch
    self._open_dialogue(ev.npc)
  File "skaapsteker/levelscene.py", line 156, in _open_dialogue
    self._close_dialogue()
TypeError: _close_dialogue() takes exactly 2 arguments (1 given)

mariofrog on 2011/04/10 05:00:

You're missing a run_game.py, although I didn't try the setup tools. I like the tea ceremony :)
 

stefanor on 2011/04/10 09:06:

Mauve: that bug got fixed in the commit after cutoff. Pass npc to _close_dialogue()
 
Aah, run_game.py got left out the tarball. We'll do better packaging later today.

scripts/skaapsteker will run the game / python -m skaapsteker / whatever you want really (this new skellington does way too much)