+- 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] arrow problem (/showthread.php?tid=3657)
[solved] arrow problem - NoneX - 09-21-2009
viedeo/
I have made an viedeo, so its easier to understand.
I want to make an move that arrows fall down, but when they fall down some of then disapear what could be the problem ^^
Code:
<frame> 310 fly_arrow
pic: 10 state: 3 wait: 1 next: 311 dvx: 0 dvy: 0 dvz: 0 centerx: 38 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0 mp: 100
bdy:
kind: 0 x: 26 y: 12 w: 27 h: 68
bdy_end:
<frame_end>
<frame> 311 fly_arrow
pic: 11 state: 3 wait: 1 next: 312 dvx: 0 dvy: 0 dvz: 0 centerx: 32 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0
bdy:
kind: 0 x: 15 y: 5 w: 35 h: 73
bdy_end:
<frame_end>
<frame> 312 fly_arrow
pic: 12 state: 3 wait: 1 next: 313 dvx: 0 dvy: 0 dvz: 0 centerx: 31 centery: 78 hit_a: 0 hit_d: 0 hit_j: 0
sound: data\022.wav
bdy:
kind: 0 x: 9 y: 9 w: 35 h: 71
bdy_end:
bdy:
kind: 0 x: 23 y: 36 w: 41 h: 16
bdy_end:
<frame_end>
<frame> 313 fly_arrow
pic: 13 state: 3 wait: 20 next: 314 dvx: 0 dvy: 0 dvz: 0 centerx: 36 centery: 78 hit_a: 0 hit_d: 0 hit_j: 0
bdy:
kind: 0 x: 24 y: 10 w: 33 h: 68
bdy_end:
bdy:
kind: 0 x: 28 y: 34 w: 42 h: 19
bdy_end:
<frame_end>
<frame> 314 fly_arrow
pic: 13 state: 3 wait: 15 next: 315 dvx: 0 dvy: 0 dvz: 0 centerx: 36 centery: 78 hit_a: 0 hit_d: 0 hit_j: 0
sound: data\024.wav
opoint:
kind: 1 x: 50 y: 100 action: 40 dvx: 15 dvy: -20 oid: 233 facing: 200
opoint_end:
<frame_end>
<frame> 315 fly_arrow
pic: 14 state: 3 wait: 15 next: 316 dvx: 0 dvy: 0 dvz: 0 centerx: 35 centery: 78 hit_a: 0 hit_d: 0 hit_j: 0
opoint:
kind: 1 x: 50 y: 100 action: 40 dvx: 15 dvy: -17 oid: 233 facing: 200
opoint_end:
<frame_end>
<frame> 316 fly_arrow
pic: 14 state: 3 wait: 15 next: 317 dvx: 0 dvy: 0 dvz: 0 centerx: 35 centery: 78 hit_a: 0 hit_d: 0 hit_j: 0
opoint:
kind: 1 x: 50 y: 100 action: 40 dvx: 15 dvy: -14 oid: 233 facing: 200
opoint_end:
<frame_end>
<frame> 317 fly_arrow
pic: 14 state: 3 wait: 15 next: 318 dvx: 0 dvy: 0 dvz: 0 centerx: 35 centery: 78 hit_a: 0 hit_d: 0 hit_j: 0
opoint:
kind: 1 x: 50 y: 100 action: 40 dvx: 15 dvy: -10 oid: 233 facing: 200
opoint_end:
<frame_end>
<frame> 318 fly_arrow
pic: 14 state: 3 wait: 15 next: 999 dvx: 0 dvy: 0 dvz: 0 centerx: 35 centery: 78 hit_a: 0 hit_d: 0 hit_j: 0
opoint:
kind: 1 x: 50 y: 100 action: 40 dvx: 15 dvy: -5 oid: 233 facing: 200
opoint_end:
<frame_end>RE: arrow problem - SirFrog - 09-21-2009
Eh, hard to know without the code, so please post it. And do post it in [code ]-tags.
RE: arrow problem - NoneX - 09-21-2009
done
thanks totally forgot about this
RE: arrow problem - x90z75ek - 09-21-2009
There's no problem here. The problem is in the code of the arrows since they all appeared and flied in the air like they should.
RE: arrow problem - Madara Uchiha - 09-21-2009
Frame 60 is the hitting the ground frame. Just make the hitting the ground arrow frames on there, then change the ball to a type 1 to make sure it hits the ground probably.
If you want something to disappear, use state 1000.
RE: arrow problem - no one - 09-21-2009
What type did you use? If it's type 3 then change it to light weapon type then adjust the on_ground/just_on_ground frame.
And why did you use next: 999 in the last frame? It suppose to be 1000.
RE: arrow problem - NoneX - 09-21-2009
Yes i used type: 3, but now it works so i wont change it
I used next: 999 because i am a noob ^^ THX I will change it
RE: arrow problem - TheNave - 09-21-2009
(09-21-2009, 03:36 PM)no one Wrote: What type did you use? If it's type 3 then change it to light weapon type then adjust the on_ground/just_on_ground frame.
And why did you use next: 999 in the last frame? It suppose to be 1000.
uhm, that code he posted belongs to henry, not the arrows, so changing it to next: 1000 would be a bad idea^^
RE: arrow problem - Madara Uchiha - 09-22-2009
Sorry not state 1000, next 1000. Just make the ball have a wait 9999 or something. Also, if the ball changes or something, just change the waits.