-
Notifications
You must be signed in to change notification settings - Fork 7
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
Final page: assignment/role #50
Comments
Well, it seems like the character sheet and the rules are the culprit here, as the book uses "role" in the character creation section, but "assignment" in the character sheet, as well as chapter 3, which is more of an RP-style explanation of what people do in Starfleet. I wonder if splitting the assignment/role in the creator is a way to go. The "assignment" is written, purely for RP/narrative stuff (and perhaps the creator defaults to filling in the chosen role). Then the "Role" becomes an optional field, that grants the role's power (displayed in the "assignment" line, and still as the "power" in the two pager). Not knowing how the creator does the "assignment" section, this may be hard, or it may be easy. But given that characters can have none (cadets) or more than one role, it seems like this needs a rework regardless (more than one per ops division book page 38, where it notes that only one role benefit per scene is allowed). Edit: Reading the "assignment" section of the core book (chapter 3.40), it really does seem like that word is used for narrative purposes. For example, "command division, helm officer, uss thunderchild". Edit: put the gist of this post on the forums, more to see if they're in line with what other forum-users think, since I get the vibe most people there aren't on github. |
I like the changes! Edit: I swear I saw on a senior cadet it said 'job1, job 2' instead of 'job 1, ship', but that no longer appears to be the case? Weird. |
Per comments on modiphius forums, this is an interesting thing, that is a legacy of the way the creator was first made. Just making this an actual "issue" so it can be addressed here/notes or discussion about its technical aspects can be kept on github.
The text was updated successfully, but these errors were encountered: