merge(v14): integrate v14 branch into main #143
No reviewers
Labels
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Athemis/ds4!143
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "v14"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #142
Summary
This pull request merges the current
v14branch intomainand brings the accumulated Foundry v14 migration work onto the default branch. The branch is focused on removing remaining compatibility shims, moving DS4 behavior onto native v14 APIs, and hardening migration and pack data handling around active effect timing and chat message modes.What Is Included
Main Change Areas
Active effect timing and expiry
A large part of the branch replaces DS4-specific legacy consume and expiry behavior with native v14 active effect timing. This includes effect creation timing, duration rendering, expiry event handling, suppression/deletion of expired effects, and cleanup of stale shims that were still carrying forward pre-v14 assumptions.
Migration and data normalization
The branch updates migrations so persisted effect data is read and normalized correctly in v14. It also removes legacy duration keys, merges older start metadata into the native structure, and normalizes remaining pack data so world data and compendium content align with the v14 timing contract.
Roll and chat message mode updates
The roll pipeline is updated to use core v14 message modes end-to-end. This removes the remaining legacy
rollModeplumbing while preserving the expected dialog fallback semantics during message creation.Test coverage
The branch adds and repairs regression coverage around consume expiry behavior, native timing contracts, legacy combat duration handling, and type-safe spec behavior. This should reduce risk when merging the v14 migration work back into
main.Review Guidance
Review is easiest if split into these passes:
Branch Status
At PR creation time,
v14was 35 commits ahead ofmainand 0 commits behind.Notes
v14fjfrom the local repository checkout