Nightly Builds Discussion for Modders/LPers/Players/etc.

[SupSuper]

Heads up to all the modders. Now when OpenXcom runs into something missing in a mod, like a sprite or an item or something, it will no longer just unexplicably crash. Instead it'll show a much more helpful "STR_FOO_BAR not found" message, and then crash. Hopefully that should help you find your typos more easily without me having to break out the debugger.

Anyways it's possible I've added too much error checking, so modders and players using mods, keep an eye out for any "not found" error messages that shouldn't be happening and report them please.

[Solarius Scorch]

How do we use builtInWeaponSets?

Because doing it the normal way, like:

Code: [Select]

    builtInWeaponSets:
      - STR_SNUBNOSE_PISTOL_CIV
      - STR_MAKAROV_CIV
      - STR_BERETTA_92FS_CIV
      - STR_GLOCK_18_CIV
      - STR_COLT45_CIV

doesn't work.

[KyronStarkiller]

Hey Scorch,
I have only seen multiple lines in the built in weapons work is in the equalterms 2.0 mod for new tanks.
In that mod it is listed as ...

builtInWeapons:
  - AUX_TANK_SMG
  - AUX_HWP_SMG
 
I edited my post I found in Migeul's pickup resistance mod also uses multiple listings in the builtInWeapons: field

[Yankes]

How do we use builtInWeaponSets?

Because doing it the normal way, like:

Code: [Select]

    builtInWeaponSets:
      - STR_SNUBNOSE_PISTOL_CIV
      - STR_MAKAROV_CIV
      - STR_BERETTA_92FS_CIV
      - STR_GLOCK_18_CIV
      - STR_COLT45_CIV

doesn't work.

because `builtInWeaponSets` is list of list:

Code: [Select]

    builtInWeaponSets:
      - - A
        - B
      - - AA
        - BA
With list will be chooses is based on current item level.

[Solarius Scorch]

because `builtInWeaponSets` is list of list:

Thanks. I suspected something like this, but there was no example to follow anywhere.

EDIT:

Another question:

Can someone please explain to me vanilla missionScripts?

Code: [Select]

  - type: recon
    firstMonth: 1

  - type: invasion
    firstMonth: 6

There is no reference to any missions or indeed anything except for the month. What do these scripts do?

[Meridian]

Can someone please explain to me vanilla missionScripts?

Code: [Select]

  - type: recon
    firstMonth: 1

  - type: invasion
    firstMonth: 6

There is no reference to any missions or indeed anything except for the month. What do these scripts do?

They generate standard vanilla missions from a mission table (which is in your save under "alienStrategy", generated at the start of the game, slowly shrinking, and regenerated after 2 years I think).

Documentation from the .rul file:

Code: [Select]

#    missionWeights:                     # the type of mission to spawn (omit to pick one from the mission table) (default none)


[Solarius Scorch]

OK, thanks. But how is this table defined? missionWeights in regions.rul?

(This is something I tried to find info on for, uh, I think two years by now.)

[Meridian]

Yes, the mission table is built from region ruleset.

[robin]

because `builtInWeaponSets` is list of list:

Code: [Select]

    builtInWeaponSets:
      - - A
        - B
      - - AA
        - BA
With list will be chooses is based on current item level.

Is this vanilla OXC or OXCE/OXCE+? seems vanilla OXC
Also, does the list of lists works in conjunction with alienItemLevels?

[Hobbes]

OK, thanks. But how is this table defined? missionWeights in regions.rul?

(This is something I tried to find info on for, uh, I think two years by now.)

https://www.ufopaedia.org/index.php/Alien_Missions_in_Enemy_Unknown_(OpenXcom)

[Meridian]

Is this vanilla OXC or OXCE/OXCE+? seems vanilla OXC
Also, does the list of lists works in conjunction with alienItemLevels?

It's vanilla OXC.
And yes, it works with alienItemLevels.

[robin]

It's vanilla OXC.
And yes, it works with alienItemLevels.

Ruleset reference says it picks a set randomly, but if it uses alienItemLevels it shouldn't be "random".
Sorry for being annoying, just want to know what is what before editing lots of stuff.

[Meridian]

Ruleset reference says it picks a set randomly, but if it uses alienItemLevels it shouldn't be "random".
Sorry for being annoying, just want to know what is what before editing lots of stuff.

I don't know who writes ruleset reference, I am looking only at the code.

Code says:
1. for XCOM vehicles... only the first item set is taken... others are ignored
2. for aliens... item set based on alienItemLevels probabilities for the current month is taken
3. for civilians... item set based on alienItemLevels probabilities for the current month is taken

https://github.com/SupSuper/OpenXcom/commit/e25e34575e11cc7c02027704e3b01ec43427c66a

There's always a small chance I may be wrong, for 100% certainty, ask Warboy

[robin]

I don't know who writes ruleset reference, I am looking only at the code.

Code says:
1. for XCOM vehicles... only the first item set is taken... others are ignored
2. for aliens... item set based on alienItemLevels probabilities for the current month is taken
3. for civilians... item set based on alienItemLevels probabilities for the current month is taken

https://github.com/SupSuper/OpenXcom/commit/e25e34575e11cc7c02027704e3b01ec43427c66a

There's always a small chance I may be wrong, for 100% certainty, ask Warboy

Thanks.

[SupSuper]

Just a heads up for modders, as of the 2018_07_08_2236 nightly, unit capturability (i.e. can they drop unconscious) is now defined by ruleset. This means every unit, even explodey ones, are now capturable by default unless you explicitly set them to "capturable: false".

On the bright side, you can now apply this to any unit!