First of all I want to say this isn't some sort of glitch, but it is a bug. The program definitely should not be working as it is.

So after a while of playing transformice, I had gathered 200 shamcoins and 50 yellow tickets. It struck me as odd as I had that exact amount (assuming it's the max size). I went to the village and decided I wanted cheese. Lots of it, I want some furs so I need it. I go to one of the traders and turn in my 200 sham coins into cheese. Feeling good with my stack I go to the other trader and then turn in my 50 yellow tickets for 100 cheese. Or at least what SHOULD have been 100 cheese.

I am aware of it now since I got gipped of my cheese, but 200 cheese seems to be the maximum cheese stack size. I don't have a problem with the size. The problem is that I wasn't informed prior nor during the transactions with the npc. I clicked on the npc, then clicked on my reward, and the little animation claiming I got 20 cheese popped up. it did indeed consume my tickets, but it did not give me any more to my cheese stack. I did not notice my stack not increasing as I saw the animation and just clicked it another 4 times. After that I looked at my cheese stack and realize it.

Here is the point. Why isn't there anything implemented that prevents you from completing a purchase if the purchase would make you exceed the maximum size of a certain stack? Why aren't the npcs implemented to stop you and inform you about it?

THEY TOOK MY CHEZ.

you should probably post this in suggestions, seen as it's not a bug. But i've heard of people feeling "ripped off" after buying stuff when they were at max so i bet you'd get lots of /support

the term bug is more of an umbrella term, it's not specific to glitches.

If the developers intended for mice to purposely rip you off with no warning, then it's not a bug since it's working as they intended it to. It being a bug pertains to how it's coded, like maybe there is some methods that aren't reached, there would be no error shown but the program would not run to how it was meant to run, and that is a bug.

i mean it's not a bug in the sense that the code is working the way it was designed and nothing is "broken" about this. The OP just desires something that's not implemented yet, hence me pointing them to suggestions.

as far as i've seen from the "closed, not a bug" posts from mods on here, bug is indeed a specific term when used in the bug forums.

Xsaintx a dit :

the term bug is more of an umbrella term, it's not specific to glitches.

If the developers intended for mice to purposely rip you off with no warning, then it's not a bug since it's working as they intended it to. It being a bug pertains to how it's coded, like maybe there is some methods that aren't reached, there would be no error shown but the program would not run to how it was meant to run, and that is a bug.

Seems more like a lack of a warning then a bugg (like Squirrelmows) since the game aknowledges the stack being on max,however gives no warning because nothing like that is implemented(?)