Tags
Creators
Details
mc1.15-1.0.0
Compatibility
Changes
Features
Redstone Multimeter allows you to track when blocks are powered, activated, or moved by placing virtual "meters" in the world. These meters log the various events. An overview of the logs of the past 60 ticks is displayed in a HUD in the top left of the screen. Each meter has its own row, and each column represents a single tick. Pressing n will pause this HUD and allow you to scroll through the logs with , and .. When the HUD is paused there will also be an extra overview on the right that displays the ordering of events within a single tick.
Pressing m on your keyboard will add or remove a meter at the block you are looking at. By default meters will move if the block they are metering is moved by a piston. This is useful for debugging flying machines. If you hold ctrl while creating a meter that meter will be immovable.
Meters are organized into meter groups. A meter group is a collection of meters and a unique name. You can have multiple meter groups, but the HUD will only display the logs of a single meter group. To subscribe to a meter group, use the /meter group <name> command. You can get a list of all meter groups by using the /meter listGroups command.
Commands
/meter name <index> <name>: re-names the meter at the given index*./meter name <name>will attempt to re-name the meter you are looking at, or default to an alias of/meter name -1 <name>.
/meter name <index> <#RRGGBB>: re-colors the meter at the given index*./meter color <#RRGGBB>will attempt to re-color the meter you are looking at, or default to an alias of/meter color -1 <#RRGGBB>.
/meter event <index>: list the types of event that the meter at the given index* is currently metering./meter eventwill attempt to list the types of event that the meter you are looking at is currently metering, or default to an alias of/meter event -1.
/meter event [start/stop] <index> <type>: make the meter at the given index* start/stop metering the given event type./meter event [start/stop] <type>will attempt to update the metered event types of the meter you are looking at, or default to an alias of/meter event [start/stop] -1 <type>.- The available event types are:
powered: track if the block is receiving power.active: track if the block is emitting power or active in another way.moved: track if the block is moved by a piston.
/meter removeAll: removes all the meters in the meter group you are subscribed to./meter group <name>: subscribes you to the group with. the given name, or creates a new group if it does not yet exist./meter listGroups: lists all the meter groups.
* Positive indices count from the top down. Negative indices count from the bottom up.
Keybindings
Toggle Meter(defaultm): Adds or removes a meter at the block you are looking at. Holdingctrlmakes the meter immovable.Pause Meters(defaultn): Pauses HUD.Step Forward(default.): While paused, move the display 1 tick ahead in time. Holdingctrlmoves 10 ticks.Step Backward(default,): While paused, move the display 1 tick back in time. Holdingctrlmoves 10 ticks.Toggle HUD(defaulth): toggles the HUD.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:X6YTb3G1:CsoHZo7N"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:X6YTb3G1:CsoHZo7N"
}

