[solved] the neverlefting shadow

[Minebot]

hi, you certainly also had this problem: you have a ball, the ball disappears,but the shadow stays forever. do you need the frames or do you already know the solution?

[Reaper]

as far as I remember it happens if you have deleted the hitting/ hit frames...

[Silverthorn]

There is a reason why there is a shadow. A shadow is only displayed when an object is not running with state: 3005 (and some IDs have it disabled, too). You're probably having this problem: you made a ball disappear but you didn't delete it. If that's the case, then just change the next-value. next: 1000 deletes the object (which means, also the shadow), so instead of making it invisible, delete it with next: 1000. Should solve your prob

[WoodySmasher]

Maybe u didn't put the frame with next: 1000 and the frame before points to it. Thus a permanent shadow can occur.
For this check all your frames for their numbers and the frames they point exists.

There is a reason why there is a shadow. A shadow is only displayed when an object is not running with state: 3005 (and some IDs have it disabled, too). You're probably having this problem: you made a ball disappear but you didn't delete it. If that's the case, then just change the next-value. next: 1000 deletes the object (which means, also the shadow), so instead of making it invisible, delete it with next: 1000. Should solve your prob

Or try what BP said.

[Alblaka]

Add dummy frames at 0, 10, 20 and 30...
In certain situations the ball will jump to this frames (due to getting hit, hit something or getting rebound, or after he CATCHED a opponent, but befoe finishing his move the opponent gets kicked down), and if they don't exist, the ball will stay invisible, but with shadow...

[Minebot]

<frame> 40 disappearing
pic: 5 state: 3004 wait: 1 next: 41 dvx: 0 dvy: 0 centerx: 54 centery: 24 hit_a: 0 hit_d: 0 hit_j: 0
<frame_end>

<frame> 41 disappearing
pic: 6 state: 3004 wait: 1 next: 42 dvx: 0 dvy: 0 centerx: 56 centery: 22 hit_a: 0 hit_d: 0 hit_j: 0
<frame_end>

<frame> 42 disappearing
pic: 7 state: 3004 wait: 1 next: 1000 dvx: 0 dvy: 0 centerx: 46 centery: 22 hit_a: 0 hit_d: 0 hit_j: 0
<frame_end>

<frame> 164 up_flying_ball
pic: 29 state: 3000 wait: 1 next: 165 dvx: 0 dvy: -5 centerx: 23 centery: 37 hit_a: 45 hit_d: 40 hit_j: 0
itr:
kind: 0 x: 7 y: 2 w: 28 h: 45 dvy: -10 fall: 70 vrest: 12 bdefend: 70 injury: 15
itr_end:
<frame_end>

<frame> 165 up_flying_ball
pic: 30 state: 3000 wait: 1 next: 164 dvx: 0 dvy: -5 centerx: 23 centery: 37 hit_a: 45 hit_d: 40 hit_j: 0
itr:
kind: 0 x: 7 y: 2 w: 28 h: 45 dvy: -10 fall: 70 vrest: 12 bdefend: 70 injury: 15
itr_end:
<frame_end>

the weird thing is, that I copied this from another hack, where the shadow disappears. I don't remember having changed anything, but maybe you can find something. if you need the other frames, just let me know.

[Silverthorn]

Well, as the ball is running with state: 3000, you need to ensure that it doesn't hit any other objects. Otherwise, it'll go to frames 10, 20, or 30. Usually, changing the state to 15 helps preventing this (and maybe solving your prob).
btw, please use [code=dc] next time

[Minebot]

it doesn't matter if it jumps to frame 10, 20 or 30, because they have all next: 1000. and using state 15 also didn't helped...

[Alblaka]

Are you using hit_A/hit_d tags? if the hit_d is going to a not.existing frame this problem woudl occur...

And maybe you could tell us what the ball is doing exactly... would help

[zxcv11791]

Does the ball disapear on impact or just disapear off into the ground after you opoint it?

Check your data.txt, see if you have your ball as a type 3. If you have it as some other type your problem occurs with the just disapearing off into shadow.