✰ ITopic: Complete List of Rejected Suggestions ✰

stickfiregames

venyanwarrior wrote:
My rejected suggestion was keyframe animation in scratch. Could you please add it to the list?

When was it rejected?

bigpuppy

duckboycool wrote:
Since this is a suggestion, support. I do feel that the sticky could be redone, and that although jvvg does update it, he's not really active enough for it. Also I just want to be on the front page of a stickied topic.

Anyway, grammar mistakes;

(Post 2) 24. Vector Eraser/b]

(Post 4)
when costum switches to costume [ v]::events//costum rather than costume, and it should be a hat.
And that's all I saw so far.

Just so you know I already mentioned those

customhacker

bigpuppy wrote:
duckboycool wrote:
Since this is a suggestion, support. I do feel that the sticky could be redone, and that although jvvg does update it, he's not really active enough for it. Also I just want to be on the front page of a stickied topic.

Anyway, grammar mistakes;

(Post 2) 24. Vector Eraser/b]

(Post 4)
when costum switches to costume [ v]::events//costum rather than costume, and it should be a hat.
And that's all I saw so far.
Just so you know I already mentioned those

Fixed!

stickfiregames

customhacker wrote:

Rejected Blocks

(showing? :: looks)

(Effect Name :: looks)

set color to hexadecimal input [] :: pen

[  v] received? :: events hat

when <> :: events

when costume switches to costume [  v] :: events

Apart from <[ v] received?> (which is a boolean, not a hat), when were any of those rejected? They look like a random selection from the workarounds sticky to me.

customhacker

stickfiregames wrote:
customhacker wrote:
Rejected Blocks
(showing? :: looks)
(Effect Name :: looks)
set color to hexadecimal input [] :: pen
[  v] received? :: events hat
when <> :: events
when costume switches to costume [  v] :: events
Apart from <[ v] received?> (which is a boolean, not a hat), when were any of those rejected? They look like a random selection from the workarounds sticky to me.

Yeah. I'm not sure. Let me remove them then.

WolfCat67

This is a nice reformatting of the current Rejections Sticky. However, if you'd expand more on some of the points and maybe add explanations under the rejected blocks, it would probably give it a much higher chance to replace the current sticky.

customhacker

WolfCat67 wrote:
This is a nice reformatting of the current Rejections Sticky. However, if you'd expand more on some of the points and maybe add explanations under the rejected blocks, it would probably give it a much higher chance to replace the current sticky.

I am working on it. It will take a few days.

WolfCat67

Just saying: www.scratch3d.org is now expired. May want to remove that from the “3D Scratch” description.

customhacker

WolfCat67 wrote:
Just saying: www.scratch3d.org is now expired. May want to remove that from the “3D Scratch” description.

Oh yeah! I remember hearing that. Ill do that in a couple.

JonathanSchaffer

reporting to be stickied

customhacker

Can anyone get me the BBCode for this block? It is taking forever!

duckboycool

all at once{...}::control

[scratchblocks]
all at once{...}::control
[/scratchblocks]

I guessed myself ninja'ing somebody from a mile away.

Last edited by duckboycool (Feb. 13, 2017 02:54:52)

WolfCat67

customhacker wrote:
Can anyone get me the BBCode for this block? It is taking forever!

all at once {
} :: control

[scratchblocks]
all at once {
} :: control
[/scratchblocks]

Here you go.
EDIT: Ninja'd!

Last edited by WolfCat67 (Feb. 13, 2017 03:31:18)

customhacker

WolfCat67 wrote:
customhacker wrote:
Can anyone get me the BBCode for this block? It is taking forever!
all at once {
} :: control
Here you go.
EDIT: Ninja'd!

Code? Thanks!

Last edited by customhacker (Feb. 13, 2017 02:56:37)

duckboycool

I know it's only one block but for the;

when [ v] recieved::events boolean

the description could be;

People have given many explanations on how the block would work. Maybe it would be true while the broadcast was running. Maybe it would be true for a certain time-frame of when a broadcast block is ran. It would be confusing if somebody didn't get what it was doing. Besides, you could just use variables and set them when you run it.

This is a rough copy though, change what you like.

Tymewalk

This looks great, I've asked for it to be stickied.

duckboycool

Again, not a big thing, but I would change “Coming Soon” to “Accepted Suggestions”. Coming soon always makes me think you just haven't put it in here yet.

Also just a BUMP as I feel this really should replace the old one.

Where's an ST member when ya' need 'em?

MathlyCat

I don't think this will replace the current one?

As it's fairly obvious jvvg is still caring for it.
https://scratch.mit.edu/discuss/topic/4789/?page=1

stickfiregames

MathlyCat wrote:
I don't think this will replace the current one?

As it's fairly obvious jvvg is still caring for it.
https://scratch.mit.edu/discuss/topic/4789/?page=1

IMO this one should be stickied, I don't like the other one's attitude of deliberately being incomplete to try and make more people read it. Having a TL;DR section like this one does would be better.

Sigton

What was wrong with the old one? It was still being updated often enough and included all the stuff you needed to know…

Sigton

Discuss Scratch