(off topic) if you are taking a break - (play game)

unhandled

#1

I have noticed (only once) the game freezing, but can’t seem to replicate it.

If you don’t mind and feel like playing a little (and get super stressed :stuck_out_tongue: ) and let me know if you encounter the freeze bug and where exactly is the moth when the freeze happens.

Game --> MathMoth

Cheers
T

(continuing from previous thread (but the links have changed) previous topic )


(Nathan 'jesterKing' Letwory) #2

Not a freeze bug, but I find it is impossible to answer results that go larger than 9. I.e. answering 46 never succeeds on 23+13.

This is on Firefox Nightly 60.0a1 (2018-02-02) on Mac OS.


#3

Cool game. Somehow made it on the second try, is it only one map tho?


(Nathan 'jesterKing' Letwory) #4

Tried it another time, now it worked. Freeze at:


#5

23+13=36. No ?
Did the game break you :stuck_out_tongue: ? I like it !


#6

There are infinite maps. The background is the same but the maze itself is unique every time.


#7

Hmm, nothing unique at that location. I hate this kind of bug, I know which line of code is throwing it, but the same thing works every other time. It is some wierd combination of events that cause of its input variables to be empty.


#8

If you can do it on the second try, then it is not evil enough.


(Nathan 'jesterKing' Letwory) #9

Oops, typo, yes, 36. I must’ve fumbled with the dollar sign (being on the four behind right-alt) for starting the mathjax rendering $36$ - 36. Always should proofread before hitting Reply (:


#10

Haha, could be. There should be a “pro” difficulty setting :rofl:


#11

Cool, and you only bumped twice !
In your case the game could make the maze more dense giving you less space to react (it was an 8x6, and now it is 9x6), or make the moth move faster sooner. At the same time, given the randomness of the maze, some of them are bound to be easier by lucky chance.


#12

I think the “occasional” freeze bug has been resolved now. You can enjoy uninterrupted frustration :stuck_out_tongue:


#13

Also edited the behavior of the key handling so that the buffer is cleared after a sort time. In the past, with two digit entries, if the first digit was wrong it would stay in the buffer until it became a pair before being rejected and caused some confusion on how to enter a correct answer after that