Making changes bit by bit

[samster]

I am not starting this thread to criticize the dev team - god knows i appreciate the work that is and has been done.
However, it can be stated that every time the changes are implemented in bulk, more 'bugs' emerge. My suggestion is obvious: fix things one at a time. Like our beloved Nalgol fixed the notorious IB AoE spam some weeks ago, or Max himself fixed the problem with RP/Zealot one-shot kills today after the patch.
That approach seems less harmful to my dilettant mind.

P.S.: please make crafting stuff fall into crafting bags - that would make more sense, save inventory space and lots of time.

[Azarael]

I agree with such an approach to updates. As for preventing patches given to the live server from containing critical bugs, it could be argued that there's no actual need to do that. It does say "alpha phase" at the top, so we're all alpha testers, no? Plus, from the info visible on IRC, it seems each individual developer works separately, pushing commits to a master codebase. Private testing might end up being inefficient.

[Kragg]

But thats the whole point of large updates: Those bugs emerge, more people log in to play, the devs find out what's wrong and then they apply an hotfix when needed. Those bugs are only harmfull to players but worth gold to devs tho know what went wrong.

[Azarael]

I think there are a few people really dedicated to testing who play regardless of update schedules - most players who are drawn in by big updates just want to play the game. I also think that faster updates actually serve as a population stabiliser, because they give players who might be dissatisfied with a particular bug or issue (such as, say, IB AoE spam or the WE being useless) hope that very soon, something will be done about it. It's also more efficient to update working features as soon as possible in terms of time spent enjoying them - if something is fixed at the beginning of a one month patch cycle, that's a month of the fix being held in reserve when it could be on the servers and benefitting people. Searing Touch and Bunch o' Waaagh are going to be a defining example of this effect.

[Kragg]

I think there are a few people really dedicated to testing who play regardless of update schedules - most players who are drawn in by big updates just want to play the game. I also think that faster updates actually serve as a population stabiliser, because they give players who might be dissatisfied with a particular bug or issue (such as, say, IB AoE spam or the WE being useless) hope that very soon, something will be done about it. It's also more efficient to update working features as soon as possible in terms of time spent enjoying them - if something is fixed at the beginning of a one month patch cycle, that's a month of the fix being held in reserve when it could be on the servers and benefitting people. Searing Touch and Bunch o' Waaagh are going to be a defining example of this effect.

Perhaps so but an hotfix will surely take care of said bugs? Dissatisfied players could drum up some patiance while the devs tackle a problem. Maybe small updates and big ones should vary. Still have large ones but in the meantime apply some smaller ones like for example the dyes?

[Spongel]

It's an alpha. Updates like the last are the point of making an alpha. I understand that ppl want to have as much fun as possible. But I m not afraid of the population progress. People will come when the game is finished. Till then it's just for freaks like you and me who have fun with an unfinished game. And in an Alpha things aren't working that's why it's called an alpha

[nalgol]

pff and i was thinking it would make ppl happy

the problem is we didn't encounter those instant kill bugs on dev with 4 ppl testing
and this update would not be possible to do in steps
if i had fixed damage first ppl would complain they die so fast
if i had fixed armor / resi / thougness first ppl would complain they cant kill anything anymore
if i had added career recurces for 1 carrere those players would complain that they underperform now that they cant spam finishers anymore
and so on you canot make it right for all


i had to do the whole combat in one go theres still stuff missing i know like bw sorc + damage but i didnt added that yet for a reason and that is that resistance buffs don't work yet so its a bit even

[Azarael]

The instant-kill bugs only manifested in PvP and against high Toughness targets anyway, those would have been very difficult to find on the test server.

By all means, keep doing what you're doing. We're just talking, no response expected, and it doesn't mean that we're ungrateful for what you are doing. It's your show.

[Tesq]

pff and i was thinking it would make ppl happy

the problem is we didn't encounter those instant kill bugs on dev with 4 ppl testing
and this update would not be possible to do in steps
if i had fixed damage first ppl would complain they die so fast
if i had fixed armor / resi / thougness first ppl would complain they cant kill anything anymore
if i had added career recurces for 1 carrere those players would complain that they underperform now that they cant spam finishers anymore
and so on you canot make it right for all


i had to do the whole combat in one go theres still stuff missing i know like bw sorc + damage but i didnt added that yet for a reason and that is that resistance buffs don't work yet so its a bit even

Yea+ this is exatly what i tought, i'm glad you haven't too (able or not) fixed guard with out sla/chop sorc/bw damage increase or some classes would be impossible to kill, or vice versa.

Guys we should all remember that what you all ask is impossible, of course they work all separatly , they are probably are geographically separete, there is no such place they cna work togheter, still they work when they can and this the best way as nalg told to keep ppl don't bother server status, while update and improve server, if we want realy help with fast update WE should, report what is not working on our classes.