Skip to content

[BUG] EcoEnchant Compat won't load. #2320

@ryzech

Description

@ryzech

Description

Using compat-ecoenchants version 6.2.0.11, it starts to enable, then suddenly just disables with no other information as to why.

Minecraft version 1.21.11
Server software Paper
Java version 25.0.2

With further investigation it appears that the API has been updated and was changed slightly:

The following line (27)

this.display = new EnchantDisplay(EcoEnchantsPlugin.getPlugin(EcoEnchantsPlugin.class));

Needs to be replaced with

this.display = EnchantDisplay.INSTANCE;

There are likely further changes needed, but this was what I could figure out in my testing.

Steps to reproduce

  1. Install QuickShop-Hikari version 6.2.0.11
  2. Install qscompat-ecoenchants version 6.2.0.11
  3. Install EcoEnchants version 13.3.0
  4. Start server
  5. Compat plugin will disable itself.

Expected Behaviour

  1. Install QuickShop-Hikari version 6.2.0.11
  2. Install qscompat-ecoenchants version 6.2.0.11
  3. Install EcoEnchants version 13.3.0
  4. Start server
  5. Compat plugin will work.

Screenshots

No response

/quickshop paste URL

Not needed.

Additional Context

No response

Checklist

  • I'm running Paper, and not a fork
  • I confirm that Paper has been updated to the latest build
  • I confirm that QuickShop-Hikari has been updated to the latest stable version released on Modrinth (or the latest CI version)
  • I confirm that I'm using QuickShop-Hikari, not QuickShop-Reremake, and I'm well aware that they're maintained by different people, and that Reremake issues shouldn't be reported here.
  • I confirm that I am running a server that is not a Hybrid Server, (e.g. Mohist, Magma, CatServer, Banner, etc.), and I am aware that QuickShop-Hikari may not function properly on a NeoForge/Forge/Fabric hybrid server, and I am running at my own risk on such a server program, and I am aware that the I run such server-side programs at my own risk and know that I will not receive any support or help for this behavior.
  • I confirm that I have not read these checkboxes and therefore I just ticked them all.
  • I am well aware that if the Issue Ticket is not filled out correctly and completely, it will simply be closed without any response or reason.

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: could-haveNice to have, low effort. Example: Dark mode toggle.scope: integrationsPlugin interop. Example: Supporting WorldGuard.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions