Quick answer

Moonlighter 2 does not require you to begin with a copied relic-price table. Put one relic on sale, read the customer response shown by the current shop interface, adjust one price variable, and record the result for that item and run. The official Version 1.0 store description supports setting prices, reading customers, finding the right deal, and reinvesting shop profits; it does not provide a complete public price table.

Start with a test you can repeat. If the response signals that the price is too low, move upward. If it signals that the price is too high, move downward. When the response is useful for the current shop session, keep the price and compare the next sale rather than changing several items at once.

Use the shop response as your guide

  1. Choose one relic. Keep the item, quantity and shop context visible while you test it.
  2. Set a deliberate starting price. The goal of the first sale is to learn the response, not to prove a permanent number.
  3. Read the customer reaction. Use the wording and visual state in the current client as the source of truth for whether the price is moving in the right direction.
  4. Change one variable. Raise or lower the next attempt, then compare the response with the previous attempt.
  5. Record the useful result. Keep the item name, date, build and observed reaction together if you want a reusable note.

This is faster and safer than guessing from a price list made for another build. It also preserves the distinction between a price that worked in one shop session and a value that has been tested broadly.

Narrow an unknown relic price

When the first price is unknown, use a narrowing loop:

  • make a clear first estimate rather than changing the price randomly;
  • use the next customer response to decide whether the next test moves up or down;
  • keep the step size large while the response is clearly wrong;
  • reduce the step size when the response is close to the result you want; and
  • stop once the current shop goal is met, then keep the observation tied to the item and version.

The exact response labels can change with the live client or translation. Do not turn a single reaction into a fixed “perfect” value for every relic without current, repeatable evidence.

Connect price to the full merchant loop

Pricing is only one part of the result. The current official description connects relic collection, backpack management, selling, shop customisation, sales perks, special events and reinvestment. If a sale is disappointing, check which step is actually limiting you:

| Symptom | Next question | Useful route | | --- | --- | --- | | The price response is clearly wrong | Did the last test move in the expected direction? | Keep testing one relic at a time. | | The shop cannot display what you want | Is backpack space or item selection the blocker? | Read Backpack and Relic Effects. | | Sales are fine but the next run is slow | Which upgrade addresses the observed bottleneck? | Read What to Upgrade First. | | Everything feels unclear | Are you still learning the first loop? | Start with Beginner: First Hours. |

Common pricing mistakes

Copying a complete table without a build boundary

Older guides and creator videos can show where the question comes from, but they may use an earlier build or a different item state. Use the current customer response before relying on a number.

Changing price, display and stock together

If several shop inputs change at once, you cannot tell which one affected the result. Test the price first, then investigate display or shop systems separately.

Treating one good sale as a universal answer

Keep the item, version and shop context with the observation. A useful price note is stronger when it can be repeated and weaker when it is detached from the conditions that produced it.

Frequently asked questions

Is there one perfect price for every Moonlighter 2 relic? The current official sources support the price-and-reaction system, not a complete universal table. Use the live customer response and keep any tested value tied to its item and build.

How do I know whether to raise or lower a price? Read the current customer reaction. A response that indicates the item is too cheap points upward; a response that indicates it is too expensive points downward.

Should I price every relic before opening the shop? No. Test the item that matters for the current sale, record the result and return to the dungeon or upgrade decision that follows.

Sources

Last verified: September 6, 2026. Exact item prices and customer thresholds require a current-client observation for the specific relic and shop state.