I have not spoken to them about my campaign. It is here for all to read. These are my stated goals and dependent on whether it is technically possible to do them will be seen. As I have mentioned I do not have a programming or IT background, but the people I play with who have a programming background, say that most of it seems possible. Of course I will seek to work together with all the developers and councilors to implement what is possible to improve the game and keep us moving forward and focused on what the player base wants as a whole. One of the main issues people want looking at are all the bugs the game has including the ones that were caused by patching the game. It took a looong time for the ACU assisting shield to not wandering off anymore I do not know if the ACU can still build&fire at the same time (this is the bug I was refering to Icedreamer, but the move&upgrade / move&build thing has indeed always been around for ever.
Regarding the patch reversal policy, I do not know how people have been working on the coding side of things in the past but I have noticed (as many others) that with almost every patch, new problems have crept into gameplay that were clearly not intended. So my main goal of bringing in a policy of reversing patches that create new unintentional problems addresses just this problem. It would involve developers keeping a log of what they have changed so that changes to the code can be quickly and efficiently reversed if a review does not help us identify what is causing the new problem. So this policy would be more of a thing looking forward than looking back.
Lets take the balance patch as an example. Previous patches rarely explained to the players what had changed and why it was changed. The balance patch on the other hand was implemented with a nice graphical display of what was changed for all to see which made it easier for people to pinpoint what they like/dislike. So having a back up of the previous unit coding which I recall is available on GitHub, would make a reversal of changes that are not working, or disliked much easier.
Personally, I am of the belief that it is better to go back one step and back to the drawing board if something does not work rather than ignoring it. I understand that sometimes changes must be made and are unavoidable like a server change from which issues can result, but other issues have come from changes that were made and did not need to be made, and those are the ones we need to apply the policy of reversing them to.
In regards to the mentioned Beta Participation numbers being so low, I will say that:
1. It is often unclear to newer players that Beta exists or what is being tested.
2. Feedback from players in posts take a lot of time to write up and take a long time to read and process by developers (surveys would do much better at gathering feedback).
3. Communication to the player base is often poor because people get on the FAF client to play and not to read what is being developed (I also often skip the "whats new" tab). Changes to the game that pop up when hosting/joining a lobby get more attention than the "what's new" tab.
4. The lack of interconnectedness between the forum and client often keeps people from finding out about news posted on the forum. I spend very little time on the forum, I am not enticed to go to the forum.
5. The forum is not easy to navigate and information is not well sorted. You have to scroll down on the "what's new" tab to find the "Recent Posts" "Recent Forum Posts". Recent posts also include a lot of posts of people who are just ranting or ideas like proposing ASF to get teleport or the likes. This hides the important posts between a jungle of posts no one cares about.
We could use a better organised '"what's new" tab with posts linking to topics that matter. For example:
A. Rules (what is considered cheating)
B. Current identified bugs (which developers are working on it and the data they need sending from users who experience the bugs to help them)
C. Voluntary trainers (for new comers who want to some basic training)Statistics: Posted by Evildrew — 01 Nov 2016, 19:56
]]>