Skip to content

HD2Runtime ModBuilder v1.6.0

Choose a tag to compare

View all tags
@SkyeShade SkyeShade released this 03 Oct 03:11
· 3 commits to main since this release
v1.6.0
0213552

HD2Runtime ModBuilder 1.6.0

In-game options without a value change. Any field that can be an in-game option can now be exposed without editing its value first. Example: the missiles of the TD-110 Maelstrom can get a Mod Options Menu slider while the mod leaves them vanilla, and players change them in game. This is a ModBuilder feature only: HD2Runtime and its SDK are unchanged, because Runtime already accepts an option value equal to the expected (vanilla) value.

Download: HD2Runtime-ModBuilder-v1.6.0-win-x64.zip (Windows 10/11 x64). Extract it and run HD2RuntimeModBuilder.exe, or use Install update from any earlier version.

New projects require HD2Runtime 0.28.1, the same as 1.4.2 to 1.5.0. The bundled SDK is unchanged. Projects bound to an older SDK keep requiring that SDK's Runtime until you rebind them. In-game options need HD2Runtime SDK 0.25 or later, as before.

In-game options

  • Expose as option on unedited fields. With in-game options switched on, an unedited field row shows Expose as option when you point at it or tab into it. This covers player weapons, projectile and explosion fields, support weapons, stratagems, vehicles and their mounted weapons, backpacks, boosters, magazine attachments, throwables and enemies. Saving the option adds the field's edit and its option in one save; Cancel adds nothing.
  • Option-only edits. The edit keeps the vanilla value. Only the option changes it in game. The field row looks unedited and shows the In-game option badge. The option editor says Vanilla N, not edited: only the in-game option changes it.
  • Defaults. The suggested slider defaults to vanilla. It runs over Runtime's published safe range where there is one, and from half to double the vanilla value otherwise. A choice starts as Default (vanilla, selected) and Modified (the slider's far end).
  • Generated Lua. The same guarded operation as an edited field: hd2.ensure({enabled=enabled, patch={..., expect=<vanilla>, value=option_<id>}}), with the same allow_* flags. Without Mod Options Menu, players get the option's default (vanilla unless you change it).
  • Keeping and removing.
    • Stop exposing (or Remove on the options page) removes the edit with the option.
    • Reset on an edited field removes the edit and leaves the option row inactive, as before.
    • Typing the vanilla value back into an exposed field keeps its option, so the field becomes an option-only edit.
    • With in-game options switched off, option-only edits stay in the project and generate nothing.
  • Shared values keep their rules.
    • The Maelstrom's two missile pods are one mounted weapon, so a weapon-level value (magazine capacity, for example) can be edited or exposed through one pod only. Exposing it on the second pod is refused in the option editor, naming the first.
    • A pod's missile damage is published as a shared damage row: its other consumers are the other pod and the MLS-4X Commando. Its option carries the same warnings and the allow_shared / allow_unverified_effect flags as an edit.
  • Checked with HD2Runtime 0.28.1's own export validator: an export with option-only edits on a Maelstrom missile pod, an AR-23 Liberator weapon field and projectile field, and an Orbital Precision Strike field validates with every operation resolved against its vanilla baseline.

Project format and compatibility

  • Existing projects stay compatible. They open, save and export as before and keep their SDK binding and format. Projects saved by ModBuilder 1.4.2 itself still open without being rewritten and export the same ZIPs, apart from the builder version in build-report.json.
  • A project with an option-only edit saves in format 13. The JSON shape is unchanged, but earlier ModBuilder versions remove edits whose value equals vanilla when they open a project, which would drop the option's operation silently. So every earlier version refuses a format-13 project with Unsupported project format or identity. and leaves the project file untouched. Like earlier formats, a project stays in format 13 after its option-only edits are removed.

Unchanged

  • Projects without option-only edits generate the same Lua and export the same ZIPs as with 1.5.0, apart from the ModBuilder version recorded in build-report.json (as in every release).
  • Options on edited fields, the master toggle, the fallback without Mod Options Menu and the generated options page are unchanged. The bundled HD2Runtime 0.28.1 SDK, project SDK bindings and the import of projects are unchanged.
Assets 6
Loading