Block Memory

This Mod was brought to you by the RoughDayGames Development group. To get help with the mod join the discord: RoughDayGames

Block Memory

Block Memory is a server-side moderation and investigation mod that helps staff work out what happened without digging through huge log files.

If Block Memory can confirm who did something, it tells you. If it can’t, it says so instead of guessing. Staff get the records and context, then make their own decision.

What can it help with?

• See who placed or removed tracked blocks.
• Check what players put into or took out of supported containers.
• Search by player, time, location, action, block or item.
• Review hopper transfers and monitored machine changes.
• Step through saved events with private visual markers.
• Check nearby activity and player presence.
• Investigate TNT and suffocation incidents.
• Create watched and suppressed areas.
• Claim investigations, add notes and track staff work through the queue and audit history.
• Use Doctor and Journal Status to check the mod’s setup and recording coverage.

What chest history looks like in-game

Look at a supported chest and run /Blockmemory Containers. Its history appears in chat, showing what went in or out, how much moved and who was recorded doing it. Click Details to see the time, location and full item movements. Deposits appear in green and withdrawals in red in that view.

For a visual investigation, run /Blockmemory Visual Start nearby. A coloured particle outline marks the chest’s recorded location: blue for a deposit and red for a withdrawal. Chat shows the selected event as you step forward, go back, play or pause. The markers are only visible to the staff member reviewing the history.

Block Memory 1.11

This update adds container history, machine monitoring, the investigation journal, combined search and visual playback. It also makes Help and the staff command displays easier to read, alongside the existing archive, restore and data management tools.

Minecraft: 1.20.1
Java: 17
Loaders: Forge and Fabric, available as separate downloads.

Block Memory uses the custom Setokaiba218 Project Licence and is not licensed under MIT.

Feedback, suggestions and bug reports are appreciated!

Full Feature List

Block Memory gives staff recorded evidence and context. Information that cannot be confirmed stays unknown.

Block investigation

• Track direct player block placement and removal.
• Check recorded players, UUIDs, times and placement/removal methods.
• Inspect tracked blocks with the Block Scanner or commands.
• Look at nearby activity and player activity summaries.
• View recent actions and top actors.
• Run configurable scans and generate reports or exports.
• Add staff notes to block records.
• Use clickable details and copy actions where supported.
• Set a personal timezone for displayed timestamps.

New placement and removal records retain their own block IDs for historical filtering. Older records without a saved type remain unknown.

Block history retains placement/removal information per position. It does not keep every repeated place/break cycle at that position.

Item and container history

Staff can check item movements in supported containers, including normal block inventories and double chests.

Look at the chest and run /Blockmemory Containers. Its history appears in chat, with the recorded player and a summary of what went in or out. Hover over a row for more context, or use the yellow Details button to open the full record.

Deposits are green and withdrawals are red in the details. Each movement shows the item and amount. The record also shows the time, dimension, coordinates, block type, capture source and recorded player name and UUID where known.

Deposits and withdrawals stay separate when a single operation moves several items. Use the batch ID to see related records. Names recorded from direct interactions can also be found in later player searches.

/Blockmemory Containers
/Blockmemory Journal
/Blockmemory Journal Player <nameOrUUID>
/Blockmemory Journal Batch <id>
/Blockmemory Journal Inspect <id>
/Blockmemory Journal Export
/Blockmemory Journal Status

Opening a container without moving anything does not create a movement record. Breaking a chest records the block action; the mod cannot identify who later picked up the spilled items from that record.

Custom storage screens, entity inventories, virtual storage and mod-specific packets need separate testing or support. A screen that looks like a chest does not guarantee its movements can be recorded.

Combined search

Search available block and journal records together in your current dimension. Filters cover player names or UUIDs, time windows, exact dates, radius, saved areas, action types, block IDs and item IDs.

/Blockmemory Search Help
/Blockmemory Search player:Alex time:24h action:remove block:minecraft:stone radius:32
/Blockmemory Search time:24h action:withdraw item:minecraft:diamond radius:32
/Blockmemory Search area:"Town Hall" time:7d action:setting

Replace the example player and saved area with ones from your server. Filters can appear in any order and must match the same action. Several action types can be selected together. Archived saved areas can also supply search bounds without being restored.

Results include hover information, Copy and journal Details buttons. Searches retain up to the newest 500 matches, with 15 rows per page. The search location and results stay fixed while paging.

Results expire after five minutes or when replaced by a new search. Buttons check the original staff member, dimension and current permissions. Narrow the filters when you need older results beyond the retained limit.

Hopper transfers and machine monitoring

Hopper transfers can be recorded as automated inventory movements. Selected blocks can also be monitored for later inventory and setting changes while their chunks are loaded.

/Blockmemory Monitor
/Blockmemory Monitor Add
/Blockmemory Monitor Remove
/Blockmemory Monitor Fields
/Blockmemory Machine

Setting capture covers block-state changes and explicitly configured block-entity fields. Monitor Fields helps staff inspect the installed machine's field names before configuring them.

Automated transfers and changes found by monitors keep an unknown player. They are never assigned to the owner or someone standing nearby.

Visual investigation

Stand near recorded activity and run /Blockmemory Visual Start. A coloured particle outline marks the location of the event in the world. For chest activity, blue marks a deposit and red marks a withdrawal. Purple is used for machine setting changes. Where a related inventory was recorded, particles can show a line between the two positions.

Chat shows the selected event, time and coordinates. Move back and forth through the records, or use Play and Pause to review several events in order. Only the staff member running the investigation sees the markers.

/Blockmemory Visual Start [minutes] [radius]
/Blockmemory Visual Next
/Blockmemory Visual Previous
/Blockmemory Visual Play
/Blockmemory Visual Pause
/Blockmemory Visual Stop

The radius is measured in blocks. Playback shows saved evidence and leaves blocks and inventories as they are.

Context and presence

• View nearby block activity around an investigated event.
• Use the Presence Wand to check recorded chunk visits.
• See visit counts, time present and last-seen information.
• Use presence as supporting context during an investigation.

Being nearby is not proof that a player caused an event. Presence records can include time spent AFK.

Incidents and alerts

Block Memory keeps persistent TNT and suffocation incident records, along with neutral alerts for bursts of block removal.

• Inspect incidents and alerts by their saved IDs.
• Generate reports and copy investigation information.
• Claim and unclaim investigations.
• Keep incident review states and staff notes.
• Configure removal-burst thresholds and time windows.
• See relevant saved-area information.
• Archive records and restore them when needed.
• Permanently delete archived records through the confirmation workflow.

Alerts report activity for staff to investigate. They do not automatically decide whether a player has done something wrong.

Saved areas

Create watched areas for important locations and suppressed areas to reduce alert noise from expected activity.

• Identify areas by ID or name.
• Inspect their bounds and check which areas contain your position.
• Preview boundaries with particles.
• Rename, resize, expand and shrink existing areas.
• Set vertical Y ranges.
• Archive, restore or permanently delete areas through the staff workflow.

/Blockmemory Area Here
/Blockmemory Area Preview <idOrName>
/Blockmemory Area Rename <idOrName> <newName>
/Blockmemory Area Resize <idOrName> Pos1
/Blockmemory Area Resize <idOrName> Pos2
/Blockmemory Area Expand <idOrName> <chunks>
/Blockmemory Area Shrink <idOrName> <chunks>

Saved area Remove archives the area. Archived watched and suppressed areas no longer affect burst matching.

Staff queue and audit history

/Blockmemory Queue brings relevant alerts and incidents together, including claim information, clickable shortcuts and staff join notifications where configured. Archived records leave the active queue.

/Blockmemory Audit records supported staff management actions with the staff member, action, target, dimension, time and a short summary. Filters are available for staff, alerts, incidents and saved areas.

Audit entries remain available when the original record is permanently deleted, subject to the audit retention settings. Older staff actions are not invented when loading an older world.

Safer deletion and data management

Alerts, incidents and saved areas must be archived before permanent deletion. Confirmation expires after 60 seconds and is tied to the same staff member, target and dimension. Pending confirmations disappear when the server restarts.

Block and staff data management includes statistics, retention settings, prune previews and confirmed manual pruning:

/Blockmemory Data Stats
/Blockmemory Data Prune Preview
/Blockmemory Data Prune
/Blockmemory Data Prune Confirm

Retention values of 0 keep that category indefinitely. Protected block/staff records are kept, including active records and the applicable staff-noted records. Audit history is kept indefinitely by default. Pruning is bounded and runs manually.

The journal has its own limits and pruning workflow:

/Blockmemory Journal Status
/Blockmemory Journal Prune Preview <days>
/Blockmemory Journal Prune Confirm <days>

The default journal limit is 50,000 records per dimension. Recording pauses at configured capacity rather than deleting old records. Use Journal Status to check recording settings, storage limits and capture gaps.

Doctor and support reports

/Blockmemory Doctor checks configuration and saved data, then writes TXT and JSON support reports. These include version information, schema checks, active and archived record counts, audit information, queue health, retention settings and saved-area checks.

logs/blockmemory/blockmemory-doctor-latest.txt
logs/blockmemory/blockmemory-doctor-latest.json

Use /Blockmemory Journal Status for journal capacity, recording settings and skipped records.

When reporting a problem, include your Minecraft version, loader and Block Memory version, the action or command involved, and how to reproduce it. Review reports before sharing server-specific information publicly.

Configuration, permissions and saved data

• Forge: <world>/serverconfig/blockmemory-server.toml
• Fabric: config/blockmemory.json

Settings cover investigation features, alerts, incidents, areas, notifications, retention and journal recording limits.

Permissions and operator/admin access control the staff tools. Journal viewing, management and visual investigations have separate permissions:

blockmemory.investigation.view
blockmemory.investigation.manage
blockmemory.visual.view

Give investigation access to trusted staff. Help follows the viewer's permissions, with paged examples, hover descriptions and commands that can be edited before submitting.

Block records, notes, presence, alerts, incidents, claims, saved areas, audit history and the journal are saved with the world. Older supported data formats are migrated when loaded. Back up your world before updating, and try the Fabric beta on a copy before using it on your main server.

Utility tools

• Block Scanner (item ID blockmemory:memory_stick) and Presence Wand.
• Block Memory creative tab, icon and item textures.
• In-game copy actions, reports and readable Help pages.