How SeedCrackerX commands work on the client
SeedCrackerX registers its command tree on the client through Fabric, so the server does not need the mod installed.
Current source registers the root literal /seedcracker and attaches render, finder, data, cracker, version, GUI, and database subcommands. Because these are client commands, they can work while connected to a vanilla server as long as your own Fabric client loaded SeedCrackerX. A server plugin with a similarly named command is unrelated and may behave differently.
If every /seedcracker command is unknown, treat that as an installation problem. Confirm the launcher started a Fabric profile, inspect the active instance mods folder, and read the Fabric log for an incompatible Minecraft range or missing dependency. If only a specific subcommand is unknown, compare your installed mod version with the command documentation because older builds used /seed and did not expose the same tree.
SeedCrackerX commands for bits, clear, and restore
The data group controls the observations feeding the current TimeMachine search.
Run /seedcracker data bits after a structure is detected. The first message reports collected base information against the normal target of approximately 32 bits. The second reports liftable information against approximately 40 bits. The values are displayed as integers, while the internal model can use fractional information based on each structure feature's placement offset.
Use /seedcracker data clear when moving to another world, correcting a wrong Minecraft version, or deliberately restarting after bad data. The reset clears pillar data, structure and biome observations, candidate sets, block-update work, and active finder outlines. The hashed seed is intentionally retained by the current source in some reset paths, so a full reconnect may still be appropriate when changing server or dimension context.
The restore command loads saved structure entries for the current server address or single-player world. Each saved line contains a structure name and chunk coordinates. Restore only data belonging to the same world and compatible generation version; an old structure file from another server can make every candidate fail.
SeedCrackerX commands for structure finders
Finder commands change what new chunk packets are scanned; they do not retroactively scan every loaded block unless you reload.
The source groups finders into STRUCTURES, DECORATORS, and BIOMES. Individual types include buried treasure, desert pyramid, End City, jungle temple, monument, swamp hut, shipwreck, pillager outpost, igloo, Trial Chambers, End pillars, End gateway, dungeon, emerald ore, desert well, warped fungus, and biome sampling. Defaults favor modern structure finders while several legacy decorator finders and biome sampling begin disabled.
After changing a category or individual finder, run /seedcracker finder reload to rescan chunks within the current render distance. Reloading can be CPU intensive because each enabled finder may construct several orientation or neighboring-chunk checks. Enable only the data sources relevant to the selected Minecraft version, especially when an older decorator implementation is documented as outdated.
- Keep End pillars enabled when you intend to use the pillar-seed route.
- Use structure finders as the main collection route on Minecraft 1.18 and newer.
- Enable biome sampling only when candidate structure seeds exist and the world-seed stage requests more biome information.
- Disable outlines separately if rendering affects performance; finder collection and rendering are different settings.
- A finder marked ON can still produce no result if the template, biome, dimension, or version check rejects the observed blocks.
SeedCrackerX commands for version, debug, and render
The version setting changes the feature definitions used to test structure positions.
Use the GUI for ordinary configuration because it presents supported versions and finder toggles together. The direct version subcommand is useful when documenting or reproducing a setup, but the supplied version must exist in the bundled seedfinding library. Changing the version reinitializes every feature definition, including spacing, salt, and supported structure behavior. Clear incompatible observations after a change.
Debug mode exposes intermediate pillar, structure, and hashed-seed information in chat or logs. It is useful when a search finishes with no result, repeatedly requests more structures, or appears stuck before world-seed recovery. Debug output can be noisy, so capture only the relevant section and disable it after diagnosis. Render commands affect colored cuboids around detected structures and do not change the mathematical constraints already stored.
SeedCrackerX commands and database privacy
Opening the database and submitting a cracked multiplayer seed are separate behaviors.
The database command opens a public Google Sheet used by the mod community. At startup, current source can also download a CSV mapping server addresses or hashed seeds to known world seeds, allowing an immediate lookup before a local search. This lookup is why a result can appear without collecting new structures on a previously recorded server.
Database submission is disabled by default. When enabled, a successful crack on a non-local server with more than ten online players can post the server address, dimension, seed, configured version, username or anonymization flag, and related hash data through a Google Apps Script endpoint. Review server rules and privacy implications before changing that option. SeedCracker Guide does not access, mirror, or query that database.