I respect your opinion, it's a very reasonable and rational one. I would like to respectfully disagree.
Every single game, especially within the 3DS family, has at least a handful of bugs and issues, on every single update version. There is clearly something wrong with the game's code and most likely the people's 3DS. Since some people have the crashing really bad, and some people seem to never have it, it would be reasonable to assume that this issue is a combination of the two factors stated above.
This variability is precisely the reason of why it is so hard to replicate and troubleshoot the crashing issue, and said crashing issue is definitely a combination of a few major bugs and issues. This makes it even harder for the devs to pinpoint an issue.
So while they (the devs) are working to fix this major issue, us, the clients, must come up with some things to take note of that may at the very least postpone a potential system crash. This isn't magical thinking, this is the core idea of troubleshooting. It is what people have to do when there's an issue with any video game that they want to actively play.
For this I thank you, I believe mutual respect is the keystone of any form of constructive dialogue.
That being said, I must respectfully both agree *and* disagree with your opinion. I will, of course, elaborate.
I'm most likely not alone in this, but I'm a gamer from among the first hours of gaming. I'm talking Amiga 500, DOS, NES, and the original Game Boy. I agree with you that most, if not every, game has bugs. What makes Terraria different, in my opinion, is the following:
It's obviously reasonable to classify bugs in *any* game by severity and frequency. Some bugs are not noticable at all for end users, and mainly affect technical stuff like memory allocation or sprites. Some bugs are noticable, but are not to be considered gamebreaking. Then, there are the malevolent bugs that you don't want to run in to. They can corrupt savegames, freeze the game, or otherwise make your gaming experience miserable.
Anyone who played Pokémon Red/Blue on the original Game Boy will remember the glitch called Missingno. It was a graphical- and memory glitch that caused a weird, nonexistent Pokémon to appear. Not only was it not gamebreaking, it was even actively exploited to duplicate items, and catch the illusive mew. Even more, it wasn't a glitch you would "randomly run in to", no, you had to follow a *very* specific set of instructions to even be able to encounter it.
Same goes for, say, Etrian Odyssey Untold : The Milennium Girl for 3DS. There is a small glitch that allows you to create so-called grimoire stones with a higher amount of skillpoints than should actually be possible. Purely an exploit, it was never fixed, but definitely not gamebreaking, and definitely easy to avoid.
I've also played almost all Harvest Moon games, and their Rune Factory spinoffs. Rune Factory 4 had a notorious gamebreaking bug that would sometimes manifest itself during the ending credits after the final boss fight. It would cause the entire game to freeze up, and forced you to restart the game, and thus, restart the boss fight. For example, it took me three times to finally "beat the game". Still, it only occurred during that specific cutscene, and all the gameplay outside of that boss fight, or *after* it, after you've cleared the game, was clean of any annoying bugs. The boss fight being rather easy, this bug could be considered an inconvenience at most, and a minor one at that.
One of my favourite adventure franchises has to be the Zero Escape series. The second installment had a potentially gamebreaking bug, which would corrupt your savegame if you saved in a specific room. I never encountered the bug, but there were a lot of people who did, and they would have to replay the entire game up until that point, to be able to clear the game. All the while avoiding said room. The developers made an official statement regarding to said bug, so after a while, most people were aware of it, and it became trivial to avoid the notorious "Decompression Room Bug". Still, the bug was, as far as I know, never fixed, and if someone was not aware of it's existence, would definitely be able to make someone's experience miserable.
Now, we'll get to Terraria. This game has some bugs, some of them minor (hammering bricks to make slopes indeed doesn't seem to last after saving, quitting, and reloading), but some of them quite serious. At this moment, I can play about 45 minutes on average before receiving an error message and being force-quit into the home screen. Now, this is annoying, but would be tolerable if this bug was rare, or hard to run in to. If I had to fulfill a very specific set of prerequisites for the bug to rear it's ugly head, I would be able to avoid it, easily. The opposite, unfortunately, seems to be the case. The first time I encountered the bug, was when I just started the game for the very first time, and was in less than 10 minutes upon starting a new character and creating a new world. I was just walking around the map, basic equipment, nothing special whatsoever going on.
As I've stated before, I am, besides a 3DS gamer, also a PC gamer, and this is where my love for Terraria originated. Therefor, I know that these bugs *WILL* be fixed in due time, and I'm no stranger to "work in progress". Also therefor, for me, personally, I find the bug annoying, but I will either play Terraria every once and again on the 3DS, or play something else for a while when I get fed up.
For the general public, however, (
EDIT: people that bought a game to play and enjoy it, rather than "troubleshoot" their purchase) I can *very* well imagine €20 for a game that has a bug of this severity and this frequency feels unacceptable, and the argument "every game has bugs" won't do.
Just my two cents though, here's hoping it will be in the past after coming update(s)