CraftEngine-first Mahjong 2.0 architecture - #131
Draft
TypeThe0ry wants to merge 75 commits into
Draft
Conversation
Tag every spawned region entity with table/session/role/slot/generation in its persistent data container, add /mahjong cleanup (orphan-only) and debug entities listing, and scan for orphans at plugin startup so leaked displays can be attributed to a table and removed without ever touching unrelated Interaction/ItemDisplay entities.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
./gradlew check shadowJar./gradlew clean check jar javadoc— 97 tests./gradlew clean check jar javadoc— 89 tests plus mahjong-utils verification./gradlew clean check jar javadoc— 35 testsB1693FB232A71C63064622208A2766801B6B4C8DFF039188952958B7636C4119Cutover status
This PR establishes the 2.0 architecture and fail-closed runtime boundary. Existing matches remain on the legacy path until each independent rule repository implements the SPI provider, passes the TCK and accuracy gates, and advances through SHADOW at new-match boundaries.