A NeoForge 1.21.1 modpack: the S1 progression questline layered on top of a large exploration / tech / magic mod set.
490 mods. Managed with packwiz.
Download bertie-<version>.mrpack from the Releases page and import it
with a launcher that understands the Modrinth pack format — Prism
Launcher, the Modrinth App, or ATLauncher.
Allocate 8–12 GB of RAM. This is a large pack; 4 GB will not boot it comfortably.
Download bertie-server-<version>.zip from the Releases page, unzip it, and run the
included start script. It ships the server-side mods, the configs, and a NeoForge
installer step — you supply Java 21.
unzip bertie-server-<version>.zip -d bertie-server
cd bertie-server
./start.sh # start.bat on WindowsAccept the EULA in eula.txt on first run.
You need the packwiz CLI on your PATH.
packwiz modrinth add <slug> # add a Modrinth mod
packwiz curseforge add <slug> # add a CurseForge mod
packwiz github add bertie-mc/<repo> # add one of bertie's own mods
packwiz update --all # update everything not pinned
packwiz refresh # rebuild index.toml — run after ANY changeAlways packwiz refresh and commit index.toml together with whatever you changed.
An index whose hashes do not match the tree is worse than no index at all.
The mods written for this pack live in their own repositories under
bertie-mc and are consumed here as tagged releases:
| Mod | Repo |
|---|---|
bertie_s1 |
bertie-s1 — the S1 progression content |
berlords_carving |
carving |
berlords_emi |
berlords-emi |
bertie_filters |
bertie-filters |
bertie_weapons |
bertie-weapons |
bertie_blackhole |
bertie-blackhole |
forgeink |
forge-ink |
hephaestusarchitecture |
hephaestus-architecture |
fdshaderfix |
fd-shader-fix |
frozenregfix |
frozen-reg-fix |
Never drop a built jar into mods/. Release it from its own repo and
packwiz github add it. A loose jar and a metafile can resolve to the same filename,
which makes the index list one path twice and installs two versions of the same mod.
Shipped, but not finished. Treat their behaviour as provisional:
| Mod | Status |
|---|---|
explodetomine (explode-to-mine) |
Raw. In the pack, but the ore/explosion balance still needs work. Its behaviour is not final. |
Deliberately not in the pack:
| Mod | Why |
|---|---|
nebs (Nekos-Enchanted-Books) |
Too work-in-progress to ship. |
| Mod | Pin | Why |
|---|---|---|
ftb-xmod-compat |
21.1.8 | Newer builds require ftblibrary ≥ 2101.1.34 and ftbquests ≥ 2101.1.28, which this pack does not run. 21.1.9/21.1.10 fail server boot. Known issue; 21.1.8 is the stable combination. |
The whole FTB family — ftb-library 2101.1.32, ftb-quests 2101.1.26, ftb-teams
2101.1.10, ftb-xmod-compat 21.1.8, ftb-filter-system 21.1.4 — matches the s1 demo
instance, which is where every quest and the whole progression was authored. Those are the
authoritative versions. Do not bump one in isolation.
| Workflow | When | What it does |
|---|---|---|
validate.yml |
every push and PR | index is current, every download resolves, no duplicate targets, every file has a side |
server-boot.yml |
PRs and nightly | installs NeoForge, resolves the server-side pack, boots a dedicated server headlessly and requires it to reach Done ( |
release.yml |
tag v* |
exports the client .mrpack and a server zip, attaches both to a GitHub Release |
A green validate means the pack is internally consistent and every mod is still
downloadable. A green server-boot means the server half actually starts with all 490
mods loaded — that is the test that catches a mod which resolves but crashes on load.
# bump `version` in pack.toml, commit, then:
git tag -a v0.2.0 -m "Release v0.2.0"
git push origin v0.2.0release.yml builds and publishes both artifacts.
| Minecraft | 1.21.1 |
| NeoForge | 21.1.233 |
| Java | 21 |
The pack manifest, configs and quest data in this repository are dedicated to the public domain under The Unlicense.
This repository contains no mod jars. Every mod is downloaded at install time from Modrinth, CurseForge, or its own GitHub Release, and each remains under its own author's licence. See NOTICE.