- Paper server
- Java
25 - CoreProtect installed and enabled
Server target:
- Paper
26.2build60beta or a newer compatible 26.2 build
Compile target:
- Paper API
26.2.build.60-beta
Declared plugin API version:
api-version: '26.2'
CoreProtect target:
- CoreProtect
24.0-dev1 - CoreProtect API
12
Notes:
- The current maintained support target is CoreProtect API
11or12. - The runtime hook still accepts some older API numbers internally, but those older versions are not the documented target for this branch.
- Install CoreProtect and start the server once so its data folder is created.
- Stop the server cleanly.
- Copy the XRayHunter jar into the server
plugins/folder. - Start the server.
- Confirm the plugin enables and reports that CoreProtect hooked successfully.
- Review
plugins/1MB-XRayHunter/config.yml. - Run
/xrayhunter infoand/xrayhunter help.
- Stop the server cleanly.
- Replace the old XRayHunter jar in
plugins/. - Start the server again.
- Review the startup self-check and
config.yml. - Run
/xrayhunter debugto confirm the build metadata and CoreProtect hook status.
The plugin keeps its own data folder as:
plugins/1MB-XRayHunter/
Use the normal Gradle build:
./gradlew buildJar naming pattern:
build/libs/1MB-XRayHunter-v<plugin-version>-<build-number>-j25-26.2.jar
Build behavior:
- a successful jar build increments
version.properties - a new jar is written into
build/libs/ - older jars remain until you run
clean
Optional clean rebuild:
./gradlew clean buildAfter installation, verify:
- CoreProtect is enabled before XRayHunter
/xrayhunter infoworks/xrayhunter helpworks/xrayhunter debugreportsCoreProtect hooked: true/xrayhunter lookup 2dreturns either results or a clear no-data message