## [3.4.8] -
### Summary
The **"Categorical Mastery"** update. Reorganized the GameRule configuration UI into themed categories for improved usability and organization.
- **Themed Categorization**: Reorganized all 50+ GameRules into 6 distinct categories:
- **VO: Better Dogs - War**: Territorial matrix and rivalry settings.
- **VO: Better Dogs - Litter**: Breeding genetics and litter size rules.
- **VO: Better Dogs - Health**: HP, speed, and damage modifiers.
- **VO: Better Dogs - Social**: AI behaviors, howling, and follow distances.
- **VO: Better Dogs - Spawning**: Cluster sizes.
- **VO: Better Dogs - General**: Utility toggles and environmental reactive rules.
- **Localization**: Added full support for the new category labels in both English (`en_us`) and Indonesian (`id_id`).
- **⚠️ Mandatory Warning**: Your gamerule might be reseted as I split it into many category and i changed stuff.
## [3.4.7] - 2026-05-16
### Summary
Finalized the architectural transition to strict Protocol standards, resolving configuration data loss and logic hoarding.
- **Registry Namespacing**: Refactored all custom GameRules to use the `vanilla-outsider-better-dogs` namespace (e.g., `vanilla-outsider-better-dogs:bd_storm_anxiety`). This prevents silent data loss caused by vanilla registry shadowing.
- **Localization Sync**: Synchronized `en_us.json` and `id_id.json` with the new namespaced GameRule keys for perfect UI parity.
- **Territorial Probability Matrix**: Fully integrated the dynamic outcome matrix into the `WildWolfTerritorialGoal` AI. Pack disputes now follow synchronized, personality-driven probabilities for War, Merge, or Retreat.
- **Config versioning**: Incremented internal config version to `3470` to trigger necessary data migration and backup procedures.
- **Cleanup**: Purged legacy "Snapshot 11" comments and documentation debt from the entrypoint classes.
## [3.4.6] -
### Summary
The **"Probability Matrix"** update. Overhauled territorial outcomes with a dynamic, personality-driven chance system.
- **Dynamic Outcomes**: Pack disputes now use a weighted probability matrix (War/Merge/Retreat) based on the personality pairing of the leaders:
- **Aggro vs Aggro**: 80% War, 10% Merge, 10% Run
- **Aggro vs Normal**: 50% War, 40% Merge, 10% Run
- **Aggro vs Pacifist**: 10% War, 50% Merge, 40% Run
- **Normal vs Normal**: 20% War, 50% Merge, 30% Run
- **Normal vs Pacifist**: 5% War, 45% Merge, 50% Run
- **Pacifist vs Pacifist**: 0% War, 50% Merge, 50% Run
- **Merge Hierarchy**: During a merge, leadership is automatically granted to the higher-ranked personality (Aggressive > Normal > Pacifist).
## [3.4.5] -
### Summary
The **"Nuanced Leadership"** update. Further refined territorial outcomes to respect Pacifist instincts and combat priority.
- **Merge Logic Refinement**: Pacifist leaders now always choose to retreat rather than merge into another pack, prioritizing their own pack's autonomy.
- **Combat Priority**: If both leaders choose to fight (Aggressive vs Normal), they will now engage in a duel regardless of rank, rather than an automatic merge.
- **Aggressive Dominance**: Aggressive leaders still win automatic merges against Normal leaders who choose not to fight.
## [3.4.4] -
### Summary
The **"Dominance Hierarchy"** update. Refined the territorial dispute logic to enforce personality-based leadership outcomes.
- **Merge Logic**: Implemented a strict personality hierarchy (Aggressive > Normal > Pacifist). Higher-ranked leaders now automatically win dominance disputes against lower-ranked rivals, merging their packs.
- **Consistency**: Disputes between leaders of the same rank still use the existing chance-based duel/retreat logic.
## [3.4.3] -
### Summary
The **"Command UX"** update. Fixed command synchronization issues that caused debug commands to appear red (Unknown) in the chat bar.
- **UX Improvement**: Moved GameRule logic to execution phase. Commands are now always visible to OPs, preventing "Red Text" confusion when toggling debug mode.
- **Production Alignment**: Incremented version for final release parity.
Developer information
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle.
maven { name = "Modrinth"; url = "https://api.modrinth.com/maven" }