Custom broken_weapon !fixed: reply if you want an explanation!

[JossuaDC]

I've fixed my work and am now able to create a custom broken_weapon without hex-editing the LF2 executable.

You guys want an explanation/example?

Original post. (Click to View)

Can someone explain the custom broken_weapon technique involving a weapon holding a weapon to me again? I get a lot of glitches whenever I give it a shot :/

Here's the 'custom broken_weapon' file I've been using:

Code:

<bmp_begin>
file(0-15): ######\######.bmp  w: 27  h: 28  row: 8  col: 2
weapon_hp: 1
weapon_drop_hurt: 1
<bmp_end>

<frame> 0 in_the_sky
   pic: 99  state: 2000  wait: 0  next: 1  dvx: 0  dvy: 550  centerx: 29  centery: 56
<frame_end>

<frame> 1 in_the_sky
   pic: 99  state: 2000  wait: 0  next: 2  dvx: 0  dvy: 550  centerx: 29  centery: 56
   opoint:
      kind: 1  x: 29  y: 26  action: 40  dvx: 2  dvy: -6  oid: 261  facing: 1
   opoint_end:
<frame_end>

<frame> 2 in_the_sky
   pic: 99  state: 2000  wait: 0  next: 3  dvx: 0  dvy: 550  centerx: 29  centery: 56
   opoint:
      kind: 1  x: 29  y: 26  action: 50  dvx: 3  dvy: -4  oid: 261  facing: 0
   opoint_end:
<frame_end>

<frame> 3 in_the_sky
   pic: 99  state: 2000  wait: 0  next: 4  dvx: 0  dvy: 550  centerx: 29  centery: 56
   opoint:
      kind: 1  x: 29  y: 26  action: 40  dvx: 3  dvy: -6  oid: 261  facing: 20
   opoint_end:
<frame_end>

<frame> 4 in_the_sky
   pic: 99  state: 2000  wait: 0  next: 5  dvx: 0  dvy: 550  centerx: 29  centery: 56
   opoint:
      kind: 1  x: 29  y: 26  action: 50  dvx: 4  dvy: -5  oid: 261  facing: 1
   opoint_end:
<frame_end>

<frame> 5 in_the_sky
   pic: 99  state: 2000  wait: 0  next: 1000  dvx: 0  dvy: 550  centerx: 29  centery: 56
<frame_end>

<frame> 10 on_hand
   pic: 2  state: 2001  wait: 0  next: 0  dvx: 0  dvy: 0  centerx: 29  centery: 56
   wpoint:
      kind: 2  x: 29  y: 56  weaponact: 35  attacking: 0  cover: 0  dvx: 0  dvy: 0  dvz: 0
   wpoint_end:
<frame_end>

<frame> 20 on_ground
   pic: 99  state: 2004  wait: 0  next: 1000  dvx: 0  dvy: 0  centerx: 29  centery: 51
<frame_end>

<frame> 21 just_on_ground
   pic: 99  state: 2000  wait: 1  next: 1000  dvx: 0  dvy: 0  centerx: 29  centery: 56
<frame_end>

<frame> 40 box01
   pic: 0  state: 9999  wait: 2  next: 41  dvx: 0  dvy: 0  centerx: 10  centery: 27  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 41 box02
   pic: 1  state: 2000  wait: 2  next: 42  dvx: 0  dvy: 0  centerx: 10  centery: 23  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 42 box03
   pic: 2  state: 2000  wait: 2  next: 43  dvx: 0  dvy: 0  centerx: 16  centery: 22  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 43 box04
   pic: 3  state: 2000  wait: 2  next: 40  dvx: 0  dvy: 0  centerx: 17  centery: 28  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 44 box11
   pic: 4  state: 2000  wait: 2  next: 45  dvx: 0  dvy: 0  centerx: 17  centery: 25  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 45 box12
   pic: 5  state: 2000  wait: 2  next: 46  dvx: 0  dvy: 0  centerx: 13  centery: 27  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 46 box13
   pic: 6  state: 2000  wait: 2  next: 47  dvx: 0  dvy: 0  centerx: 11  centery: 27  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 47 box14
   pic: 7  state: 2000  wait: 2  next: 44  dvx: 0  dvy: 0  centerx: 13  centery: 22  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>


<frame> 50 box21
   pic: 8  state: 2000  wait: 2  next: 51  dvx: 0  dvy: 0  centerx: 10  centery: 27  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 51 box22
   pic: 9  state: 2000  wait: 2  next: 52  dvx: 0  dvy: 0  centerx: 10  centery: 23  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 52 box23
   pic: 10  state: 2000  wait: 2  next: 53  dvx: 0  dvy: 0  centerx: 16  centery: 22  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 53 box24
   pic: 11  state: 2000  wait: 2  next: 50  dvx: 0  dvy: 0  centerx: 17  centery: 28  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 54 box31
   pic: 12  state: 2000  wait: 2  next: 55  dvx: 0  dvy: 0  centerx: 17  centery: 25  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 55 box32
   pic: 13  state: 2000  wait: 2  next: 56  dvx: 0  dvy: 0  centerx: 13  centery: 27  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 56 box33
   pic: 14  state: 2000  wait: 2  next: 57  dvx: 0  dvy: 0  centerx: 11  centery: 27  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

<frame> 57 box34
   pic: 15  state: 2000  wait: 2  next: 54  dvx: 0  dvy: 0  centerx: 13  centery: 22  hit_a: 0  hit_d: 0  hit_j: 0
<frame_end>

(The oid: 261 points towards this file. It summons the 'box' pieces.)

The two frames inside the actual weapon which summon the custom broken_weapon weapon (ASDHFGDS):

Code:

<frame> 150 ready_break
   pic: 5  state: 2004  wait: 0  next: 151  dvx: 0  dvy: 0  centerx: 58  centery: 75
<frame_end>

<frame> 151 break_prepare
   pic: 5  state: 2004  wait: 0  next: 17  dvx: 0  dvy: 0  centerx: 58  centery: 75
   opoint:
      kind: 2  x: 58  y: 75  action: 10  dvx: 0  dvy: 0  oid: 261  facing: 0
   opoint_end:
   wpoint:
   kind: 1  x: 58  y: 75   weaponact: 10  attacking: 0  cover: 1  dvx: 0  dvy: 0  dvz: 0
   wpoint_end:
<frame_end>

Wpoint used inside the actual weapon which holds the custom broken_weapon weapon:

Code:

wpoint:
   kind: 1  x: 58  y: 75   weaponact: 10  attacking: 0  cover: 1  dvx: 0  dvy: 0  dvz: 0
   wpoint_end:

My character currently needs 8 data files to run... Gotta find a way to shrink that number down to 6...

Edit: Some extra info:
The weapon summons the custom broken_weapon weapon and holds it just the way I want it to, but the box-pieces don't show up when the holding weapon is destoyed. Can you guys find the faulty code in my DC-work?

Edit2: The opoints in the 'in_the_sky'-frames don't function at all; will have to find a different way to opoint the box-pieces :/

[MH-Razen]

well, I`ve never heard of a broken weapon method without hex edit to be serious, but I might be able to help out with the activating broken weapon of a box - you can study klf2 for it.

In this stage there`re boxes filled with drinks, but they`re t5 objects and spawn the broken weapon - how? Well, I activated a frame inside the box-dat-file, this frame had state 3005 and pic 999 to hide it and a bdy on y: 1000, when I wanted to show the broken weapon I simply activated a itr with an injury higher the weapon health and on y: 1000 - the box will be destroyed, the broken weapon show up...

Hope this helps a bit...

[YinYin]

bluna has a custom broken weapon
julio has a custom broken weapon
the sandbag has a custom broken weapon

all with weapons holding another object - not necessarily a weapon
most important is that the broken action in that object starts at frame 0 - you can there put your animation/opointing

[MH-Razen]

bluna has a custom broken weapon
julio has a custom broken weapon
the sandbag has a custom broken weapon

all with weapons holding another object - not necessarily a weapon
most important is that the broken action in that object starts at frame 0 - you can there put your animation/opointing

wow, thats interesting, will have a closer look

[HappyHouR]

I updated the weapons guide. I saw you useing that thing but I didn't pay attention to that lol. Here I updated the guide.

http://www.lf-empire.de/forum/showthread.php?tid=3788

[JossuaDC]

bluna has a custom broken weapon
julio has a custom broken weapon
the sandbag has a custom broken weapon

all with weapons holding another object - not necessarily a weapon
most important is that the broken action in that object starts at frame 0 - you can there put your animation/opointing

Checked out Bluna; she uses the weapon-hit-ground-technique.
I need my weapon to be able to opoint the custom broken_weapon from the sky-frames.

I'll report back here if I get the opoint to work.

Edit: Oh, dear god... I'm an idiot. Thanks, YinYin; you've solved my problem.
When the original weapon disappears, the held weapon doesn't go to the sky-frames, but to a different set of frames.
Time to fix my stuff.

Edit2: Okay, I've fixed it. I might update my first post with the solution (and an example) if you guys wish me to.
Thanks are given to the legend of LF2; YinYin.

[naruto hyuuga]

i will like an explanation please

---

i would like an explanation please
Lol, twice power! - Simoneon

[JossuaDC]

[youtube]DpJRYotGlYI[/youtube]

[Simoneon]

To be honest, I don't think it is very realistic that coffin is bouncing like that.
But it's another story.

[JossuaDC]

To be honest, I don't think it is very realistic that coffin is bouncing like that.
But it's another story.

I know it's not realistic, but you do realise that this is just an example, right?
Absolutely - Simoneon