Bug Thread
This thread is for bugs caught while playing the games
I am LagomorphWhen I attempt to sell what is in slot 1 the money total moves to the left of the dollar sign and I get the following in the console.
Traceback (most recent call last):
File "C:\Documents and Settings\zerobyte\Desktop\media.pyweek.org\dl\PyWeek8\Y
ukkuri\IAmLagomorph-1\layer\command.py", line 230, in run
res = context.run(cmdstring, vars=vars, active=active)
File "C:\Documents and Settings\zerobyte\Desktop\media.pyweek.org\dl\PyWeek8\Y
ukkuri\IAmLagomorph-1\layer\command.py", line 211, in run
res = command.run(args)
File "C:\Documents and Settings\zerobyte\Desktop\media.pyweek.org\dl\PyWeek8\Y
ukkuri\IAmLagomorph-1\layer\command.py", line 105, in run
try: return self.func(*args)
File "C:\Documents and Settings\zerobyte\Desktop\media.pyweek.org\dl\PyWeek8\Y
ukkuri\IAmLagomorph-1\lagomorph\__init__.py", line 241, in dialogue_advance
if not d.advance(choice) and d == self._dialogue:
File "C:\Documents and Settings\zerobyte\Desktop\media.pyweek.org\dl\PyWeek8\Y
ukkuri\IAmLagomorph-1\lagomorph\dialogue.py", line 170, in advance
try: exec self.choices[int(choice)][1]
File "", line 3, in
File "C:\Documents and Settings\zerobyte\Desktop\media.pyweek.org\dl\PyWeek8\Y
ukkuri\IAmLagomorph-1\lagomorph\__init__.py", line 548, in _set_money
self._moneylabel.number = self._money = n
File "C:\Documents and Settings\zerobyte\Desktop\media.pyweek.org\dl\PyWeek8\Y
ukkuri\IAmLagomorph-1\lagomorph\__init__.py", line 486, in _set_number
self._update()
File "C:\Documents and Settings\zerobyte\Desktop\media.pyweek.org\dl\PyWeek8\Y
ukkuri\IAmLagomorph-1\lagomorph\__init__.py", line 476, in _update
spr = Sprite(image=self._symbols[digit].image,
KeyError: '.'
(log in to comment)
Comments
I have no idea why pymike would say that. This is a bug in our bitmap font rendering / money-giving code.
Maybe because I kept getting that error till I upgraded from 1.1.1 to 1.1.3? ^_^
No wait, that was a different bug. However your game does require 1.1.3 to run, if I recall correctly.
kent_turbo on
2009/05/07 12:06:
pymike said this happens because of pyglet being older than 1.1.3, but I havn't tested it yet.