Scratch

Bippity bumpity boo

Lucario621 wrote:

RHY3756547 wrote:

Bippity bumpity boo

Lol 

O RLY?

Sorry...

Uh, RHY - you can already do object groups - I'll upload a project with it in.

But for one, that doesn't work online because they didn't foresee anyone using it. Two - that doesn't work with the *trigger if* function I mentioned so that the application could grab the variable from the item it touched.

RHY3756547 wrote:

greenflash wrote:

This would be awesome! I don't think it needs to be broken into other categories though.

Yeah - I just think they should also rename the "Variables" section to something more general though.

Definately.

Bippity Bumpity Boo.
Add this Noo-w!

Fanofcena:

Doing everything in the bloody universe with the current scratch blocks just results in lag. ...and a lot.

I support 110%. This is an amazing Idea, and useful too.

RHY3756547 wrote:

It'd also be nice if the existing list and variable blocks could go into things and work online.

If touching (Item (any) of list) doesn't work online, nor does (variable (bla) of (variable) )

... which are quite good workarounds and/or little-known thingies, thank you for mentioning it!

This idea can actually be implemented now but it's not very easy. Just create a list named "enemies" and fill it with the sprite names of all enemy sprites. Then to check collisions against them:

i=0
repeat( length of (enemies)) {
  if(touching (item i of enemies)){
    broadcast("something bad")
  }
  change i by 1
}

What would be really helpful is a (my name) reporter that holds the name of a sprite. That way you wouldn't have to populate the enemies list manually.

The-Whiz wrote:

Yeah... I've used that before, and it works well offline, but not at all online. I call it "sprite iteration".

Really? Weird! I've never tried this in practice, so I'll take your word for it  . It's a shame the Scratch team hasn't paid more attention to this feature, it's really useful.

fullmoon wrote:

The-Whiz wrote:

Yeah... I've used that before, and it works well offline, but not at all online. I call it "sprite iteration".

Really? Weird! I've never tried this in practice, so I'll take your word for it  . It's a shame the Scratch team hasn't paid more attention to this feature, it's really useful.

Yeah... This project. The ball uses the sprite iteration... But, as you can see, it doesn't work online. I think it is because the Scratch project player can't process variables or lists in blocks like [go to []] and <touching []>.

GirWaffles64 wrote:

RHY3756547 wrote:

It would be great if objects could be put in groups that we could use to detect collisions for objects of the same type, report variables and much more.

Here's how it would work.

Say we made a group called enemies. There would be "Add me to group ()" and "Remove me from group()" blocks, as well as "Empty group" etc. Now, we make a lot of enemies and add them to the Ememies group. Now - in the unfortunate player who has to face these enemies' scripts we put something like "if touching (Group (enemies)) { Set (Y-velocity) to (Y-velocity of (Trigger If))". Trigger if would refrence to the object from the group that the script interacted with.

An example of this would be the implementation in The Sims Carnival Game Creator. Trust me - it made multiple object collision a LOT easier.

This idea has been in my head for years. Now somebody agrees with me!

(does victory dance)

Good Idea I Agree

"Sarcasm doesn't work on paper" 

I just noticed that Wolfie's method DOES NOT WORK RIGHT. Implementing it in a game I am making allows my character to go through the wall sometimes because the item selected from the list is random.

There is no other way (without atomicism, but even then scratch's interpreter would make games too darn slow). We need object groups. D: