0
First, thank you for making the wonderful game. My suggestion is that once the next patch or two goes live that the developmet team take some time to work on stabilizing the build to knock down some bugs and tech debt. Whether it's time boxing the effort, dedicating a sprint or two (depending if you use agile and 1-3 week sprint cycle), or allocating large chunk of next patch or two on stabilization, etc.
Since we went open beta, lot of new features have been added, ton of tweaks, and felt bit aggressive timeline. Part of it was evident with some codes making on to Prod that should've and would've have been very easily caught during test game play. Perhaps more thorough code review would've caught it as well. I'm speaking of LRM flight arc/grouping and too much buff on LRM damage when Artemis was introduced as an example.
Plus there are some bugs that's still outstanding that has been around for a while and I do mean since closed beta. So it may be good idea for the team to spend ttime to stabilize the build instead of working on new feature. I think once you spend some time stabilizing and then going back to iteratively releases of features will be extremely great for gameplay and for us to continue beta testing.
Some of the problems I'm talking about are the ones often quoted as 4 FPS issue, no HUD, overheat/no HUD/yellow, black screen, yellow screen, terrain where you get stuck, which all have been persistent issue since early start of closed beta. I know these are being addressed in bits and pieces per release and I did notice less of them. However considers it's been months and we're in open beta, I believe it should warrant a rise in priority for these bugs/issues.
Thank you and keep up the good work.
Thank you.
Edited by Blood78, 01 December 2012 - 09:36 AM.
