Scratch

Zparx · 2012-10-19 21:31:53

I think that we should be able to assign tags to sprites for more efficient means of detection. This would be especially helpful in platformer games. For instance, the ground sprites. Here is what someone would normally use for their scripts (this is my personal style. idk about anyone else);

when gf clicked
forever
if <(touching? [sprite 1 v]) or <(touching? [sprite 2 v]) or <(touching? [sprite 3 v]) or (touching? [etc! ;b v])>>>
//execute actions here        
end

That script always becomes a pest, and fairly large if you're making some huge platformer/scroller

Instead of putting that code, I think we should be able to go to the menu where the scratch blocks are (upper left corner) and have another category called "Tags". It would work similar to the variables function, and when you clicked it, there would be various functions, two of which called "Create Tag" and "Delete Tag". When you create a Tag, you could name it whatever you want (sort of like a variable), then "assign" your created Tag to any sprite you wanted. In this case, we would assign the tag to all of your ground sprites in the project you're making. So let's say you made a tag called "ground". You could then go to all of the sprites you are going to use to simulate ground in your project, and under the control blocks you would see blocks that say something like ;
add me to Tag [Ground v] delete me from Tag [Ground v]
I think this would make this sort of programming very very efficient. Your script would look something like this after you've created and assigned your tag;

when gf clicked
forever
if (touching? [Tag: Ground v])
//execute actions here

Zparx wrote:
In BYOB, I've actually put this script together but without tags. I edited a true/false sensing block, like this:
when gf clicked
forever
if <(touching [sprite 1 v]?) or (touching [sprite 2 v]?)>
report true
else
report false
And called the block "touching ground sprites?"

and it worked like a charm! I added 5 new sprites to the created block and it still worked flawlessly. So I doubt it will be hard to implement if BYOB has already (sort of) done it!

Let me know what you think!

--------------------
SUPPORTERS
-------------------

* Firedrake969
* Mokat
* 777w
* taddl
* dvd4
* ErnieParke
* subzerostig
* technoboy10
* Martiscratch
* Rexpup
* Willpower
* nitromian
* TorbyFork234
* scratchisthebest

Last edited by Zparx (2012-11-08 00:14:26)

777w · 2012-10-19 21:38:40

interesting idea

Firedrake969 · 2012-10-19 21:39:22

Mega support.

Mokat · 2012-10-19 21:42:53

Support.

Zparx · 2012-10-19 21:43:59

Thanks! I'll add you guys' names to the supporters list! (:

Firedrake969 · 2012-10-19 21:49:25

Duplicate. Reporting to be closed.
EDIT: Oh, and this

Last edited by Firedrake969 (2012-10-19 21:51:12)

Zparx · 2012-10-19 21:51:33

Firedrake969 wrote:
Duplicate. Reporting to be closed.

Organization and tagging are two completely different things. I don't think you fully understand my suggestion.

Mokat · 2012-10-19 22:02:38

Firedrake969 wrote:
Duplicate. Reporting to be closed.
EDIT: Oh, and this

That's different...

Zparx · 2012-10-19 22:34:25

Mokat wrote:
Firedrake969 wrote:
Duplicate. Reporting to be closed.
EDIT: Oh, and this
That's different...

Thank you..

taddl · 2012-10-20 09:31:19

support

Zparx · 2012-10-20 14:40:45

bumpdate

dvd4 · 2012-10-20 14:56:24

I support your idea Sparks ! tongue

(I support your idea)

ErnieParke · 2012-10-20 15:45:40

This can really help in quite a few situations and I don't think that it'll be confusing for children, so I support.

subzerostig · 2012-10-20 16:15:28

Definitely support. For some projects I have to resort to 'touching colour?' Instead of touching sprite a - b

dvd4 · 2012-10-20 19:49:59

A proof of it's usefulness:

when gf clicked
forever
if <(touching? [sprite 1 v]) or <(touching? [sprite 2 v]) or <(touching? [sprite 3 v]) or <(touching? [sprite 4 v]) or <(touching? [sprite 5 v]) or (touching? [sprite 6 v])>>>>>
//execute actions here        
end

does this look simple ?

Last edited by dvd4 (2012-10-20 19:50:15)

Zparx · 2012-10-21 09:22:46

dvd4 wrote:

A proof of it's usefulness:

when gf clicked
forever
if <(touching? [sprite 1 v]) or <(touching? [sprite 2 v]) or <(touching? [sprite 3 v]) or <(touching? [sprite 4 v]) or <(touching? [sprite 5 v]) or (touching? [sprite 6 v])>>>>>
//execute actions here        
end

does this look simple ?

exactly (:

Firedrake969 · 2012-10-21 09:40:17

Once, I worked for half an hour doing that, then realized that it didn't work and I deleted that script....

Zparx · 2012-10-21 09:45:08

Firedrake969 wrote:
Once, I worked for half an hour doing that, then realized that it didn't work and I deleted that script....

Which script?

northmeister · 2012-10-21 10:08:03

I think you may have suggested this before... tongue

Zparx · 2012-10-21 11:26:19

northmeister wrote:
I think you may have suggested this before...

I did, but everyone mistook it for "organizing" and putting the sprites in "folders" when that's not what I'm suggesting. I decided to reword some things so that hopefully people understand more clearly.

technoboy10 · 2012-10-21 11:45:53

Support. This would be cool.

Zparx · 2012-10-21 19:14:52

technoboy10 wrote:
Support. This would be cool.

woop! updated the list.

Zparx · 2012-10-22 20:40:41

bump

TorbyFork234 · 2012-10-22 20:59:26

I support, but in the meantime you can use this relatively long workaround:

Make a list with a name of Tags:(TagName)
Then, for every sprite you have that you would want to be under that tag, you would put a

add [spritename] to [Tags:TagName v]

then, for sensing, you would do this:

when I receive [touching tagName v] //has to be under the sprite that you want to be checked for touching
set [i v] to [1]
set [touching v] to [0]
repeat <length of [Tags:TagName v]>
if <touching <item (i) of [Tags:TagName v]>?>
set [touching v] to [1]
end
change [i v] by (1)
end
if <(touching)=[1]>
say [you touched one of the sprites with a tag of tag name!]
end

Alternatively, for that script, since it's only for sensing, if you want to make it go faster, you could change the repeat to this:

repeat until <<((i)+(1))=<length of [Tags:TagName v]>>or<(touching)=[1]>>
end

You could also just have the bunch of or's sitting at the edge of the screen, and when you need it just duplicate it.

Anyways, it would be better to have it built in.

Zparx · 2012-10-22 22:24:39

TorbyFork234 wrote:
I support, but in the meantime you can use this relatively long workaround:

Make a list with a name of Tags:(TagName)
Then, for every sprite you have that you would want to be under that tag, you would put a
add [spritename] to [Tags:TagName v]
then, for sensing, you would do this:
when I receive [touching tagName v] //has to be under the sprite that you want to be checked for touching
set [i v] to [1]
set [touching v] to [0]
repeat <length of [Tags:TagName v]>
if <touching <item (i) of [Tags:TagName v]>?>
set [touching v] to [1]
end
change [i v] by (1)
end
if <(touching)=[1]>
say [you touched one of the sprites with a tag of tag name!]
end
Alternatively, for that script, since it's only for sensing, if you want to make it go faster, you could change the repeat to this:
repeat until <<((i)+(1))=<length of [Tags:TagName v]>>or<(touching)=[1]>>
end
You could also just have the bunch of or's sitting at the edge of the screen, and when you need it just duplicate it.

Anyways, it would be better to have it built in.

This is an effective method, and I've used it in some of my big games, such as "Cyber Defense" in which I added 10 sprites to the list. It worked fine because the turrets didn't require quick touch sense detection. However, if I had 10 or more ground sprites added to a list for a platformer and used this method, it would be very ineffective unless I used turbo mode.

Last edited by Zparx (2012-10-22 22:25:09)

Scratch

archived forums

#1 2012-10-19 21:31:53

New Scratch Function: Assigning "Tags" to Sprites for Better Detection

Zparx wrote:

#2 2012-10-19 21:38:40

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#3 2012-10-19 21:39:22

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#4 2012-10-19 21:42:53

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#5 2012-10-19 21:43:59

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#6 2012-10-19 21:49:25

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#7 2012-10-19 21:51:33

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

Firedrake969 wrote:

#8 2012-10-19 22:02:38

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

Firedrake969 wrote:

#9 2012-10-19 22:34:25

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

Mokat wrote:

Firedrake969 wrote:

#10 2012-10-20 09:31:19

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#11 2012-10-20 14:40:45

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#12 2012-10-20 14:56:24

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#13 2012-10-20 15:45:40

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#14 2012-10-20 16:15:28

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#15 2012-10-20 19:49:59

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#16 2012-10-21 09:22:46

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

dvd4 wrote:

#17 2012-10-21 09:40:17

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#18 2012-10-21 09:45:08

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

Firedrake969 wrote:

#19 2012-10-21 10:08:03

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#20 2012-10-21 11:26:19

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

northmeister wrote:

#21 2012-10-21 11:45:53

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#22 2012-10-21 19:14:52

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

technoboy10 wrote:

#23 2012-10-22 20:40:41

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#24 2012-10-22 20:59:26

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

#25 2012-10-22 22:24:39

Re: New Scratch Function: Assigning "Tags" to Sprites for Better Detection

TorbyFork234 wrote:

Board footer