Some years ago spring games got an awesome innovation:
Built-in singleplayer menus!
With these lua'ed menus players can select missions or set up skirmishes.
short version: Lobbies need to make these menus available to players.

others:
http://media.indiedb.com/images/games/1 ... n00489.png
&
http://h-4.abload.de/img/spmenuwse0.png
Since the moddevs have full control over the menus they made, they can ensure players can for example not select any AIs that will not work with the game.
So all very nice but big problem:
How does the player get into these ingame-menus?
He has to start spring.exe, select mod, select map, click start.
Seems simple but...
Problems with that:
Average player might not find spring.exe, especially if it was automatically downloaded like some lobbies now can.
After start, the spring.exe menu ("the beach") comes up which is like a silly pre-menu to get into real menu. For example you have to select a map and AI just so the game and its menu will start.
How it could work:
In the lobby is a button "Launch internal game menu"
After clicking, spring starts with the game selected and the game's menu takes it from there.
Details
Spring must be started a script.txt, so that chosen game will be launched. Since the AI, map etc in that script.txt does not really matter it can maybe something generic. Or would it be good if this launchscript was somehow read from modfile?
But basically no complicated stuff is required:
Just a button that launches spring with the mod selected.
Other possible solutions which are not as good:
"Lobby XY already has a singplayer menu"
Why it is not good:
These menus look different in every lobby.
There is little control that would prevent players from setting up games that will not work. ("game vs allied NullAI and everybody starts in the same spot")
"Why don't game makers make their own installer, then you can include a singleplayer.exe like this one: http://springrts.com/phpbb/viewtopic.ph ... nu#p458934"
Why it is not good:
Lobbies can already download the game file, engine and maps and update all that. Making own installer means reinventing all that. It might also only work on one OS while they are already lobbies for every OS. There is no need to make new installers: Almost all is already done, just needs to be put together.
To me it seems like an potential easy way to improve Spring?