-
Notifications
You must be signed in to change notification settings - Fork 0
English
🏠 Wiki home — 🇩🇪 Deutsche Version
This page walks through day-to-day usage of InvSpy, plus the full command and activity-log reference. For a quick feature overview see the README — this page goes into more depth.
-
/invspy inventory <player>or/invspy enderchest <player>opens the target's inventory or enderchest — works for both online and offline players automatically. -
/invspy checkitem|checkplayer|checkinventory ...queries the admin activity log.
Base command /invspy, alias /is. All OP level 4.
| Command | Description |
|---|---|
/invspy inventory <player> |
Opens the target's inventory (online: live proxy container, offline: reads/writes their saved data). |
/invspy enderchest <player> |
Same, for the target's enderchest. |
/invspy checkitem <item> [player] [limit] |
Activity log: recent events involving a specific item. |
/invspy checkplayer <player> [limit] |
Activity log: recent events involving a specific player. |
/invspy checkinventory <player> [limit] |
Activity log: recent inventory/enderchest edits for a specific player. |
/invspy config retention <days> |
Sets activity-log retention (1–365 days, default 90). |
/invspy config logging playerinventory <true|false> |
Toggles logging of inventory/enderchest edits. |
/invspy config logging containers <true|false> |
Toggles logging of container interactions. |
/invspy config logging itemcreation <true|false> |
Toggles logging of creative-mode item grabs and /give. |
InvSpy keeps a compact, admin-facing log of inventory-related activity in a single SQLite
database (invspy/invspy_activity.db in the world save) — not a file per item, and not
NBT item-tagging (which would break vanilla stack-merging).
What gets logged:
- Player inventory/enderchest edits made through InvSpy itself.
- Container interactions (opening chests etc.).
- Creative-mode item grabs from the creative inventory.
-
/givecommand usage.
Each category can be toggled independently via /invspy config logging ... or the config file
in the server's config folder (FMLPaths.CONFIGDIR, not the world save — this is
intentional, so the logging toggles survive across different worlds on the same server install).
What is deliberately NOT logged:
- Plain block mining — too high-volume to be forensically useful, and mining by itself isn't suspicious the way an item with no traceable origin is.
- Hopper/automated container transfers — only real player container interactions are recorded.
Retention is configurable from 1–365 days (default 90), stored in the database itself
(/invspy config retention <days>). Older entries are pruned automatically.
Querying: use /invspy checkitem, /invspy checkplayer, or /invspy checkinventory — each
opens a scrollable results screen with timestamp, actor, location, and item details.
Editing an offline player's inventory while they're about to log back in is guarded against data loss (their edits are discarded rather than silently overwriting the live session), but this is still an admin power tool — use it responsibly and be aware every edit is logged.