Studio board: [Game Name]

My tasks

Choose who you are

Garrack (lead)

#2 Shared objective: capture point rules plan
Plan approved P1 Prototype Small Risk: Low
Since just now. Next: Start
Files: docs/design/ docs/design/objective-capture.md
Start Drop

On the website you are recognized automatically. Inside Mr. Mak, pick your name; the choice stays on this device only. Buttons open the task on GitHub when one-click is not available.

Open tasks by role

Role Milestone Priority New task

3D Art 2 open

#8 Hero character model and textures
Open P1 Vertical Slice Large
Model, UV and texture the hero from the approved concept sheet.
Claim
#9 Modular wall and floor kit
Open P2 Vertical Slice Large
Replace the test map greybox walls and floors with a small modular kit: 3 wall pieces, 2 floor tiles, 1 corner, on a 1 m grid.
Claim

Animation 2 open

#15 Locomotion set: idle, run, jump, land
Open P1 Vertical Slice Medium
Create the core locomotion set for the hero: idle, run forward, run strafe left and right, jump, fall and land.
Claim
#16 Capture interaction animation
Open P2 Vertical Slice Small
A short capture pose and loop the hero plays while standing on the point.
Claim

Audio 1 open

#25 Footstep and jump sound set
Open P2 Vertical Slice Small
Footsteps on two surfaces, jump and land sounds for the hero.
Claim

Backend 1 open

#22 Match result record (server to backend)
Open P3 Alpha Medium
When a match ends the server posts a small result record (teams, score, duration, build ID) to a backend endpoint.
Claim

Build/DevOps 1 open

#24 Build machine setup checklist
Open P1 Vertical Slice Medium
Write the checklist for the self-hosted build machine: OS, runner install, engine install, cache folders, disk layout.
Claim

Community 1 open

#30 First devlog post draft
Open P3 Vertical Slice Small
Draft the first short devlog: who we are, what we are building, a few screenshots of the test map and the board.
Claim

Concept Art 2 open

#6 Hero character concept sheet
Open P1 Prototype Medium
Three silhouette options for the hero character, then one developed into a front, side and back sheet with a color pass.
Claim
#7 Capture point prop concepts
Open P2 Prototype Small
Concept the capture point object so it reads from across the map: shape, size relative to the hero, and a lit state versus an idle state.
Claim

Design 2 open

#1 Movement feel pass: run and jump tuning
Open P1 Prototype Medium
Tune run speed, acceleration, jump height and air control so moving around the test map feels good with 4 players at 150 ms.
Claim
#3 Prototype test map blockout
Open P1 Prototype Medium
Build a greybox test map sized for 4 to 8 players with one capture point, two spawn areas and a few sightline breakers.
Claim

Gameplay Code 3 open

#17 Character movement controller (replicated)
Open P0 Prototype
Implement the base movement controller: run, jump, air control, with server authority and client prediction.
Claim
#18 Capture point gameplay logic
Open P0 Prototype Medium
Implement the capture point: entering, contesting, progress, scoring and the end-of-match condition from the design rules.
Claim
#19 Spawn and respawn system
Open P1 Prototype Small
Players spawn at their team's area and respawn after a short delay.
Claim

Lighting 1 open

#13 Test map lighting pass
Open P2 Vertical Slice Medium
Light the test map so spawns, lanes and the capture point read clearly.
Claim

Marketing 1 open

#29 Studio one-pager for recruiting
Open P2 Prototype Small
A one-page PDF about the studio and the project for prospective developers: what we make, how we work, how to join.
Claim

Music 1 open

#26 Main theme sketch (90 seconds)
Open P3 Vertical Slice Medium
A 90 second sketch of the main theme in the direction from docs/vision.md.
Claim

Narrative 2 open

#4 Setting pitch: where and when
Open P2 Prototype Small
Write a one-page setting pitch: the world, the time, who the players are and why they are here.
Claim
#5 Character barks: first 20 lines
Open P3 Vertical Slice Small
Write 20 short in-game lines for the hero: spawn, capture, win, lose, low health.
Claim

Network Code 2 open

#20 Session and team assignment
Open P0 Prototype Medium
Server assigns players to two balanced teams on join, handles late joiners and leavers, and keeps the team list in sync on every client.
Claim
#21 Network emulation preset for local testing
Open P2 Prototype Small
Add a one-click preset for local testing: 2 to 4 players, 120 ms latency, 2 percent packet loss, so everyone tests the same way.
Claim

QA 2 open

#27 Playtest feedback form and bug template
Open P1 Prototype Small
Create the short Google Form used after each playtest and a bug task template so bugs become tasks in one click.
Claim
#28 Smoke test checklist for test trains
Open P2 Vertical Slice Small
A 10 minute checklist to run on each new test train build: join, move, capture, respawn, leave.
Claim

Rigging 1 open

#14 Hero rig with IK and facial basics
Open P1 Vertical Slice Medium
Rig the hero model: body with foot and hand IK, a simple face rig for the barks.
Claim

Tech Art 1 open

#10 Master material and naming validator
Open P2 Vertical Slice Medium
Set up one master material with the common parameters and write a small script that flags assets not following the naming rules.
Claim

Tools 1 open

#23 Export standards checker for hand-off files
Open P2 Prototype Small
A script that checks files in a hand-off folder against the export standards (scale, naming, texture sizes) and writes a short report.
Claim

UI Art 1 open

#11 HUD layout: health and objective state
Open P1 Prototype Medium
Design the in-match HUD: health, the capture point state, score and a small team list.
Claim

VFX 1 open

#12 Capture point ring effect
Open P2 Vertical Slice Medium
A looping ring effect on the capture point that changes color per team and pulses when contested.
Claim

Claim opens the task on GitHub when one-click is not available. Comment /claim there.

Who has what

Who	Active	Holding
Garrack (lead) Producer, Design	1	#2 Shared objective: capture point rules Plan approved since just now

Plan inbox

Approved 1

#2 Shared objective: capture point rules plan by bradevanolson-cloud
Plan approved P1 Prototype Small Risk: Low
Orchestrator says Approve: This plan serves the "one shared objective" pillar directly and is listed in the Prototype milestone under capture point rules and logic. It is a single design page with no collisions, no code and no binary assets, so the risk is low. One suggestion for the page itself: include how capture state is shown to players, since "readable at a glance" is a pillar and the HUD and audio work will lean on it. (Oct 14, 01:39 UTC)
Files: docs/design/ docs/design/objective-capture.md

Orchestrator mode: suggest. It suggests, the lead decides with Approve or Request changes.

Test trains and previews Demo data, coming in Phase 2

Current train: train-1014-3

Building client and server. About 18 minutes left.

Tasks: #8 Hero character model and textures, #23 Export standards checker for hand-off files

Train	Result	Tasks	Build	Started
train-1014-2	Build ready on the test server	#19 Spawn and respawn system	1014-9c1e	Oct 14, 10:05 UTC
train-1013-1	Task 12 failed its checks and was returned; the rest shipped	#3 Prototype test map blockout, #12 Capture point ring effect	1013-77b0	Oct 13, 20:30 UTC

Live previews

#17 Character movement controller (replicated) by dev-a: preview-17.example.com:7777 (until Oct 14, 17:00 UTC)

Merged today Demo data, coming in Phase 2

artist-b	#8 Hero character model and textures
dev-a	#23 Network emulation preset for local testing

Orchestrator log

When	Task	Decision	Reason
Oct 14, 01:39 UTC	#2	suggest-approve	This plan serves the "one shared objective" pillar directly and is listed in the Prototype milestone under capture point rules and logic. It is a single design page with no collisions, no code and no binary assets, so the risk is low. One suggestion for the page itself: include how capture state is shown to players, since "readable at a glance" is a pillar and the HUD and audio work will lean on it.

[Game Name]: Prototype