Hi,
I'm back at working on the QML Launcher. :)
I've been thinking about howto separate the Launcher of the Engine.
This is how i would do it for Singplayer games:
1) The Launcher takes care of the set-up (~/.warzone../config /,
maplist, etc.)
2) When the user starts a game it creates a file for all settings
(including the contents of the ./config for simplicity) as
~/.warzone.../launcher.cfg.
3) The frontend starts the engine with the path to launcher.cfg ?and
wait until the game is finished?.
And Multiplayer:
Basically as above, but the Launcher starts a
Server on port 2100 and waits for incoming connections.
The usual MP game setup/chat goes over that link.
so:
1) "Server" Launcher waits for connections.
2) "Client" Launcher connects setup starts.
3) game starts: All clients get an individual token, then the Launcher
closes the listening socket and starts the engine.
Clients wait until the connection is up (This could be
problematic/error prone).
4) Connected clients transmit the token to the server which validates it.
5) game starts as usual.
Integration into the warzone Repo:
For now i have no clue, as I want to rewrite as much as possible code
for the Launcher to make things simpler and easier to adjust (modable).
Thx at Buginator for some of the ideas (Launcher in general and Tokens).
Thanks for reading,
Fastdeath.
_______________________________________________
Warzone-dev mailing list
[email protected]
https://mail.gna.org/listinfo/warzone-dev
