Do not run this jar in production; copy it to another setup. Don't worry that it is Mojang mapped, plugins jars will automatically be remapped. Only the CB package relocation cannot be handled automatically. This test is only relevant for you if you either try to parse the relocated CB package version, or if you are using internals/nms.

The first startup on this jar will take a bit longer depending on your system and number of plugins.

In the following cases you have to take action:

• Your plugin fails to load because it tries to parse the no longer existing package version: Please see https://forums.papermc.io/threads/important-dev-psa-cb-package-relocation-will-be-removed.1106/ for solutions
• You are creating a new classloader to load classes: These will not be remapped by our rewriting, so you will either have to make sure they are compatible with a Mojang mapped server without CB package relocation, or you have to use the Paper plugin classloader
• Your plugin fails to load or run due to errors not related to package version parsing: Please report them on our Discord or under https://github.com/PaperMC/testing/issues
• You get the exception Caused by: java.lang.IllegalStateException: Duplicate entries detected: The plugin in question contains duplicate class entries, which should be solvable by improving your dependency tree or ignoring duplicate classes (ask us for help in the Discord if you need any)

You may also test whether your plugin is able to run natively on an unrelocated, Mojang mapped server by adding -Dpaper.disable-plugin-rewriting=true to your startup flags. With its proper release, you will also be able to individually disable remapping of your plugin via the jar manifest.