MadCamel wrote:I'd like to point out that the development team is fairly small and doesn't have the resources to do everything as properly as they'd like to.
Right. But nothing screws up things as much as lack of ambitions and large-scale plans. For TMW it has always been an issue that devs usually "fixing" things in easiest (and dumbest) ways, at expense of gameplay and players experience. Then, since issue is "less daunting", there is less traction to actually fix it in better ways. The result? Nearly all long-standing issues are worked around in hackish/half-working/dumb ways, this plagues game here and there for years. And since most of devs do not play it, and it looks "less daunting", nobody is motivated enough to improve state of things at all. Result? Well, I've attempted to show TMW to some friends and learned the very same things I know myself. Unfortunately these things do not sound too nice for TMW devs. I think it could be better, eh? Such a stockpile of efforts from different people deserves better perception by humans, IMO.
It's not out of malice that things get pushed without much feedback. It's not out of absent-mindedness most of the time either.
But it's still some lack of responsibility and failure to understand such actions can affect quite many people around. Who could actually care about what would be thrown on their heads. If it happens to be far from expectations, churn and grief takes place. It could be expected, no? Both too-dev-centric and too-consumer-centric approaches suxx equally bad. It only rocks when it's more or less balanced.
It's a time issue. People quickly lose motivation if they cannot see the results of their hard work in action, so pushing new updates is always a priority.
Sounds reasonable. However, there are test servers to see how it performs "ASAP". Then, why not to call some players from testers group to test "new good things" and then collect feedback on how it feels from players side? This would be responsible and would also allow to notice things you've missed yourself. I've got
nice example myself, missing really obvious bug. You see, I've got bug even if it has been simple thing and I've done some testing myself. Good example why it's nice to have feedback from others. Nobody is perfect.
The TMW developers work for free, and they need to get some gratification out of what they do in order to continue doing it. As much as everyone who develops for TMW would like to be more precise and thorough, that just doesn't work with so few team members. Doing so would slow development to a crawl and de-motivate everyone involved.
Right but still it's a bit question if devs should be able to do completely arbitrary actions, screwing up players and causing grief, making players to leave their homes, going to servers/projects with better, more friendly climate. When everyone stops caring about community around, it would follow ManaServ's fate. Which maybe not so bad technically, but it failed to keep momentum and mostly abandoned by content makers and players. Up to degree ManaPlus stopped supporting this protocol at all.
Can improvements be made? Sure! There's always room for improvement.. But when coming up with suggestions please keep the above in mind

And when you think it's okay to throw arbitrary chunks on players heads, keep above in mind too. Unless you want TMW to follow fate of ManaServ. I think it should be more or less balanced approach where devs and players views are mixed to make something really nice.
One thing I would like to see is the "tmw testers" group actively tracking development instead of waiting to be asked to do something. I think that would be a big help. Get on IRC and into #themanaworld-dev guys.Testing and feedback is very important, and we hardly have any at all!
Somewhat true. And proper place to remember about time again, isn't it? Fully tracking all development requires some time and most of time WIP is not really okay to test. Most notably, future changes would negate most of testing results anyway. So unless it's something more or less ready, it's rather waste of testers time. It's possible to get some improvements this way, but here we come to fact testers aren't full time employees either. On other hands, throwing one message to testers group does not takes much time and then it's easier to notice there're some things to chew on. Also, if testing something for a while, from my experience testers tend to lose freshness of their sight. To be honest, as QA I can admit best testing happens when you encounter something for 1st time in your life. In this case you feel exactly like some new user would do. So it's just a matter of taking into account things which make you unhappy and being able to describe them. Repeated testing requires testers to be able to "switch roles" between development and testing. Very few mortals possess this rare skill (not everyone could be good QA, can you imagine that?) and even then it's not as efficient as looking on something new with fresh eyes.
P.s. also I think now I'm finally got why corporate nuts are so inclined on their damn "deadlines", even if it often harms quality of software a lot. It turns out some devs can tell something about "alpha" versions even after 10 years of development. So I guess someone invented it as "watchdog timer" to prevent such insane things from happening.