Inky-Inky
commented
2 years ago My PR #92 offers an elegant solution to this itching annoyance.
As a mapper, if you want your map XYZ to start right away after the menus without any intro screen, then this is an "old mission situation" and you add -startold XYZ in the command line.
If you want your map to start after the menus with an intro screen, then this is a "new mission situation" and you add -startnew XYZ in the command line.
If you add none of those, of course, it's the vanilla behavior.
And if you want the player to play your map no matter the mission type chosen, -startold XYZ -startnew XYZ of course.
Like "You can skip my cool intro if you want, bastard, but you'll play my map anyway!!!"
No more forced to name one's maps demo1 or keep1. Just a small batch file containing the right command line instructions to provide.
If a custom content is launch through a command line with +map X, the game starts on map X directly and forces the class choice and difficulty setting, which is very player-unfriendly imho.
Conversely, not using the +map thing welcomes the player with the menus but requires the starting map to call either demo1 (old mission) or keep1 (new mission). In other words, with just a tiny bit of exaggeration, us mappers should name literally each map keep1.
What trick could we find to have the best of both worlds? Menus AND whatever name for the starting map?