Funkencool did the most work in that area so far (basing some of it on chililobby). Since then, chililobby has had a few changes and I think I would need to help Funkencool with updating to it, but there's still a lot of time before chililobby can get a new stable version, and I ask people not to use dev versions.
I'm personally not sure we need an
engine-default in-game lobby, but the existing one could be dropped when Lua alternatives become available.
abma wrote:
Whats (imo) needed:
1. empty / VERY small map, ideally lookling like current background menu image
3. small engine change which loads the menu (atm just the menu- map & game) as default when no parameter is set
I'd rather there be an engine change which allows in-game lobbies to be loaded without maps.
Is this what LuaIntro is supposed to be?
abma wrote:
5. edit settings
I'm not really sure that a user version of an in-game lobby should expose all spring settings. I would certainly not do it if I was making this for players, or make it hidden below a few "Advanced", "Detailed options" menus.
It still might be important to have it since we often recommend users to change an arbitrary setting when troubleshooting, but designing such a system so they don't break their configs requires some thinking.
abma wrote:
7. select missions / campaign
Needs a mission/campaign format implemented. I just shiver of the thought of restarting that discussion as I remember how unproductive that was last time it was attempted.
abma wrote:
8. "switch" game menu
Needs clarification.
abma wrote:
9. lobby
If you want a full in-game lobby, then it might be best to just use chililobby for this from the start. This would be my preference too - I see no reason to limit ourselves to just singleplayer skirmish initially (joining a multiplayer game is even easier than starting a singleplayer one).
abma wrote:
10. download game/maps/missions
Am on it, but not that much free time.
abma wrote:
engine side, some stuff could be optimized:
- improve load time of menu
(Re-)creating the cache is something that can take too long and that might drive away new users.
I think it would be great if spring could have a command line parameter that would update the cache (and do just that), so games can do that in the installation phase.
Once Spring starts, the menu is loaded instantly.
abma wrote:
thoughts? will/would this work? or ideally: is there already such a project?
To summarize: I just want the ability to load the in-game lobby, without any map. I don't want any hardcoded engine default, although I would like to see a future like this:
1) Games with an in-game lobby use chililobby(+liblobby) and extend it/brand it as they see fit (ideally just by changing settings/API, but maybe even by forking it and modifying code).
2) A default chililobby still usable by gamers without any branding (much like SL and SWL).
3) An easy way to start Spring with one of these lobbies. (I have no idea how to do that without making one lobby the default, and rest configurable by params or springconfig.cfg).
I really want to work with funk on chililobby as he seems to be an early adopter. I didn't know there was already a repo available, so I went and implemented the background image support in chililobby -> it's configurable, and the default is pretty neutral. I do need a good Spring-related, but game-neutral background image I can use if anyone has suggestions.
I'll do my best to solve some hard problems so
ideally lobby developers only have to think about configs, skins and extra widgets they'd like to add, so if there's any other feature you'd like, feel free to ask for it.
PS: Ofc I wouldn't mind if people don't use chililobby, but that just seems irrational atm as there's no alternative.