Add /cb pipes networks, an admin menu of recently active pipe networks - #1382
Open
RasmusKD wants to merge 1 commit into
Open
Add /cb pipes networks, an admin menu of recently active pipe networks#1382RasmusKD wants to merge 1 commit into
RasmusKD wants to merge 1 commit into
Conversation
Admins had no way to find pipe systems: a laggy or stuck network has to be located by walking the world. The pipe search already visits every block of a network on every pulse, so activity, size and throughput are now recorded as a free side effect of pulses that actually ran, nothing traverses anything extra. The menu lists networks active in the last ten minutes, newest first: size (high-water mark of the traversal), items moved, last pulse, and whether the last pull was refused everywhere. Clicking an entry teleports to the pulsing piston. Paginated at 45 per page, bounded at 256 networks per world, and identity is the smallest visited position so a network pulsed from several pistons appears once.
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
1 participant
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.
Admins have no way to find pipe systems: a laggy or stuck network has to be located by walking the world. The pipe search already visits every block of a network on every pulse, so this records activity, size and throughput as a free side effect of pulses that actually ran. Nothing traverses anything extra.
/cb pipes networks (permission craftbook.pipes.networks) opens a menu of networks active in the last ten minutes, newest first: size (a high-water mark, since a delivering pulse only walks until its items are placed), items moved, last pulse, and whether the last pull was refused everywhere. Clicking an entry teleports to the pulsing piston, so a big or stuck system can be visited directly.
Kept deliberately bounded: entries expire ten minutes after their last pulse, 256 networks per world, pagination at 45 per page. Only pull pulses are recorded for now.
Registered through the normal command framework as a nested command under a new 'pipes' top level. Same pull-loop area as the other open pipe PRs, happy to rebase whichever lands last.