Guide to Expansive Weaponry's API Targets

Latest API version: 1.1.0

Last updated on March 21st, 2023

Expansive Weaponry specifies an internal API version, which is compared to the target version specified in a content pack's exwpack.info file. This process verifies that any changes made in Expansive Weaponry's API are compatible with the content pack being loaded.

For example, if a new feature is added in a future release, like for instance support for OBJ weapons, the API version would be increased to 1.1.0, indicating that a backwards-compatible feature has been added. However, if a future release dropped support for Toolbox models, the API version would be updated to 2.0.0, indicating a breaking change.

v1.0.0 - v1.0.1		v1.0.2 - v1.0.6					v1.0.7 - v1.1.0				v1.1.1 - v1.1.2		v1.1.3
~~Modulus Transition~~		~~N/A~~					~~Build Revision 0~~				Target API 1.0.X		Target API 1.1.X

Transition State	Content Pack Status
Modulus	Expansive Weaponry v1.0.0 - v1.0.1 Modulus content packs have to be recompiled under the new package name.
v1.0.2 - v1.0.6	Expansive Weaponry v1.0.2 - v1.0.6 Expansive Weaponry's mod ID has been changed from `modulus` to `exw`. Assets will no longer load in old content packs. Content packs have to be recompiled for v1.0.5 or newer.
Build Revision 0	Expansive Weaponry v1.0.7 - v1.1.0 No breaking changes, most content packs will work fine.
Target API 1.0.X	Expansive Weaponry v1.1.1 - v1.1.2 Introduces new API enforcement. Content pack authors going forward will be required to specify a targeted API version, to ensure the version of Expansive Weaponry a player is using will work with their content pack. Old content packs will continue to work even with no changes for the near future.
Target API 1.1.X	Expansive Weaponry v1.1.3 Adds support for tanks, fully compatible with API 1.1.X. Content packs with a valid `exwpack.info` can now be loaded from the mods folder.