Don't have the mod selector as first startup screen

[Itms]

I think the mod selector is too complex for the user, especially new people discovering 0ad.

I'd suggest having the public mod as default configuration (i.e. like if you selected it in the modmod then toggled "Save configuration"), and being able to restart into the mod selector from the public mod's main menu.

This wouldn't change the fact that the modmod must be standalone, with public "a mod like any other". We would just release 0ad as "pyrogenesis with public mod enabled by default".

[Yves]

I think that should be as simple as removing the ";" from this line in default.cfg:

;mod.enabledmods = "mod public" 

[Itms]

Eeeeeeh, I had seen that config line but I hadn't noticed the mod selection entry in the main menu :D

Well, do we all agree to remove that semicolon? :P

[leper]

Adding a 0ad.sh and a 0ad.bat script to the binaries/system/ folder should solve this for SVN users. (or we could just change the documentation, but that might not be the nicest way for Windows users)

Releases already call pyrogenesis with the right flags (see the changes in r15677 to source/tools/dist/0ad.nis, build/resources/0ad.sh) (We should be able to specify default parameters for an OSX bundle by providing a simple shell script as the default target, which just calls pyrogenesis with the right parameters)

[leper]

In 15796:

Load the public mod by default. Fixes #2754.

[leper]

If public isn't present it'll still load the mod selector, but as that shouldn't be the case it will just load public if it is present.