Repository navigation
Conversation
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
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.
Block commands could use a different hit from the one the client saw, and a held dig could continue after its block left view. Preserve the hit cursor for placement, add
dig stop, and cancel held mining when the original target disappears. The Commands module owns pending work and awaits cancellation during disposal.Validation: all 1,980 DMCBK tests pass against rebuilt local UMPK libraries. Release build, formatting, and Core/Commands packaging pass. MCC live checks cover held target changes on four releases from 1.8.9 through 26.3.
Keep this in draft alongside the UMPK changes. Consumer checks use the authorized local project overrides outside Git; the published UMPK package and complete interaction matrix remain pending.