Discuss Scratch
- Unithlees3
-
Scratcher
1000+ posts
Random costume block
lolalso I believe that this is a duplicatebruh
Last edited by Unithlees3 (May 3, 2021 13:19:20)
- TheTrillion
-
Scratcher
500+ posts
Random costume block
There is a easy workaround:
switch costume to (pick random (1) to (. . .::grey)It is easy to understand for New Scratchers, and you can easily follow the logic of how this workaround works.
Last edited by TheTrillion (Feb. 23, 2022 16:29:21)
- Unithlees3
-
Scratcher
1000+ posts
Random costume block
No support. There is a easy workaround:https://scratch.mit.edu/discuss/topic/510102/?page=1#post-5191807switch costume to (pick random (1) to (amount of costumes in sprite)
Last edited by Unithlees3 (May 3, 2021 16:24:37)
- han614698
-
Scratcher
1000+ posts
Random costume block
removed - why was i being so annoying???
Last edited by han614698 (March 13, 2024 13:07:28)
- Unithlees3
-
Scratcher
1000+ posts
Random costume block
I said It's not a dupebumpStop bumping a dupe. again
- Unithlees3
-
Scratcher
1000+ posts
Random costume block
bump
Sorry, you have to wait 60 seconds between posts.
- PkmnQ
-
Scratcher
1000+ posts
Random costume block
Let's use the handy workaround chart to help us here.

This suggestion suggests a very simple block, and the workaround is simple, as pointed out before:
If the suggestion will be commonly used, then the workaround is not relevant. If it won't, then the workaround is relevant.
I don't see any purpose to this that makes it common enough for the workaround to be irrelevant. Therefore, the workaround is relevant.

This suggestion suggests a very simple block, and the workaround is simple, as pointed out before:
switch costume to (pick random (1) to (costume count :: looks))Now, you may say that this doesn't work because you can't detect the costume count in the script, unless you use the complex “RSWR” block. But in each sprite, the costume count stays constant. Therefore, we can just put the number in without any problem. This means it depends on the usage. Here's how that works:
If the suggestion will be commonly used, then the workaround is not relevant. If it won't, then the workaround is relevant.
I don't see any purpose to this that makes it common enough for the workaround to be irrelevant. Therefore, the workaround is relevant.
- mybearworld
-
Scratcher
1000+ posts
Random costume block
This is workaroundable:
switch costume to (()+())
switch costume to (pick random (1) to (costume [number v]::looks))
Last edited by mybearworld (May 7, 2021 13:44:00)
- PVC1
-
New Scratcher
23 posts
Random costume block
I really want arandom costume :: looksblock
BTW there is no workarounds for this block
An actual workaround
Rejected, this is already a series of blocks and remaking it is useless just to save time. Just make a variable or a custom block and you can get away without building it every time
- PkmnQ
-
Scratcher
1000+ posts
Random costume block
Or using something intended:Wait, WHAT?!switch costume to (()+())
- han614698
-
Scratcher
1000+ posts
Random costume block
removed
Last edited by han614698 (March 13, 2024 13:10:39)
- PGBFLITE6373
-
Scratcher
1000+ posts
Random costume block
bumpPlease bumb after 24 hours or off front pageSorry, you have to wait 60 seconds between posts.
- Steve0Greatness
-
Scratcher
1000+ posts
Random costume block
Rejected, this is already a series of blocks and remaking it is useless just to save time. Just make a variable or a custom block and you can get away without building it every timeas far as I'm aware, this isn't rejected. What I think you mean is “No-Support?”








