Is there a reason Input.update is called after update()?

[Draknek]

I was expecting this to be the other way round... Might be adding a frame of input lag?

Can't immediately think of any problems that would be caused by switching them around.

[danishgoel]

I have looked through that part of code, and agree that this is causing one frame of input lag.

I tried moving both occurrences of Input.update() above if (!paused) update() in Engine.as and that broke input handling for me. The first key/mouse press was registered, but nothing after that. I did not debug further.