Township Regatta Planning: Choose Tasks Your Team Can Finish

A high-point Regatta task is useful only if you finish it. The best choice for a short evening session can be different from the best choice when you have plenty of time but few task opportunities left. Plan around your actual bottleneck: time, task allowance, available products or reliable match-3 wins.

Start with a small agreement your team can keep: how many tasks each player expects to finish, which resources they can help with, and when they will be online. Then choose tasks that fit that agreement. A smaller completed plan is worth more than a larger imaginary one.

Start from the current task rules

The Regatta board offers twelve tasks: six town tasks and six match-3 tasks. Reservations are unavailable, and match-3 progress counts only after a successful level. Seasonal tasks sit among the town tasks; older relay, Mystery, Combo and Hot-task advice does not describe the current board.

This changes preparation. You can prepare resources for a likely task, but you cannot treat an unclaimed task as secured. Avoid tying up your whole production plan for something another teammate may take. Prepare goods that remain useful elsewhere, and coordinate in chat before committing scarce resources to one specific task.

Playrix now calls co-ops Teams. Its updated rules list task allowances of 9 in Wooden, 11 in Copper, 13 in Steel, 15 in Silver and 17 in Gold, with no cooldown after taking tasks. Do not build a plan around an old league allowance or assume an extra purchase is included in those figures.

Decide what you are trying to maximize

There are two different questions: “How many points can I finish before I log off?” and “How many points can I get from my remaining task opportunities?” They are not interchangeable.

Consider a hypothetical board: Task A is worth 120 points and should take you 12 minutes; Task B is worth 150 points and should take 30 minutes. These are example values, not fixed Township task rewards or timers.

With 36 minutes available and at least three task opportunities, three comparable A tasks would yield 360 points, while one B yields 150. That comparison assumes suitable follow-up tasks actually appear and your estimates hold. It does not promise that the board will supply three identical tasks.

With only one task opportunity remaining and enough time for either, B instead offers 30 more points. A points-per-minute ranking would hide that distinction. Use speed to solve a time shortage, not as a universal reason to prefer the smallest task.

Before accepting anything, add a practical margin. If a task looks like 25 minutes of work and you must leave in 25 minutes, it is not a comfortable fit. A failed level, missing ingredient or delayed helper can consume the entire margin.

Estimate completion time from the bottleneck

For a town task, identify the step that actually determines your finish: production, crop growth, transport, available materials or your next login. Do not add every timer blindly if some work can run in parallel, and do not ignore a missing prerequisite just because the final product is quick.

Suppose your plan needs two preparation steps that can run simultaneously: one takes 20 minutes and the other 35. A final action takes another 10 minutes after both finish. The earliest planned completion is 45 minutes, not 65 and not 35. This is a scheduling example, not a claim about a particular task's production chain.

If the second step cannot begin until the first finishes, the same numbers become 65 minutes. The practical question is whether your own queues and ingredients let the steps overlap. That is more useful than copying someone else's claimed completion time.

For match-3 tasks, estimate from successful levels rather than attempts. If recent wins have been slow or inconsistent, do not use your fastest lucky level as the expected pace. You do not need a precise win-rate spreadsheet: a conservative estimate based on what you can currently finish is enough to reject an unrealistic commitment.

Booster tasks: count creation, not the fireworks

For booster-creation tasks, Playrix distinguishes making a booster from activating one. Eligible sources include manual creation, creation through falling pieces after a match, and boosters created from remaining moves at the end. Starting boosters, Chef's Gift bonuses, gifts and generators do not count toward this creation requirement.

Here is a hypothetical tally for a task asking you to create the relevant booster type. Assume you successfully finish the level and each eligible item is of the type the task requests.

Twelve boosters appeared, but only nine fit the creation rule. Activating those nine does not turn them into eighteen creations. If the level is unsuccessful, the successful-level requirement still applies; a spectacular attempt is not a banked result.

This is why spending a starting booster is not the same as buying task progress. It may help you win the level, which can be useful, but its presence alone does not satisfy a creation objective. Evaluate that purchase as help toward a win, not as an automatic addition to the task counter.

Coordinate without pretending chat is a reservation

Use chat for short, actionable messages: “I can finish one town task before 20:30,” “I have these products available,” or “I am preparing for this task; is anyone already working toward it?” A teammate's reply is a social agreement, not a reservation enforced by the game.

A good team message includes a finish window and a fallback. For example: “I can supply the requested goods in about 20 minutes. If you need them sooner, choose another task.” This prevents a hopeful promise from becoming someone else's failed deadline.

Product requests are limited to teammates, cannot be changed after sending, and have a four-hour cooldown. The request quantity depends on the product, and lower-level teammates may not be able to supply it. Put the exact missing ingredient into the request, not something vaguely useful that blocks your next request.

Treat an offer of help as confirmed only when the donor has agreed and can meet the timing. If the task works only with an immediate donation that nobody has promised, it is not yet a reliable choice. Choose a different task or delay accepting it while you arrange the supply.

Build a team target from actual commitments

Make a simple plan before chasing an ambitious total. In this hypothetical example, four players estimate what they can finish during the same planning window. The averages are planning assumptions, not game rules.

If the team wants 1,000 additional points during that window, the plan is short by 230. Name that shortfall early. Two additional 120-point tasks would cover it by ten points, but only if someone has the allowance, time and feasible tasks to complete them. “Everyone will do a bit more” is not a replacement for those conditions.

Do not count Dani as a contributor just because they belong to the team. They may still help with products, but that is different from committing completed tasks. Separating task work from supply help makes the plan fairer and more accurate.

Review the plan when circumstances change. If Alex cannot finish the third task, subtract its expected contribution immediately rather than leaving the original total in chat. The point of the estimate is to expose a gap while there is still time to respond, not to create a permanent quota.

Participation changes rewards and matchmaking

Joining late can cost rewards: earlier collected chests are not retroactively awarded to a newcomer. Playrix also says at least one completed task is needed for Regatta rewards. If rewards matter to you, plan a feasible contribution rather than waiting until the team has finished everything.

Opponent matching uses approximately similar numbers of active participants. For an established team, Playrix bases that count on the previous Regatta; completing at least one task defines activity. New teams use participation at the start of their first race. This is not a promise of identical opponents or a guaranteed winning bracket.

Use that information to set expectations, not to promise a matchmaking trick. A team with many members but only a few reliable contributors should plan from those contributors. Recruiting more members helps only when their actual availability and goals fit the team's approach.

Keep points, tokens and spending separate

Points determine race progress; tokens buy store items. Tokens carry across seasons, but their holding limit is 2,000. The store can restock exhausted offers at double the price, while some offers are one-time purchases. A repeated offer is therefore not automatically the same deal.

Set a spending boundary before the final push. Decide which development item you actually want and how much premium currency, if any, you are comfortable using to support tasks. Do not convert a small ranking gap into an open-ended spending commitment. Extra points do not guarantee that a rival will stop scoring.

A practical routine for your next session

1. Decide how long you can play and how many tasks you can reasonably finish.
2. Compare available tasks against that time and your remaining allowance.
3. For town tasks, identify the missing resource and the longest dependent step.
4. For match-3 tasks, confirm what counts and allow for unsuccessful attempts.
5. Tell teammates what help you need and when you can finish; do not assume a chat message reserves the task.
6. Accept a feasible task, complete it, then revise the team plan using actual points earned.
7. Before spending tokens or premium currency, compare the reward with the budget you set beforehand.

The aim is not to find one task type everyone must always choose. It is to turn the board in front of you into completed contributions without committing time or resources your team does not have.