Like in Flashpoint Levant it would be nice for it to be possible to take up a mission and be responsible for it.
This could be nice for bigger missions that would require more flight time for example. (would be nice to know your target is there when you get there)
However, in my opinion it would be nice to think of a new way of doing it.
Owning a mission
(Should make sure synchronisity works)
For the owning player
Instead of currently pin mission it would be assign mission
Then instead of pinned mission it would have assigned mission.
For other players
The mission is not removed from the list.
The briefing command does not return the briefing, but returns the people assigned. (In order to communicate etc.)
Request To Join should be available now in stead of assign mission
The people that are inside of the mission will then have the option to accept or deny a join request.. {SpearheadRoot} => Join Requests => <player name> => Accept/Deny
"Groups"
Groups are joined by joining the same mission. Then continuing to a new mission will transfer that entire group.
Disbanding a group should be possible before joining a new mission.
Giving missions back to the pool
When all players are gone from the server a mission should be returned back to the pool.
This should be monitored in a loop as the mission environment does not have connect/disconnect. Shouldn't be an issue.
Players should also be able to "unassign" the mission.
Initial raw idea.
## General Concept
Like in `Flashpoint Levant` it would be nice for it to be possible to take up a mission and be responsible for it.
This could be nice for bigger missions that would require more flight time for example. (would be nice to know your target is there when you get there)
However, in my opinion it would be nice to think of a new way of doing it.
## Owning a mission
(Should make sure synchronisity works)
### For the owning player
- Instead of currently `pin mission` it would be `assign mission`
- Then instead of `pinned mission` it would have `assigned mission`.
### For other players
- The mission is **not** removed from the list.
The briefing command does not return the briefing, but returns the people assigned. (In order to communicate etc.)
- `Request To Join` should be available now in stead of `assign mission`
- The people that are inside of the mission will then have the option to `accept` or `deny` a join request..
`{SpearheadRoot} => Join Requests => <player name> => Accept/Deny`
## "Groups"
- Groups are joined by joining the same mission. Then continuing to a new mission will transfer that entire group.
- Disbanding a group should be possible before joining a new mission.
## Giving missions back to the pool
When all players are gone from the server a mission should be returned back to the pool.
This should be monitored in a loop as the mission environment does not have connect/disconnect. Shouldn't be an issue.
Players should also be able to "unassign" the mission.
dutchie031
changed title from Make it possible for missions to be "assigned" and "owned" to Make it possible for missions to be "self assigned" and "owned"2026-08-20 06:49:01 +00:00
If we end up implementing the ability to have mission-specific drawings that only get shown when a mission is active, should these drawings then only be shown to players assigned to that mission?
If we end up implementing the ability to have mission-specific drawings that only get shown when a mission is active, should these drawings then only be shown to players assigned to that mission?
Ref: #38
EDIT: Added reference
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Initial raw idea.
General Concept
Like in
Flashpoint Levantit would be nice for it to be possible to take up a mission and be responsible for it.This could be nice for bigger missions that would require more flight time for example. (would be nice to know your target is there when you get there)
However, in my opinion it would be nice to think of a new way of doing it.
Owning a mission
(Should make sure synchronisity works)
For the owning player
pin missionit would beassign missionpinned missionit would haveassigned mission.For other players
The briefing command does not return the briefing, but returns the people assigned. (In order to communicate etc.)
Request To Joinshould be available now in stead ofassign missionacceptordenya join request..{SpearheadRoot} => Join Requests => <player name> => Accept/Deny"Groups"
Giving missions back to the pool
When all players are gone from the server a mission should be returned back to the pool.
This should be monitored in a loop as the mission environment does not have connect/disconnect. Shouldn't be an issue.
Players should also be able to "unassign" the mission.
Make it possible for missions to be "assigned" and "owned"to Make it possible for missions to be "self assigned" and "owned"If we end up implementing the ability to have mission-specific drawings that only get shown when a mission is active, should these drawings then only be shown to players assigned to that mission?
Ref: #38
EDIT: Added reference