How the people who deliberately hijacked this thread describe the code flys in the face of the reality of the code I am actually seeing. Still we can't let that get in the way of preventing anyone else giving feedback on the beta now can we?
I set up the separate thread in bug reports to in an effort to avoid this thread being spammed with regards to the pricing model feedback, as it amounts to only one aspect of the beta patch. While I feel it's a major concern, and clearly many others do too, I had no intention of hijacking a thread intended for general discussion and feedback - so I hived it off from the main discussion and bug reported it for consideration elsewhere. The number of improvemets to the economy (and the rest of the game) generally in 1.3 is staggering, but that doesn't preclude it from potential bugs.
I'm glad to hear that this issue was anticipated, but not adjusted enough; surely the entire point of beta releases is so that we can provide the feedback that shows it needs to be slightly stronger? I can provide screenshots of goods hovering at base price with huge demand and low supply, which I felt was worthy of consideration, could not be WaD and indicated something needing adjustment. I encouraged others to avoid spamming this thread with it by directing them to the bug report thread if they wished to comment on it, and that appears to have worked - the number of comments in here regarding it drops sharply after that point in the thread. So it doesn't seem entirely fair to accuse us of threadjecking when I took steps to avoid it, or of preventing others from giving feedback.
I made no claims to be 'so important'; I actively attempted to prevent it spamming the thread and preventing others from having their opinions heard by setting up the bug thread. I just flagged up game activity that appears not to be working as intended, and posted a bug report about it when comments about it began to overload in this thread. I apologise if that made you angry, as my only intention was to help find issues - and since you have made an adjustment based on this, I think we did find just such an issue, which is hopefully fixed by that adjustment.