Just a heads up, in un updated player versions, wait seconds still registers as milliseconds even though it may say wait seconds
For me it still says wait milliseconds :p
While it may say that, it’s still counting in milliseconds until you update the draft
That’s why I don’t like wait seconds or sound wait seconds. Using decimals for that kind of thing in code is very unprofessional. Like, take the webplayer for example. It’s much easier to code that kind of stuff when waiting by milliseconds
Pretty much all major languages use it.
However, that’s really just my preference. I can understand how seconds is easier for a newcomer to grasp.
It might be cool to have separate blocks for milliseconds and seconds. I miss milliseconds a lot
Same here.
And coding music with seconds is so so so much harder with seconds
That’s why start sound ms is now part of secret blocks!
I can add those to any project you’d like, and if you want me to add like 200 of those because tapping the block is tedious, no problem!
Yeah i confused I edited the post
I agree, I prefer wait milliseconds so ima just hold off on updating the app till I finish a few projects
I swear every project I make gets stuck in the filter no matter what I do
@ me on the filter topic
This is what we’ll make with it
Hey awesomeonion, may we have a bit of a faster running webplayer? It lags a lot currently and gets really infuriating
Thanks in advance!
Best regards - Rodrik834
Yeah, I would appreciate it if they did that.
Great idea–we’re doing it. Look for it in the next update!
Hi,
Can you explain more what you mean by lag? We do want to make it faster and it helps a lot if we can understand what actions in particular feel slow.
I think hopscotch webplayer is able to support bigger amounts of clones, if it’s worked to do so, because I know you guys have an extreme potential
Having lots of conditionals and creating clones that so them is an example