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.

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

Combinations of specification of species/sourcebook/gender are possible #28

Open
kkotenko opened this issue Jan 23, 2021 · 0 comments
Open
Labels
backlog Task that needs to be reevaluated to see if it's worth the effort.
Milestone

Comments

@kkotenko
Copy link
Collaborator

kkotenko commented Jan 23, 2021

#21, #24 and #26 define that !support should receive different parameters further specifying

  • source book
  • species
  • gender

The following results should be provided when they are combined:

If any of the parameters is invalid, Majel returns the first error it produces.

If species is given, source book is ignored, UNLESS the species is present in multiple source books (the "Source" field contains multiple entries, in which case, Majel tries to pick the version from the respective source book). If gender is also given AND the gender is valid for the species, a character of the gender specified by gender is generated; otherwise, a character with the given species and a valid gender for the species is returned as a fallback (That means that !support vulcan XXX has the same effect as !support vulcan). Valid genders are genders defined in the "Genders" field of the species.

If source book is given AND species is NOT given: If gender is also present AND any species from source book has the gender in its gender options, a character of the specified gender is generated; otherwise, a character with the given source book and a valid gender is returned, as above. (That means that !support ds9 XXX has the same effect as !support ds9).

I am not sure how the command would decide say, for !support vulcan male, whether vulcan is a gender, a source book, or a species. Also, this may be all too complicated. Any thoughts?

@engooyen engooyen added this to the Zora milestone Feb 12, 2021
@engooyen engooyen added the backlog Task that needs to be reevaluated to see if it's worth the effort. label Sep 27, 2022
@engooyen engooyen modified the milestones: Zora, Backlog Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Task that needs to be reevaluated to see if it's worth the effort.
Projects
None yet
Development

No branches or pull requests

2 participants