Open jcdesimp opened 7 years ago
Based on existing documentation, these are the teams and their objective/mature at values:
Team | Objective (DevCaps) | Mature At (Round Number) |
---|---|---|
iOS | 30 | 3 |
Android | 30 | 3 |
Web | 28 | 1* |
API | 20 | 2 |
Cloud Services | 24 | 1* |
Automated Warehouse | 30 | 2 |
Drone Delivery | 30 | 3 |
Streaming App | 40 | 0^ |
* Indicates the team begins the game as Mature. ^ Indicates the team will never be Mature.
@andymeneely Should these fields be modifiable by the Storyteller on the Team
model, much like the other initial... attributes?
I don't need it per se. Once a game is started, I won't be changing objectives or maturity. I would balance it other ways.
@andymeneely Sorry, I don't think I communicated my question clearly enough...
When the Storyteller is configuring a new game, and is configuring the Teams, should they be able to modify those values (prior to sending the out the Team link codes)?
It's a bit nit-picky, but determines whether the Team
model requires the field as well.
Although the same balance could be achieved by event damage modifiers and event selections, I suppose, which is what your comment was getting at.
Yeah. At that point I'd probably be re-seeding the database anyway so I still probably don't need it.
TeamType model should change one field and add another
objective - Integer
initial_mature - bool
tomature_at - Integer