alf2 - current state: fire/ice affinity exception

[mfc]

Have another idea for weapon:

1) Freeze has a special body on his frame 200. (ice frame, normally it has a wait: 2)
2) Weapon7, opoints a type-3 ball tike this:

DC-Code: <frame> xxx catcher_ball pic: 999 state: 3005 wait: 2 next: 1000 dvx: 0 dvy: 0 dvz: 0 centerx: 0 centery: 0 itr: kind: 3 x: 0 y: 6000 w: 1 h: 80 vrest: 7 catchingact: 1000 1000 caughtact: 0 0 itr_end: <frame_end>

2.a) The problem is; "In which frames weapon7 opoints this ball?"
2.a.1) Normally it should be frame 24 for a type1 object.
2.a.2) But everychar uses weaponact: 24 even when they don't attack.
2.a.3) For example louis.dat; frame 101; rowing frames uses weaponact: 24.
2.b) How can we stop this?
2.b.1) We can create a fake on_hand frame for every type1 object.
2.b.2) And we can change the "weaponact: 24" of all the characters in their "normal_weapon_atck, jump_weapon_atck, run_weapon_atck, dash_weapon_atck"

If we can do these these will happen:

i dont know whether that can get us up to 4 different reactions - but even if, the sword will still lag on every swing

1) This problem will be solved because we didn't changed any itrs.
2) Freeze will be quick frozen, caught and dropped. So it can be a cool exception for weapon.
3) It doesn't matter if another char uses the weapon. It will act same for everychar.

If we want to leave freeze in standing frames;

yes its possible to do that but it will only work properly for chars of the same height (79 because most have that)
julian and knight will cause problems
basically because using a vaction that doesnt have a cpoint will act as if its cpoint is at x: 0 y: 0

So i wish it helps...

---

And i have a little question:
Do you want your flame to hurt teammates?