Discuss Scratch
- Discussion Forums
- » Suggestions
- » PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
![[RSS Feed]](//cdn.scratch.mit.edu/scratchr2/static/__5b3e40ec58a840b41702360e9891321b__//djangobb_forum/img/feed-icon-small.png "[RSS Feed]")
![[RSS Feed]](http://cdn.scratch.mit.edu/scratchr2/static/__5b3e40ec58a840b41702360e9891321b__//djangobb_forum/img/feed-icon-small.png "[RSS Feed]"){kind=icon}
- hahasamian
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
So, I have another block idea, this time it should hopefully be much simpler to make.
So, I'm working on a new type of engine, one that uses colors at heart but masks over a display that adds more quality to the game.
Well, the way I tried it didn't work, but I figured out an alternative if we just have one new block.
Here it is:
Please add! I hope it won't be too complicated to make.
Please support if you want this to happen!
So, I'm working on a new type of engine, one that uses colors at heart but masks over a display that adds more quality to the game.
Well, the way I tried it didn't work, but I figured out an alternative if we just have one new block.
Here it is:
<touching color [#00ff00] of [ v] ?>This allows the object to see whether it is touching a certain color of an object.
Please add! I hope it won't be too complicated to make.
Please support if you want this to happen!
- mrbobbygreathead
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
P
Support.<touching color [#00ff00] of [ v] ?>
- 1004587
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
No support; easy workaround,
<<touching [sprite v] ?> and <<touching color [#ff0088] ?> >>
- alexphan
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?
Last edited by alexphan (Feb. 5, 2016 22:42:18)
- 1004587
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?
<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >>
- hahasamian
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >>
- 1004587
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
Still no support. I have a feeling it will not be needed often.That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >>
- hahasamian
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
If you have a engine like mine it would. My engine is very clever, just had one problem.Still no support. I have a feeling it will not be needed often.That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >>
The ST doesn't need to do it now: this game won't come out for awhile.
- Zekrom01
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >>
<<touching color [#ff0088] ?> and <touching [sprite v] ?> >IS a valid workaround.
No support.
- hahasamian
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
No, it's not. I don't think you understand what I'm trying to do here! If you have two objects, one displaying, say, something green, and the real sensing object displaying, say, red, then this would glitch:That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >><<touching color [#ff0088] ?> and <touching [sprite v] ?> >IS a valid workaround.
No support.
when green flag clickedThat would TOTALLY glitch. IT'S NOT A WORKAROUND!
forever
if <<touching color [#00ff00] ?> and <touching [sense v] ?> > then
Program something that goes here!
end
if <<touching color [#ff0000] ?> and <touching [sense v] ?> > then
Program something here!
end
- Sheep_tester
-
Scratcher
500+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
No, if the sprite was touching the target sprite but it wasn't touching the targeted color on the sprite (and the targeted color was on the stage or another sprite), your workaround wouldn't work.That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >><<touching color [#ff0088] ?> and <touching [sprite v] ?> >IS a valid workaround.
No support.
- 1004587
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
No, it's not. I don't think you understand what I'm trying to do here! If you have two objects, one displaying, say, something green, and the real sensing object displaying, say, red, then this would glitch:That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >><<touching color [#ff0088] ?> and <touching [sprite v] ?> >IS a valid workaround.
No support.when green flag clickedThat would TOTALLY glitch. IT'S NOT A WORKAROUND!
forever
if <<touching color [#00ff00] ?> and <touching [sense v] ?> > then
Program something that goes here!
end
if <<touching color [#ff0000] ?> and <touching [sense v] ?> > then
Program something here!
end
<<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and <<not <touching color [#00ff00] ?>>>>>>You were saying?
Last edited by 1004587 (Feb. 5, 2016 23:58:15)
- 1004587
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
No, if the sprite was touching the target sprite but it wasn't touching the targeted color on the sprite (and the targeted color was on the stage or another sprite), your workaround wouldn't work.That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >><<touching color [#ff0088] ?> and <touching [sprite v] ?> >IS a valid workaround.
No support.
<<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and <<not <touching color [#00ff00] ?>>>>>>You were saying?
- hahasamian
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
You sent that twice and did something weird the second time. I'm tired of arguing, also, that block would KILL any sensing, have you not noticed? It's just a worse repetition of the first…lNo, if the sprite was touching the target sprite but it wasn't touching the targeted color on the sprite (and the targeted color was on the stage or another sprite), your workaround wouldn't work.That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >><<touching color [#ff0088] ?> and <touching [sprite v] ?> >IS a valid workaround.
No support.<<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and <<not <touching color [#00ff00] ?>>>>>>You were saying?
- hahasamian
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
-I was about to say nothing. LOL ^see that^? LOLYou sent that twice and did something weird the second time. I'm tired of arguing, also, that block would KILL any sensing, have you not noticed? It's just a worse repetition of the first…lNo, if the sprite was touching the target sprite but it wasn't touching the targeted color on the sprite (and the targeted color was on the stage or another sprite), your workaround wouldn't work.That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >><<touching color [#ff0088] ?> and <touching [sprite v] ?> >IS a valid workaround.
No support.<<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and <<not <touching color [#00ff00] ?>>>>>>You were saying?
- MathlyCat
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
-I was about to say nothing. LOL ^see that^? LOLPlease don't spam.
@1004587
An assumption is not a valid point to not support; elaborate why you assume that.
It's a nice feature, and it's probably needed, so I semi-support; I'm a bit iffy on the fact of the design. Can it be workaround-ed?
- hahasamian
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
I don't think there's a possible workaround for this one. That's why I asked for it to be made.-I was about to say nothing. LOL ^see that^? LOLPlease don't spam.
@1004587
An assumption is not a valid point to not support; elaborate why you assume that.
It's a nice feature, and it's probably needed, so I semi-support; I'm a bit iffy on the fact of the design. Can it be workaround-ed?
Also, the “spam” is a joke on the fact that I accidentally put the word “I” at the end of the message I sent before it. “It's just a worse repetition of the first…l” <<<See?
- hahasamling
-
Scratcher
1 post
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
I support, I'm his little bro and I understand what he's doing.
Since I currently have no forums signature…
-hahasamling
Since I currently have no forums signature…
-hahasamling
- ealgase
-
Scratcher
100+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
I agree. If the workaround doesn't work, use broadcasts.You sent that twice and did something weird the second time. I'm tired of arguing, also, that block would KILL any sensing, have you not noticed? It's just a worse repetition of the first…lNo, if the sprite was touching the target sprite but it wasn't touching the targeted color on the sprite (and the targeted color was on the stage or another sprite), your workaround wouldn't work.That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >><<touching color [#ff0088] ?> and <touching [sprite v] ?> >IS a valid workaround.
No support.<<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and <<not <touching color [#00ff00] ?>>>>>>You were saying?
- hahasamian
-
Scratcher
1000+ posts
PLEASE ADD THIS BLOCK! It's MUCH better than my last one!
You agree with what? No one said anything about broadcasts, and how would that fix this?I agree. If the workaround doesn't work, use broadcasts.You sent that twice and did something weird the second time. I'm tired of arguing, also, that block would KILL any sensing, have you not noticed? It's just a worse repetition of the first…lNo, if the sprite was touching the target sprite but it wasn't touching the targeted color on the sprite (and the targeted color was on the stage or another sprite), your workaround wouldn't work.That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!No support; easy workaround,<<touching [sprite v] ?> and <touching color [#ff0088] ? >>
But what if the color doesn't belong to that sprite? What if you're touching one sprite, but the target color is from a different one?<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and < <not <touching [other sprite v] ?>>>> >><<touching color [#ff0088] ?> and <touching [sprite v] ?> >IS a valid workaround.
No support.<<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and <<not <touching color [#00ff00] ?>>>>>>You were saying?
Also, I've already told everyone, THERE ARE NO WORKAROUNDS FOR THIS BLOCK THAT PROPERLY WORK!!!
And, I tried something that used broadcasts, and it totally glitches. Everything kept blinking.
I'm tired of arguing, there are no workarounds!
Last edited by hahasamian (Feb. 6, 2016 15:19:53)
- Discussion Forums
- » Suggestions
-
» PLEASE ADD THIS BLOCK! It's MUCH better than my last one!