Skip to content
Discussion options

You must be logged in to vote

I've just fixed it - so the latest 'cutting edge' build (or 2v30 when it's released) will be working again.

Sorry for the inconvenience - the changes on timers were pretty large but they made things much more efficient and also enabled some pretty neat new functionality (the require("timer") library and the ability to set JS code to run on a timer and actually interrupt other JS code)

Replies: 3 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@gfwilliams
Comment options

Answer selected by Serpen
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants