You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Based on the discussion here: #25. We need database structures, API, and UI for starting a flight. I'll break the individual tasks out into their own issues once this issue is approved.
Describe the solution you'd like
This involves a lot of things to be considered complete. See the screenshots below for how this was implemented in Thorium Nova Prime.
These are the buttons which are present on the welcome screen. I think we'll skip the custom flight config and just have "Start Flight", "Load a Saved Flight", and "Join a Server". At some point, there needs to be an option for choosing which plugins are included in a new flight, but we won't worry about that right now.
The first step in starting a flight is choosing the number of stations the ship will have, as well as whether there will be a flight director. The flight director choice will likely affect which missions are available. I can't remember why I made it so crew count includes the captain - it probably should always include captain.
In Thorium Nova Prime, the ship was chosen first. You can see a list of all available ship templates and search through them. This is also the place where you would be able to choose a saved ship config from a previous flight, so you can transfer over the state of your ship from one flight to the next for longer campaign-style missions.
The final screen is picking a mission. As nice as it would be to have any mission runnable by any ship, some missions will only work for big ships (multiple decks, NPC crew members) and some will only work for small ships (few internal decks, no NPC crew members). I can't remember why I decided to have them pick the ship first and then the mission, but it might make more sense to pick the mission first and then the ship. Easily adjustable later if we prefer something different.
This is the Flight Admin Lobby, where whoever is in charge of the flight can assign connected clients to specific stations. They pick the client on the left and place them in the station on the right. They can also assign themselves to a station and click "Go to station" to open their controls.
And this is the station selection screen for the connected clients. They just pick the client they want to connect to and it automatically takes them to that station. Clients should have the ability to return to this screen to pick another station later, probably through the ESC key.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Based on the discussion here: #25. We need database structures, API, and UI for starting a flight. I'll break the individual tasks out into their own issues once this issue is approved.
Describe the solution you'd like
This involves a lot of things to be considered complete. See the screenshots below for how this was implemented in Thorium Nova Prime.
Additional context
Screenshots from Thorium Nova Prime
These are the buttons which are present on the welcome screen. I think we'll skip the custom flight config and just have "Start Flight", "Load a Saved Flight", and "Join a Server". At some point, there needs to be an option for choosing which plugins are included in a new flight, but we won't worry about that right now.
The first step in starting a flight is choosing the number of stations the ship will have, as well as whether there will be a flight director. The flight director choice will likely affect which missions are available. I can't remember why I made it so crew count includes the captain - it probably should always include captain.
In Thorium Nova Prime, the ship was chosen first. You can see a list of all available ship templates and search through them. This is also the place where you would be able to choose a saved ship config from a previous flight, so you can transfer over the state of your ship from one flight to the next for longer campaign-style missions.
The final screen is picking a mission. As nice as it would be to have any mission runnable by any ship, some missions will only work for big ships (multiple decks, NPC crew members) and some will only work for small ships (few internal decks, no NPC crew members). I can't remember why I decided to have them pick the ship first and then the mission, but it might make more sense to pick the mission first and then the ship. Easily adjustable later if we prefer something different.
This is the Flight Admin Lobby, where whoever is in charge of the flight can assign connected clients to specific stations. They pick the client on the left and place them in the station on the right. They can also assign themselves to a station and click "Go to station" to open their controls.
And this is the station selection screen for the connected clients. They just pick the client they want to connect to and it automatically takes them to that station. Clients should have the ability to return to this screen to pick another station later, probably through the ESC key.
The text was updated successfully, but these errors were encountered: