I suppose slippery means 3 things. Slow acceleration. Slowly decelerate. Animations.

For the first two you have the actions ... Sprite > platform ..

Set acceleration & Set deceleration

Setting the deceleration to a low value will slip.

It can be automated with 1 included event sheet. Did you see the post i linked to ?

I have no idea why the pin is not recalled by the persist behaviour.

Some one brighter than me will probably find the cause or mark it as a bug.

In the mean time, if you need a workaround, here is one, by 'assisting' the persist. Just 'mimic' what it supposed to do:

https://www.dropbox.com/s/2g6q5digc7wky ... .capx?dl=0

Place helper objects on the corners ? On overlap .. play ..

In this post the placing of those helpers is automated.

No, it is an easy way to mark newly created instances and to pick them out of the not newly created instances, in the next top-event on the moment that they are available to pick.

If you use containers, picking one always picks the others.

Ah !

But, you have done 'it' ?

'Jump' only happens when the 'jumper' is standing on a solid.

The 'Double Jump' happens when the 'jumper' is in the air. I suppose that this is what you are looking for.

https://drive.google.com/open?id=0B1SSu ... VBuUFFBWDA

Your assuming is as good as mine.

I assume that poeple who ask how lerp works, ask how lerp works.

Lerp, when used with a liniair lerpfactor, wil indeed move at a liniar speed. So yes, you are right.

But, lerpfactor can as well be sqrt(abs(counter – 1)) ... where 'counter' goes from 0 to 1

Lets split things up. Lerp can (indeed) in two ways.

Method 1.. lerp(StaticStart,StaticEnd,DynamicFactor)

Method 2.. lerp(DynamicStart,DynamicEnd,StaticFactor)

Method 1 is (in my opion) the base-lerp, the base to learn.

Awesome to do grid movements, by instance. Base means also that it has no 'side effects'. It works as intented. And it is very easy to use.

Method 2 is (in my opion) a version that brings problems that have to be countered. Yet, you will have to use it when Start or/and End has a dynamical character. Not because of the smooting. In my opion that is mis-use. And yes it smooths, but more by accident, than intended. But you will have to take care of the problems.

Dynamical character ? When lerping a moving sprite to a moving sprite.

(In the above given situation Start and End are not dynamical)

What problems you will meet ? (you suggest to use this method, but dont tell about the problems)

Well,

The lerp will never ever arrive to its endpoint. Causing all sort of problems, that fill the forums. When lerping a camera, the camera will start shaking when the lerp is close to its end.

When close to the End, the value returned by the lerp will change in very very small amounts. Since positions and angles are always 'calculated values', this will result in randominess on sub pixel level. You see shaky sprites.

Most people use 'lerp' in a 'every tick' event. But since this lerp never arrives, and since the calculations get slighty heavyer, this lerp will just run every tick and it will eat noticable CPU.

That are my 10 cents, dont know the exchange rate.

I am not ! Containers are just the max.

For the future. If you need to pick newly created objects. Do this easy littlle trick.

Give them a Instance Boolean 'JustCreated'.

Right after the creation action (or spawn) set the boolean to true.

A new top-level event.

Condition ... Sprite ...Is Boolean Instance Variable Set .... 'JustCreated'

(+ all the pick conditions you need)

Actions ... set 'JustCreated' to false ... and all the other actions you need

First thing that i think to notice is that you try to pick newly created objects before the next top-level-event. A function does not count as a new top-level-event.

I really think that you should use containers for this kind of stuff.

This 'overlap' solution is totaly not needed when using containers.

I dont know if you have more instances of the array 'party' ?

You should destroy them all, and then create only the pokemonback in a loop. When using containers, the others get auto created and picked. Then position them as you do in the first lines. Then (still in the same event and in the same loop) give them the values from the array. Dont use the function, because in the function you will have to pick them, which is impossible on that moment.

Drop the capx if you want me to do it.

Post links like this ....

tutorials/997/how-to-code-monster-loot-drops