Can we get internal testing before you put things into the beta testers?

You somehow managed to harvest enough wood, cobblestone, and iron to make all the necessary preparations for making a sword in 5 minutes? I'd love to see that on youtube.

Wow, where to begin with that. Just wow.

 

Allow me to quote Tiy about stage 1 of the beta:

Stage 1 will be move at a breakneck speed. This will be the buggiest and busiest stage of the beta. A bunch of unfinished features will be disabled whilst we finish them up. Updates will come thick and fast, sometimes as often as multiple updates a day.

If you choose to take part during stage 1 you should expect bugs, lots of balance changes, you shouldn’t get too attached to your character or universe as we may make changes that require you to start from scratch. You should expect the game to be broken at points as we make sweeping changes but you’ll get to enjoy exciting new content added constantly. The engine won’t optimized during this stage of the beta so performance could be poor on some low end machines.

You’ll get to see a bunch of ‘behind the scenes’ content at this stage and provide feedback during this crucial period.

DO take part in this stage if:

- You enjoy testing buggy and unfinished code

- You enjoy providing feedback

- You want to leave your mark on the game

- You just can’t wait any longer

DO NOT take part in this stage if:

- Bugs infuriate you

- You don’t like spoilers

- You can’t stand losing your save

- You want the full Starbound ‘experience’ the first time you play.

 

Beta test... Alpha test... Semantics.
This game is completely open to the public now, and whatever it's in, they released a patch with a game-breaking flaw.
I mean if you're going to update the combat system, I don't think it's unreasonable to recheck the numbers on weapons before just blindly releasing it.

 

I think the main reason for this particular update was to change the basic damage system, not to have it balanced right out of the gate. From what I have read, it was not expected to be balanced a bit until a later patch. Groundwork, then tweaks. My understanding of it, anyway.

 

In addition to what has been re-iterated about the stages of beta (the current stage admittedly being more alpha like... but that's arguing semantics), there actually is a development and staging branch of Starbound in the Steam database:

http://steamdb.info/app/211820/#section_depots

 

"Beta" testing comes after "alpha" testing. All the OP is saying is that 10 minutes of alpha would have been very handy before a release in beta.

 

This ^^

 

That's not how those terms are applied - they refer to states of the game, rather than a sequence of tests.

OP shouldn't be involved in this stage of the beta if they don't like that the game gets broken now and again.

 

Why are we getting so many freaking trolls like the OP these days? Seriously...

 

Yes, but a lot of people are completely missing the OP's point / have no clue what they're talking about ( I'm not saying that goes for you too). It's also only partially relevant, since the OP is talking about how this particular 'gamebreaking' bug got through.
Let me start by saying I haven't played the game a single second yet, so I can't comment on whether or not it is actually gamebreaking or give any other opinion on the state of the game.

While beta testing, we are obviously coming across bugs. That is completely understandable AND acceptable. What the OP however means (and in my opinion is completely right about) is how this particular thing could slip through when 1) it appears to be apparent from the early stages of the game and 2) this patch was very much about the systemoverhaul that caused this bug. Hell, I wouldn't even want to call it a bug, if its as bad as the OP is saying, I'd call it a complete oversight.
It appears that some (external?) tester could easily have noticed this and they could've made sure it didn't come into the beta in this stage. You simply need internal testers for things like this. It makes sure the company doesn't compromise their good name, it avoids fans getting pissed and it saves time.

I can not comprehend only a handful of people in this thread seem to grasp that concept.

 

I am sure the devs did some testing beforehand. Nobody is 'right' or 'wrong' here. It's a rant, not a competition.

 

People need to chill.

Yamachin has a point, and like Yoonaii said, you shouldn't post just to bash people, this is unconstructive.
This patch shouldn't have been released if they were discrepencies with weapon. I came here to speak about said swords myself, do not get why i get a sword on a chest with green rarity which has 5 DPS and the ones i can craft are 90.

Even if it's possible, i don't get how you can manage to have a gap of 1800% on the same tier, this is just not logical.
And yes, you can see that a few minutes into the game.

 

thank you at least some people understands what im trying to explain

 

People spent money on a testing phase and assumed they'd get a fully working game.

 

Partly right; it wasn't to "fix" weapons, but to change out the level-based AP system to something easier to understand. The patch notes even say that the damage numbers at this point are probably all screwy and will need adjusting in the future updates, but the straight DPS system is working.

And that's where the beta testers come in. The devs have spent the weekend working on the mechanism, not on the fine tuning. For that, they rely on our feedback. If you want polished patches that address all issues then you're probably better off waiting for the final release.

 

I spent money to help Chucklefish develop a game and got a free beta test out of it. ^^

 

If that's true, that would explain a lot. Thank you.

 

oh yeah if you want to see what im talking about the bug i mean

make an iron 2 hand sword and then go find any weapon drop from a monster. im flying around in a tier 2 world now and nothing compares to the iron sword.

guess i should report this asuming that im not the only one.

 

Still, apparently a futile battle you're trying to have...

 

The reason there is a beta, is because internal testing doesn't catch everything. There's probably only 5 'internal' testers at most. How many of them do you think got past tier 1? Crafted much? Etc.? On the other side of things, there literally 500 THOUSAND beta testers, that catch every single bug/mishap/problem.