[Nightly Build] HWP Issues

[KingMob4313]

Right now I'm working on porting my (unreleased) Equal Terms 2.0 mod over to the new nightly and I've encountered some full on weirdness.

All of the sudden when I start a mission, I can equip the tank as if it's a soldier. This, of course, jacks up the built in weapons and all the rest.

This yaml code worked just fine previously, anyone have any idea what could have changed?  Getting the two weapons working on a tank always was a semi hack, it seemed, so it might be involving that.

[new_civilian]

You have to add allowinv: false or something to the armor, should be in the newest wiki

[KingMob4313]

You have to add allowinv: false or something to the armor, should be in the newest wiki

Okay, I will do a scan and see what I did wrong.

[KingMob4313]

Hmm, I'm using     

Code: [Select]

    allowInv: false
    builtInWeapons:
      - STR_TANK_GMG
      - AUX_TANK_GLAUNCHER
      - STR_HWP_GMG
      - AUX_HWP_GLAUNCHER
on the units and

Code: [Select]

    fixedWeapon: true
On the 'items' list for the weapon. Still no go.

[KingMob4313]

An oddity:

I can't go into the equip once the map has started, but during the equip phase is where the problem pops up.

I'm running a nightly so I see the getBuiltInWeapons() method being fired in debug by the yaml...

I have to be missing something easy, but neither builtInWeapons or allowinv is covered in the wiki....

[Hobbes]

I had the same problem with my improved HWPs and it was solved by "allowInv: false" added to the relevant armor entry. However, I've just checked my ruleset and builtinWeapons should be under the relevant items entry, not armor.

[KingMob4313]

I had the same problem with my improved HWPs and it was solved by "allowInv: false" added to the relevant armor entry. However, I've just checked my ruleset and builtinWeapons should be under the relevant items entry, not armor.

Ah, okay, I'm digging into the X-Piratez mod and seeing how it's done there. I remember that there was some issues with getting secondary ammo to work on the auxillary weapon, but I was pretty sure I had it working on the previous version, but it may have been due to some fragility. 

Seems that Diox uses 'builtInWeapons:' at the unit level and... allowInv: false on the armor

Gonna try what you proposed, maybe that will clear it up.

[KingMob4313]

I had the same problem with my improved HWPs and it was solved by "allowInv: false" added to the relevant armor entry. However, I've just checked my ruleset and builtinWeapons should be under the relevant items entry, not armor.

Bawooop, got something. It's showing the automatic grenade launcher in both spots, but seems to be tracking ammo separately for each 'hand', I can probably work from here.

Thanks for the fix, man!

[KingMob4313]

Bawooop, got something. It's showing the automatic grenade launcher in both spots, but seems to be tracking ammo separately for each 'hand', I can probably work from here.

Thanks for the fix, man!

Even fixed the last issue: just needed the aux weapon and ammo in the builtInWeapons: section and now even the secondary weapons take ammo.

Hobbes (and by proxy, Diox) thanks for all the help.

[Solarius Scorch]

...are you suffering from multiple personality issues?

[Arthanor]

Actually, this "one person conversation" proved quite useful for me as I am trying to update the XAE

@KingMob: So builtInWeapons indeed changed to items instead of units? That's kind of weird.. Especially since I'm pretty sure my dogs are working as intended, despite being essentially 2 weapons HWP with their builtInWeapons defined in units.

[KingMob4313]

...are you suffering from multiple personality issues?

...We are still building a consensus.

[KingMob4313]

Actually, this "one person conversation" proved quite useful for me as I am trying to update the XAE

@KingMob: So builtInWeapons indeed changed to items instead of units? That's kind of weird.. Especially since I'm pretty sure my dogs are working as intended, despite being essentially 2 weapons HWP with their builtInWeapons defined in units.

That's what seems to have fixed it for me.  The other issue I was having was creating a BigObs for my HWP ammo so it could appear in my ufopedia entries now leaves them on the floor.... Which on further review makes perfect sense and is expected behavior.

[Arthanor]

Create a "dummy version" with the same power and the BigOb you intend to use, the article of which is unlocked exactly at the same time as the ammo, and the user will never know.

That's a trick I intend to use for weapons with more than 3 ammos as well. You unlocked the 2nd article  with any of the 4th+ ammo, in the same way the plasma cannon is unlocked by either the rifle or heavy).

Say heavy cannon:

Normal Heavy Cannon ufopaedia:
HC-AP
HC-HE
HC-I

Dummy Heavy Cannon ufopaedia (unlocked by either HC-A or HC-El):
HC-Alloy
HC-Elerium

Now you have a 2 pages UFOPaedia for the Heavy Cannon, showing the "same" weapon (the dummy having the same stats as the original), but different ammo and different text.

[Hobbes]

@KingMob: So builtInWeapons indeed changed to items instead of units? That's kind of weird.. Especially since I'm pretty sure my dogs are working as intended, despite being essentially 2 weapons HWP with their builtInWeapons defined in units.

My improved HWPs were working fine until a month or two ago, then they started appearing on the equip screen and I had to change the settings (I also asked on the forums I think, I can't remember who provided me with the answer, unfortunately), so yes, something was changed most likely due to TFTD integration.