-
Notifications
You must be signed in to change notification settings - Fork 178
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.
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
RFE: Tertiary Roles #1911
Comments
Now that it's said yes, as well as rotating negotiators... |
You know, LAM pilots are desperately need for this, for they have both Mechwarrior and Aerospace Fighter role by default. |
First thing, this should have been split into two different requests, as there are two requests here. In future, please open one issue per request. However, I've opened #1914 to handle this one. Second, I'm planning on switching LAM Pilot to its own role in the very near future as part of my role work @binaryspica. |
Under Campaign Operations rules admin have no subset such as transport etc. Admin is just a catchall for lawyers, doctors, intel, cooks, etc etc. Also, the rules only mention secondary roles for techs/admin. For the more rpg focused games... Not even sure what aToW allows. One of the two aToW books has merc rules that are the same or similar to the old FMMr rules. |
I'm not entirely sure what the various rule books have to say about this, but it would be nice (especially for smaller commands during the scroungy eras) to have the option of assigning a third role for certain members.
For example, if my mechwarrior commander has the appropriate skills, he should be able to fill not only the role of mechwarrior and admin/command, but I feel he should also be able to do admin/transport. This would help to reduce roster bloat for smaller commands.
See #1914 : Additionally, being able to set a negotiator flag would be beneficial. I can imagine having a team of negotiators rather than a single administrator handling all contract negotiation. (this was split off after this issue was opened)
The text was updated successfully, but these errors were encountered: