Open broxen opened 4 years ago
Assigning Stakeholders. Feel free to remove yourself after viewing.
Use cases to consider: Server groups - in some cases we might want to have multiple auth-servers in a group: | Group | Server |
---|---|---|
SEGS | ||
Internal-testing | ||
Testing | ||
Live | ||
Local-host | ||
Internal-testing |
Client assets - we will need a way to notify our dear users that they'll need to download some assets to play on a given server, or that a new version of client/asset will be downloaded.
I think, that in the end, we'll end up with a directory structure something like:
client_executables/
segs_client_1.0.0.exe
common_plugins/
v1.0.0/
asset_cache/
a_file_that_is_used_by_many_servers.file
assets/
segs/
live/
.manifest
plugins/
I threw together the layout for the launcher design rather hastily, and without a lot of community engagement.
I based the concept off the beautiful Guild Wars 2 launcher by Ryan McIntyre: http://ryanmcintyredesign.com/portfolio/guild-wars-2-launcher/
I'm posting those files here, and the design iteration for posterity, but also to open up dialog about how to proceed with the implementation. Through Discord it seems that there is a desire for the following changes:
We'll need new concept UI for all of these screens, widgets, and assets.
Original Concept Art
Main Screen Loading
Revised Concept with @mobbyg Art!
Main Screen Settings
Current Launcher [WIP]
Main Screen