scratchisthebest wrote:

hahasamian wrote:

I think that I might just use my other idea. You may have read it. 1/4 of the screen is a screen display for each player, while the extra 2/4 are actually used for sensing and are hidden with ghost. That will probably work well, but it will cut down screen size.

Why split them up?

If the sprites are made invisible with the ghost effect, you can put them wherever you want on the screen, because they will be… invisible! You could even put them directly on top of the game window itself.

when I see argument
switch costume to [holding popcorn v]
play sound [John Cena]
say [Carry on fighting - This is entertaining.]

hahasamian wrote:

scratchisthebest wrote:

hahasamian wrote:

I think that I might just use my other idea. You may have read it. 1/4 of the screen is a screen display for each player, while the extra 2/4 are actually used for sensing and are hidden with ghost. That will probably work well, but it will cut down screen size.

Why split them up?

If the sprites are made invisible with the ghost effect, you can put them wherever you want on the screen, because they will be… invisible! You could even put them directly on top of the game window itself.

I can't really put them anywhere on the window, because the display would collide with the sensor stuff, and then it will be really messed up.
And they're not really unable to get to each other, they just have separate screens in case they each are in separate levels.
They're friends, after all. I won't keep two friends apart.

dude341 wrote:

hahasamian wrote:

scratchisthebest wrote:

hahasamian wrote:

I think that I might just use my other idea. You may have read it. 1/4 of the screen is a screen display for each player, while the extra 2/4 are actually used for sensing and are hidden with ghost. That will probably work well, but it will cut down screen size.

Why split them up?

If the sprites are made invisible with the ghost effect, you can put them wherever you want on the screen, because they will be… invisible! You could even put them directly on top of the game window itself.

I can't really put them anywhere on the window, because the display would collide with the sensor stuff, and then it will be really messed up.
And they're not really unable to get to each other, they just have separate screens in case they each are in separate levels.
They're friends, after all. I won't keep two friends apart.

If you use ghost effect instead of hide sprites can still collide with it.
so much

Theunicornworld wrote:

when I see argument :: control hat
switch costume to [holding popcorn v]
play sound [John Cena]
say [Carry on fighting - This is entertaining.]

please dont spam

gamebeater187 wrote:

Theunicornworld wrote:

when I see argument :: control hat
switch costume to [holding popcorn v]
play sound [John Cena]
say [Carry on fighting - This is entertaining.]

please dont spam

define Touching Red Stuff //no screen refresh
broadcast [Hide Cover v] and wait
if <<touching color [#ff0000] ?> and <touching [Object v] ?> > then
    ...//do stuff
end
broadcast [Show Cover v]

when green flag clicked
if <touching color [#ff0088] ?> then
    
broadcast [stuff v]
or
broadcast [waiting stuff v] and wait
end



when I receive [stuff v]
...

hahasamian wrote:

ealgase wrote:

hahasamian wrote:

1004587 wrote:

Sheep_tester wrote:

Zekrom01 wrote:

hahasamian wrote:

1004587 wrote:

alexphan wrote:

1004587 wrote:

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] ?>>>> >>

That's impossible. No workarounds for that block. THAT'S WHY I'M ASKING!

<<touching color [#ff0088] ?> and <touching [sprite v] ?> >

IS a valid workaround.

No support.

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.

1004587 wrote:

<<<touching [sprite v] ?> and <<<touching color [#ff0088] ?> and <<not <touching color [#00ff00] ?>>>>>>

You were saying?

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…l

I agree. If the workaround doesn't work, use broadcasts.

You agree with what? No one said anything about broadcasts, and how would that fix this?
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!

hahasamian wrote:

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:

<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!

banana439monkey wrote:

hahasamian wrote:

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:

<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!

No support. Work-aroundable

Icely wrote:

I tried to read through everything, but I am not sure if this has been mentioned yet:

define Touching Red Stuff //no screen refresh
broadcast [Hide Cover v] and wait
if <<touching color [#ff0000] ?> and <touching [Object v] ?> > then
    ...//do stuff
end
broadcast [Show Cover v]

Would that work for you?