Scratch

The image above shows my previous attempts that have failed.

Last edited by colorfusion (2010-07-15 15:15:28)

Ok, here you go. This only works if you use trigger variables to make sure that each different routine is completed in order. This is basically colorfusion's idea 2 sped up.

This is in loop order...
1-the list "Touching" deletes all of its items
2- Each sprite will do its own check to see if it is touching the player. If it is, it adds its sprite number to the list (sprite #50 adds "50", etc)
3-The player sprite checks to see if the list has any items
if not, presumably most of the time, it skips ahead
4-If the list is longer than 0 items, set a loop to the number of items in the list.
One at a time, start with (presuming you have 100 items) if list item (loop #) is <50 else if <25 else if <12 etc. This way you can reduce the entire process to A. not even running most of the time and B. narrowing down what is touching faster.
5-do whatever else then restart the loop

The biggest drawback I foresee with this system depends on how many items are simultaneously touching the player and how often? PS. have you actually made a project with over 100 sprites in it yet?

edit: Another idea.. all items that share the same attribute, like items that simply block player movement like a tree stump, a table, a big rock, etc can be lumped together into groups. This will speed up searching because now you can say If item < biggest group item and item > smallest group item then block player movement, or whatever.

Last edited by Locomule (2010-07-15 21:27:31)

I'm talking about the second method, there are three shown in the picture. The second one doesn't use the Any (and no it doesn't mean random) but is the one labeled "needs to work faster"

Last edited by Locomule (2010-07-16 01:11:11)

It doesn't mean random. It means any. Which it goes through the whole list to detect. Try
it. The item any of list.

It works.

fg123 wrote:

It doesn't mean random. It means any. Which it goes through the whole list to detect. Try
it. The item any of list.

It works.

Are you absolutely sure? I'm not on a computer that has Scratch on it right now, but as I recall, the "item (any) of" block is random.

It only works offline though. 
http://scratch.mit.edu/projects/fg123_tests/1195719

whoops

Try " <if touching (bleh)>
blah blah blah."

Neva mind.

Last edited by laser100 (2010-07-16 15:26:36)

fg123 wrote:

It doesn't mean random. It means any. Which it goes through the whole list to detect. Try
it. The item any of list.

It works.

It only works offline though. 
http://scratch.mit.edu/projects/fg123_tests/1195719

Nah, if you just pull the block (Item any of list) into the script editing window and click on it, it returns a random item of the list. Therefore, the result is the same in this situation.

If it was as you say, it would be inconsistent. The Scratch team would never make a block like that. It would be too confusing for people. 

I wish it would be changed to (Item random of list) and the block you're talking about added though; it would be so much easier.

Ok, now link the actual project 

If your character it a circle, you could use the distance block, but then again, maybe its not fast enough or it's random.

"Actually, wait, if all your sprites are the same color, than you can just use color sensing!!

The counting method seems to work for me.  How many sprites are you using?"


So far I have 6 sprites, but I only just started the first aura, I plan to make a lot of auras so it could take up to 100 and the counting method would take about 3 seconds every time it moved 2 steps.

The sprites are all different colours, and some are to thin to outline.