More support for actual basic skills: The GMC has too much focus on activity-specific training (e.g. how to make specific game genres) and break-fix help, and not enough on actual basics (e.g. basic control structures, scoping, design and code patterns, handling common errors). This is creating a generation of perpetually dependent rookies whose technical creativity and ability to self-help are essentially nonexistent. I would like to see a prominent go-to section where novices can pick up these skills, and I am willing to contribute to this section if YoYo would like to get it started.
More serious support for D&D: It has come to my attention that many novices who explicitly want D&D answers are met with uneducated responses from intermediate responders with no D&D experience. The responders first openly proclaim ignorance in D&D, then the novices are given GML answers (which often have obvious D&D equivalents for anyone with experience) and told to use GML only if they want help. As one of the few responders who can use D&D and GML, I absolutely despise these kinds of responses. There should be more learning and support resources for the D&D front, and if it needs to be sponsored to encourage activity, so be it. According to Forrester (source:
https://kissflow.com/no-code/), no-code development platforms will be worth $21.2B by 2022. YoYo should not pass up on this and squander the work that has gone into the D&D system.
More support for extension development and maintenance: This is an area of chronic neglect that I would like to see more YoYo attention going forward. The extension mechanism has many functionality holes and missing injection points, and the lack of a critical mass in developers familiar with it allows these issues to hide until a particular integration demands it. Tickets raised for them also tend to be neglected because the developers raising them are a lone voice. I would like a section where extension development techniques are taught and actively discussed, so that holes are more likely to be discovered and extension issues get more helping hands. Members of the YoYo dev team who are involved in vendor API integration should also be active here, since they will likely be more effective getting news and broadcasting here than individually responding to numerous tickets of the same stripe at the helpdesk.
Leveraging the GMC for helpdesk tickets: I can't help but wonder how much of the poor turnarounds at the helpdesk is caused by service technicians being distracted by coding-related tickets that the GMC is designed to handle, as opposed to being dedicated to actual engine-level faults and genuine support issues. There should be a consent box on the helpdesk authorizing reposts on the GMC in a dedicated section, where responders with at least 1-2 years of experience or admin permission may answer. Any ticket that the helpdesk can delegate is one that won't distract from things only YoYo can handle.