You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Labyrinth location has various sublocations that you can collect clues in. Given that the amount of clues dropped is tied to the specific mouse, one can calculate the expected number of clues dropped per hunt.
Similarly, if the amount of crop coins dropped were tied to the specific mouse, one could calculate the expected number of clues dropped per hunt. There is some consideration for the "Hired Hands" area upgrade, which doubles the number of crop coins (amongst other things), that could be implemented similarly to how the check for lantern oil is implemented.
The Labyrinth location has various sublocations that you can collect clues in. Given that the amount of clues dropped is tied to the specific mouse, one can calculate the expected number of clues dropped per hunt.
Similarly, if the amount of crop coins dropped were tied to the specific mouse, one could calculate the expected number of clues dropped per hunt. There is some consideration for the "Hired Hands" area upgrade, which doubles the number of crop coins (amongst other things), that could be implemented similarly to how the check for lantern oil is implemented.
From https://public.tableau.com/app/profile/alex.claxton/viz/MH-by-mouse-ID2/MouseDroppingsandItemDroppers, it is reasonable to assume that the amount of coins dropped is fixed and dependent on area upgrades.

Similar mechanics could be applied to the Table of Contents area, but crop coins are rarely the metric optimized for in the area.
The text was updated successfully, but these errors were encountered: