Yes. 100% free.PedroSteckecilo said:um... Aren't Minecraft updates free?
I'm just trying to figure out what episode that comes from, help me out?Neverhoodian said:I'd rather have a delayed update that's stable rather than a rushed one with bugs and glitches up the wazoo. Just be patient. Remember the old adage, "good things come to those who wait."
Again, if they were game breaking, and the devs knew, then this delay is fine, but if ITS NOT known, thats the point of beta, the devs should be focusing on making the game better, and allowing the testers actually weed out bugs for them, instead of them trying to make each patch flawless.TestECull said:So I suppose releasing a patch so badly broken we can't play at all is helping us find things?Aprilgold said:And I'll point this out while I can, Minecraft is in beta, people who bought the game are, essentially, beta testing it. Therefore, all their doing is witholding tests for players to tell them the bugs, I don't know, the few MILLION [I think] testers out there.TestECull said:ITT: Nerd rage.
Seriously, good on Mojang to delay it. Means there's less chance of bugs in it.
The players are finding the small, rare bugs. The big game breakers should be found and remedied before a patch goes out at all.
Any triple A developer gets no god damn slack from me if they pull this shit. But mojang is indie, therefore, we can at least TRY to help.TestECull said:Aprilgold said:Again, if they were game breaking, and the devs knew, then this delay is fine, but if ITS NOT known, thats the point of beta, the devs should be focusing on making the game better, and allowing the testers actually weed out bugs for them, instead of them trying to make each patch flawless.TestECull said:So I suppose releasing a patch so badly broken we can't play at all is helping us find things?Aprilgold said:And I'll point this out while I can, Minecraft is in beta, people who bought the game are, essentially, beta testing it. Therefore, all their doing is witholding tests for players to tell them the bugs, I don't know, the few MILLION [I think] testers out there.TestECull said:ITT: Nerd rage.
Seriously, good on Mojang to delay it. Means there's less chance of bugs in it.
The players are finding the small, rare bugs. The big game breakers should be found and remedied before a patch goes out at all.
...So you're perfectly fine with, say, for example, Obsidian doing that?
Frankly, I'm fucking tired of it. Every dev in the market it seems, Valve excluded, seems to treat their customers as free beta testing. I'd love to see Mojang set an example, fixing the vast majority of the bugs before they release the update at all instead of letting us facepalm at the ruined savegames...again.
Mojang is hardly indie when it comes to funding, and frankly, if they incrementally released this new patch instead of keeping it some big secret, it could be debugged sooner. Also, what he means is, when I load up a new save file with a new patch, and withing 10 SECONDS I encounter a bug, that is unacceptable. Obscure crashes I can understand, but when (for example) the halloween update came out, and I went through my portal and back, and ended up 100 blocks away from it (which was reproduceable in 1.2.0 btw), that should have been fixed prior to release. When you break the graphics of a block (redstone) in a very obvious way, that should be fixed before release. When pistons break saves under certain conditions that are not exactly hard to reproduce by accident, that should be fixed before release. My point is, they barely even play their patches half the time, and seem to have no consideration for their paying customers. The least they could do is spend an hour playing their own damn game in the office before ok-ing the release.Aprilgold said:Any triple A developer gets no god damn slack from me if they pull this shit. But mojang is indie, therefore, we can at least TRY to help.TestECull said:Aprilgold said:Again, if they were game breaking, and the devs knew, then this delay is fine, but if ITS NOT known, thats the point of beta, the devs should be focusing on making the game better, and allowing the testers actually weed out bugs for them, instead of them trying to make each patch flawless.TestECull said:So I suppose releasing a patch so badly broken we can't play at all is helping us find things?Aprilgold said:And I'll point this out while I can, Minecraft is in beta, people who bought the game are, essentially, beta testing it. Therefore, all their doing is witholding tests for players to tell them the bugs, I don't know, the few MILLION [I think] testers out there.TestECull said:ITT: Nerd rage.
Seriously, good on Mojang to delay it. Means there's less chance of bugs in it.
The players are finding the small, rare bugs. The big game breakers should be found and remedied before a patch goes out at all.
...So you're perfectly fine with, say, for example, Obsidian doing that?
Frankly, I'm fucking tired of it. Every dev in the market it seems, Valve excluded, seems to treat their customers as free beta testing. I'd love to see Mojang set an example, fixing the vast majority of the bugs before they release the update at all instead of letting us facepalm at the ruined savegames...again.
Simple math below.
Paying 60$ for beta testing is a NO NO!
Paying 15$ at quarter of retail price is ALRIGHT, and the game hasn't been release.
If its game breaking, then the devs should catch it, very fast. If they DON'T catch it, then the players [testers in Mojangs case] should report it. Again, you compared a INDIE developer to a triple A developer, both have a different amount to work with.