Skip to content
This repository was archived by the owner on Aug 1, 2026. It is now read-only.

Repository files navigation

bertie

Important

Development has moved to the bertie monorepo. This repository is retained read-only for historical tags, releases, and issues.

An exploration, technology and magic modpack for NeoForge 1.21.1.

About 500 mods. Managed with packwiz.


Installing

Client

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.

Server

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 Windows

Accept the EULA in eula.txt on first run.


Developing the pack

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 change

Always 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.

bertie's own mods come from GitHub Releases

The mods written for this pack live in their own repositories under bertie-mc and are consumed here as tagged releases:

Mod Repo
bertie_progression bertie-progression — the pack's progression mod
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.

Known-raw content

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.

Pinned versions — do not "update" these

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 familyftb-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 development instance where current quest and progression work is authored. These versions are the tested compatible set. Do not bump one in isolation.


CI

Workflow When What it does
validate.yml every push and PR index is current, target filenames are unique, every metafile has a side, and no JAR is tracked
server-boot.yml nightly or manual prepares the server-side pack and requires a headless dedicated server to reach readiness
client-boot.yml nightly or manual prepares the client-side pack and requires a headless client to join an integrated world
release.yml tag v* or manual independently exports the client .mrpack and no-mod-JAR server zip; tags publish both

A green validate means the pack manifest is internally consistent. Preparing each runtime resolves and verifies that side's downloads before launch. A green server-boot means the complete server half actually starts; a green client-boot means the complete client half loaded resources, created an integrated server, generated a world, and joined it. Together the two runtime suites cover installation and side-specific composition.


Releasing

Before tagging, manually dispatch both runtime workflows for the exact commit being released and confirm that Client world join and Server readiness are green for that SHA.

# bump `version` in pack.toml, commit, then:
git tag -a v0.2.0 -m "Release v0.2.0"
git push origin v0.2.0

release.yml composes the shared client and server exporters, then publishes their artifacts without duplicating either export recipe.


Versions

Minecraft 1.21.1
NeoForge 21.1.233
Java 21

Licence

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.

About

Archived modpack; development moved to bertie-mc/bertie.

Topics

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors