NH-Quest-Editor

The GT New Horizons questbook in the browser, recreated from BetterQuesting's own GUI code and textures. Quests come straight from the modpack's master branch; item names, icons and recipes come from a headless export of the latest GTNH daily build.

Click any item in a quest to see its recipes in an NEI-style window (right click for its uses). Crafting, smelting and all GregTech recipe maps are shown so far.

Planned next: more recipe handlers.

Editing quests

Edit mode (Settings) turns the site into BetterQuesting's editor, as /bq_admin edit does in game, with the same screens: the quest editor (Edit in a quest: name, description and the text editor, icon, visibility, logic, notification settings and the raw NBT), the task, reward and prerequisite editors, the quest line editor (the gear at the bottom left) with its Add/Remove Quests screen, and the designer (next to it) with the toolbox: open, new, grab, link, copy, scale, delete, remove, icon and frame, grid snap and box selection.

Every change is one undo step (Ctrl + Z, Ctrl + Y) and is kept in the browser. The Edits screen (the brush at the bottom left) lists the changes and downloads them as the changed files or as a git patch for a pull request to the modpack. The files are written as BetterQuesting would save them after the same edit in game, so the pull request only holds the real changes.

The browser has no player or world, so a few things work differently: items are picked from NEI's item list (NEI's bookmarks stand in for the inventory), mobs are saved by id only, and the progress tools, importers and the notification preview are off.

Reviewing pull requests

The questbook can show a pull request to the modpack as it would leave the quests: open the review button at the bottom left (or Settings, or #/review), pick an open pull request that changes quests or type any number. Every change is listed with a checkbox, grouped by quest line, and marked in the questbook itself:

• quest lines with changes show how many in the list;
• on the map, changed quests are outlined (green new, blue changed, purple moved) and quests that were removed or moved show as dashed outlines where they were;
• in a quest, changed tasks and rewards are tinted with their title in colour, a bar beside the description and lines under the name and buttons mark other changes, and the description shows added words underlined in green and removed words struck out in red;
• B (or the button in the side bar) switches between the questbook before and after the pull request.

Ticks are kept in the browser per pull request; a tick stays until a later commit changes that quest again. Links keep the pull request (?pr=<number>), so any screen can be shared.

How it works: GitHub's API gives the pull request and the files it changes since its merge base (about three requests; GitHub allows 60 an hour without a token, and a token entered in the review screen raises that). The files themselves come from raw.githubusercontent.com, at the merge base and at the head, and are compared object by object (quest, quest line, placement) over the site's own quest data, so changes made on master since the branch started are not mistaken for the pull request's. Those changes are then applied to master's quests, which is what the site shows; changes that master also made since are flagged.

npm run review -- <number> prints the same list in a terminal (NODE_USE_ENV_PROXY=1 behind a proxy).

Layout

site/        the website (TypeScript + Vite, no framework; the GUI is drawn on a <canvas>)
  src/gui/       port of BetterQuesting's GUI toolkit: themes, panels, Minecraft font
  src/screens/   questbook screens: quest lines, quest, search, properties, settings
    editor/        BetterQuesting's editor screens: quest, tasks, prerequisites, lines, designer
  src/nei/       NEI's recipe window and its handlers (crafting, smelting, GregTech)
  src/edit/      edit mode: the quest files as a database with undo, autosave and exports
  src/review/    review mode: a modpack pull request's quest changes, fetched from GitHub
  scripts/       data build steps (quests, items, recipes, vanilla assets)
exporter/    Forge 1.7.10 mod that exports items, icons and recipes from a running client
.github/workflows/
  export.yml     runs a daily build headless with the exporter, publishes the "game-data" release
  site.yml       builds the site from modpack master + game data and deploys GitHub Pages

Working on the site

Needs Node 22.18 or newer.

cd site
npm install

# Quest data from a checkout of GT-New-Horizons-Modpack
npm run data:quests -- ../../GT-New-Horizons-Modpack/config/betterquesting/DefaultQuests

# Minecraft's font and a few GUI textures, downloaded from Mojang (not stored in this repository)
npm run data:vanilla

# Optional: item names and icons, from the files in the "game-data" release
npm run data:items -- path/to/export.json path/to/icons public/data/questbook.json

# Optional: recipes for the NEI views, from the same files; their GUI textures are in the
# release's gui-textures.tar.gz (unpack it into public/)
npm run data:recipes -- path/to/export.json path/to/icons public/data/nei

npm run dev

Without item data the questbook still works; items show their registry names and a placeholder.

Credits

• GUI textures, theme definitions and translations in site/public/assets/betterquesting and site/public/assets/bq_standard are from BetterQuesting (MIT, see the LICENSE files there).
• The exporter is based on gtnh-calc-oracle from gtnh-factory-flow (MIT); see exporter/README.md.
• The recipe views draw with GUI textures from NotEnoughItems, GT5-Unofficial and ModularUI (LGPL-3.0). They are taken from the pack's jars when the game data is exported and published with it; they are not stored in this repository. The recipe window's layout follows NEI's and GregTech's, reimplemented here.
• Minecraft assets belong to Mojang and are downloaded at build time.