I explained why it was not correct. I don’t even know what an “implementation” issue is or what you even mean by it. You seem to think that the market should be able to determine what OP meant to do when he changed his buy order, and that because it took what he said that it is somehow implemented wrong. I explained that the market doesn’t know what he’s intending, only what he did. Same as any other situation where a player inputs a number into the game, whether it’s through a buy order, contracts or sell orders.
So what does the game do when the number inputted is way out of wack? It provides a pop-up warning - “this is 23094820938420398423% above the local price, are you sure you want to do this?” or “you’re about to buy a contract for 23423094820938423 bil is, are you sure you want to do this?”
In this situation, because OP was changing an existing buy order, the system didn’t give him a pop up that asked if he really wanted to do it, or if he had fat fingered it. He recognized this because he specifically said “What makes no sense here is that the game actually lets me do this. Didn’t get a warning either.”
He suggests that he should have paid the “best sell offer” but that’s not what he told the system to do, and as I noted, it’s a bad idea if the market starts assuming when you input a number that you really meant to do something completely different. Thus, if you want to fix this, the only way that makes any actual sense is to make a pop-up warning when the number is out of wack, like we see with every other market input where fat fingering a number is possible.
Had that been implemented, he would have got a warning, realized he ■■■■■■ up and not did it. That solves the problem. That is why I am bringing up the pop-up, especially since this is literally how the market works in every other way in the game.
You seem to be suggesting (like OP did) that he should never be allowed to pay more for an item than the lowest price, and I think that’s a bad idea and going way too far. The game should do what you tell it to do, not assume it knows more than you do about what you’re trying to do.
Regardless, as I’ve already noted, I think this whole issue is a waste of time to be talking about because this is such a miniscule issue, and to fix it would require far more dev time than it’s worth and thus is a bad use of resources. And I certainly think it’s the dumbest issue I’ve ever seen someone get so salty and ragey about, dude.