AdvancedEnchantments tasks

• Fix an AdvancedEnchantments book assigned to a missing group
• Separate enchantment application failure from activation failure
• Test custom enchantment equipment restrictions with ordinary players
• Check a custom enchantment level limit before selling higher books
• Audit who can issue AdvancedEnchantments books and gear
• Compare a fresh enchantment book with an older stored copy
• Check enchantment group selection in a random-book reward
• Keep an enchantment configuration edit from breaking YAML loading

Fix an AdvancedEnchantments book assigned to a missing group

A book can be misclassified when its enchantment points to a group that is absent or named differently. Follow the reference from enchantment to group before editing shop prices.

Check the installed content

AdvancedEnchantments separates enchantment definitions, groups, book presentation and permissions. Keep test equipment away from player inventories until both application and activation work. Use the reference for your installed plugin version instead of assuming a configuration from another server will match.

Work through the change

1. Record the affected enchantment ID and the group value in its definition. Back up the enchantment and group files together so the relationship can be restored.
2. Find the matching group in groups.yml, using the exact identifier expected by the installed release. Compare case and spelling rather than only the visible colour or display label.
3. Correct the relationship on staging without changing the enchantment ID or existing equipment. Obtain a disposable fresh book through the documented administrator workflow.
4. Compare the new book in the intended menu and application interface. Test with an ordinary account and check any shop or reward integration that selects books by group.

Verify the result

The book should use the intended existing group and remain available through the correct distribution path. Other groups should retain their display and selection behaviour.

If the result differs

If its group looks correct but the shop fails, inspect the shop integration separately. If only old books differ, check their stored data and the release-supported update behaviour before reissuing equipment.

Keep a recovery path

Restore both saved files if the relationship remains uncertain. Keep test books out of the live economy; a group configuration rollback does not remove previously distributed books or undo applications.

References and related help

Check the maintainer reference: AdvancedEnchantments documentation, AdvancedEnchantments documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Separate enchantment application failure from activation failure

A custom enchantment that appears on equipment is not necessarily triggering during use. Test application and activation as different stages before increasing the chance or level.

Check the installed content

AdvancedEnchantments separates enchantment definitions, groups, book presentation and permissions. Keep test equipment away from player inventories until both application and activation work. Use the reference for your installed plugin version instead of assuming a configuration from another server will match.

Work through the change

1. Record the enchantment ID, supported equipment and triggering activity from the installed-release definition. Use a disposable item with no other custom enchantments as the baseline.
2. Apply the enchantment through the documented administrator command or normal book workflow on staging. Confirm the expected level and inspect initial configuration errors.
3. Perform the exact activity the enchantment requires with an ordinary player. Use a repeatable low-risk target and keep other effects out of the comparison.
4. Compare the unenchanted baseline, the single-enchantment item and the original multi-enchantment item. Note whether application, eligibility or the actual effect is the first stage that differs.

Verify the result

The book or command should apply the intended level, and the eligible activity should produce the documented effect. The baseline should not produce the same custom behaviour without the enchantment.

If the result differs

If application fails, inspect equipment restrictions and book rules first. If application succeeds but the effect fails, inspect trigger type, chance, conditions and conflicts rather than adding a second copy of the enchantment.

Keep a recovery path

Restore the original definition and discard only the disposable test equipment if the trial fails. Do not strip custom enchants from live player gear while the failing stage is still unidentified.

References and related help

Check the maintainer reference: AdvancedEnchantments documentation, AdvancedEnchantments documentation, AdvancedEnchantments documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Test custom enchantment equipment restrictions with ordinary players

An equipment restriction should reject the wrong item without blocking the intended one. Test both cases without operator privileges before distributing a new enchantment book.

Check the installed content

AdvancedEnchantments separates enchantment definitions, groups, book presentation and permissions. Keep test equipment away from player inventories until both application and activation work. Use the reference for your installed plugin version instead of assuming a configuration from another server will match.

Work through the change

1. Read the installed-release setting reference for the enchantment and record its eligible equipment types. Include any condition or integration that further restricts use.
2. Create a staging book and two disposable items: one intended eligible item and one deliberately ineligible item. Remove unrelated custom enchants from both.
3. Attempt application through the ordinary player route on each item. Record the message and resulting inventory rather than relying only on whether the display lore changes.
4. Use the eligible item in the intended activity, then test any supported offhand or armour-slot case relevant to the design. A valid item in the wrong slot may still fail to activate.

Verify the result

The eligible item should accept and activate the enchantment where intended. The ineligible item should be rejected without consuming unexpected extra books or modifying unrelated equipment.

If the result differs

If both accept it, inspect the actual loaded restriction and administrative bypass permissions. If neither accepts it, check the item type, group and parser errors before weakening all restrictions.

Keep a recovery path

Restore the earlier restriction and retain the test results for comparison. Keep valuable equipment outside the experiment and remove temporary test permissions when the ordinary-player checks are complete.

References and related help

Check the maintainer reference: AdvancedEnchantments documentation, AdvancedEnchantments documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Check a custom enchantment level limit before selling higher books

A higher-numbered book needs a corresponding supported level and sensible effect settings. Check the level definition before adding it to a paid shop or reward table.

Check the installed content

AdvancedEnchantments separates enchantment definitions, groups, book presentation and permissions. Keep test equipment away from player inventories until both application and activation work. Use the reference for your installed plugin version instead of assuming a configuration from another server will match.

Work through the change

1. Record the current highest level and the new level requested. Back up the enchantment definition and every shop or reward file that would distribute the new book.
2. Check the installed-release level settings and define the new level on staging. Keep its effect deliberately modest while checking whether the level is recognised and applied.
3. Obtain an expendable book at the requested level using documented administration syntax. Apply it to eligible test equipment and compare with the previous maximum level.
4. Test the effect, displayed level and any combining or upgrading workflow your server offers. Include an attempt above the allowed maximum to confirm the failure behaviour.

Verify the result

The new level should be recognised, display correctly and produce its intended bounded effect. An unsupported higher level should not become available accidentally through a shop or combination route.

If the result differs

If the book label changes but the effect does not, inspect the level-specific definition and trigger conditions. If the wrong level is issued, trace the distribution command before editing the underlying effect.

Keep a recovery path

Restore both the definition and distribution files if the new level is not ready. Record any test books issued so they cannot be mistaken for a production product or left in a public reward pool.

References and related help

Check the maintainer reference: AdvancedEnchantments documentation, AdvancedEnchantments documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Audit who can issue AdvancedEnchantments books and gear

Routine players should not need the ability to issue custom books or enchant equipment administratively. Review command access separately from the permissions needed for normal gameplay.

Check the installed content

AdvancedEnchantments separates enchantment definitions, groups, book presentation and permissions. Keep test equipment away from player inventories until both application and activation work. Use the reference for your installed plugin version instead of assuming a configuration from another server will match.

Work through the change

1. Open the command and permission reference matching the installed version. List the administrative book, item and enchantment actions actually used by staff and integrations.
2. Inspect inherited permission groups and temporary grants for those actions. Work on staging or a narrowly scoped test group rather than removing broad permissions from every player at once.
3. Test an ordinary account against the issue commands it must not use, then test normal book application and enchantment activation. Keep a second trusted staff session available for administration.
4. Grant an integration only the documented command access it requires. Where the action runs from console, confirm the integration executes the intended fixed command rather than accepting arbitrary player-supplied arguments.

Verify the result

Players should retain legitimate enchantment use while unauthorised issuance is rejected. The intended staff or console integration should still issue the exact item and quantity required.

If the result differs

If access remains, inspect inherited groups and operator status before changing plugin files. If normal use breaks, restore the narrow tested permission and identify which action needs it instead of granting a wildcard.

Keep a recovery path

Restore the saved permission changes if the trial affects unrelated commands. Remove temporary test groups and document the final nodes so later staff changes do not reintroduce unrestricted book issuance.

References and related help

Check the maintainer reference: AdvancedEnchantments documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Compare a fresh enchantment book with an older stored copy

Changing an enchantment definition can leave previously issued books looking different from new ones. Compare stored item data before concluding that the plugin ignored the update.

Check the installed content

AdvancedEnchantments separates enchantment definitions, groups, book presentation and permissions. Keep test equipment away from player inventories until both application and activation work. Use the reference for your installed plugin version instead of assuming a configuration from another server will match.

Work through the change

1. Record the enchantment ID and the exact change, such as its group or visible name. Preserve the old book in a backed-up staging inventory rather than overwriting it.
2. Load the changed definition on staging and obtain a fresh book through the supported workflow. Keep the same enchantment and level so the age of the copy is the main difference.
3. Compare display, application and resulting equipment for both copies using expendable items. Test after relogging to distinguish a client display cache from stored item information.
4. Read the installed-release guidance for item or book updates before planning any migration. Keep presentation differences separate from a book that applies the wrong effect or level.

Verify the result

The comparison should establish whether the old copy is cosmetic, still valid or incompatible. Fresh issuance should reflect the intended definition and activate the correct enchantment on eligible equipment.

If the result differs

If both copies fail, inspect the definition and its group rather than old-item handling. If only one fails, capture its origin and metadata through supported inspection without publishing player inventory or private data.

Keep a recovery path

Restore the previous definition if the change breaks application. Do not replace every player book during diagnosis; prepare a backed-up, documented migration only after the release-supported update method is confirmed.

References and related help

Check the maintainer reference: AdvancedEnchantments documentation, AdvancedEnchantments documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Check enchantment group selection in a random-book reward

A random-book reward should draw from the intended group, not every available enchantment. Test the distribution path with disposable books before connecting it to a public crate or shop.

Check the installed content

AdvancedEnchantments separates enchantment definitions, groups, book presentation and permissions. Keep test equipment away from player inventories until both application and activation work. Use the reference for your installed plugin version instead of assuming a configuration from another server will match.

Work through the change

1. Record the reward command and intended group identifier. Compare that identifier with the installed group definitions and the current command reference.
2. Run the documented random-book workflow on staging with a small quantity and a fixed test recipient. Keep valuable currency charges and public announcements disabled for the trial.
3. Inspect each issued book for group and valid enchantment level. Check that the intended group actually contains eligible enchantments rather than relying only on its display colour.
4. Repeat through the real reward integration with an ordinary test player. Compare its command substitution and quantity with the successful direct test, then test the unavailable-group case safely.

Verify the result

Every issued book should belong to the selected group and reach the correct player in the correct quantity. A missing group should produce a diagnosable error instead of granting an unintended reward.

If the result differs

If direct issuance works but the crate fails, inspect its placeholders, quoting and execution context. If the wrong group is used in both paths, correct the group reference before changing randomisation or reward prices.

Keep a recovery path

Restore the original reward action and keep the new group out of public distribution until the trial passes. Remove disposable books and record any real reward already issued; rollback cannot recover sold or applied books.

References and related help

Check the maintainer reference: AdvancedEnchantments documentation, AdvancedEnchantments documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Keep an enchantment configuration edit from breaking YAML loading

A small indentation mistake can disable more than one custom enchantment. Review the first loading error and the edited section before replacing the plugin or resetting its files.

Check the installed content

AdvancedEnchantments separates enchantment definitions, groups, book presentation and permissions. Keep test equipment away from player inventories until both application and activation work. Use the reference for your installed plugin version instead of assuming a configuration from another server will match.

Work through the change

1. Save the affected file and identify the last known working version. Record which enchantment section changed and the first configuration error from an orderly staging startup.
2. Compare that section with the installed-release setting reference. Check indentation, list structure and quoting around text containing YAML punctuation without blindly reformatting the whole file.
3. Make one minimal correction on the staging copy and restart it normally. Read the first remaining error, since later missing-enchantment messages may only be consequences of the initial parse failure.
4. Obtain one disposable book from the edited section and one from an unchanged section. Confirm that both load and that the changed setting has the intended effect.

Verify the result

The file should load without the original parse error and both representative enchantments should remain available. A successful server startup alone does not prove that a rejected section was registered.

If the result differs

If the same line fails, inspect the preceding line and enclosing list or mapping. If syntax loads but a setting is rejected, check version support rather than inventing an alternative configuration key.

Keep a recovery path

Restore the last working file if the correction is uncertain. Keep the broken copy for comparison and preserve player data; a configuration parse error does not justify deleting enchantment inventories or reinstalling the server.

References and related help

Check the maintainer reference: AdvancedEnchantments documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.