Includes a lightbar/hotkey message area selector.

getMessageThreads(sub)
(See comments.)

clean up leftover text when moving tree, clear remaining lines when tree doesnt fill frame. draw +/- characters for subtree expansion. add pageUp(), pageDown() methods, make home() and end() work relative to the top-level.
various other shite.

timestamps the supplied message in logs, relative to last function call

add frame.invalidate() method,
which destroys the screen buffer "memory"
redraws on next cycle() or draw()
fix frame.clear(), cleartoeol(), clearline() methods to affect
entire data array instead of just what is visible

remove frame.refresh() call from tree.addItem()
use frame.setData() to display menu (faster)

active_clients (protected integer) could be 0 at the time of recycle because
there can be delay at the beginning of the FTP ctrl thread (e.g. looking up
filtered IPs/hostnames) before the active_clients is incremented which could
be during/after it was destroyed by the cleanup() function. Now tracking
number of threads using protected integer which increments immediately upon
child thread creation and is not destroyed until the main thread terminates.
There is currently *not* timeout while waiting for child threads to terminate
upon shutdown/recycle, so this could result in a hung server thread if a child
thread is indefinitely hung - consider using a timeout.

Some updates to comments and example code.

Support for a "movement" key in sprite.ini, possible values are currently "rotating" (default) or "directional".
Replaces prior mechanism for direct directional movement, which was only good for platformers.

Sprite.moveTo(x, y)
Sprite.turnTo(bearing)
Improved Sprite.checkOverlap(margin), although it still needs work.

also try to avoid dividing by zero :|

this prevents the "big ridiculous island" that occurs when a map is processed a lot (1000's of times)

(perhaps digitalman might rename this file to terraingenerator.js)

log send errors.
remove deuce's testes.

...no really... I swear it's almost done!

(this only affects people who might be running a synchronetris server)

everything seems to be working now.