Skip to content

HD2Runtime ModBuilder v1.7.1

Choose a tag to compare

View all tags
@SkyeShade SkyeShade released this 09 Oct 04:17
· 1 commit to main since this release
v1.7.1
b35c779

HD2Runtime ModBuilder 1.7.1

HD2Runtime 0.30.3. ModBuilder now bundles the HD2Runtime 0.30.3 SDK (the published release asset). 0.30.2 resolved seven weapons that were read-only because each matched two weapons in the game data; their fields are now editable. 1.7.1 also authors what 0.30.2 added: sentry and emplacement rounds, status effects on player weapon explosions and 23 more status effects. Backpack-fed ammunition rows are read-only now, with HD2Runtime's reason. Custom stratagems can be given unlimited uses clearly (HD2Runtime 0.30.3). The project format does not change.

Download: HD2Runtime-ModBuilder-v1.7.1-win-x64.zip (Windows 10/11 x64). Extract it and run HD2RuntimeModBuilder.exe, or use Install update from any earlier version. The ZIP now also contains LICENSE, TRADEMARKS.md and THIRD_PARTY.md.

New projects bind to HD2Runtime 0.30.3. Projects bound to 0.30.0 (ModBuilder 1.7.0), 0.30.2 or the 0.30.0-dev test SDK keep their binding and export exactly as before until you Rebind them; rebinding keeps every edit. An export requires the bound SDK's Runtime, raised where the project uses something newer (below). HD2Runtime 0.30.3 also fixes two Runtime problems players reported with 0.30.2: a false Another mod changed the stratagem data card, and one stray entity row that blocked every mod's writes.

HD2Runtime 0.30.2 and 0.30.3

  • Seven weapons unlocked. The GP-31 Grenade Pistol, P-72 Crisper, LAS-5 Scythe, LAS-7 Dagger, CQC-42 Machete, CQC-73 Entrenchment Tool and SMG-37 Defender were read-only (each matched two weapons in the game data). Their fields are now editable. A mod that edits one of them requires HD2Runtime 0.30.2. The GP-31 and the Dagger now show their own values (the Dagger's old 2000 heat capacity belonged to another weapon). The Scythe's heat capacity and heatsinks stay read-only: its default Laser Heatsink overwrites them.
  • Renamed weapon sounds. primary/smg37/seaf is now seaf/3 and secondary/gp31/alt is now other/wep_grenadier_rifle/1. A custom stratagem saved with an old name shows the problem under its sound field, with a button to use the new name. HD2Runtime still plays the old names. The new names require HD2Runtime 0.30.2.
  • Retired projectile. SMG-37 Defender (projectile 150) was the SEAF SMG's round, so 0.30.2 removed it from the projectile list (31 donors). A swap to it is reported at its projectile selector after a rebind; pick another projectile or the weapon's own.
  • Minimum Runtime. Exports of projects bound to 0.30.3 require HD2Runtime 0.30.3. On an older binding, each feature asks for the release that added it: 0.30.2 for the seven weapons, the new sound names, sentry and emplacement rounds and the status effects below; 0.30.3 for a custom stratagem that keeps an explicit unlimited uses value (below). Custom content otherwise still requires 0.30.0.

Sentry and emplacement rounds

  • Stratagems › Defensive: the A/AC-8, A/M-12, A/MLS-4X, A/M-23 and A/GM-17 sentries and the E/MG-101 and E/AT-12 emplacements have a Fired round section to fire another projectile.
  • The swap changes every sentry of that stratagem on your machine, teammates' too (other machines keep the stock round). A sentry still aims for its own round: the section shows both rounds' speed and warns that it may miss.
  • Not live-tested; the opt-ins are written for you. The A/MG-43 and A/G-16 stay read-only. Requires HD2Runtime 0.30.2. ModBuilder 1.7.0 refuses to build a project that holds one (it names the host) rather than dropping it.

Status effects

  • On explosions. The explosion of 13 player weapons (CB-9, GL-15, GP-20, GP-31, P-33, P-34, P/40-K, PLAS-1, PLAS-101, PLAS-15, PLAS-39, R-36, SG-8P) can apply a status: pick it and its strength on the explosion row (Player Weapons, impact actions). Set the PLAS-101 Purifier's charged blast to Fire, strength 2, for HD2Runtime's own PurifierIncendiaryCharge test. Not tested in game yet: the export writes allow_unverified_effect (and allow_shared on the four shared rows) and requires HD2Runtime 0.30.2.
  • 23 more status effects. Every status picker (player weapons, support weapons, mounted weapons) now offers HD2Runtime 0.30.2's extended statuses, grouped as Attachable, Enemy slot (unverified) and Experimental (blind, bleed, electric, poison, …). Choosing one shows Runtime's text for its group (bleed lasts 9999 s). None is tested in game: the export writes allow_unverified_effect for it, even on rows that need no opt-in for the other statuses, and requires HD2Runtime 0.30.2.

Backpack-fed ammunition rows

  • The AC-8 Autocannon's spare, starting and supply rounds, and the starting and spare magazines of the GR-8 Recoilless Rifle, FAF-14 Spear, RL-77 Airburst Rocket Launcher and StA-X3 W.A.S.P. Launcher, are now read-only, with HD2Runtime's reason: these weapons keep their ammunition in their backpack, so a value there has no effect in game.
  • Above the rows, Show the backpack opens the drop-pod slot that delivers it. HD2Runtime keeps that backpack's ammunition read-only too.
  • A project that already edits one of these rows keeps the edit, and it is still exported unchanged (HD2Runtime accepts it). The row shows the saved value, with Remove this edit and Show the backpack, and the Changes entry shows how many such edits it has.

Custom stratagems: unlimited uses

  • Uses per mission in a custom stratagem's call-in is now a choice: Unlimited or Limited with a count (1 to 100). Unlimited writes no uses value, which every HD2Runtime 0.30 release reads as unlimited, as before. Typing 0 as the count also means unlimited.
  • HD2Runtime 0.30.3 also accepts uses = 0 and uses = -1 as unlimited. A Runtime project imported with one of them keeps it, so it round-trips. The field then says that this value requires HD2Runtime 0.30.3 (0.30.2 refuses it) and offers Use unlimited (no value), which removes the requirement. Below -1 is refused, in Runtime's words.
  • An Eagle's uses stay per rearm, as before.

Project format and compatibility

  • No format change. Projects stay at format 14, as with 1.7.0. Projects bound to 0.30.0 or the 0.30.0-dev test SDK open, save and export as before.
  • ModBuilder 1.7.0 cannot open a project bound to 0.30.2 or 0.30.3 (it supports SDKs up to 0.30.0).

Unchanged

  • Projects bound to an earlier SDK generate the same Lua and export the same ZIPs as with 1.7.0, apart from the ModBuilder version recorded in build-report.json (as in every release).
  • Custom projectiles, in-game options, additional packaged files and the import of projects are unchanged from 1.7.0.
Assets 6
Loading