Prepare a useful ViaVersion support report without leaking configuration

Applies to: ViaVersion; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A useful compatibility report explains which client, server and translation path failed. A screenshot of a disconnect message rarely supplies enough context. Conversely, posting an entire panel archive can expose unrelated credentials. Build a small report that a maintainer can reproduce without accessing your service.

Record the starting point

Write down the server platform and build, Java version, ViaVersion family releases and affected client version. Identify whether the client connects through a proxy. Keep the original error locally, including its timestamp, and separate account or address information from the technical reproduction.

Work through the change

Reproduce the issue using one short sequence of actions. Include the expected behaviour, actual result and whether the native server client behaves differently.
Use the diagnostic or dump facility documented for your installed ViaVersion release if support requests it. Read the output before sharing its link; generated reports may expose plugin and network details.
Add only the relevant startup or disconnect excerpt. Redact passwords, tokens and unrelated player information without removing version numbers or the first error in the stack trace.
Check the maintainer's issue template and search for the same server/client combination. Submit one report with the minimal reproduction instead of multiple reports containing different guesses.

Check the result

A reader should be able to identify the protocol direction, components involved and exact failing action. Keep a private copy of the report and its original logs so staff can answer a follow-up without asking the player to repeat the failure repeatedly.

If the result differs

If the reproduction disappears after removing a packet-dependent plugin on a test copy, include that comparison. It does not prove either maintainer is at fault, but it narrows the interaction. If no clean reproduction exists, say which observations are confirmed and which remain uncertain.

Remove a public diagnostic link where the hosting tool allows it if you discover a secret after sharing. Rotate an exposed credential rather than assuming deletion removed every copy. Keep gameplay configuration unchanged while preparing the report.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report