[solved] Bugged ball.

[JossuaDC]

Old. (Click to View)

The ball works pretty much as intended, even though it's not finished yet, but there's a small bug which I can't get rid of.

Play around with the move and you'll notice that one of the balls tends to seperate itself and becomes static and unremovable.
This is caused by one of the other balls 'stealing' the enemy from the original balls' cpoint.

Now, this wouldn't be a problem if the original ball would still respond to anything, but that is not the case.
I've tried hitting it, forcing it into different frames and all that kind of whatnot, but all my attempts have proven unsuccesful so far.

The finished ball has a lock which prevents two balls from being active in the same match at the same time, but I haven't included this in the seperated file, so keep in mind that you only spawn 1 ball at a time to accurately re-create the bug.

tl;dr: How do I remove the static ball from play without altering the properties of the move itself?
Solved by: Alblaka.

Edit: A fun little side-effect.

[Alblaka]

If i got it right, your ball catches an opponent via itr/kind:3 and the bug occurs if another ball catches the same opponent?

2 solutions:
-Add a hurtable: 0 in the cpoint, then the char can't be grapped or affected by something else (dunno what exactly your move is doing, may a hurtable: 1 is required, then just check below)
-If an object looses a catched char it usually jumps to frame 0. Had the same problem somewhen, too (i think it was with Nohan). Solved it with replacing some frames (to get frame 0 free) and turning it into a deletion frame (wait:0/next:1000).

For the case this solutions don't help you anything at all, you are allowed/supposed to shout at me for being to lazy to download the files ^^

[JossuaDC]

If an object looses a catched char it usually jumps to frame 0. Had the same problem somewhen, too (i think it was with Nohan). Solved it with replacing some frames (to get frame 0 free) and turning it into a deletion frame (wait:0/next:1000).

Fixed it.
My file didn't have a frame numbered 0, even though there are about 300 frames in it. Silly, hmh?

I somehow always mess up at the cpoints.