MCLabs Staff Docs

    🔍 CoreInspect Investigations And Rollbacks

    This walkthrough details how to use CoreInspect for standard block investigations and rollback operations, set up Xray baiting blocks, and verify Ore Magnet claims.

    Plugins & Commands Used

    • CoreInspect: Block logging and rollbacks via /co
    • Xray Baiting: Skript command /xray
    • Ore Magnet Checker: Skript command /oremagnet

    Step 1: Investigating Block Changes (CoreInspect)

    When a player reports theft or griefing, use CoreInspect to find out who placed or broke blocks:

    1. Enable the inspection tool:
      /co inspect (or /co i)
    2. Left-click or right-click any block or chest to view its edit log (showing who modified it, when, and the action taken). Right-clicking a chest or container will show container transactions.
    3. Run /co inspect again to disable the tool when you are finished.

    Advanced Lookup (/co lookup or /co l)

    To search through block, container, command, or chat logs more precisely, use the following syntax:
    /co l u:<user> t:<time> r:<radius> a:<action> b:<blocks> e:<exclude>

    • Parameter Rules:

      • Except for the username (which must go first), the order of parameters does not matter.
      • Action (a:): Can be block (default), container, command, or chat. Note that logs must be looked up per-world.
      • Block (b:): Can be filtered with + or - to show only placed or broken blocks (e.g., b:+stone to show placed stone).
      • Time (t:): Required when looking up block logs, but optional when checking chat/commands.
      • Paging Trick: Use /co l 1:50 (or /col 1:50) to display 50 results per page instead of the default 5.

    • Examples:

      • /co l goodchum_ a:block b:+stone t:1h (Stone placed by goodchum_ in the last hour)
      • /co l goodchum_ (General block edit query for goodchum_)

    Step 2: Performing Rollbacks and Restores

    To undo griefing or rollback changes within a specific area:

    [!WARNING]
    New Admins: Do not use rollback or restore commands on your own until you have been trained or approved by an Admin+. Talk to an Admin+ if you suspect a rollback is needed.

    1. Rollback blocks:
      /co rollback u:<player> t:<time> r:<radius>
      • u:<player>: Specify the username of the player whose actions you want to undo.
      • t:<time>: Specify the timespan (e.g., 24h for 24 hours, 3d for 3 days, 30m for 30 minutes).
      • r:<radius>: Specify the block radius around you to affect (e.g. 10).
      • Example: /co rollback u:GrieferPlayer t:12h r:20
    2. Reapply edits (Restore):
      /co restore u:<player> t:<time> r:<radius>
      • Reapplies rolled back blocks/edits (restores the blocks).
    3. Undo Rollbacks/Restores:
      To undo a rollback or restore command because a mistake was made, use:
      /co undo
      • Note: The /co undo command can sometimes be buggy. You can also run /co restore with the same parameters as the rollback to undo it.

    Step 3: Investigating Xray (Baiting Blocks)

    If you suspect a player of using Xray mods but lack concrete proof, you can place bait blocks at their mining level:

    1. Fly to the coordinate/tunnel where the suspect is mining (while vanished).
    2. Deploy a bait block:
      • /xray chest: Places a chest at your current position (automatically deletes itself and undos after 5 minutes).
      • /xray chests: Places a chest expanding 1 block east.
      • /xray diamond: Places a diamond ore vein expanding 1 block up.
      • /xray iron: Places an iron ore vein expanding 1 block up.
    3. Observe if the suspect tunnels directly towards your bait block.
    4. Once the test is complete, clean up the bait block:
      /xray undo (instantly undos your last xray block placement)

    Step 4: Verifying Ore Magnet Claims

    Players may claim they found hidden ores legitimately using their custom Ore Magnet tool. To verify this claim:

    1. Fly to the location of the suspected ore vein.
    2. Stand near the block and run:
      /oremagnet <player>
      • Example: /oremagnet SuspectPlayer
    3. The command will scan a 5-block radius and verify if that player's Ore Magnet actually registered and highlighted that ore.
      • If found: Displays &aNearby ore was found with Ore Magnet! (meaning the claim is legitimate).
      • If not found: Displays &cNo records of nearby ore being detected by Ore Magnet. (meaning the player likely used Xray).

    Step 5: Investigating Suspected Xray Raids

    When reviewing a raided base or vault to determine if it was found via Xray:

    1. Confidentiality & Permission: Do not attempt to investigate xray tickets alone until you have shadowed another admin and been approved to handle them.
    2. Setup:
      • Ask the reporting player to stay out of the base while you are looking into it.
      • In the ticket, ask who they share the base with to avoid accidentally banning the wrong person.
    3. TNT Rollback:
      If the base was blown up, reverse the TNT damage first to inspect the walls and paths:
      /co rb #tnt r:30 t:1h a:block e:tnt
      • Note: e:tnt is critical as it prevents the TNT blocks from rolling back and immediately reigniting. Keep the radius small (e.g. 30) to avoid lag.
    4. Locating the Tunnel (Filled-In or Hidden):
      Xrayers often fill their tunnel back in with cobblestone/dirt on their way down to hide their path.
      • If the dug-in hole is known: Go to the hole and clear the filled-in blocks quickly by running:
        /co rb <player> a:+block t:<time> r:<radius>
        • Note: Using a:+block will roll back only placed blocks, which clears the player's fill blocks and leaves their dug tunnel wide open.
      • If the hole is unknown:
        • Check if the player accepted any /tp requests or set any homes in the base during the raid timeframe.
        • Go near the top/sides of the base and use /co near while flying around. This displays edits near you to help spot tunneling.
        • If the xrayer had an accomplice dig the hole, run /co rb using the suspects' names. Start with a smaller radius/time close to the raid and work up to avoid undoing the base owner's work. Check block rollback results in chat.

    Step 6: Troubleshooting Glitched Rollbacks (Container Fix)

    Often, when you roll back a chest, the container items might glitch and not return, even though the block logs show them as returned (crossed out). This bug is fairly common.

    • Do not undo the rollback completely and redo it, as this can make the glitch worse.
    • Fix Procedure: Modify the container logs specifically.
      1. Restore the chests to their post-raided state (which uncrosses the items in core inspect):
        /co rs <player> t:<time> r:<radius> a:container
      2. Roll back the chest logs again to return the items:
        /co rb <player> t:<time> r:<radius> a:container
      • Why this works: CoreProtect thinks it has already returned the items and won't re-rollback. Restoring first "resets" the transaction log so the rollback can be run a second time successfully.