v3.3.0

3.3.0 - Public API and Husbandry Runtime Update - 2026-08-30

Added

• Added the stable 2.0.0 public Java API contract. It includes custom command page and command HUD renderers, namespaced contributors, partial-update hints, command-page actions and flows, redacted diagnostics, and standard UI fallback.
• Added a durable population-group owned count for integrations that must include unloaded, dead, and lost companions in capacity checks.
• Generic command panels can permanently abandon owned companions. This releases their durable owner capacity and tool links, including when the companion is unloaded, dead, or lost.
• Managed activity profiles can map authorized TameworkCullNpc item interactions to a domestic drop list and a tamework:cull_success Activity V2 event. Profiles that omit the mapping keep the normal cull death drops and publish no cull activity.
• Revised the capability-gated husbandryOutcomes() API. One optional provider can adjust needs decay, happiness disposition, harvest and cull output, and parent breeding cooldowns. Tamework keeps ownership of random rolls and game-state changes.

Changed

• Prerelease API change: the Husbandry outcomes contract is now 2.0.0. Providers built against the earlier development preview must replace CARE_RESTORATION and PRODUCT_BONUS with the new outcome kinds and use the five-field HusbandryOutcomeModifiers record. The preview's four-field constructor and old multiplier accessors are not part of the released API.
• Clearing a companion owner through the owner-population transition now commits the terminal RELEASED lifecycle and clears its durable capacity claims and command-tool links in the same transaction.
• Companion harvests, passive animal products, filled containers, and cull rewards now share one finalized-output boundary before Activity V2 reports their produced item quantities.

Fixed

• Companion attack and defend sensors no longer remove the companion when the marked owner is a player. Threat checks now use the candidate NPC's attitude toward the owner.
• Revive-ready updates now correlate replacement death snapshots with the current lifecycle revision. Interrupted updates no longer block Tamework startup because of a stale snapshot revision.
• Dead companions now release deployed capacity. Companions affected by the older stale-capacity behavior can revive without a database reset.
• Managed companions can now revive through owner-scoped capacity admission.
• Revival failures now identify the failed stage and write the diagnostic cause to the server log.
• Owner-clearing capture items can capture both ordinarily tamed companions and managed-admission companions without failing lifecycle admission.
• Captured companions that predate population-group classification can now create their first managed group assignment when released.
• Dead managed companions that predate population tracking can now initialize their group and owned or deployed domain claims when revived.