Melvor Idle 2 Offline Progress & Crafting Stops

Three checks for a short offline session

Read the return summary

The community's October demo walkthrough shows Welcome Back cards for skills that progressed, with levels, XP and items. It also shows inactive time when ingredients run out. Time away therefore does not necessarily equal productive time.

Use that distinction when comparing an overnight result with a short active session. Record the action, starting stock and elapsed time, then change one variable at a time. That makes a useful bug report much easier to distinguish from an exhausted batch.

Crafts and products are not the same target

In the documented demo interface, select a recipe, review Manage Stop Conditions, then press Create. Recipe Creations counts completed crafts; Products Gained counts new output; Products Owned targets the amount in your bank. Ingredients Spent and Ingredients Remaining instead control input use.

For example, if a recipe in your current build displays several output items per craft, a target of 100 crafts is not a target of 100 items. Read the displayed output quantity before setting the target. This example explains the distinction without assuming a fixed recipe yield.

Changing a running batch

The demo guide reports that changing a condition while the same batch is running does not retroactively apply it: stop the batch and start it again with the new condition. Recheck the current build's controls after an update.

Before a long absence, try a small batch with a clear target. Check that it starts, consumes the intended material and stops where expected. This is a recommended verification routine, not a guaranteed optimal training route.