Check an EconomyShopGUI section edit before reloading it

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

A malformed shop section can stop a menu from loading. Validate one saved edit with the installed release’s schema before sending another reload request or replacing the entire shop directory.

Before you start

EconomyShopGUI distinguishes shop items, sections and permissions. Free and Premium releases expose different options, so check the documentation for your installed edition. Test ordinary players and a single section before sharing a change across the shop.

Work through the check

Take a copy of the active section and note which file the installed release uses; configuration layouts can differ across editions.
Edit one listing at a time, preserving indentation and documented field types. Use the supplied example for the same release rather than a random older shop file.
Check the edited YAML with a parser, then apply it on an isolated test server using the plugin’s documented reload or restart procedure.
Open the section with a normal account, navigate back to its parent and complete one inexpensive trade to check both structure and effective prices.

Confirm the result

The server should parse the edited file without an exception and show the intended section. Other sections should remain accessible with their previous item order and prices.

If the result differs

A YAML parser only checks syntax, not whether a material or setting exists in EconomyShopGUI. Read the first plugin error for an unknown field or item rather than repeatedly retrying a broken reload.

Recover safely

Restore the saved section file and use the same supported apply procedure if the menu fails. Avoid replacing all shop files, which can erase unrelated price and permission changes.

CloudExa game console with the log controls visible. — The CloudExa console provides the log view used in this check. This is a general panel screenshot, not plugin-specific output.

Documentation and related help

Check the EconomyShopGUI maintainer documentation and EconomyShopGUI maintainer reference against your installed release before applying changes.

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