Skip to content
InviteMeInviteMe

Statistics & Logging

InviteMe records all invitation activity and provides statistics commands to monitor server health.

Statistics

Section titled “Statistics”

View Server Stats

Section titled “View Server Stats”
/im stats
/im stats 10

Permission: invite.stats (default: op)

Output:

══════ Server Invite Statistics ══════
  Total invites given:    47
  Total invited players:  47
  ─────────── Top Inviters ───────────
  1. Alice — 8 invites
  2. Bob — 6 invites
  3. Steve — 5 invites
════════════════════

The optional number after /im stats N sets how many inviters appear in the top list (default: 5).

What Stats Tell You

Section titled “What Stats Tell You”
Stat Use
Total invites given Overall server growth
Total invited players Current tracked whitelist size
Top inviters Most active community builders

Action Log

Section titled “Action Log”

The action log records every invitation event with timestamps and reasons.

View Recent Actions

Section titled “View Recent Actions”
/im log list

Permission: invite.log (default: op)

Shows the last 20 entries by default. Maximum per request: 200 (requests above this are capped automatically).

Output:

══════ Invite Action Log ══════
  [INVITE] Alice → Bob (2024-01-20 16:45)
  [UNINVITE] Admin → Charlie (2024-01-20 15:30) — rule violation
  [SYNC_ADD] Console → Eve (2024-01-17 20:30)
════════════════════

Custom Entry Count

Section titled “Custom Entry Count”
/im log list 50
/im log list 100

Log Event Types

Section titled “Log Event Types”
Type When it Appears
INVITE /invite add PlayerName executed
UNINVITE /invite remove PlayerName executed
EXPIRED Temporary invite timed out automatically
SYNC_ADD Player added via /im sync

Reasons in the Log

Section titled “Reasons in the Log”

When an admin removes a player with a reason:

/invite remove Bob Rule violation - griefing

The log shows:

  [UNINVITE] Admin → Bob (2024-01-20 16:45) — Rule violation - griefing

Always provide a reason when removing players — it makes moderation audits much easier.

Player Profiles

Section titled “Player Profiles”

To view a specific player’s invite history and recent activity:

/im log list Alice

Output:

══════ Invite Profile: Alice ══════
  Invited by: Console (2024-01-01 10:00)
  Has invited: 3 players
    • Bob (2024-01-15 14:30)
    • Charlie (2024-01-17 09:00)
    • Diana (2024-01-19 20:15)
  ─── Recent Activity ────────────────
    [INVITE] Alice → Bob (2024-01-15 14:30)
    [INVITE] Alice → Charlie (2024-01-17 09:00)
══════════════════════════════════════

You can limit the history shown:

/im log list Alice 10

Exporting Logs

Section titled “Exporting Logs”

Export to CSV

Section titled “Export to CSV”
/im log export                  # full global log
/im log export global           # explicit global export
/im log export Alice            # one player's log

Files created in plugins/InviteMe/logs/:

  • Global: global_log_YYYY-MM-DD_HHmmss.csv
  • Per player: user_log_<name>_YYYY-MM-DD_HHmmss.csv

CSV columns:

Column Content
timestamp Date and time of action
action_type INVITE, UNINVITE, EXPIRED, SYNC_ADD
actor_name Who performed the action
actor_uuid Actor’s Minecraft UUID
target_name Player affected
target_uuid Target’s Minecraft UUID
reason Reason (if provided, otherwise empty)

Use cases:

  • Monthly activity reports
  • Evidence for ban appeals
  • Import into spreadsheets for analysis
  • Long-term archiving

Moderation Workflows

Section titled “Moderation Workflows”

Investigating a Suspicious Player

Section titled “Investigating a Suspicious Player”
1. /im log list SuspiciousPlayer
   → Check who invited them, when, and full action history


2. /invite remove SuspiciousPlayer Reason for removal
   → Remove with a logged reason


3. /im log list
   → Confirm the action appears in the log

Weekly Audit Routine

Section titled “Weekly Audit Routine”
1. /im stats
   → Overview of server activity


2. /im log list 50
   → Review last 50 actions for anything unusual


3. /im log export
   → Archive logs to CSV


4. /im debug
   → Confirm all systems healthy

Bug Reports

Section titled “Bug Reports”

The /im report command generates a full diagnostic snapshot and uploads it to a paste service, returning a URL you can share when requesting support or reporting a bug.

What It Collects

Section titled “What It Collects”
Section Content
Plugin & server version InviteMe version, Paper/Spigot build
Storage backend Active backend type
config.yml (sanitized) All settings — password, host, username, api-key replaced with ***
Active plugins Name and version of every loaded plugin
InviteMe console log Last 200 lines mentioning InviteMe (including full stack traces)

Running the Command

Section titled “Running the Command”
/im report

Permission: invite.admin

Output:

⟳ Generating bug report...
✓ Report generated: https://pastefox.com/abc123

The URL is clickable in-game. Share it in your bug report or support ticket.

Upload Backends

Section titled “Upload Backends”
Feature PasteFox (default) mclo.gs
Log highlighting Generic ✅ Minecraft-specific
Expiry control ✅ Configurable (default: 24 h) ❌ No control
Visibility ✅ PUBLIC / UNLISTED / PRIVATE ❌ Always public
Password protection ✅ Optional ❌ Not supported
API key Optional Not needed

Switch backend or adjust PasteFox options (visibility, expiry, password, API key) under report: in config.yml. See Config Reference.

Next Steps

Section titled “Next Steps”