Tribes That May Be

You find yourself in an endless desert with some books and barely appropriate provisions.

Have fun with that.

Launching the modpack

Information on launching the modpack is available on the Tribes That May Be website. For most users it is recommended that builds from the curseforge project page are used.

Modifying the modpack

Adding and removing mods is done by editing the packmaker template. It is important to also keep our mod listing up to date with licensing information as part of changing which mods are included.

Configuration for mods can be done by modifying (or creating) files in the config directory. By using the copy paste mod it is possible to ensure that files will appear in new worlds as well. We use this for customnpcs clones.

Release Management

Tagged commits to mainline branch are generated by including the bump:patch, bump:minor, or bump:major keywords in commit messages. These correspond with changes to the modpack based on semantic versioning.

• A major change is backwards incompatible. Mod changes for example.
• Minor change is new functionality, like quest items.
• Patch changes are bugfixes, like quest typos.

Upon succesfull builds of these tagged releases, the dev server will be updated and a new alpha build will be pushed to curseforge. The devtool is used to interact with the dev server via apis and rcons and ftps.

Building the modpack locally

You've got gumption, kid. I like that.

This has only really been tested on a Windows Subsystem for Linux system. You will need Docker, Python3, the build-essentials package, and water. Because it is always important to stay hydrated.

1. Follow the instructions in config.yml.sample to get a Twitch token for testing
2. Create a YAML file named config.yml with the content twitch_token: "<token>"
3. make build

This will result in a uniquely versioned client and server artifact.