A detailed community guide currently lists ten Mine a Mountain Runes obtained from Boulders and placed in the Plot for temporary effects. The official Roblox description does not document the Rune system. Every exact effect below is therefore Community reported, checked August 14, 2026, and still needs current in-game testing.
Currently documented Rune Dex
The source also reports that higher-tier Boulders can drop lower-tier Runes. It gives no reliable current odds.
Obtain and activate a Rune
Search deep in the current hourly mountain for a named Boulder, confirm the live Pickaxe requirement, and leave Backpack space for the drop. After breaking it, identify the Rune from its current label. Return to the Plot and use the live placement prompt. Record the timer and visible effect before beginning the route.
Do not call a Rune obtained until it appears in inventory, and do not call it active until the Plot accepts it and the effect appears. The Boulders Guide lists reported pairings.
Choose by the session goal
Use Warmth when cold is the blocker, Weight when capacity is the blocker, and Haste when mining time is the blocker. Fortune belongs in a sale-focused test. Detonation or Excavator belongs in a Bomb test. Storm has weak value when Weather is not visibly active. Luck and Colossus need careful result tracking because rare or size chances cannot be proved from one run.
Record paid passes because x4 CARRY KG, Fast Dig, x8 Power, x2 Coins, and x2 Crystals may overlap the same goals.
Handle duplicates cautiously
The same community guide says duplicate Runes can be merged to increase size and duration, except Luck Runes, which are placed separately and stack. It reports four Luck Runes as +600% by adding four +150% effects. This exact duplicate behavior and arithmetic need live confirmation.
Before merging, record both original Runes, the menu preview, resulting item, timer, and whether the action is reversible. Do not consume a rare duplicate based on an undated screenshot.
Test duration and stacking
Start a Rune with a visible timer and note the time. Complete one controlled route. Compare the end state and whether leaving, selling, resetting, or rejoining changes the effect. Test only one additional Rune at a time. Preservation needs a direct timer comparison before its reported 50% claim is treated as current.
Common Rune mistakes
- Presenting community effect values as official.
- Assuming a Boulder guarantees its listed Rune.
- Activating Storm when Weather status is unknown.
- Comparing a Rune-boosted sale with an unboosted baseline.
- Merging duplicates without reading the live preview.
- Calling four Luck Runes multiplicative when the source’s example is additive.
Build a goal-based Rune loadout
Start from the session goal, then select the smallest reported effect that could remove its blocker. A summit attempt may value Warmth or Weight; a timed mining loop may value Haste; a Bomb test may value Detonation or Excavator; a sale session may value Fortune; and a visible Weather event may make Storm relevant. These pairings follow community descriptions, not a confirmed optimal build.
Activate only what the current Plot interface identifies, and capture the displayed timer before leaving. Record the Rune name, source Boulder, start and end time, route, active paid products, and result. When two Runes appear compatible, test the first alone before stacking the second. Otherwise a faster route, larger Backpack, changed mountain, or lucky crystal can be mistaken for a Rune interaction.
Preserve duplicates until the live merge or placement preview explains the cost and result. If inventory pressure forces a decision, keep one example of an untested Rune and use the lower-value duplicate for the experiment. Recheck all descriptions after a major update. A dated ten-entry community Dex is a useful checklist, but only the current item card can confirm that a Rune still exists, keeps the same wording, and behaves the same way.