Offensive strategies

The 8-plate constraint changes everything

You effectively have 8 opportunities to score a meal.

Therefore:

Meal

Full-value points

8 plates

🥗 Salad

10

80

🍕 Pizza

30

240

🥪 Sandwich

50

400

If you could choose eight sandwiches and successfully score all eight:

8 × 50 = 400 points

If you chose eight pizzas:

8 × 30 = 240 points

If you chose eight salads:

8 × 10 = 80 points

So the plate is now the scarce resource.

2. This makes the Quality Check decision much clearer

Quality Check does not create another scoring opportunity.

It uses one of your limited plates.

For example:

Sandwich on field

50 points

Same sandwich through Quality Check

25 points

You haven't created another 25 points.

You've used one of your eight plate opportunities to obtain 25 instead of 50.

Therefore:

Quality Check should NOT be viewed as additional scoring.

It should be viewed as:

An alternate, lower-value method of scoring one of our eight plates.

That's a major strategic distinction.

3. When would Quality Check make sense?

Only if the time savings or other strategic advantage compensates for losing half the points.

For example:

Full-value sandwich

50 points
30 seconds

1.67 points/sec

QCA sandwich

25 points
10 seconds

2.50 points/sec

In that hypothetical case, QCA could make sense because the robot gets back into another scoring cycle much faster.

But remember:

You only have 8 plates.

Once you've scored all 8, you can't keep generating additional meal points simply because you have time remaining.

4. This creates a new equation

For Rooted Robotics, I would now use:

VALUE OF A PLATE

Instead of just:

Points per second

you need:

Points per plate + time per plate

Because you have only eight.

5. Maximum meal value from eight plates

Assuming eight plates can each receive one meal:

All salads

8 × 10 = 80

All pizzas

8 × 30 = 240

All sandwiches

8 × 50 = 400

That's a potential 320-point difference between an eight-sandwich strategy and an eight-salad strategy.

That's enormous.

6. Drinks become extremely important

You also have:

8 maximum drinks

And adding a drink to a completed meal gives:

+12 points

So if all eight plates receive a matching drink:

8 × 12 = 96 additional points

Therefore:

Eight sandwiches + eight matching drinks

400 + 96 = 496 points

before considering other scoring-location bonuses.

That makes the drink mechanism potentially very valuable.

But the engineering question is:

Can we add the drink without slowing the meal cycle enough to prevent us from scoring all eight plates?

7. Now consider Autonomous Dining Room

This is potentially even more significant.

Your table says:

Autonomous Dining Room: 50 points

and the maximum is 8.

If the same completed plate/meal can receive the Autonomous Dining Room scoring value in addition to its normal meal value, then a sandwich could potentially be:

Sandwich

50

Autonomous Dining Room

50

=

100 points per plate

Then eight successful autonomous sandwich placements would represent:

800 points

before applicable drink scoring.

However, I would want to verify the complete 2026 scoring language before we assume every bonus/location value can be stacked on the same plate. The wording you provided says the Autonomous Dining Room points are added to the Robot Carried/In Field points, so it appears to be a major scoring opportunity.

8. This makes Autonomous Dining Room a completely different strategy

If it is possible to repeatedly place completed sandwiches in the Autonomous Dining Room, the team should investigate it very seriously.

But there's a critical limitation:

You only have 8 plates.

So the question isn't:

"Can we score 8 autonomous meals?"

It is:

"Can we make each of our 8 plates worth as many points as possible?"

That changes robot design.

9. Your robot should potentially be designed around the PLATE

Think of each plate as a scoring investment.

Plate 1

Acquire → Build → Drink → Score

Plate 2

Acquire → Build → Drink → Score

Plate 3

Acquire → Build → Drink → Score

...

Plate 8

Acquire → Build → Drink → Score

The goal is:

MAXIMIZE VALUE × 8

10. Here's where meal selection gets interesting

Suppose your testing shows:

Meal

Points

Cycle time

Salad

10

6 sec

Pizza

30

12 sec

Sandwich

50

20 sec

Eight cycles:

Salad

8 × 6 = 48 sec

80 points

Pizza

8 × 12 = 96 sec

240 points

Sandwich

8 × 20 = 160 sec

400 points

You can still finish eight sandwiches within 180 seconds.

So:

Sandwich wins on total score.

But imagine sandwich takes 30 seconds:

8 × 30 = 240 seconds

You can't complete eight.

Then:

Six sandwiches

6 × 50 = 300 points

with 60 seconds remaining.

Now the team needs a secondary strategy.

11. This gives you a much better match-planning model

Instead of:

"We will score sandwiches."

The team should say:

Our 180-second production plan

Goal:

Score the maximum value from 8 plates.

Then establish:

Primary plate

🥪 Sandwich

Secondary plate

🍕 Pizza

Emergency/fast plate

🥗 Salad

For example:

Sandwich → Sandwich → Sandwich → Pizza → Sandwich → Pizza → Sandwich → Pizza

could potentially be better than trying to force eight sandwiches if the sandwich cycle is substantially slower.

12. Quality Check now becomes an emergency/efficiency option

I would NOT make QCA the default strategy.

Why?

Because:

Full-value sandwich

50

QCA sandwich

25

That's a 25-point loss on one of only eight plates.

If you do that eight times:

Full field

400

QCA

200

Difference:

200 points

That's too significant to ignore.

So QCA needs to save enough time or provide enough strategic advantage to justify that loss.

13. Example of when QCA DOES make sense

Imagine:

Field scoring

50 points
25 seconds

Eight plates:

200 seconds

You can't finish all eight.

But:

QCA

25 points
10 seconds

Eight plates:

80 seconds

Now you can process all eight.

Field:

Maybe 7 sandwiches:

350 points

QCA:

8 sandwiches:

200 points

Field is still better in this hypothetical.

But if QCA enables additional scoring bonuses or frees the robot to perform other high-value actions, the calculation changes.

That's why your team needs actual cycle testing, not assumptions.

14. Defense also becomes easier to evaluate

With only eight plates, you don't have an unlimited scoring stream.

Suppose the opposing robot is carrying a nearly completed sandwich.

That plate could potentially be worth:

50+ points

depending on where it is scored.

Stopping that scoring opportunity could therefore be much more valuable than preventing an opponent from harvesting a 4-point item.

But there's another side:

If your robot spends 20 seconds defending, you're giving up part of your own opportunity to process those eight plates.

So defense should be evaluated as:

Points denied to opponent

versus

Points sacrificed from our eight-plate production system

15. I would now define Rooted Robotics' strategy this way

THE 8-PLATE STRATEGY

Objective 1

Maximize the value of every plate.

Objective 2

Complete all eight plates as quickly as practical.

Objective 3

Prioritize high-value meals.

Objective 4

Add drinks when the time cost is justified.

Objective 5

Use Autonomous Dining Room when its expected value justifies the complexity/risk.

Objective 6

Use Quality Check selectively—not as a bonus, but as an alternative scoring route.

Objective 7

Use remaining match time for secondary scoring or legal defensive actions once the primary scoring plan is constrained.

16. The most important testing data

I would have your students run 10–20 complete cycles for each option.

Record:

Strategy

Points/Plate

Cycle Time

Success Rate

8-Plate Total

Time for 8

Salad Field

10

Pizza Field

30

Sandwich Field

50

Salad QCA

5

Pizza QCA

15

Sandwich QCA

25

Sandwich + Drink

62

Pizza + Drink

42

Sandwich + Autonomous

100*

*Assuming the scoring combination is confirmed by the complete rules.

17. And this gives Rooted Robotics a fantastic BEST presentation story

Your students can say:

"Our team identified the eight scoring plates as a limited production resource. Rather than simply maximizing the number of tasks our robot could perform, we analyzed the points, cycle time, and reliability associated with each plate. We designed our robot to maximize the value generated by each of those eight opportunities within the 180-second production window."

That is much stronger than:

"Our robot can score sandwiches, pizzas, and salads."

It demonstrates that Rooted Robotics is thinking like an actual company:

Limited resources → Customer requirements → Market analysis → Engineering tradeoffs → Data → Product design → Business value.

Defensive strategies

Don't defend points. Defend the opponent's limited scoring opportunities.

Because the opponent has only 8 plates, every plate they successfully convert into a high-value meal is a scarce opportunity you cannot get back.

1. The opponent's 8 plates are the real target

Assuming the same 8-plate limitation applies to each team, the opponent has only:

8 plates × their scoring opportunities

So the opponent cannot score an unlimited number of meals.

Your defensive objective becomes:

Force the opponent to spend time on lower-value plates, miss opportunities, or use their eight plates inefficiently.

That is potentially more valuable than simply pushing their robot around.

2. Defensive value hierarchy

Based on the scoring table you've provided, I would rank what you want to deny by potential value:

Opponent opportunity

Potential value

Defensive importance

🥪 Sandwich + major scoring location

Very high

🔴 Critical

🥪 Sandwich

50

🔴 Critical

🍕 Pizza + major scoring location

High

🔴 High

🍕 Pizza

30

🟠 High

🥤 Drink added to completed meal

+12

🟠 Moderate

🥗 Salad

10

🟡 Lower

Harvest task

4–8

🟢 Low

QCA sandwich

25

🟠 Moderate

QCA pizza

15

🟡 Moderate

QCA salad

5

🟢 Low

But there is an important wrinkle:

You don't necessarily want to stop the opponent from scoring a low-value task if doing so costs you more than the points you're denying.

3. The 3-minute clock makes defense expensive

Suppose your robot is capable of earning:

300 points / 180 seconds

That's:

1.67 points/second

If your robot spends 20 seconds defending:

20 × 1.67 = 33.4 points

of potential offensive production.

Therefore, if you spend 20 seconds defending, you need to ask:

Can this defensive action realistically deny more than ~33 points of opponent value?

If you're blocking a salad worth 10 points:

Probably not worth dedicating 20 seconds.

If you're disrupting a 50-point sandwich opportunity:

Potentially much more significant.

4. But there's a second calculation: the opponent's time

This is where defense can become powerful.

Suppose you spend 10 seconds interfering with an opponent's sandwich cycle.

You might not actually prevent the sandwich.

But if you force them to spend an additional 15 seconds recovering:

Your cost:

10 seconds

Opponent's cost:

15 seconds

You have created a 5-second time advantage.

And, more importantly, you may have disrupted their ability to use all eight plates.

5. This is the defensive objective I would give your drivers

Don't tell them:

"Block the other robot."

Tell them:

"Increase the time and difficulty required for the opponent to convert a plate into points."

That is a much better defensive philosophy.

6. The best defensive target may be the opponent's plate

Imagine the opponent is carrying a sandwich.

They have already invested time:

Acquire ingredients → assemble sandwich → transport

Now they're approaching the scoring area.

If they successfully score:

50 points

If they also have an applicable bonus:

Potentially substantially more.

Therefore, the final stage of a high-value scoring cycle may be the most valuable point to contest, provided the rules allow the interaction.

7. Don't waste defense on harvesting

This is probably one of the clearest conclusions from your scoring table.

Suppose the opponent is harvesting:

Vegetables

4 points

or:

Fruit

4 points

Your robot spends 15 seconds trying to stop them.

The opponent might only be gaining 4 points.

Meanwhile, your robot could potentially have been working on a:

30-point pizza

or

50-point sandwich.

That's generally a poor trade from a pure scoring perspective.

So:

Don't spend significant time defending low-value tasks.

8. Defense should focus on HIGH-VALUE PLATE CONVERSION

Think of every opponent plate as going through a pipeline:

Empty Plate

↓

Ingredients

↓

Completed Meal

↓

Transport

↓

Scoring Location

↓

Points

Your defense should focus on the point in the pipeline where you can create the greatest disruption for the least time.

For example:

Empty plate

Low value.

Ingredients

Low-to-moderate value.

Completed sandwich

High value.

Completed sandwich approaching high-value scoring location

Very high strategic value.

9. This also changes how I would think about blocking resources

If two robots need the same resource, the defensive value isn't necessarily:

"Block the resource."

Instead:

"Can we make the opponent spend additional time acquiring a plate's contents while we continue scoring?"

That is a much more efficient form of defense.

Your robot should ideally be:

OFFENSE

Scoring its own plate

while

DEFENSE

Making the opponent's plate take longer.

That's much better than having your robot sit somewhere doing nothing.

10. The ideal defensive robot is actually an offensive robot

This is an important design conclusion.

I would not design Rooted Robotics as a dedicated defensive robot unless the full rules reveal a very strong reason to do so.

Instead, build a robot that can:

Primary

Score quickly

Secondary

Control space

Tertiary

Disrupt high-value opponent cycles when appropriate

That gives you flexibility.

11. Think of defense in three levels

🟢 Level 1 — Passive defense

Simply occupy strategically important space while continuing to score.

Example concept:

Score → return → score → return

while your normal movement makes an opponent's path less convenient.

This costs relatively little offensive time.

🟡 Level 2 — Route denial

If legal, position the robot so the opponent has a harder time reaching a valuable scoring location.

The goal is:

Increase opponent cycle time.

Not:

Destroy the opponent's robot.

🔴 Level 3 — Active disruption

Use only when the opponent is attempting a high-value scoring cycle and the rules permit the interaction.

Potential target:

Completed sandwich → high-value scoring attempt

rather than:

opponent collecting a 4-point harvest item.

12. The 8-plate limit creates a powerful defensive tactic

Suppose the opponent has:

8 plates

and 180 seconds.

If you can cause them to spend so much time on their first several cycles that they only successfully score:

6 plates instead of 8

you have effectively denied them:

2 scoring opportunities.

If those would have been sandwiches:

2 × 50 = 100 points

That's potentially much more meaningful than denying several small harvest tasks.

This is why time denial can be more powerful than direct point denial.

13. Here's the defensive strategy I would test

Early match

Don't immediately commit to defense.

Establish your own scoring cycle.

Determine what the opponent is trying to do.

Middle match

Identify:

What is the opponent's highest-value scoring route?

If they're rapidly producing sandwiches:

Consider targeted defensive interference

If they're spending most of their time harvesting:

Continue scoring.

Don't waste your robot's time chasing 4-point tasks.

Late match

Now the eight-plate limit becomes extremely important.

If the opponent has several completed plates still needing to be scored, those may become valuable defensive targets.

Meanwhile:

Your robot should continue converting your remaining plates.

14. A useful driver decision rule

I would put this directly into your driver training:

BEFORE DEFENDING, ASK:

1. What is the opponent trying to score?

2. How many points is that opportunity worth?

3. How much time will our defense take?

4. What could our robot score during that same time?

5. Can our action actually disrupt the opponent?

6. Is the defensive action legal under the specific rule?

If the answer to #5 is uncertain:

Keep scoring.

15. The strategy can be expressed mathematically

Defensive Net Value

Points potentially denied

−

Our lost scoring opportunity

−

Risk of penalty/failure

If the result isn't favorable, don't defend.

For example:

Scenario A

Deny salad:

10 points

Cost your robot:

20 seconds / ~35 potential points

Result:

Not attractive.

Scenario B

Disrupt sandwich:

50 points

Cost:

10 seconds / ~17 potential points

Potential opponent denial:

50+

Result:

Potentially worthwhile.

Scenario C

Disrupt a high-value autonomous meal:

Potentially 50+ points

Cost:

10 seconds

Result:

Potentially very significant—if the rules permit the defensive interaction.

16. One more important consideration: penalties

This is why I wouldn't teach the drivers:

"Go after the other robot."

I'd teach:

"Control the opponent's scoring options without creating a penalty."

A defensive strategy that occasionally earns a penalty can destroy the mathematical advantage you're trying to create.

So your defensive testing should include:

Effectiveness + legality + penalty risk.

17. Revised Rooted Robotics philosophy

Given everything you've told me:

180 seconds

8 plates

full-value vs half-value QCA

high-value sandwich scoring

limited scoring opportunities

I would define the strategy as:

SCORE → PROTECT → DISRUPT → SCORE

SCORE

Convert our eight plates into as many points as possible.

PROTECT

Don't allow our own high-value scoring cycles to be unnecessarily disrupted.

DISRUPT

When legal and worthwhile, increase the opponent's time/cost to convert a high-value plate.

SCORE

Return immediately to our own scoring cycle.

The key defensive principle for Rooted Robotics

Our robot should never defend simply because it can. It should defend when disrupting a high-value opponent scoring cycle is worth more than the points we give up by spending time on defense.

That gives you a data-driven offensive/defensive strategy, rather than simply calling the robot an offensive or defensive robot.

And for the BEST presentation, this is particularly strong because you can show judges an actual "8-Plate Offensive/Defensive Strategy Model" demonstrating how your team analyzed the game as a constrained production system.