Minecraft plugin NexEngine

🔌 About NexEngine

NexEngine — is a lightweight Minecraft plugin engine/framework designed to be used as a shared dependency for other plugins. NexEngine provides APIs and shared utilities (menu API, editor API, localization assets and helpers) so authors can avoid reimplementing common functionality. NexEngine is intended for Paper/Spigot‑style servers and for plugin authors who need a stable internal engine.

🎯 Purpose

NexEngine solves reuse and consistency: instead of each plugin re‑creating menu systems, editors and localization handling, NexEngine centralizes those features so child plugins can focus on game logic. NexEngine is an engine/framework rather than a gameplay plugin itself and is most valuable when other plugins depend on it.

⚙ Main capabilities

• Menu API (menu building & handling) — API for interactive GUI elements.
• Editor API — utilities to accept and validate editor input from players.
• Localization / assets folder for default game elements and multiple languages.
• Version compatibility handling (reduced NMS usage; aims to work across multiple server versions).
• Placeholder integration support (release notes reference a "papi" argument for lang messages).

(These capabilities and change notes are documented in the project release notes and repository.)

🧩 Who is it for

• Plugin authors who want a shared menu/editor/localization engine.
• Servers running multiple dependent plugins that need consistent UI/locale behavior.
• Teams preferring to keep gameplay logic separate from UI and localization code.

🏗 Examples of usage

• A crate or GUI plugin uses NexEngine for menus and localization rather than implementing its own menu system.
• An author uses the Editor API to validate complex player input for custom item creation.

⌨️ Commands

Information about in‑game commands is not present in the official repository release notes or README. The official sources inspected do not list plugin commands or a plugin.yml with command nodes. Therefore: Commands: Information absent in official sources. ()

🔐 Permissions

The official repository and release notes do not publish a clear permission node list. Permissions: Information absent in official sources. ()

⚙ Installation

📥 Install

• Download the NexEngine .jar from the official GitHub releases (or use the provider plugin that bundles it).
• Place the .jar into your server's plugins/ folder.
• Restart the server (full restart recommended).

📦 Dependencies / Integrations

• No mandatory external dependencies documented. Optional integrations mentioned in release notes:
  • PlaceholderAPI ("papi" argument referenced for language messages) — optional integration. ()

🧾 Configuration

• The repository/release notes do not provide a detailed config reference in the README. Child plugins typically create their own config folders; behavior of NexEngine config generation is not present in the inspected official sources. Configuration files: not documented in official sources. ()

🧠 Additional information

• Repository archived: the GitHub repository for NexEngine was archived by its owner; the author indicated NexEngine is being replaced by a new project (nightcore). Users and plugin authors should review the GitHub release notes before upgrading. ()
• Known code changes: recent releases removed hard NMS dependencies and improved multi‑version handling (release notes mention removal of most NMS and added 1.20.x known versions). ()
• bStats / telemetry: not documented in the inspected official sources.
• Discord support: not documented in the inspected official sources.

⚠ Known conflicts & limitations

• NexEngine is an engine/framework: compatibility depends on child plugins that integrate with it.
• Because the repository is archived and a successor (nightcore) exists, long‑term maintenance and updates may require migration to nightcore for newer plugins.

❓ FAQ

Q1: Is NexEngine still maintained? A1: The GitHub repository shows it was archived and the author pointed to a replacement (nightcore). Check the GitHub repository and release notes for the final status. ()

Q2: Do I need NexEngine to run plugins that list it as a dependency? A2: If a plugin requires NexEngine as a runtime dependency, you must keep the NexEngine jar present. Release notes advise to keep NexEngine installed until dependent plugins are updated or moved to the successor engine. ()

Q3: Does NexEngine support modern Minecraft versions? A3: Release notes document known versions up to 1.20.x (1.20.2 / 1.20.4 mentioned). Exact compatibility depends on the release used; consult the GitHub releases for known version markers. ()

Q4: Where to report bugs? A4: Use the project's GitHub Issues on the NexEngine repository (or the successor repository) — the project uses GitHub for releases and issue tracking. ()

🤝 When to use NexEngine

Use NexEngine when you need a shared, tested engine for menus, editors and localization across multiple plugins. If you are starting a new plugin, check whether the successor (nightcore) is recommended by the author before adding NexEngine as a new dependency. ()