+- Little Fighter Empire - Forums (https://lf-empire.de/forum)
+-- Forum: Little Fighter 2 Zone (https://lf-empire.de/forum/forumdisplay.php?fid=7)
+--- Forum: Data Changing (https://lf-empire.de/forum/forumdisplay.php?fid=11)
+---- Forum: Solved Problems (https://lf-empire.de/forum/forumdisplay.php?fid=14)
+---- Thread: [solved] What's wrong with the code? (/showthread.php?tid=872)
Pages:
1
2
[solved] What's wrong with the code? - vktewari - 08-17-2008
I have used the following code but when I catch the opponent he goes to first falling frame and remains in that frame forever. I can't even hit him. Please tell me if something is wrong with the code.
Code:
<frame> 266 run
pic: 88 state: 9 wait: 3 next: 267 dvx: 0 dvy: 0 dvz: 0 centerx: 43 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0 mp: 200
bdy:
kind: 0 x: 25 y: 12 w: 47 h: 68
bdy_end:
<frame_end>
<frame> 267 run
pic: 88 state: 9 wait: 2 next: 268 dvx: 18 dvy: 0 dvz: 0 centerx: 43 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0
sound: data\003.wav
itr:
kind: 3 x: 20 y: 22 w: 49 h: 57 vrest: 7 catchingact: 269 269 caughtact: 130 130
itr_end:
<frame_end>
<frame> 268 run
pic: 88 state: 9 wait: 2 next: 999 dvx: 18 dvy: 0 dvz: 0 centerx: 43 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0
sound: data\004.wav
itr:
kind: 3 x: 20 y: 22 w: 49 h: 57 vrest: 7 catchingact: 269 269 caughtact: 130 130
itr_end:
<frame_end>
<frame> 269 upkick
pic: 14 state: 9 wait: 1 next: 270 dvx: 0 dvy: 0 dvz: 0 centerx: 36 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0
cpoint:
kind: 1 x: 54 y: 30 vaction: 130 throwvz: -842150451 throwinjury: -842150451 cover: 10
cpoint_end:
bdy:
kind: 0 x: 9 y: 8 w: 49 h: 72
bdy_end:
<frame_end>
<frame> 270 upkick
pic: 15 state: 9 wait: 1 next: 271 dvx: 0 dvy: 0 dvz: 0 centerx: 43 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0
sound: data\007.wav
cpoint:
kind: 1 x: 54 y: 30 vaction: 180 cover: 10 throwvx: 0 throwvy: -58 throwvz: 0 throwinjury: 30 decrease: 3
cpoint_end:
bdy:
kind: 0 x: 19 y: 15 w: 28 h: 65
bdy_end:
<frame_end>
<frame> 271 fly
pic: 61 state: 3 wait: 2 next: 272 dvx: 0 dvy: -49 dvz: 0 centerx: 41 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0
bdy:
kind: 0 x: 17 y: 13 w: 31 h: 66
bdy_end:
<frame_end>
<frame> 272 fly
pic: 62 state: 3 wait: 2 next: 273 dvx: 0 dvy: -49 dvz: 0 centerx: 41 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0
bdy:
kind: 0 x: 17 y: 13 w: 31 h: 66
bdy_end:
<frame_end>
<frame> 273 downpunch
pic: 25 state: 3 wait: 2 next: 274 dvx: 0 dvy: 550 dvz: 0 centerx: 41 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0
bdy:
kind: 0 x: 17 y: 13 w: 31 h: 66
bdy_end:
<frame_end>
<frame> 274 downpunch
pic: 26 state: 3 wait: 2 next: 275 dvx: 0 dvy: 550 dvz: 0 centerx: 30 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0
sound: data\007.wav
itr:
kind: 0 x: 22 y: 39 w: 70 h: 70 dvx: 18 dvy: 18 fall: 70 arest: 15 bdefend: 60 injury: 50
itr_end:
bdy:
kind: 0 x: 43 y: 35 w: 28 h: 18
bdy_end:
<frame_end>
<frame> 275 balldiag
pic: 76 state: 3 wait: 3 next: 276 dvx: 0 dvy: 550 dvz: 0 centerx: 39 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0
bdy:
kind: 0 x: 30 y: 18 w: 28 h: 60
bdy_end:
bdy:
kind: 0 x: 23 y: 35 w: 37 h: 24
bdy_end:
<frame_end>
<frame> 276 balldiag
pic: 83 state: 3 wait: 5 next: 277 dvx: 0 dvy: 550 dvz: 0 centerx: 39 centery: 79 hit_a: 242 hit_d: 0 hit_j: 0
opoint:
kind: 1 x: 74 y: 38 action: 50 dvx: 0 dvy: 0 oid: 301 facing: 0
opoint_end:
bdy:
kind: 0 x: 39 y: 19 w: 21 h: 61
bdy_end:
bdy:
kind: 0 x: 51 y: 34 w: 26 h: 16
bdy_end:
<frame_end>
<frame> 277 balldiag
pic: 78 state: 3 wait: 3 next: 278 dvx: 0 dvy: 550 dvz: 0 centerx: 39 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0 mp: -8
bdy:
kind: 0 x: 27 y: 17 w: 31 h: 63
bdy_end:
<frame_end>
<frame> 278 balldiag
pic: 84 state: 3 wait: 5 next: 276 dvx: 0 dvy: 550 dvz: 0 centerx: 39 centery: 79 hit_a: 240 hit_d: 0 hit_j: 0
opoint:
kind: 1 x: 76 y: 38 action: 50 dvx: 0 dvy: 0 oid: 301 facing: 0
opoint_end:
bdy:
kind: 0 x: 28 y: 17 w: 29 h: 63
bdy_end:
bdy:
kind: 0 x: 45 y: 37 w: 32 h: 11
bdy_end:
<frame_end>RE: What's wrong with the code? - Silverthorn - 08-17-2008
I think you don't need state: 9 in the running-frames, you could use any state, for example state: 3. Just as long as the frames that contain a cpoint, you need a state: 9.
RE: What's wrong with the code? - vktewari - 08-17-2008
But that doesn't solve the problem.
RE: What's wrong with the code? - Azriel - 08-17-2008
must have state: 9
try in this order:
take away decrease: 3
make throwvx: 1 (don't think u need this, just the decrease 3 to be taken away)
Azriel~
RE: What's wrong with the code? - Silverthorn - 08-17-2008
would it change anything if you change vaction: 180 to vaction: 181 in frame 270?
edit: dang, Azzy, you were faster :P
RE: What's wrong with the code? - vktewari - 08-17-2008
All that makes no difference. On changing the vaction to 180 the opponent gets hanged in that Frame only.
Edit: I have changed the cpoint in frame: 270 to itr which sends the opponent in the air. And this problem is solved.
But, there's another problem. I want to make a diagonal ball to be thrown by my character after hitting the opponent down (Frame 275) but the balls look quite absurd, I don't know why. Here's the ball sprite and the code for the ball.
Code:
<frame> 50 flying
pic: 12 state: 3000 wait: 1 next: 50 dvx: 18 dvy: 18 centerx: 51 centery: 41 hit_a: 0 hit_d: 0 hit_j: 0
itr:
kind: 0 x: 22 y: 27 w: 55 h: 27 dvx: 10 dvy: -10 fall: 70 vrest: 10 bdefend: 16 injury: 15
itr_end:
bdy:
kind: 0 x: 22 y: 27 w: 55 h: 27
bdy_end:
<frame_end>RE: What's wrong with the code? - Hypermodder - 08-17-2008
lol
your prob is next: 50 and vrest: 10
no wonder the enemy cant move anymore, its like setting the vrest down to 1--
you need frame 51 at least, and you should set up the vrest to 20!
RE: What's wrong with the code? - vktewari - 08-17-2008
My problem isn't that. The problem is that the balls don't display properly. I think it's something with dvx and dvy.
RE: What's wrong with the code? - Silverthorn - 08-17-2008
oh, you want something similar to firzen's upper chase? you need a hit_Fa: 7.
RE: What's wrong with the code? - vktewari - 08-17-2008
Thanks BP, Problem is solved.