MeowMC

/meow report

/meow report
/meow report --share

Permission: bukkit.command.meowmc.report.

report produces one JSON artifact on disk: a health snapshot, the last profiler session if one exists, the platform, and a small block naming the configuration a reader of the report needs to interpret the numbers.

What the command answers

Report written to reports/meowmc-report-20260101-120000.json
(web upload is off: no endpoint)
Example output.

Web upload, off by default

The report viewer (meowmc.org/r/<id>) and the receiving API (POST /api/v1/reports) are live on the domain. The upload sink is off by default — a host switches it on with the endpoint key (metrics.reports.endpoint), which is not shipped. When the key and the sink land, the artifact schema, the command path and the user-facing string stay as they are.

The --share flag

--share names the report to share: the most recent artifact written this boot — writing a fresh report first only when none exists yet — then answers:

report written to reports/meowmc-report-20260101-120000.json
— web upload is off (endpoint key not shipped)
Example answer.

The artifact

The file lands at reports/meowmc-report-<yyyyMMdd-HHmmss>.json, next to dumps/meowmc-benchmark.json. Two reports written inside the same second never overwrite each other — a unique-name pass appends -2, -3, and so on. The full field-by-field reference: Report artifacts.

Privacy

The report contains no player names, no IP addresses, no world coordinates. The only identifying field is worlds[].name — the world's name in the per-world load table.

Preconditions

  • The global configuration must be loaded — the artifact embeds a config block, so a report against an unpublished configuration is refused with the reason.
  • Nothing else is needed for a plain report: no profiler session is required; profiler is null in the artifact unless one ran.