Not sure what that could be, but you might as well stop looking at the code from C2's side its just one big json interpreted by the engine.
C2 has a built in debugger, its actually a lot like Firebug, or Chromes.
Eventing also can be a bit hard to get the hang of at first.
You have to remember the events run in order top down every tick.
The capx I made just shows how to deal with the server so that the server doesn't have to send every tick, just when something changes.
Sending back to the server is a different story, its a little more complicated.
Right now your options are to monitor the key presses, and send that when something changes, or monitor the objects x,y, speed, angle, etc and send that data... when something changes. Obviously the former being less exact.
Or another option is to change the the movement, and set up a timer.
Something like on this Boolean start a timer, while the timer is running move until the timer is over, and when it ends reset the Boolean.
And yes the forum time out is a pain.