Scratch

The reason I'm posting here is I can't login in 2.0 Beta on Internet Explorer, the only internet browser installed on school comptuters. (FIX THIS, ST!!!)

Actually, there are two reasons; the other is that here I can use the forums to make pictures of scripts.

So my idea is individual lists of "statuses" for all sprites, under sensing, meaning that they would be blue and not red. Let's say you're programming a game with all kinds of enemies in all kinds of colors that you want to make your many characters sense. This would help.

Blocks would look like:

add [status] status to [sprite v]

This adds the desired status to the desired sprite. On the dropdown menu, you could also select "all sprites," "all clones," "all," and "myself."

remove [status] status from [sprite v]

This is the block to to remove statuses.

<touching [status] status?>

This would be simple- all sprites with the status would tell the block if they're touching the sprite containing this boolean. If even one is touching, it registers as true.

<[sprite v] has [status] status?>

Just a simple block to check for these things.

One more thing, all sprites would permanently have "sprite" status, and all clones would have "clone" status. These couldn't be removed. Stage/Backdrop would not have statuses.

Problems I can think of:
Generally, it's not needed. But it would be helpful in games with lots of characters, enemies, projectiles, etc.
It uses more data, which might slow down the system.
There is probably a workaround.
...etc, you get the idea.

So what do you think? I know there are flaws, but are they big and bad enough to deny this? Is it a good idea? Please let me know, and provide lots of reasons!

Last edited by Failord (2013-04-27 23:20:53)