place_meeting, position_meeting, instance_position, instance_place etc.

Note: The only reason why I am linking about Game Maker stuff is so that you who make Stencyl can and will understand what I am talking about for suggestions for Stencyl (especially for new drag and drop blocks).


http://docs.yoyogames.com/source/dadiospice/002_reference/objects%20and%20instances/instances/instance%20functions/instance_place.html


http://docs.yoyogames.com/source/dadiospice/002_reference/objects%20and%20instances/instances/instance%20functions/index.html


http://docs.yoyogames.com/source/dadiospice/002_reference/objects%20and%20instances/objects/index.html


Also search on https://www.google.com/ or http://www.google.com/ all of the following 13:
docs yoyogames while loop

docs yoyogames switch statement

docs yoyogames with statement

docs yoyogames id

docs yoyogames collision_line

docs yoyogames collision_circle

docs yoyogames collision_rectangle

docs yoyogames collison_triangle

docs yoyogames place_empty

docs yoyogames place_free

docs yoyogames position_empty

docs yoyogames collision_point

docs yoyogames collision_ellipse

And the point of this post is..?
If you posted a suggestion and you need to give the readers some examples then do it in the same thread as the suggestion, or at least put a link to the original thread so we can find it with 1 click.

The point of this is so that Stencyl makers will (at least hopefully) make snap blocks like collision_line, instance_position etc. so that people can make awesome games easier because of more snap block functions such as switch, case, instance_place, collision_ellipse, collision_rectangle etc.

I mean...what exactly do you think is missing in Stencyl. It already has collision checks, while loops, "If" loops (case), and  those "instances" from gameMaker (called Actors in Stencyl), with all the things you could need from them (unless you need something that nobody needed and you made this post).

If you're coming from a GameMaker, and you think that a specific thing would be useful then point it out, or, if you don't know if it exists then do ask about it.

My point is...your post actually looks like you want people to read the GameMaker docs without any specific reason to do so.
 

hi there

I also came from GM and I think he meant that GM had some very useful functions, which I used a lot:
- position_meeting(x,y,obj) - which returned if an object (actor for stencyl) is at position x,y. I still didn't figure out how to do this in Stencyl, and I used this function a lot in my GM games, and now I find it hard to remake them in Stencyl.
- position_destroy(x,y) - which destroys every actor with mask in x,y - very useful and want it in Stencyl
- place_free(x,y) - which checked if x,y has no actors there, excluding sensors.
- place_empty(x,y) - same as above, but checking sensors also.

About the while, for, and the rest of the loops I figured them in Stencyl with <repeat until> block. Still it could be easier with a for loop And while I can use the <repeat n times> for a single <for>, for a <for> in <for> it didn't work for me....

Hope it is clear now

About the while, for, and the rest of the loops I figured them in Stencyl with <repeat until> block. Still it could be easier with a for loop And while I can use the <repeat n times> for a single <for>, for a <for> in <for> it didn't work for me....

That's because the toolset can get "confused" about which index you want to use in a nested for-loop. You can actually get around this: just store the first index in an attribute before moving on to the second for loop.