Chat
Discord
03-27-2012, 01:15 PM
Oh, I found out something that may cause this.. maybe this is not bug after all?
That is frame 55 in julian_ball.dat
It is strange. In every other frames, fall: 20, but in this only frame, fall: 60, which causes DoP in 1 hit.
I am not a good data-changer so I don't understand how chase balls work in the dat file :P . I don't know what next: 999 means in frame 5 , so I don't know either how the projectile can even enter frame 55. However, frames 50-55 is a cycle (it goes frame 50 then 51 then 52 ... to 55 and then go back to 50).
One more important thing about frame 55 is that it deals 45 damage instead of 40 damage (which all other frames do). By seeing the video, we can be sure that the projectile hit me in frame 55, as it does 45 damage instead of 40.
If that is so, then this 'bug' is implemented deliberately in the projectile's data, and so it is not a 'bug' :P . But, do anyone know when the projectile will enter the cycle in frames 50-55 ? Is it right when it hits 'next: 999' ? If the projectile cycles in frames 50-55 then everytime you get hit you have 1/6 chance of being into DoP in 1 hit or falling down before 4 hits, which I am sure doesn't happen as often, so I really want to know when the projectile enters that cycle :) .
|
DC-Code:
<frame> 55 flying pic: 9 state: 3000 wait: 01 next: 50 dvx: 0 dvy: 0 dvz: 0 centerx: 31 centery: 41 hit_a: 14 hit_d: 5 hit_j: 0 hit_Fa: 14 itr: kind: 0 x: 10 y: 19 w: 56 h: 51 dvx: 16 fall: 60 vrest: 10 bdefend: 16 injury: 45 itr_end: bdy: kind: 0 x: 10 y: 19 w: 56 h: 51 bdy_end: <frame_end> |
That is frame 55 in julian_ball.dat
It is strange. In every other frames, fall: 20, but in this only frame, fall: 60, which causes DoP in 1 hit.
I am not a good data-changer so I don't understand how chase balls work in the dat file :P . I don't know what next: 999 means in frame 5 , so I don't know either how the projectile can even enter frame 55. However, frames 50-55 is a cycle (it goes frame 50 then 51 then 52 ... to 55 and then go back to 50).
One more important thing about frame 55 is that it deals 45 damage instead of 40 damage (which all other frames do). By seeing the video, we can be sure that the projectile hit me in frame 55, as it does 45 damage instead of 40.
If that is so, then this 'bug' is implemented deliberately in the projectile's data, and so it is not a 'bug' :P . But, do anyone know when the projectile will enter the cycle in frames 50-55 ? Is it right when it hits 'next: 999' ? If the projectile cycles in frames 50-55 then everytime you get hit you have 1/6 chance of being into DoP in 1 hit or falling down before 4 hits, which I am sure doesn't happen as often, so I really want to know when the projectile enters that cycle :) .
TEMPE
Spoiler (Click to View)