Velocity Arena — Today's mission

"You have 20 points. Four stats. One Robot Soccer Tournament. Figure out the best way to use them. Then prove it."

You are on a three-person team. Your team programs a robot to play soccer on a coordinate grid. Every team gets the same 20 points to split across four stats: Speed, Endurance, Turning, and Power. No one gets more. No one gets less.

Your job is to figure out which split wins. You will use math to predict what your robot will do. You will run matches to test the predictions. You will change the rules. You will compete.

By Day 20, you will be able to look at a formula, tell someone what it means, and show them on the field.

When You're Stuck

Make these three moves before raising your hand. They solve most things.

Check the reference card

Most answers are here. Read the formula. Try it.

▾

The four formulas

Speed

motorPower% = (S×100) ÷ 20

Endurance

P(t) = 100−(20−E)×1.5×t

Turning

arcSegments = T
turnRatio = 0.2+(T×0.02)

Power

charge = P²
followThrough = 120 + (P×35)

Budget: S + E + T + P = 20

Does the formula on the card match your question?

Formula found. Try the calculation. If your answer still doesn't make sense after plugging in, move to Step 2 ↓

That's okay. The formula you need might be in today's worksheet. Check the dashboard next ↓

Check the dashboard

Look at your last three residuals. The pattern is usually there.

▾

Your last 3 match residuals

Match Log — recent

M34 goals2 goals+2L

M43 goals3 goals0W

M55 goals2 goals+3L

A residual of +2 or +3 means you're over-predicting. Check your Endurance formula — is your bot losing power faster than the formula says?

Can you see a pattern in your last three residuals?

Name the pattern in one sentence. Write it in your Match Log. Now you know what to change for your next match.

Three data points isn't always enough. Try Step 3 — your teammates might see something you don't ↓

Ask your teammates

Each role sees a different part of the system.

▾

Analyst

Knows the numbers. Ask about predictions and residuals.

Coder

Knows what the program actually does. Ask about formula execution.

Fabricator

Knows what the bot does on the field. Ask about hardware behavior.

Did a teammate help you figure it out?

Nice. Log what you found — it'll help you predict better next match.

Raise your hand. Tell your facilitator: (1) what formula you tried, (2) what your residuals showed, (3) what your teammates think. That's all they need.

🤖

Velocity Arena Pit Crew — AI Hint Assistant

Describe your problem. Get a hint — not the answer. Tell it what you tried in Steps 1–3.

Protocol If you lost the match ▾

Breathe. Nobody writes anything for 60 seconds.

Open the Match Log. Point to the residual. What did you predict, and what actually happened? Name the gap.

Pick one thing. One variable you will change, or one formula you will verify, before the next match. Write it in the dashboard.

If your team lost three matches in a row, your facilitator will check in. That is normal. It does not mean your loadout is bad. It means the rest of your week needs a different plan.