Staff testing? Why not community feedback? c:

[ZingBing]

Is it acceptable if I write in the thread after the CEO of Cubecraft steps in and explains the whole problem/solution? :D Not sure, but I will anyway...

Well, I like the idea! The only problem, though, is that people would probably complain about how the testing was organised and getting people to actually test the games for bugs and such without just playing them and then (maybe) giving up. Along with that, the rest of the members in this string probably summed it up really well :)

 

[MagnificentSpam]

Creating a new server is not quite as simple as making a new subdomain (I wish it was!).

From my understanding it's just about what the player sees, it doesn't have to be a separate physical server. You can use the "forced_hosts" feature in the bungeecord configuration to redirect players to different game servers based on which domain they used, like virtual hosts in a web server.

Bug reports are an interesting thing. On the one had making them public would stop duplication of issues but on the other people could abuse them. Again it's about finding the balance and isn't something we'll get right on day 1.

In general once the new system goes out it *should* be easier to handle duplicate bug reports. I would say that it's better to get 30 reports of the same bug rather than everyone assuming that someone else will have reported it!

Everyone can download a hacked client that will probably give bigger advantages than most bug exploits will. I can't imagine many players going through all the reported bugs looking for something to exploit. You could possibly add an option to create a hidden bug report if we think a bug could heavily be expolited and also allow mods and helpers to change a bug report to hidden. Most bugs are just annoying for everyone and can't really be used.
It would be easier for us if we could just see what others have reported and add to that instead of documenting and reporting everything ourselves.