SP Core

Version 0.3.0 · Minecraft Java Edition 26.2 · Fabric

SP Core provides shared APIs and a unified admin interface for SP Minecraft mods, connecting economy, quests, and RPG progression through reusable services and consistent management tools.

Manage your installed SP mods from one place with /spadmin.

Created by xMrShadyx. Supports singleplayer and multiplayer.

Features

• One admin command: open /spadmin to access the installed SP modules.
• Shared interface: a dark emerald and gold window with module icons, tabs, tables and a detail preview.
• Draft editing: review changes before applying them, or cancel the draft.
• Flexible forms: text fields, automatic read-only values, dropdowns, new-category input and lists with Add/Remove controls.
• Responsive navigation: scrollable details and forms, with paging for smaller windows and long lists.
• Server permission checks: admin actions require game-master permission and are checked again when submitted.
• Shared economy integration: participating mods use the wallet supplied by SP Economy.
• Shared character experience integration: supported quest rewards use the progression supplied by SP RPG.
• Extensible modules: new mods can register their own panels and services through Core's APIs.

In-game previews

These are actual Minecraft screenshots with the English interface, captured on October 14, 2026 with SP Core 0.3.0 and SP Quests 0.4.0.

Unified admin window

Shared editor

SP Quests uses Core's shared form controls for its catalog editor. The example below shows an automatic quest ID, category selection and separate lists containing three objectives and three rewards.

Category dropdown

Choose an existing category or select + Add category.... The new category remains part of the quest draft until it is saved with Apply.

Requirements

SP Core requires Fabric API. Other SP mods are installed separately and are optional for Core itself. Individual modules may have their own dependencies.

How to use

Run /spadmin while in a world. It requires game-master command permission, normally operator level 2 on a server or cheats enabled in singleplayer. Creative mode alone does not grant access.

1. Choose an installed module from the sidebar.
2. Choose a tab and select the entry or setting you want to manage.
3. Use the available action to open its form or module editor.
4. Review your changes, then choose Apply, Apply and close, or Cancel.

Use Reload to refresh the admin window's data. A module's separate reload action reloads that module's own settings or catalog. Mouse-wheel navigation handles longer lists and forms.

Some modules open their existing editor screens from the hub. Their own access rules still apply: for example, SP Economy's editor also requires Creative mode, and World PIN Lock's settings are limited to the appropriate local world.

Supported SP modules

Core 0.3.0 has been checked with these versions:

What is new in 0.3.0?

Core's shared editor now supports read-only fields, dropdowns, category creation and lists of editable entries. SP Quests 0.4.0 uses these controls for automatic IDs and multiple objectives and rewards.

The new character experience API lets SP RPG 0.5.6 provide explicit RPG experience rewards. Vanilla Minecraft XP and RPG XP remain separate reward types. The existing economy API remains unchanged.

FAQ

Do I need every SP mod?

Does Core create another wallet or reset progression?

No. The owning mods keep their existing balances, character data and quest progress. Core provides the shared connection between them.

Will a new SP mod require another Core update?

A mod using the existing APIs can register itself without changing Core. A new shared capability or API change may require a newer Core release.

Can I remove Core while keeping mods that require it?

Those mods need Core to load. Keep Core installed while using a dependent module.

For mod developers

Register a provider or module descriptor to integrate your mod with the hub. Each module owns its validation, configuration and persistence; Core supplies shared controls and the service registry.

• Economy API: balance access and transactional payments.
• Admin API: module registration, panels, typed fields and permission/session handling.
• Character experience API: provider registration, complete awards and rollback snapshots.