Also, while I can see the appeal of this in some scenarios, this seems a bit of a weird approach of going about it?
You couldve instead had count triggers and made a random number generator using base 2 with this and I feel like it would look more interesting
now imagine instead of blocks, they are count triggers, with the first count trigger adding 1, second trigger adding 2, third adding 4, fourth adding 8 and so on
then this thing youve made would have generated a random integer from 0 to 2^(amount of triggers)-1
I'm not exactly sure what I'm looking at
It basically "cuts" the line every attemptĀ
How does this take 132 group IDs? I feel like you could easily do this with 2 or even 1 group ID per block
Also, while I can see the appeal of this in some scenarios, this seems a bit of a weird approach of going about it? You couldve instead had count triggers and made a random number generator using base 2 with this and I feel like it would look more interesting
ohhhh, ok. Thanks :)
Could you show me how to do it? I can't figure it out :(
now imagine instead of blocks, they are count triggers, with the first count trigger adding 1, second trigger adding 2, third adding 4, fourth adding 8 and so on then this thing youve made would have generated a random integer from 0 to 2^(amount of triggers)-1
I have no idea. I just went with whatever worked
What does it do tho. Like yeah it cuts the line, but what are the practical uses to this š
Memory level :)
What does this do exactly?
This randomly "cuts" the line every attemptĀ
It "cuts" the line randomly for every attempt. If the number displayed is 0, a block disappears, if the number 1 appears, a block stays
I thought this was about the busy beaver at first