[solved] Fall

[RenanDez]

I need change Fall of charcters to 2 frames
Maintaining Dash and others patterns
I'dont know if question DC

example:

[MH-Razen]

and I don't know what you mean.

If you want less frames to use for fall just set the next: 999 one frame earlier, but this might cause bugs, not sure.

dash and other patterns? to be a bit more concrete isn't you thing eh?

example: oh nice, this solved all my questions.

Please give more details...

[vandesdelca]

i think he want to make his char only use 2 frames for the falling.
and dash, jump, walking,etc. but... i know why'd u post this, maybe it's cuz u think u have TO delete some of the basic datas AND renumber them all...
things like this really annoy me some time...

[RenanDez]

The jump use the pic 60, 61 and 62
fall use pic 62 i need other pic

[Simoneon]

The jump use the pic 60, 61 and 62
fall use pic 62 i need other pic

If You need other pic just make it on grid, like: 63 , and then make pic: 63 in the frame

[Boop]

Moved to DC section, feel free to move it back if you think this is somehow related to hex editing(you need to give proper reasoning ).

[Silverthorn]

I honestly don't think that you can alter the sequence in any way by DCing. Fact is, the falling-frames aren't linked to each other, instead, they are linking to themselves (next: 0). This means, the sequence is hard-coded. If anybody can prove me wrong, feel free to do so but I'm quite certain that it's impossible without hex-editing. That's the first thing I got out of your first post.

The second thing (the one which you probably mean) is this frame:

DC-Code: <frame> 212 jump pic: 62 state: 4 wait: 1 next: 0 dvx: 0 dvy: 0 dvz: 0 centerx: 39 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0 bpoint: x: 43 y: 27 bpoint_end: wpoint: kind: 1 x: 25 y: 37 weaponact: 34 attacking: 0 cover: 0 dvx: 0 dvy: 0 dvz: 0 wpoint_end: bdy: kind: 0 x: 31 y: 15 w: 21 h: 64 bdy_end: bdy: kind: 0 x: 18 y: 29 w: 48 h: 17 bdy_end: <frame_end>

And you want to expand this frame into two frames, right? Well, check this:

DC-Code: <frame> 212 jump pic: 62 state: 4 wait: 1 next: 300 dvx: 0 dvy: 0 dvz: 0 centerx: 39 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0 bpoint: x: 43 y: 27 bpoint_end: wpoint: kind: 1 x: 25 y: 37 weaponact: 34 attacking: 0 cover: 0 dvx: 0 dvy: 0 dvz: 0 wpoint_end: bdy: kind: 0 x: 31 y: 15 w: 21 h: 64 bdy_end: bdy: kind: 0 x: 18 y: 29 w: 48 h: 17 bdy_end: <frame_end>   <frame> 300 jump pic: 28 state: 4 wait: 1 next: 301 dvx: 0 dvy: 0 dvz: 0 centerx: 39 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0 bpoint: x: 43 y: 27 bpoint_end: wpoint: kind: 1 x: 25 y: 37 weaponact: 34 attacking: 0 cover: 0 dvx: 0 dvy: 0 dvz: 0 wpoint_end: bdy: kind: 0 x: 31 y: 15 w: 21 h: 64 bdy_end: bdy: kind: 0 x: 18 y: 29 w: 48 h: 17 bdy_end: <frame_end>   <frame> 301 jump pic: 0 state: 4 wait: 1 next: 300 dvx: 0 dvy: 0 dvz: 0 centerx: 39 centery: 79 hit_a: 0 hit_d: 0 hit_j: 0 bpoint: x: 43 y: 27 bpoint_end: wpoint: kind: 1 x: 25 y: 37 weaponact: 34 attacking: 0 cover: 0 dvx: 0 dvy: 0 dvz: 0 wpoint_end: bdy: kind: 0 x: 31 y: 15 w: 21 h: 64 bdy_end: bdy: kind: 0 x: 18 y: 29 w: 48 h: 17 bdy_end: <frame_end>

I just took frame 300&301 because they weren't used yet. By altering the pic-numbers, you'll see that it works flawlessly (at least I haven't discovered any bug so far).

[RenanDez]

I tried long time
the next that frame 212 Don't working
Is a HEX question

[Silverthorn]

I tried long time
the next that frame 212 Don't working

I actually tested this (which I usually never do) and it works flawlessly.

[RenanDez]

Sorry, I'am wrong
works flawlessly³