Progreso y recompensas de misiones de Scrap Mechanic 1.0

The accepted 1.0 quest catalog contains 46 quests implemented through 25 script classes. The audited scripts expose 163 tracker messages, 66 progress steps, 60 fixed public reward records, and 18 explicit successor links. Those counts show why a single linear checklist cannot describe every active objective.

Main progression, side work, repeatable or order-dependent jobs, and tracker-only states have different rules. A useful index labels the quest kind and preserves the distinction between a formal successor link and a progress message that merely describes the next action.

A quest page should separate the high-level objective from its underlying progress conditions. Tracker messages may react to location, inventory, interaction, construction, delivery, combat, or a scripted world state. Reading only the quest title often hides the specific event that advances it.

When progress appears stuck, reproduce the expected action in the intended context. Confirm the correct save version, active quest, item identity, quantity, target facility, and interaction order. Then leave and re-enter the relevant area if the script depends on a trigger volume or refreshed state.

Sixty rewards are exposed as fixed public records, which can be attached to their quests with confidence. The six Scrapper builder jobs are different: their rewards depend on completion order rather than belonging permanently to one named job. Assigning one fixed item to each of those six quest titles would create a false guide.

For order-based jobs, report the reward sequence and the player's completion position. This lets a player predict the next payout without pretending the job identity controls it. The same evidence standard should be used for any future rotating or conditional reward.

First verify that the tracker is showing the quest and step you think it is. Next check whether the condition wants an item held, delivered, placed, built, or consumed; these events are not equivalent. Confirm the current quantity and the exact target rather than relying on a similar icon.

If the objective involves a world location or NPC, approach through the normal progression route and complete any explicit predecessor. For an old save, verify branch compatibility before deeper troubleshooting. Back up the save before experimenting with mods or manual file changes.

• Confirm game version and active quest.
• Read the current tracker step, not only the quest title.
• Verify exact item UUID, quantity, target, and action type.
• Check explicit predecessor or successor relationships.
• Retest without assumptions introduced by an old guide or mod.

Start with the quest list and filter by kind. Open only the current objective, then read its requirements and fixed reward if you need help. Follow related links only when a predecessor or successor relationship is explicitly documented.

This layered approach provides enough information to solve a blocker while keeping later story details out of view. It also makes the page useful for completionists, who can audit missing side quests and reward states without forcing every visitor through a full walkthrough.