Player observations · saved in this browser
Fell & Sell Price Test Log
Log your Fell & Sell sold and refused prices by item, build and shop context. Keep observations in your browser and compare clearly labeled test bands.
Reviewed 2026-09-19 · Ver. 1.4.3 named baseline · September 18 public update
Loading this browser’s saved log…
Observed prices by matching context
No observations yet. Add your first actual sale or refusal; no item values are preloaded.
How to keep a useful Fell & Sell price log
Record a completed sale or an observed refusal with the exact item variant, game build and shop conditions. The log reports the highest successful price and lowest refused price only within matching context. It starts empty so that every recorded value belongs to your own playthrough.
When to use it
- Test small price changes while keeping prestige, comfort, bonuses and demand steady.
- Separate a new patch or changed shop from older observations.
- Notice contradictory reactions before treating one refusal as a pricing limit.
Current-build context
The September 4 Shop Update changed pricing logic and base market values. Ver. 1.4.3 improved the pricing interface and fixed furniture price stacking. The public September 18 Dungeon Update also adjusted furniture bonuses and loot balance. Retest after a build or bonus change and return to the shop for the announced furniture balance changes to take effect.
Named patch baseline: Ver. 1.4.3. Newer public bulletin: Dungeon Update, September 18, 2026. Official-source review: September 19, 2026. Check the dated update history.
Worked example — hypothetical numbers
Hypothetical example: in one unchanged test context, an item sells at 100 and 110 gold, then is refused at 120 gold. The summary shows 110 gold as highest observed sold, 120 gold as lowest observed refused, and 3 observations. A sale at 150 in another build belongs to a different group. A later sale at 125 in the original group creates an overlapping band, not a newly proven maximum.
How to interpret the result
A refusal can have causes beyond price. The Shop Update distinguished a full checkout queue from an expensive-item complaint. Record the reaction in notes and keep path, queue and demand changes in separate comparison contexts. Unknown context is flagged; a larger sample still does not prove a universal price formula.
Frequently asked questions
Does this find the official maximum item price?
No. It summarizes observed outcomes. The band connects one successful observation to one refused observation; it is neither a hidden-price formula nor a guarantee about untested prices.
Which fields keep tests separate?
Item and variant, patch/build, prestige, comfort, bonus, demand and other comparison context must all match. Notes and outcome do not split groups. Keep labels consistent; capitalization and punctuation remain distinct.
Where is my log saved?
In this browser’s local storage for this site. It is not an account backup, game save or shared item database. Browser cleanup removes it, and another browser or device will have a separate log. Storage failures and invalid saved data are shown explicitly.
Related guides and next steps
Evidence and model limits
Official announcements support the game changes described here. Input values, forecasts and decision scores are supplied by you or explicitly identified as editorial examples. Hidden price coefficients, drop rates and salvage percentages are not assumed.