Administration

Modpack update process

Step-by-step

1. Update mods using Modpack Update Manager. Commit & push to develop or a new branch based on develop.
2. Update an existing client instance, based on your branch. Start the client and create a new world. Check if it's working.
3. Check updated configs & breaking changes.
4. Update configs using Modpack Update Manager. Commit & push again.
5. Copy the private test server instance locally and update it, based on your branch. Ensure it the server starts successfully.
6. Update an existing client instance again, based on your branch. Connect to the server. Ensure everything works.
   • Fix issues, commit & push them. Repeat with step 5.
7. Update test server instance, based on your branch. Test connecting via client again. Check if it's working.
   • Fix issues, commit & push them. Repeat with step 5.
8. Create a pull request (if not done already) with the name release X.Y.Z.A
9. Review your changes in the PR. Approve and merge.
10. Update productive client & server instance. Test connecting to the productive server.
11. Update Modlist & Changelog. Also post changelog in Matrix & Discord channel.
12. Build general client & server packages.

Checklist template

## Checklist

### Preparation

- [ ] Update mods
- [ ] Add new mods
- [ ] Remove mods
- [ ] Bump version
- [ ] Check & handle breaking changes
- [ ] Check & update configs

### Tests

- [ ] Updating existing client instance works
- [ ] Updating local test server instance works
- [ ] Create local world with client works
- [ ] Connecting client to server works
- [ ] World from private test instance has no breaking issues
- [ ] Updating private test instance works
- [ ] Updating private prod instance works

### After release

- [ ] Update Modlist & Changelog in Wiki
- [ ] Post changelog in Matrix & Discord channels
- [ ] Create client & server packages