None of this is definite, it is only a rough way forwards.
General
Each package will have its own ruleset for picks/bans, allowing cpu players, teams.
Each package would also like to create custom UI for fighter and stage selection.
We can combine these needs by embedding a web browser and letting package creators use HTML/CSS/Javscript to define their UI (and thus its functionality as well)
Netplay
Doesn't seem like this would mesh well with rollback netplay code, may need to create some sort of alternate messaging system between them o.0 oh dear
Also of note: when using netplay it may be desirable to have a unique display for each player. (For blind picks etc)
API
We will need to expose to the embedded browser an API with:
Controller inputs
List of fighter names + a way to render fighters
List of stage names + a way to render stages
function start_match(players, stage)
function is_netplay()
Current UI
The current primitive UI hacked together with vulkano_text, will stay for the purpose of providing a default UI that packages can then overwrite with their own web version.
None of this is definite, it is only a rough way forwards.
General
Each package will have its own ruleset for picks/bans, allowing cpu players, teams. Each package would also like to create custom UI for fighter and stage selection. We can combine these needs by embedding a web browser and letting package creators use HTML/CSS/Javscript to define their UI (and thus its functionality as well)
Netplay
Doesn't seem like this would mesh well with rollback netplay code, may need to create some sort of alternate messaging system between them o.0 oh dear Also of note: when using netplay it may be desirable to have a unique display for each player. (For blind picks etc)
API
We will need to expose to the embedded browser an API with:
Current UI
The current primitive UI hacked together with vulkano_text, will stay for the purpose of providing a default UI that packages can then overwrite with their own web version.