Thanks Veldmaarschalk! And for those who don't know: Balor is Johan's home account.
And for those who don't know: Balor is Johan's home account.
I believe he's mentioned it a few times when addressing the community in dev diaries, such as "Hey it's Johan at home", don't quote me on that though.What are the evidences? Do you know that Irl sometimes i give Johan my account to post from home. Did you know that that Blue Emu?
What are the evidences? Do you know that Irl sometimes i give Johan my account to post from home. Did you know that that Blue Emu?
anyway why not keep a list of those 20-25 "tested and approved" active testers and use them as a double check besides using professional testers?
There's nothing wrong with using non-professional testers as a base. There are bound to be enough of volunteers who happen to combine their professional IT work with their spare volunteer work. The main issue (from our experience within CORE itself) is that quality and dedication vary widely amongst volunteers. So if you want to rely on volunteers as a base, as we have to ourselves, you have to make sure to separate the wheat from the chaff wherever possible. I'm safe to say that, during our last development cycle for CORE2 0.4.0 - which took a whopping two years! - there was little doubt about the quality of our testers after reviewing their performance during the first year, and rotating whenever possible. Those that stayed on could be relied upon without any reservations whatsoever. What stunned me myself at the time was that - according to Johan's statement - we were having more dedicated Betas for CORE2 at the time than Paradox was having for HoI3, despite the overall complexity of the HoI3 testing effort being much higher. And as a result there was hardly anything in need of fixing once we - finally - were able to release 0.4.0.anyway why not keep a list of those 20-25 "tested and approved" active testers and use them as a double check besides using professional testers?
I'm safe to say that, during our last development cycle for CORE2 0.4.0 - which took a whopping two years! - there was little doubt about the quality of our testers after reviewing their performance during the first year, and rotating whenever possible. Those that stayed on could be relied upon without any reservations whatsoever. What stunned me myself at the time was that - according to Johan's statement - we were having more dedicated Betas for CORE2 at the time than Paradox was having for HoI3, despite the overall complexity of the HoI3 testing effort being much higher. And as a result there was hardly anything in need of fixing once we - finally - were able to release 0.4.0.
This is where you are wrong in my opinion. It isn't (or shouldn't be) part of anyones job to be treated like garbage.
In my opinion if people can't bother to make their complaints in a polite and clear way, then I wouldn't bother actually taking those complaints seriously...
As stated here we want to avoid cycles like that in the future ourselves as well for CORE3. Though CORE2 popularity has picked up considerably once the hype regarding HoI3's initial release quited down somewhat. Besides, with the current team size things look rather different now than two years ago. For the current QA discussion that's all a bit off-topic though...And in all fairness, there was hardly any interest in 0.4, relative to CORE's historical popularity. Why? Because two years was WAY too long. The fan base died off. Lost interest. There has to be a balance. CORE's obsession with perfection during the HOI2 cycle rendered it irrelevant. Based on the amount of time it took to get to 0.4, we could expect 1.0 in 2015. That's unrealistic. It's the death of a thousand cuts. As a longtime fan, I am desperately hoping that the CORE team's approach to HOI3 will be much less ambitious and much more realistic.
You sound you like you worked in a service industry job and took the wrong lessons away. Just because a certain level of jackassery is inevitable doesn't absolve the individual jackasses of responsibility. Paying someone for a product doesn't give you the right to treat them without basic human decency. I can't think of a part of the EULA that read, "if the game does not work as expected or advertised, the end user can make personal and profane attacks upon the developers and fans." :rofl:
Here is one such posts
No, not at all. I'm not a fan of jackassery consumership, i.e., demanding the perfect latte and kicking and screaming until the barista gives it to me. That said, if a product or service sucks, you can expect people to complain about it. So arguing that no one shouldn't be complaining despite the failure of the product or service is a bit rich, in my opinion.
Paradox isn't a service provider, they make computer games, i.e., a product. They live and die by people buying their game, not entering their establishment and sitting down to eat. They just can't tell people to shut up and get out of their building. They either make a good product that people buy, or they go out of business. So, at some level, this means they need to listen to their customers.
That said, I enjoy the game and I'm looking forward to 1.4 (hopefully with the manpower issue fixed).
No need to shout - just kiddingOnce again, I never said "shut up and take it", I said "being civil in your feedback helps more in the long run".
There's nothing polite about people quitting on a brand. They either buy the product or they don't. And if you can't provide a product that people want to buy, you go out of business. Being nice or polite has nothing to do with it.
You sound you like you worked in a service industry job and took the wrong lessons away. Just because a certain level of jackassery is inevitable doesn't absolve the individual jackasses of responsibility. Paying someone for a product doesn't give you the right to treat them without basic human decency. I can't think of a part of the EULA that read, "if the game does not work as expected or advertised, the end user can make personal and profane attacks upon the developers and fans." :rofl: