Thanks!

Here's an isolated case that I threw together. When the ball hits the pink surface, I want the ball to behave as though the surface absorbed its shock, so slow it down, yes.

So are you saying that I should manually set the ball's velocity on collision with the pink surface?

storage.wertle.com/construct2/Example.capx

I feel like this is a simple question and I'm just searching for the answer incorrectly.

I'm making a physics puzzler where different surfaces do different things to a falling/bouncing object.

I've got surfaces that bounce it away and surfaces that launch it like a speed boost, but the one that's giving me trouble is a surface that slows down the object when it hits, kind like a sticky wall or some kind of shock absorber. I wasn't sure what settings I needed to adjust and if I needed to adjust them on the surface object or the bouncing object or both, and playing around with various numbers in the objects wasn't getting me anywhere.

Do I need to do something to the bouncing object on its collision with the sticky surface in the events?

Sorry to dredge this up again, but i'm facing a similar issue and no answer is yet to be found.

I did come up with a rather convoluted workaround that involves spawning invisible anchors to pin to so you are pinning to a different sprite type, but if there is a more elegant way to do this I would love to hear!

storage.wertle.com/construct2/SnakeTrailExample.capx

doesn't the "pick by highest/lowest value" action already do this?

That only lets you compare instance variables on the object, versus say it's x or y value (unless you just copied those into an instance variable beforehand)

So my theory about negative angles wasn't right, but I was able to get what you want using "Rotate Towards Angle" instead of "set angle"

storage.wertle.com/construct2/SlopeAngleFixed.capx

You can change the angle number to get a faster or slower transition

I may be able to help with this as I was facing something similar recently, something to do with weirdness about handling -angle values, but I have my own noob question first.

It says the version of that capx was saved in release 141 or newer, so I can't open it. Where can I download that release version? I only see 139 on the site. Let me know so I can try and help :)

The player character in my game leaves a trail of footprints behind them when they move around, and the trail needs to stick around for the whole level, not fade away.

For the prototype I'm just doing this by spawning footprint sprites, but since this ends up with many, many sprites, I'm wondering if there's a better way to approach this when I do it "for reals."

Suggestions? Past related topics seem to only have to do with trails that fade, which is not what I want.

Thanks!

Perfect! I was thinking I'd have to do something along these lines but did not know about the Replace Object thing.

Thanks.

So I'm at a point where I've built a prototype with a player sprite getting things feeling pretty good. I've realized now after the fact that I should have done the player as a family (I'm going to try having different player characters with slightly different rules to them, but that share a lot of stuff).

I'd like to create a Family with all the instance variables and behaviors from my one sprite and then change my events to reference the family instead of the individual sprite.

However, I can't just make duplicate instance variables in the family (families can't have instance variables named the same as a member's instance variables). I can't delete the member's variables first because that will mess up my events.

Are there any best practices for this sort of situation? Should I just set up an "empty" family with the instance variables and duplicate all my events with the new references?

Looks like that's the way to go for now, thanks :)

Greetings! I did some searching but did not find anything in past topics on this.

Is there a way to use the LOS behavior to detect things *behind* a sprite? For example if my sprite is moving to the right, could I have the cone of view facing the left?

My backup plan is to pin an invisible sprite with LOS to the main one and always set its angle to be the opposite of the main sprite, then just use that for my LOS checks, but if there's a way to do it with just the LOS behavior I'd like to do that.

Thanks!