Lords Mobile Guild Helps: why 30 does not mean 30%

A long research project makes it easy to misjudge your speed-up stock: mentally subtract 30% for Guild Helps and assume you have enough. The original article checked that arithmetic in IGG's official Project Calculator. For a test project of 100 days with no speed boost, 30 Helps left 73 days, 23 hours and 17 minutes. That is almost 74 days, not 70.

Guild Helps do accelerate construction and research, as IGG's Game Guide confirms. All figures below, however, came from the web calculator on September 27, 2026. This explains a planning method, not a new patch or a measurement in the game client.

Three fields you must keep separate

Original Time Required is the project's starting duration in days, hours and minutes. Build/Research Boost is the construction or research speed bonus as a percentage. Guild Helps is the Help count assumed in the calculation. After Calculate, the tool separately shows time before and after Helps.

A common mistake is entering an already reduced timer as the original duration, then applying the same boost again. The source test kept 100 days, entered a 100% boost and zero Helps, and received 50 days in both result rows. The boost field already participates in the calculation. Entering the adjusted 50 days and another 100% instead describes a different project.

Before entering a duration, identify what you took from the game: base time, the pre-launch time including boosts, or the remaining time of an active project. Do not substitute one for another. For your account, compare the calculation with its timer, active bonuses and available Helps.

Why 30 Helps did not remove 30%

Use matching starting conditions: 100 days, zero hours, zero minutes and a 0% boost. With one Help, the tool showed 99 days. With two, it showed 98 days and 14 minutes. If each Help removed exactly one day from the original hundred, the second result would be exactly 98 days. Simple addition already differs from the calculator at this step.

With 30 Helps, the result was 73 days, 23 hours and 17 minutes. The displayed hundred days lost 26 days and 43 minutes, approximately 26% of the time. Assuming only 70 days remain understates speed-up requirements by almost four days in this example. The hundred days is a convenient test input, not the duration of a particular research project.

This demonstrates the tool, not a promise that every account can receive 30 Helps. It does not establish your Castle's limit, the minimum reduction on short timers or every mode's rules. The screenshot preserves the entered fields and result together without redrawing numbers. Open the original screen at full size.

Turn the calculation into a spending plan

Estimate the project without Helps, then with the count you realistically expect. The second figure supports planning; the first shows your dependence on guild activity. Do not count expected Helps as time already saved.

When finishing with speed-ups, compare their stock with the actual remaining timer after received Helps. If you can wait for guildmates, wait and recalculate. If a deadline is close, rely on what is already on screen. For example, eight hours remaining and six hours of suitable speed-ups leave a two-hour shortfall. Your plan should identify whether ordinary waiting, extra stock or Helps still expected will cover it.

For an event task, separately check which action counts, when it must count and the deadline. A duration calculator does not know those conditions. Our Lords Mobile calendar guide explains why registration, event start and preparation time should be recorded separately.

Before spending, answer three questions: did you avoid applying the same boost twice, are Helps received or only expected, and do suitable speed-ups cover the deadline? Resolve any unknown first. A useful-looking calculator result is only as reliable as its starting inputs.