Block Debug Tools is a lightweight command utility for mod developers, modpack creators, map makers, and server administrators who need to inspect block placement and world generation.
The mod can locate the nearest instance of any registered vanilla or modded block, display its coordinates, teleport the executing player to a safe position near it, or count matching blocks within a selected radius.
All searches are performed in the player's current dimension.
## Features
- Locates the nearest matching block
- Teleports the player to a safe position near the located block
- Displays block coordinates without teleporting
- Counts matching blocks inside a true three-dimensional sphere
- Supports vanilla and registered modded blocks
- Uses Minecraft's native block autocomplete
- Displays distance, search radius, center coordinates, and scan time
- Requires no additional library mods
## Commands
### Find and teleport
```text
/findblock <block> [radius]
Finds the nearest matching block and teleports the player to a safe air position near it.
Examples:
/findblock minecraft:deepslate
/findblock minecraft:diamond_ore 100
/findblock modid:block_name 64
When the radius is omitted, the default radius of 64 blocks is used.
Find coordinates only
/findblockpos <block> [radius]
Finds the nearest matching block without teleporting the player.
Examples:
/findblockpos minecraft:granite 50
/findblockpos minecraft:ancient_debris 128
Count blocks
/countblock <block> <radius>
Counts every matching block inside a true three-dimensional sphere centered on the player's block position.
Examples:
/countblock minecraft:granite 50
/countblock minecraft:deepslate 64
/countblock modid:block_name 80
Permissions
All commands require Game Master permission.
In singleplayer, cheats must be enabled. On a dedicated server, the player must have the required operator permissions.
Commands must be executed by a player and cannot currently be used directly from the server console.
Compatibility
- Minecraft 26.2
- NeoForge 26.2.0.59 or newer
- Java 25
- Server-side command logic
- No additional mod dependencies
For singleplayer, install the mod in the client profile so it can run on the integrated server. For multiplayer administration, install it in the dedicated server's mods folder.
Search limits
- Default
/findblockand/findblockposradius: 64 blocks - Maximum radius: 128 blocks
/countblockrequires an explicit radius- Searches use a real sphere rather than a cube
Performance warning
Block scanning is performed synchronously.
Large search radii can briefly pause an integrated or dedicated server, especially when using /countblock. A radius between 32 and 64 is recommended for routine debugging. Radius 128 should only be used when necessary.
Current limitations
- Block tags such as
#minecraft:logsare not supported in version 1.0.3. - Matching is performed by block type. Individual block-state properties such as facing, axis, or waterlogged state are not filtered separately.
- Searches only inspect the player's current dimension.
- The mod does not provide a graphical interface or configuration screen.
Intended use
Block Debug Tools is intended for:
- Testing ore and terrain generation
- Checking whether modded blocks generated correctly
- Debugging structure placement
- Inspecting modpack world generation
- Verifying datapack and mod compatibility
- Locating rare blocks during development
- Counting generated blocks around a test position
Modpack permission
You may include Block Debug Tools in CurseForge modpacks as long as the original CurseForge-hosted file is used and the mod is not re-hosted or redistributed separately.

