NeoProtect

NeoProtect is a CoreProtect-style logging mod for NeoForge, Fabric, and Forge. It is built for servers that need reliable inspection and rollback tools without placing unnecessary load on the server.

It tracks the activity that matters when something goes wrong: block placement, block breaks, block changes, container item movement, sign edits, explosions, and fire spread.

Whether you are investigating griefing, missing items, accidental damage, or activity in a particular area, NeoProtect provides a searchable history and practical rollback tools to help you understand and repair what happened.

Features

• Block logging for placed, broken, and modified blocks
• Container logging for item additions and removals
• Sign edit tracking with global sign history searches
• Explosion logging with player attribution where possible
• Fire logging for spread and destruction, including chained causes where possible
• Inspect mode for checking block history directly in the world
• Paginated inspect results for locations containing more than five events
• Paginated search history with Previous and Next page controls
• Global searches across retained history and dimensions
• Player history for reviewing everything recorded for a specific player
• Advanced filters for player, action, target, world, radius, coordinates, and page
• Clickable coordinates in search results for teleporting directly to logged locations
• Rollback previews showing affected blocks, container transactions, and item units before changes are applied
• Clickable Confirm and Cancel rollback controls with a 60-second expiry
• Directional rollback filters such as +blocks, -blocks, +containers, and -containers
• Command suggestions for filters, time ranges, radii, pages, players, and rollback scopes
• The shorter /np command as an alternative to /neoprotect
• Asynchronous database writes and embedded persistent storage
• Historical records remain available unless they are manually removed

Screenshots

Block break and placement history

Container item tracking

Rollback logging

Explosion logging

Commands

Every /neoprotect command can also be used with the shorter /np alias.

• /neoprotect inspect
  Toggles inspect mode. Interact with a block or container to view its recorded history.

• /neoprotect lookup <pos> [radius] [limit]
  Shows recent records around a position.

• /neoprotect search <time> [filters]
  Searches recorded activity using durations such as 30m, 2h, 7d, or all.

• /neoprotect player <player> <time> [filters]
  Shows recorded activity for a specific player.

• /neoprotect signs <time> [filters]
  Searches recorded sign modifications.

• /neoprotect rollback <scope> <time> <radius> [player]
  Previews matching changes around your current position before allowing you to confirm the rollback.

• /neoprotect flush
  Immediately writes queued log data to storage.

• /neoprotect stats
  Shows basic logging, storage, and queue statistics.

Search filters

Search commands support filters for narrowing results by:

• Player
• Action
• Block or container target
• World
• Radius
• Coordinates
• Result page

Commands provide tab-completion suggestions for common filters and values.

Rollback scopes

NeoProtect supports precise rollback control instead of limiting administrators to complete area restores.

Available scopes include:

• blocks
• containers
• both
• all
• +blocks
• -blocks
• +containers
• -containers
• +all
• -all

These scopes let you restore destroyed blocks, remove placed blocks, return removed items, or remove added items depending on the incident being handled.

NeoProtect always displays a preview before applying a rollback.

Performance

NeoProtect is designed for active servers. Logging uses asynchronous database writes, embedded storage, batching, and a lightweight event pipeline to reduce its effect on normal gameplay.

Database records are stored persistently and remain available after server restarts.

Loader support

NeoProtect supports:

• NeoForge
• Fabric
• Forge

Each release is marked with its compatible Minecraft versions and loaders. Some Minecraft versions may require a separate jar because loader APIs can change between releases.

Notes

• No additional dependency mods are required
• Logging data survives server restarts
• Historical records remain stored until manually removed
• Server operators can use either /neoprotect or /np
• Use the file matching your Minecraft version and mod loader