SP Quests

0.4.0 · Minecraft 26.2 · Fabric · Java 25+

/spadmin → SP Quests → Add quest opens the shared native editor. IDs are assigned on successful Save (quest_000001, quest_000002, ...), skipping catalog and saved history IDs. Existing IDs stay unchanged; editing cannot rename them. The Category dropdown offers existing categories and + Add category.... A new category is a draft until Apply; Cancel writes nothing. Objectives and Rewards open list editors with Add/Remove, previous/next entry navigation and type dropdowns. Each quest has 1–16 objectives and 1–16 rewards. All objectives must be completed before the entire reward batch can be claimed once.

Objective types: KILL, MINE, SUBMIT. Rewards: COINS, ITEM, and experience. With RPG installed, select RPG_XP; without RPG, select XP for vanilla Minecraft experience. These are distinct currencies. Minecraft MMORPG disables vanilla XP, so XP rewards are refused when it is installed. RPG_XP requires MMORPG 0.5.6+ and Core 0.3.0+. Coin rewards use the existing SP Economy wallet; Core stores no second balance.

/quests opens the player journal with category tabs, missions on the right and individual objective progress plus rewards on the left. Accept starts a mission; Submit items delivers matching items; Finish quest appears when all tasks are done. Long details and lists scroll independently; rewards and categories can be paged. The server sends 16 missions per page and filters the entire catalog/history by category. Admin catalog and own-progress tables also send 16 rows per page.

Data and migration

Catalog: config/sp-quests/quests.json, format 2 with nextQuestNumber, categories, quests and optional disabled. Maximum 128 missions and 64 categories (32 characters each). Names are at most 80 characters; descriptions 1000. Objectives contain type, target, count (1–100000). Rewards contain type, item, amount: coins 0–10^12, items 1–4096 per entry, XP/RPG_XP 1–1000000 combined per type. Registry IDs are validated. Non-item rewards use an empty item value. The ID counter is saved only with a valid successful quest save. Catalog reload/edit/disable affects future acceptance only.

World data: <world>/sp-quests.json, format 2, per-player UUID, up to 1024 retained quest IDs. Each state contains its frozen definition, progressByObjective, aggregate progress, and claimed. Every successful mutation saves through temp-file replacement. Invalid/future files stop loading instead of resetting data.

Format-1 catalogs and progress load automatically. Missing arrays become the old single objective/coin reward; IDs, accepted rules, partial progress and claim history are preserved. First format-2 write backs up the original file once as quests.json.pre-v2 (catalog) or sp-quests.json.pre-v2 (world). Existing backups are never overwritten. Old scalar quest fields remain compatibility adapters. Do not load format-2 data with old binaries; restore a complete backup for a downgrade.

Rewards preflight the entire inventory and XP/wallet limits. A full inventory refuses the batch without dropping items. Normal wallet/quest/effect write failures restore coins, inventory, XP and claim eligibility. Separate wallet, quest, Minecraft player and RPG character files are not crash-atomic: back up the complete world. An abrupt process crash is not an exactly-once transaction guarantee.

Daily/Weekly/Monthly are categories without automatic resets. Quest chains, party credit, NPCs and admin progress resets are not implemented. Already accepted missions remain available even if their catalog definition is disabled or removed.