Clone disappearing

is there a reason why when i clone the hammer it pops up and instantly disappears?

2 Likes

When it disappears, does it shrink to 0, move to a far away location, or does it become parented to nil (i.e. deleted)?

it moves to a really far away location

And it also works with other unions if i change it but with the hammer it just doesn’t work even though everything is the same

How long after you create it does it vanish?

it disappears three seconds max


it gets put this far away

1 Like

Try setting the DivineBlast’s Size to a small value that isn’t 0, like as an example: Vector3.one * 0.0001. Setting a part’s size to a zero Vector3 can result in unstable behavior Edit: Just ran a test to confirm, and setting the size to 0 seems to no longer be a problem since it will automatically adjust to 0.001, hence why my suggestion unfortunately didn’t work

alright ill try that and see if it works

1 Like

nope still does the same thing it spawns and deletes i guess

Can you disable the linear velocity and check if it still happens?

2 Likes

whoaaa it doesn’t delete now but what should i use to make it a projectile? isnt body velocity depricated? or is there a way to make it work?

Pretty sure you can still use the LinearVelocity but maybe try to cap the MaxForce or tone down the VectorVelocity to see if that helps? If not then the issue might be something else interacting weirdly with the LinearVelocity but I don’t know what it could be.

The issue might lie with how the direction is being calculated, if the result of (Mouse - MagicCircle.Position * Vector3.new(0, 0, 0)) results in: Vector3.new(0, 0, 0), then attempting to convert it to a unit vector will result in a nan Vector3 Vector3.new(nan, nan, nan), which will cause the LinearVelocity to go out of control


@AmProSlice123 BTW, what’s the point of multiplying the MagicCircle’s Position with a zero Vector3? Currently your formula is the exact same as doing: local direction = Mouse.Unit, since MagicCirle.Position * Vector3.new(0, 0, 0) will be calculated first, and always result in Vector3.new(0, 0, 0), then Mouse - Vector3.new(0, 0, 0) will result in the same value as Mouse

1 Like

I did that but

OHHH i get it no wonder its going out of control

2 Likes

@JohhnyLegoKing let me try and fix it

1 Like

well i fixed it but the result is still this Clip, Edit, and Share Your Game Clips & Gameplay - Medal

well not exactly that but it does this it constantly spins around Clip, Edit, and Share Your Game Clips & Gameplay - Medal