This block would make a lot of things easier...

stickfire-test

childgamer wrote:
stickfiregames wrote:
childgamer wrote:
stickfiregames wrote:
So you want to be able to make this?
<(costume #) = <<[1]::operators> or <[2]::operators>>>
No support because it's not possible - what would the value of
<<[1]::operators> or <[2]::operators>>
be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier
<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>
above shows that the value is simultaneously 1, 2, and 4 all at the same time.

Oh, I just caught that it's a boolean script. Perhaps we should make a
<() or ()>
Block to solve that problem
That still wouldn't work because the value of a reporter can't simultaneously be two different things.
It would still work, because the knowledge in question is either 1 or 2 would work.
when green flag clicked
forever
    
if <(some random varible) = [<<[1]::operators> or <[2]::operators>>]> then
do some random stuff

end

end

It wouldn't work. A reporter can only return one value, and its value can't change depending on context.

The only way it would work is if they added a whole new type of reporter for lists. But even then, the check would look something like this:

<([1] [2] ◄► :: list) contains (costume #)>

ShinySkarmory227

childgamer wrote:
Iditaroid wrote:
childgamer wrote:
Iditaroid wrote:
childgamer wrote:
stickfiregames wrote:
childgamer wrote:
stickfiregames wrote:
So you want to be able to make this?
<(costume #) = <<[1]::operators> or <[2]::operators>>>
No support because it's not possible - what would the value of
<<[1]::operators> or <[2]::operators>>
be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier
<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>
above shows that the value is simultaneously 1, 2, and 4 all at the same time.

Oh, I just caught that it's a boolean script. Perhaps we should make a
<() or ()>
Block to solve that problem
That still wouldn't work because the value of a reporter can't simultaneously be two different things.
It would still work, because the knowledge in question is either 1 or 2 would work.
when green flag clicked
forever
    
if <(some random varible) = [<<[1]::operators> or <<[2]::operators> >> ]> then
do some random stuff
end
end
What happens if you try to do this?
say <(1) or (2)>
the sprite has a choice of 1 or 2 to say. Here, I'd say that you are just as well off with
say (pick random (1) to (2))
I feel like this block's function is a bit ambiguous then! Still no support!
Sure, it's not best for everything, but it's a lot simpler this:
 ((variable) = ([1] or [2]::operators))
than this:
<<(variable) = [1]> or <(variable) = [2]>>

That's what I was going for!

Please tell me why I like this Chara-cter?
CLick the image to go to the creator's deviantart.

ealgase

No support, too complex.

ST should get the top ten users from Advanced Topics to code Scratch 3 instead of the project they created.

Cyoce

No support. If I understand correctly, the proposed block converts a string to a boolean, so it can be put into an if-statement. This would be the only type-conversion block in Scratch, because Scratch automatically converts data types! It would be much easier to simply allow boolean slots to take strings.

The ability to compose a function of more complex functions does not invalidate the usefulness of said function. | Test how well your computer runs Scratch! | The platypus lives.

ChildCritic

Iditaroid wrote:
childgamer wrote:
Iditaroid wrote:
childgamer wrote:
stickfiregames wrote:
childgamer wrote:
stickfiregames wrote:
So you want to be able to make this?
<(costume #) = <<[1]::operators> or <[2]::operators>>>
No support because it's not possible - what would the value of
<<[1]::operators> or <[2]::operators>>
be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier
<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>
above shows that the value is simultaneously 1, 2, and 4 all at the same time.

Oh, I just caught that it's a boolean script. Perhaps we should make a
<() or ()>
Block to solve that problem
That still wouldn't work because the value of a reporter can't simultaneously be two different things.
It would still work, because the knowledge in question is either 1 or 2 would work.
when green flag clicked
forever
    
if <(some random varible) = [<<[1]::operators> or <<[2]::operators> >> ]> then
do some random stuff
end
end
What happens if you try to do this?
say <(1) or (2)>
the sprite has a choice of 1 or 2 to say. Here, I'd say that you are just as well off with
say (pick random (1) to (2))
I feel like this block's function is a bit ambiguous then! Still no support!

what if you wanted

say <(1) or (3)>

*I don't think this is a necropost. I'm bringing a new point to the discussion.*
Just cause:
*I was curious to see what 3sal2's 250th post was,and it came to this, where I always wanted to come back on.*
*skipping 2 accounts in this discussion*

Wings.io!!! Challenge. Contest! How much like me are you? Fall damage Collab Songtrack Crush damage experiment My 100th post! My 250th post! My 500th post!
kumquat poison. Don't try to eat this signature.

wizard192

No support, it doesn't seem very useful

Could this link have anything to do with Jaffa Cakes? | Save the pancake

Iditaroid

ChildCritic wrote:
Iditaroid wrote:
childgamer wrote:
Iditaroid wrote:
childgamer wrote:
stickfiregames wrote:
childgamer wrote:
stickfiregames wrote:
So you want to be able to make this?
<(costume #) = <<[1]::operators> or <[2]::operators>>>
No support because it's not possible - what would the value of
<<[1]::operators> or <[2]::operators>>
be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier
<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>
above shows that the value is simultaneously 1, 2, and 4 all at the same time.

Oh, I just caught that it's a boolean script. Perhaps we should make a
<() or ()>
Block to solve that problem
That still wouldn't work because the value of a reporter can't simultaneously be two different things.
It would still work, because the knowledge in question is either 1 or 2 would work.
when green flag clicked
forever
    
if <(some random varible) = [<<[1]::operators> or <<[2]::operators> >> ]> then
do some random stuff
end
end
What happens if you try to do this?
say <(1) or (2)>
the sprite has a choice of 1 or 2 to say. Here, I'd say that you are just as well off with
say (pick random (1) to (2))
I feel like this block's function is a bit ambiguous then! Still no support!
what if you wanted
say <(1) or (3)>
*I don't think this is a necropost. I'm bringing a new point to the discussion.*
Just cause:
*I was curious to see what 3sal2's 250th post was,and it came to this, where I always wanted to come back on.*
*skipping 2 accounts in this discussion*

I don't know what your point is. Can you explain some more?

ChildCritic

Iditaroid wrote:
ChildCritic wrote:
Iditaroid wrote:
childgamer wrote:
Iditaroid wrote:
childgamer wrote:
stickfiregames wrote:
childgamer wrote:
stickfiregames wrote:
So you want to be able to make this?
<(costume #) = <<[1]::operators> or <[2]::operators>>>
No support because it's not possible - what would the value of
<<[1]::operators> or <[2]::operators>>
be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier
<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>
above shows that the value is simultaneously 1, 2, and 4 all at the same time.

Oh, I just caught that it's a boolean script. Perhaps we should make a
<() or ()>
Block to solve that problem
That still wouldn't work because the value of a reporter can't simultaneously be two different things.
It would still work, because the knowledge in question is either 1 or 2 would work.
when green flag clicked
forever
    
if <(some random varible) = [<<[1]::operators> or <<[2]::operators> >> ]> then
do some random stuff
end
end
What happens if you try to do this?
say <(1) or (2)>
the sprite has a choice of 1 or 2 to say. Here, I'd say that you are just as well off with
say (pick random (1) to (2))
I feel like this block's function is a bit ambiguous then! Still no support!
what if you wanted
say <(1) or (3)>
*I don't think this is a necropost. I'm bringing a new point to the discussion.*
Just cause:
*I was curious to see what 3sal2's 250th post was,and it came to this, where I always wanted to come back on.*
*skipping 2 accounts in this discussion*
I don't know what your point is. Can you explain some more?

my point is, this block would make many things easier. I know of the workarounds, and that it's simple, but it is also used a lot. Read the rest of the chain.

Wings.io!!! Challenge. Contest! How much like me are you? Fall damage Collab Songtrack Crush damage experiment My 100th post! My 250th post! My 500th post!
kumquat poison. Don't try to eat this signature.

Iditaroid

ChildCritic wrote:
Iditaroid wrote:
ChildCritic wrote:
Iditaroid wrote:
childgamer wrote:
Iditaroid wrote:
childgamer wrote:
stickfiregames wrote:
childgamer wrote:
stickfiregames wrote:
So you want to be able to make this?
<(costume #) = <<[1]::operators> or <[2]::operators>>>
No support because it's not possible - what would the value of
<<[1]::operators> or <[2]::operators>>
be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier
<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>
above shows that the value is simultaneously 1, 2, and 4 all at the same time.

Oh, I just caught that it's a boolean script. Perhaps we should make a
<() or ()>
Block to solve that problem
That still wouldn't work because the value of a reporter can't simultaneously be two different things.
It would still work, because the knowledge in question is either 1 or 2 would work.
when green flag clicked
forever
    
if <(some random varible) = [<<[1]::operators> or <<[2]::operators> >> ]> then
do some random stuff
end
end
What happens if you try to do this?
say <(1) or (2)>
the sprite has a choice of 1 or 2 to say. Here, I'd say that you are just as well off with
say (pick random (1) to (2))
I feel like this block's function is a bit ambiguous then! Still no support!
what if you wanted
say <(1) or (3)>
*I don't think this is a necropost. I'm bringing a new point to the discussion.*
Just cause:
*I was curious to see what 3sal2's 250th post was,and it came to this, where I always wanted to come back on.*
*skipping 2 accounts in this discussion*
I don't know what your point is. Can you explain some more?
my point is, this block would make many things easier. I know of the workarounds, and that it's simple, but it is also used a lot. Read the rest of the chain.

I wrote part of this chain! This block does different things in different situations, which complicates things unnecessarily and doesn't make any sense, and Stickfiregames's point that reporters should only give out a single value stands as well.

-Cherri-

The block doesn't make sense, the way you used it.. and no support, easy workarounds.

Hiii! :3

I'm the one and only cherbear who loves helping newbies!

navysmeagol_175

No ,suport

Cream_E_Cookie

Can someone explain what this does? For now, no support because if I'm confused, New Scratchers would too.

liam48D

I see what you mean and I can see it being useful but it would break the fundamentals of programming, so no support.

202e-202e-202e-202e-202e UNI-CODE~~~~~

PH-zero

I see what you want to achieve

Is this what you are looking for?

<(costume #) equals any of  (myVar) [3] [] (-::operators)(+::operators) ::operators>

———-

A value that equals more than one other value is a very interesting concept,
and i already used it in C++ (it's called bit-flgs there, and is even more flexible and complex)
However, for scratch, it would be too complicated. So no support for the original post.

Scratch on

Ever wanted to rotate the stage? Or to

go to x:() y:() z:() ::custom

Click me!

miniepicness

I think this is getting a little off-topic

—————————–
-Click here to go to my profile —-Invited to scratch by AmazingProgrammer123
-Some Old Games: Racing Cats,Hungry Cat, Trapped, Mini-nation, ᴍAdvεnturᴇ﹗ and more!
- My“Any-Game”studio- All of My Projects/Games -My first project -my 200th project - handimation old shop:ACM-PICSHOP
click here for all my posts search the forums my first post :) my first thread/topic | click here
this signature is old⁽¹⁾

uV3b51yWZStHBjA8Lw7k

miniepicness

miniepicness wrote:
I think this is getting a little off-topic

Oops, accidentally necroposted, sorry, also, I think you can already type in those boxes like:

<<Example> or <Example >>

So, i dont think this would be needed.

—————————–
-Click here to go to my profile —-Invited to scratch by AmazingProgrammer123
-Some Old Games: Racing Cats,Hungry Cat, Trapped, Mini-nation, ᴍAdvεnturᴇ﹗ and more!
- My“Any-Game”studio- All of My Projects/Games -My first project -my 200th project - handimation old shop:ACM-PICSHOP
click here for all my posts search the forums my first post :) my first thread/topic | click here
this signature is old⁽¹⁾

uV3b51yWZStHBjA8Lw7k

Sheep_maker

Apologies for not reading all the posts
Coding is not literal English; the if block won't be checking if the costume number is 1 or 2, even with this block. It always be false, no matter what, in this scenario.

- Sheep_maker This is a kumquat-free signature. :P
This is my signature. It appears below all my posts. Discuss it on my profile, not the forums. Here's how to make your own.
.postsignature { overflow: auto; } .scratchblocks { overflow-x: auto; overflow-y: hidden; }

EDawg2011

What would the block report? There's no condition.

Please note that I may sometimes make a mistake and give wrong information.

Can you please put this at/near the top of your signature and tell people that tag spam isn't allowed and it manipulates the algorithm, to start a chain and spread the word? - Thanks, @EDawg2011.

But then I had a very good idea. I used F5. See, using F5 gave me a whole new perspective and I was able to see a chest I couldn't have seen before.

(Highlight text + down arrow + shift to see the rest of my signature.)

Help find out who ate @cheddargirl's signature! l JOIN WORLD DOMINATION INC. TODAY! l Donate your soul! l me when i accidentally spread misinformation l Platformer Skibidi

<0-0::sensing>//This is Charles; he protects my signature from evil kumquats.
when I'm spawned::events hat//This is the code Charles' brain runs on.
forever
if <[100] > (distance to [an evil kumquat v])> then
delete the evil kumquat::control
end
end

Be moist.

usefun

Support, there are many times where I had to write extra code because that wasn't a block.

Last edited by usefun (Jan. 11, 2024 04:27:36)

Alt: @usefun2
My profile
Sinistar (My best game)
See your exact post count here.

unfortunately this signature has been corrupted by an evil cat blockCAT BLOCKS WILL RULE

among_us1w2

usefun wrote:
Support, there are many times where I had to write extra code because that wasn't a block.

easy workaround bro

scratchers on the forums from 10-500 posts have at most, a 7 short sentence span for replies. if you cant keep your posts in this range, then dont act suprised when someone asks for simplified version
bag randomizer for good games
experience the true chicken nuggies theft simulator : gobo | story
(Removed by Moderator - People with a TV head for a profile picture cannot discuss about the heart and soul of art) /j

OwO :: #44bd8d
^-^ :: #44bd8d

Discuss Scratch