Ember’s Questing

Ember’s Questing

Curseforge is taking a exceptionally long time approving a few of the releases, for fabric and 1.20.1 releases you can download from the forgejo https://git.tysontheember.dev/TysonTheEmber/embersquesting/releases

Ember’s Questing is a quest mod for modpacks. Players get a quest book with chapter maps, a HUD tracker, rewards and shops. Pack developers get quests as plain JSON files, an in-game editor that writes those same files, and a one-command import from FTB Quests. The server owns all progress.

It runs on Minecraft 1.20.1 (Forge and Fabric), 1.21.1, 26.1.2 and 26.2 (NeoForge and Fabric). Quest files are the same on every version, apart from a few differences on 26.x.

New to the mod? Getting started walks through your first chapter in about ten minutes.

For pack developers

• Every quest is a file. Chapters are folders, books hold chapters, and the whole thing lives in your pack and your git history.
• JSON schemas give autocomplete and error squiggles in VS Code and IntelliJ. /eq validate lists every broken item id, missing quest and bad reference before a player finds it.
• /eq import ftbquests converts an FTB Quests book, including FTB Money shops, and writes a report of anything it could not carry over. See From FTB Quests.
• The in-game editor saves to the same files, so you can mix hand-written JSON with in-game edits.
• KubeJS scripts get quest events, custom tasks and rewards, and custom content blocks. See KubeJS.
• The cookbook has copy-paste setups for daily quests, secret quests, gated chapters, team chapters, exclusive branches and more.

Writing quests

A quest file holds its tasks, rewards, dependencies and conditions. A quest can wait for other quests, stay hidden until it unlocks, repeat daily or weekly, fail, or let the player pick one reward from a list. Progress belongs to each player, a team or the whole server, chosen per chapter.

Tasks cover items and fluids, kills, crafting, breaking and placing blocks, builds, locations, advancements, stats, XP, money, energy, mod resources and more. Rewards cover items, loot tables, XP, commands, effects, stages, money, a choice between rewards and tables that roll. The full lists are in Tasks and Rewards.

The in-game editor covers everything the files do, with undo, copy and paste, templates, and pickers for items, recipes and quests. It needs op level 2 by default, and editor_permission in the main book.json changes that. See Editor.

Descriptions that teach

Descriptions take Markdown for headings, lists, quotes and links. With Ember’s Text API in the pack, text can also wave, glow or run through a rainbow.

Between the paragraphs you can place images and GIFs, video and audio clips, item lists that open recipes, crafting recipes, entity models, buttons and 3D block scenes. A scene plays a build step by step with camera moves and captions, so the player learns the machine inside the book instead of on a wiki.

A build task shows the structure layer by layer with its material list. The player can project it into the world as a ghost and build over it.

Every content type is listed in Content.

Make it match your pack

Themes are color palettes. The mod ships eight. Deepslate is the default, Minecraft is the lighter vanilla look, and Classic looks like FTB Quests. /eq theme new opens a color picker to make your own, and the result is a small resource pack you ship with the pack.

For bigger changes, every part of the quest screen is a resource pack. Stylesheets work a lot like CSS, and layouts are XML files you can build in an in-game editor. The style pad applies rules as you type, and the inspector shows which rule styles the element you pin. A book can also switch themes on its own while a condition is true, such as night or low health.

Four complete designs ship with the mod to start from. One of them is this star chart.

Start at Themes for palettes, or Quest screen for stylesheets, layouts and the designs.

World view

A chapter can be a small world instead of a flat map. Quests sit on pedestals, the player’s figure walks between them, and mobs wander around. The mod ships islands, plains, caves, a village, a nether fortress and more, and you can capture your own build. Create and AE2 blocks in a captured build keep turning and glowing when those mods are installed. See World layout.

Quest blocks

The Quest Screen block shows a quest on its face, and screens placed side by side merge into one display. It takes items, fluids, energy and mod resources from pipes, so an automation quest completes without a player holding anything. The Quest Port does the same without the display, and can hand fluid, energy and resource rewards back out to pipes. See Quest blocks.

Money and shops

Add a money block to the main book.json and the pack gets a currency. Quests can ask for money and pay it out, shop chapters let players buy and sell, and /eq money pay sends coins to another player. Packs without the block never see any of it. See Money.

Also included

• Pinned quests on the HUD, toasts, popups and a reward inbox
• Team progress through FTB Teams or Open Parties and Claims
• Commands that work on offline players, and a backup of the progress file after each load
• Quest sounds with subtitles that a resource pack can replace
• Default client settings a pack can ship, which still reach players after an update
• A Java API for mods that want their own tasks and rewards

Integrations

Not every integration exists on every Minecraft version and loader.

Without FTB Teams or Open Parties and Claims, team chapters count each player on their own.

Requirements

LDLib2 is bundled. Forge 1.20.1 needs Forge 47.4 or newer and Kotlin for Forge 4.11 or newer. The NeoForge 26.1 jar needs NeoForge 26.1.2.109 or newer. The Fabric jars need Fabric API 0.92 on 1.20.1, 0.116 on 1.21.1, 0.155 on 26.1 or 0.161 on 26.2 or newer.

Docs and support

Everything is documented at tysontheember.dev/embers-questing. Start with Getting started, keep the cheat sheet open while you write, and grab a setup from the cookbook.

Found a bug or have an idea? Open an issue, and upload any logs to logs.tysontheember.dev.