| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
anymore; optional support for hy
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
renamed InputHandler to CommandHandler.
made InputHandler for input code that used to be in gameclient
also started my own getstr() replacement.
|
|
|
|
|
|
|
|
|
|
|
|
keybindings are now a JSON format.
Somehow hy errored for me, and the cleanest solution seemed not to use hy at all
Thinking about it, the client was basically loading a new interpreter to optimize something that didn't need optimizing.
It didn't make it more readable/writable either, and it always was a lot of hassle.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
directional attacks back
|
|
|
|
|
|
This theoretically also changes the meaning of the code from running
the callback always, to only running the callback when there wasn't an
error, which is what I'm assuming was meant, but in pratical terms,
attempting to use `data` in the case of an error would have raised a
`NameError` anyway.
`else` on a try block will only run if nothing was raised.
|
|
Both work, but the identity check is the more correct/idiomatic
approach (and also ever-so-slightly more efficient).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
