Contract Blade 1.0.0 — Stable Release

Contract Blade has officially left beta. Version 1.0.0 focuses on contract reliability, NBT safety, data migration, and a more stable maid deployment experience.

Highlights

• Added stable contract manifestation and recall systems.
• Added support for intrinsic weapon spirits, including Akatsuki from Blade Tetra.
• Added contract resonance progression and combat integration.
• Improved compatibility with modular weapons, SlashBlade, Tetra, and Touhou Little Maid.
• Added comprehensive safeguards against oversized and recursive contract NBT.

NBT Storage Improvements

• Active intrinsic contracts now use a single authoritative copy of their maid data.
• Removed the duplicate full contract previously stored in both the active projection and intrinsic archive.
• Sleeping intrinsic contracts are moved safely back into their archive.
• Switching between an intrinsic spirit and an ordinary external contract no longer mixes their data.
• Existing saves containing duplicate projected contracts are migrated automatically.
• During migration, the active root contract is preferred because it is more likely to contain the latest maid state.

Compressed Maid Data

• MaidEntityData is now stored in a versioned compressed format.
• Added checksum and uncompressed-size validation.
• Added bounded decompression to protect against malformed data and compression bombs.
• Legacy uncompressed maid data is migrated automatically.
• Original data is retained if compression, validation, or migration fails.
• A failed operation will not silently delete the maid, weapon contract, inventory, model, favorability, or combat progress.

In testing, a fully upgraded modular contract weapon with a filled maid inventory was reduced to approximately 13.5 KiB of total item data, with the maid payload compressed from 16.3 KiB to approximately 5.0 KiB.

NBT Diagnostics

• Added tiered warnings at approximately:

  • 256 KiB
  • 512 KiB
  • 1 MiB

• Warnings are informational and do not prevent maid recall.

• Added /maidweapon nbt for inspecting the held item.

• The audit reports:

  • Complete serialized item size
  • Item tag size
  • Maid data size before compression
  • Compressed maid payload size
  • Intrinsic contract archive size
  • External contract archive size
  • Active projection identity
  • Duplicate-projection status

Anti-Recursion Protection

• Preserved and strengthened protection against placing a contract weapon inside the inventory of its own bound maid.

• This prevents recursive storage chains such as:

  Weapon → MaidEntityData → Maid Inventory → Same Weapon

• The weapon is returned to the player before the maid is serialized.

Reliability Improvements

• Contract capture is now transactional: the maid is removed only after her data has been encoded and verified successfully.
• Deployment failures retain the stored contract for a later retry.
• Corrupted or unsupported compressed data is rejected without clearing the original contract.
• Intrinsic-spirit ensure, activation, sleep, and migration operations remain idempotent.
• Repeated activation and sleep cycles no longer cause continuous NBT growth.
• Improved recovery behavior during deployment, recall, death, and weapon switching.
• Preserved maid inventories, capabilities, appearance models, favorability, ownership, and combat progression across contract transitions.

Compatibility

Designed for:

• Minecraft 1.20.1
• Forge 47.4.x
• Touhou Little Maid
• Blade Tetra 1.2.0
• SlashBlade: Resharped 1.9.63 and later

Updating from a Beta Version

Back up your world before updating.

Existing contracts are migrated automatically when they are accessed. Do not remove the weapon or interrupt the server while testing the first deployment and recall after upgrading.

For important contracts, we recommend the following after updating:

1. Hold the contract weapon.
2. Run /maidweapon nbt.
3. Confirm that the audit displays [Single Authority].
4. Deploy and recall the maid once.
5. Save and restart the world, then verify the maid’s inventory, model, favorability, and contract progress.

Notes

Contract Blade can greatly reduce its own NBT footprint, but it cannot bypass Minecraft’s overall network NBT limits. Avoid placing very large numbers of complex contract weapons inside a single backpack or portable container that serializes all contents into one item tag.