Version Compatibility and Known Limitations

Version Compatibility and Known Limitations

Overview

This page tracks verified compatibility expectations and behavior limits to reduce upgrade surprises. Use it as a pre-change checklist before enabling new subsystems.

How It Works

Declared plugin API version is 1.13, and the project targets Java 8 source compatibility while also running in newer Java runtimes in current development workflows.

Compatibility subsystems

• Runtime platform subsystem (Spigot/Paper API level)
• Java runtime subsystem
• Backend dependency subsystem (MySQL/Mongo requirements)
• Optional integration subsystem (Citizens/Placeholder/etc)
• Command and open-route behavior subsystem

Configuration

Compatibility-sensitive areas:

• save backend driver availability
• optional integration plugins
• conversion and upgrade flags

Admin preflight:

1. Confirm server/runtime compatibility.
2. Confirm backend dependencies are available.
3. Confirm optional integrations are installed before enabling their keys.
4. Confirm open-route behavior with subset settings.

Commands

No dedicated compatibility commands exist.

Permissions

No dedicated compatibility permissions exist.

Data and Storage

Known storage constraints:

• MongoDB mode requires external mongodb-loader plugin.
• Non-SQLite backend connection failures revert to SQLite.

Examples

• Multi-server interest setups should designate one main handler server for offline interest systems.

Troubleshooting

• If optional integrations fail to load, disable their feature flags or install missing dependency plugins.

Known Limitations

• Open-type routing currently maps MENU, ITEMS, MONEY, and EXP directly in inventory manager selection; LOANS and CHEQUES enum values are present but not directly routed by that selector.
• In generated conf/commands.yml, Admin > Tax > Info and Admin > Tax > Withdraw both use the command token withdraw, which can cause command-shape ambiguity.
• No built-in automated backup orchestration command is present.

Operational interpretation:

• Keep loans/cheques navigation expectations aligned with current open-route behavior.
• Validate tax-admin command behavior on your command map before production rollout.

Related Pages

• GUI and Inventory Interactions
• Backup, Recovery, and Migration