I only used it as an example really, the philosophy should be the same for all bugs. And I would call that specific one a bug, because the stat is “Area size increase” and not “Radius increase”. It would be inconsistent to work differently for a single skill or effect when it is not worded differently.
Except they promised the client it was gonna work a certain way, but it doesn’t. You’re right, it doesn’t matter to the client how it works, just that they deliver what is promised, and well, the Ballista Explosion Area scaling just doesn’t do that.
That is indeed a company issue, but a communication one, not a coding one. The code is still gonna be written in the same language, no matter what you use in your job, right? My argument here shouldn’t change whether I write it English, French, German, whatever language you speak or even in Klingon for that matter. Especially not in this case, because the underlying idea is surface area instead of radius, and that’s just mathematics, not spoken language. (My primary language is not English either, btw)
Why would them delay fixing bugs to 1.1 matter? You still wouldn’t know if something is a bug or not, right? So without looking at any build guides or whatnot in 1.1, you’ld still base your next build on the info you have now, right? The only way for you to know would be to come to the forums and look it up. On that part, I do think EHG need to maintain a “known bugs” list better so you can find it easily, but other than that, the patch notes aren’t available in the game/Steam until 1.1 goes live.
And I think this survey showed that they do care about player’s feelings. Their initial stance was that they wouldn’t change things, and a large majority of responses was negative to that stance. The votes on “warn us first” also shows that in case that does happen, they should give players a heads-up that a mechanic is broken and will be fixed soon. How long that “soon” should be is, imho, a different topic than this.