gdfsgdfsgdfg wrote:

or

broadcast [☁️ message v]
broadcast [☁️ message v] and wait

when I receive [☁️ message v]

broadcast and wait might be problematic, as what if someone closes the project or “pauses” the project by going to another tab? it doesn't STOP the script which means it wouldn't go “the script ended so I dont have to wait”, but it would never finish the script, hence being capable of breaking projects.

cookieclickerer33 wrote:

snip-
Cloud broadcasts should definitely have a ton less limitations because they can’t be custom set to a value I don’t see a reason not to allow you to have a ton of them. Because broadcasts are just a binary value it’s only 1 extra byte for each broadcast so we could at least have up to 256

As other have mentioned above you would only be able to broadcast any cloud broadcast once every 1/10th of a second like with cloud variables
But unlike them it apllies to every cloud broadcast so you can’t broadcast 1 and then broadcast another within 1/10th of a second

Isn't a binary value a bit rather then a byte or something? (idk tbh)
also that would allow the sending of 10 letters per second, I was gonna say itd be harder to monitor this incase someone abuses it but then again cloud chats so yea

Woah
坤坤 of the page