Erth Paradine
Server Admln & Bug Reporter
- Joined
- Feb 15, 2016
- Messages
- 239
- Reaction score
- 58
I can't agree with total negligence, as Schine staff are very approachable for support related needs; speaking first as a player and then later as a server owner. Further, recent changes to the game have improved the experience for all: Chunk32 proved to be a positive performance improvement (once players got around to manually updating client-side settings), and a transition to sparse files significantly reduced disk space requirements. While that's just a short-list from recent memory, it is clear that someone is paying attention......
what we see here is total negligence to work with community and to face their potential customers' requirements.
What I see though, is a mixed software development method. At times iterative or agile methods are in play, while waterfall seems to have a strong influence as well. In waterfall development, testing always follows a build phase, "preview" (e.g. prototype) releases are often accompanied with buggy features that may not get attention until much later dates, and requirements are pre-determined with user input rarely altering the ordering, pace or final outcome (unless it's correcting an architectural defect, such as sparse files or chunk32).
Whereas with more modern development methods such as iterative or agile, there is a constant pace of change iterations, and then iterations become releases (which are frequent), evolving user requirements are expected and readily accommodated, members of multiple small teams closely collaborate, faith and trust in personal motivations is implicit, there is a strong emphasis upon simplicity and technical excellence (e.g. good design, minimal typos, and early stabilization of released features before introducing more), and automated testing is heavily leveraged with exploratory and procedural testing (e.g. QA) also in play.
While I realize the engine has been in development for nearly a decade, with a consumable modern incarnation for nearly half that time, we're all investing our own resources to scratch personal, creative, and professional itches...I suppose this is where confusion leads to frustration: I see token gestures of modern software development conjoined with older practices. The gestures are confusing, they do not help illuminate where user feedback and suggestions fit into the greater picture...and that could lead to perceptions of negligence.