What stronger should mean for your route
For a delivery game, stronger is useful when it lets you carry more blocks or complete a load with less repeated work. The important output is not a large-looking stat; it is fewer trips for the same pyramid target, or a higher blocks-per-minute rate after the extra handling is included. Use the capacity value shown by your current interface rather than assuming a community-defined Strength formula.
Start with a target you can finish in one short session. A target that is too large makes the comparison noisy because the server may change while you are working. A target that is too small can hide the difference between a full and partial load. Ten full loads plus a final partial load is usually enough to see a directional result.
Strength routine
Record current capacity
Write down blocks per load, pickup batch, and placement batch. If the UI uses another name, record the label exactly.
Choose a fixed block target
Use the same remaining-block amount before and after training so you compare the same job.
Train or use the available strength activity
Follow the current in-game interaction. This guide does not publish exploit or script shortcuts.
Retest the complete route
Include walking, pickup, and placement. Keep the change only if the rate or finish time improves for your goal.
When capacity is not the answer
A larger load is not automatically faster. If pickup and placement each process one block, doubling capacity can also double the interaction actions on a full load. In a short route, the saved return trip may be smaller than the added processing time. In a long route, removing a return is more likely to matter. That tradeoff is exactly what the calculator makes visible.
Strength is also less useful when your real problem is pathing or crowding. If you lose time finding the quarry, waiting for a placement spot, or returning around other players, first improve the route. Once the route is clean, retest the same strength scenario so the result reflects the stat rather than the noise.
Test a larger carry capacity
Enter the capacity you can reach after training and compare full-route completion time.
Pickup & placement timing
Defaults: one block per action, 0.25 seconds each. Open this section to use your measured values.
Compare an upgrade
- Travel
- 15s
- Pickup
- 2.5s
- Placement
- 2.5s
Round-trip travel = 2 × one-way distance ÷ walk speed. Processing time = ceil(load ÷ pickup batch) × pickup time + ceil(load ÷ place batch) × place time. The estimate includes a return after every load, including the final partial load. It assumes a clear route, no boosts, no lag, and no server-wide placement delay. Replace the example values with a timed in-game observation.
Strength FAQ
Can this page tell me the exact Strength formula?
Not reliably from the public evidence reviewed. Use the live displayed capacity and your own timed route; the formula is intentionally input-based rather than invented.
Should I stop training Speed while building Strength?
Not necessarily. Alternate short tests so you can see which change helps the target you care about. Avoid changing both at once if you want a clean comparison.
What should I record for a future update?
Record the date, server condition, displayed stat, capacity, batch sizes, target blocks, route time, and the exact game activity used.
