Prices don't save

[Weather]

So sometimes when client buy items at the right price, the said price doesn't get saved in the book, is it a bug or am i missing something ?

[Xynen]

I was wondering this same thing. I just got to the Forest Temple and only about a fifth of the new items I've sold are actually having their price saved to the journal. I'm having to price all the forest items by memory which is a bit of a pain.

[DigiScot]

noticed this a few times also, definately a bug

[Handbanana]

Prices save when you sell the item not when a person grabs it off the table. Also if a theif picks it up it will reset. Haven't actually noticed this legitimiately happen outside of these scenarios.

[Xynen]

Prices are not saving when I sell the items, OP said the same as well. I've sold the same item multiple times and it's price is not saved in the book.

[Red Inferno]

I have had one item sell happily for 2k but it never updates from 1k.

[jep]

Plenty of reports in the Bug Reports forum about this same thing. It's happened to me, too. Like Xynen, I feel like it started happening for me with the Forest temple.

On patch 1.4.4.0.

[Sylverone]

I'm still having this price journal problem in version 1.8.19.1. To be fair, it's an old save, in case it's the sort of issue that only fixes under a new save.

I have heard that one additional reason for the price to not update is because the buyer is a special customer type like scholar etc. Since they will pay more for their specialty items they don't update the journal

[Sylverone]

Wait, maybe I misread, but are they saying here that having high popularity on an item can keep it from updating in the journal?

Originally posted by Azuron:

Bit late reply but here goes:
[[Snippety]]

140% will drop high popularity if thats blocking you from recording the prices.

Whatever the case it seems like it would be nice if this whole mechanic was reworked a bit. If the problem is that special cases are frequently interfering with price journaling, some sort of fix for that seems appropriate.

Suggestion: When an NPC with a price modifier (special NPC, item is un/popular now) buys an item at a modified price, reverse the price calculation and update the journal with the price relative to base under normal conditions. It might feel slightly weird but would be less jarring and frustrating than the current system not registering prices after much careful price adjustment. If it was consistent it would work.

Either that or add more fields to the journal to account for most of the special cases.

Or just let us enter values manually (possibly in secondary fields if that is preferred). I imagine some highly-organized people have resorted to using their own text/spreadsheet lists out of frustration.

[Decagon]

Originally posted by cliftut:

Wait, maybe I misread, but are they saying here that having high popularity on an item can keep it from updating in the journal?

Originally posted by Azuron:

Bit late reply but here goes:
[[Snippety]]

140% will drop high popularity if thats blocking you from recording the prices.

Whatever the case it seems like it would be nice if this whole mechanic was reworked a bit. If the problem is that special cases are frequently interfering with price journaling, some sort of fix for that seems appropriate.

Suggestion: When an NPC with a price modifier (special NPC, item is un/popular now) buys an item at a modified price, reverse the price calculation and update the journal with the price relative to base under normal conditions. It might feel slightly weird but would be less jarring and frustrating than the current system not registering prices after much careful price adjustment. If it was consistent it would work.

Either that or add more fields to the journal to account for most of the special cases.

Or just let us enter values manually (possibly in secondary fields if that is preferred). I imagine some highly-organized people have resorted to using their own text/spreadsheet lists out of frustration.

I think I’ve seen something in game that said it wouldn’t save if it was outside of the popularity norms in either direction.

[BossStompTV]

It's not a bug it just means they bought it for a price that wasn't normal. Uhh. For example this will happen if the item is in high demand. Becuase the book prices only reflect neutral demand. It will also happen if the customer is wealthy.

[BossStompTV]

Interesting. Does this happen when the customer is mad about the price but still buys maybe?

[25th Zam]

Originally posted by BossStompTV:

Interesting. Does this happen when the customer is mad about the price but still buys maybe?

I mean if by mad you mean 1 or more gold over optimal price but they still buy, then yes. So once they buy the item at over the ideal price, but are still willing to buy, that item then drops to LOW demand. If you've got another stack of that item on queue to sell then, sucks to suck

[Sylverone]

Well this explains a lot maybe, because I keep ALL of my items at high popularity continually. It just seems to make even less sense, then. You're telling me that a merchant running a business more competently has LESS sense of the real value of an item? That just doesn't fly. It doesn't make much sense to have to deliberately slow down your game just to update the prices properly, and it's made worse if it's true that it doesn't work for some people under ideal conditions. And how would I come up with deliberately upsetting my customers as the solution to my problem? I think enough people have been confused to indicate the mechanic is a bit awkward.

I stand by my suggestion. Either the journal updating could incorporate the special cases by reversing the multipliers and updating the journal as if the item had been sold at neutral popularity with the appropriately scaled price (i.e. reverse the modifiers then update journal), or manual journal keeping could be allowed, or at least communication to the player could be increased about what conditions they need to bring about to update the price correctly.

As it is, it feels hit and miss in an odd way that tends to feel inconsistent and therefore gives the impression of being a bug. When I sell an item for twice it's currently listed price and a customer accepts it happily, there is no way Will should not take that as an indication that his listed price needs raised. Maybe just nudge the price up toward the ideal by some percentage, to simulate Will's learning curve. There are a number of ways to remove the unresponsiveness of the current system.

Not that it's necessarily of highest importance; it just bugs me. I can deal with it if it isn't worth the dev's time to fix. Some issues are simply like that. I guess i'm just talking out what I'd consider more ideal, for what it's worth.