Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Strike Team Support #3

Open
8 of 15 tasks
jacobtread opened this issue Aug 6, 2023 · 0 comments
Open
8 of 15 tasks

Strike Team Support #3

jacobtread opened this issue Aug 6, 2023 · 0 comments
Assignees
@jacobtread
Labels
enhancement New feature or request

Comments

@jacobtread
Copy link
Member

jacobtread commented Aug 6, 2023 •
edited
Loading

Description

Full support for strike teams and all the required components within the server

Checklist

  • Strike teams can be randomly created with different names and icons
  • Strike teams can be viewed
  • Strike teams can be retired
  • Strike teams can be purchased
  • Strike team equipment store list
  • Can purchase strike team equipment
  • Mission config (Already done? not sure if this needs to be changed yet)
  • Strike team missions are created and randomly generated (Needs to handle expiring)
  • Determine how strike team missions are given out (Are they unique to each player? No they are same for all players)
  • Strike team per mission success chances
  • Strike team missions can be started
  • Strike team mission reward claiming ("mission resolving")
  • Strike team possible traits known
  • Strike team mission result traits and trait randomness
  • Strike team renaming from mobile app (I don't know if we can support this)
@jacobtread jacobtread added the enhancement New feature or request label Aug 6, 2023
@jacobtread jacobtread self-assigned this Aug 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jacobtread jacobtread

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jacobtread