How we work
[Game Name] by Garrack Gaming Studios
[One-paragraph pitch from docs/vision.md goes here. What do players do, with whom, and why is it fun?]
The loop
Every task goes around this loop. You pick what you want to work on, say how you will do it, and ship it when it is ready. Nobody waits for a meeting to get started.
| Stage | Who acts | What happens |
|---|---|---|
| Claim | Anyone | Take one or more open tasks from the board. |
| Plan | You | Fill in a short form: goal, files you will touch, what done looks like. |
| Quick check | The studio | Your plan is checked for overlap with other work, fit with the game, and risk. Usually within the hour. |
| Work | You | Work on your own branch or in your own tools, with the latest build on your PC. Test as much as you like. |
| Preview | You (optional) | Try your branch on a private short-lived test server with friends. |
| Ready to test | You | Put finished work in the queue. |
| Test train | The studio | Everything ready is merged, built once and put on the shared test server. |
| Play | Whoever is online | Join the shared server. Bugs become new tasks. |
You never wait on a person to read your plan
When you submit a plan, it is checked right away: do your files overlap with someone else's approved work, does the idea fit the game's vision, and how risky is the change. Low and medium risk work gets a clear answer quickly. Only high risk work, like netcode or build settings, waits for the studio lead.
Every decision comes with a reason you can read, and the lead can change any of them.
Test whenever you are ready
Local testing on your own PC is unlimited and never required. When you press Ready to test, the next test train merges your work with everything else that is ready, builds it once, and puts it on the shared test server. The board shows the build number and a matching client download.
Anyone can call a playtest at any time, and there is a planned slot every week. Bugs found in a playtest become tasks on the board for anyone to claim.
What the board looks like
This is an example of the board with sample data, so you can see how it reads before you join. The real board lives behind a sign-in for the team.
Tools we use
- GitHub holds the tasks, plans and code. Most people only ever see the board; the buttons do the GitHub part for you.
- Google Workspace for sign-in, the shared Drive, chat and the calendar.
- The game engine is being decided between Unreal Engine 5.8 and Unity 6.3 LTS.
- Your own tools for art, animation, audio and writing: Blender, Substance, a DAW, Photoshop, or whatever you already know.
Artists, musicians, sound designers and writers only need a web browser. You claim a task and submit a plan from the board, work in your own tools, and upload finished files to the task's hand-off folder on the shared Drive. The studio takes it from there.
Want in?
See which roles need help right now and how a first week goes.