To be more specific, dashing into another player/dummy will cause the user to get launched up into the air. This isn’t flinging though, just getting launched diagonally upward.
I’m not really sure where to begin on finding a solution for something like this.? I’ve tried looking on the dev forums, but I couldn’t find anything for my issue. That’s why I’m creating one myself, I normally avoid creating forum posts like the plague xD
The system uses a BodyVelocity and is largely done on the server. Main thing done on client is detecting the input.
Also, the issue doesn’t seem to be consistent. Sometimes the dash will cause the user to just slide right on by the player/dummy (pretty sure the 2nd dash in the video is not an example of this. I just missed).
Thanks!
Trimping momento*
(trimping refers to the thing where you charge up a ramp and gain ALOT of height)
Velocity means that it can be turned into another direction.
Try to apply the velocity more spread out (by repeatedly setting the velocity to a constant)
That should prevent trimps.
Edit: maybe just avoid player/npc collision altogether using collision groups?
interesting. I’ve never heard of trimping before.
Also, it definitely has something to do with an AlignOrientation. a couple of the moves I’ve created use one, and those moves alone cause the target to act like that. To compound that, Normally the effect only lasts until the AlignOrientation is destroyed/disabled. Thats fine, but if I create the AlignOrientation within 0.1(ish) seconds of disabling the target’s ragdoll (custom function I made for ragdolling), the effect stays forever. THEN GOES AWAY ONCE ITS RAGDOLL IS TURNED ON AND OFF AGAIN. I’m at my wits end here 
Honestly I may have to just turn off the collisions, but I’d really like to keep them enabled. sigh.
1 Like
hm, idk, maybe try to just, as i said before:
Instead of applying velocity once or twice.
SET the velocity to a constant each frame.
Handle this on client side too!
movement MUST be client side or it will be of great lag and delay.
