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

Mixed languages for runes / hitlocation dropdowns #689

Closed
wake42 opened this issue Jan 22, 2024 · 0 comments · Fixed by #690
Closed

Mixed languages for runes / hitlocation dropdowns #689

wake42 opened this issue Jan 22, 2024 · 0 comments · Fixed by #690
Assignees
Labels
type: bug Something isn't working. Use "fix: " commit message
Milestone

Comments

@wake42
Copy link
Collaborator

wake42 commented Jan 22, 2024

What: Describe the bug

If you have compendiums with different language versions of runes or hit locations you will get mixed language in the dropdowns

How: To Reproduce

Steps to reproduce the behavior:

  1. Activate 2 compendiums with runes or hit locations in different languages
  2. open a item sheet that displays the rune / hit location dropdown

Expected behavior

Use the world language version and only include a fallback language (en) version if the item does not exist in a world language version.
The rqid language of items will need to be included in the compendium index to fix this.

Screenshots

image

Environment - please paste the information from foundry settings tab "support" button:

RQG v3.4.1

@wake42 wake42 added the type: bug Something isn't working. Use "fix: " commit message label Jan 22, 2024
@wake42 wake42 added this to the 3.5.0 milestone Jan 22, 2024
@wake42 wake42 self-assigned this Jan 22, 2024
@wake42 wake42 closed this as completed in 7f6f303 Jan 26, 2024
@wake42 wake42 modified the milestones: 3.5.0, 3.4.2 Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working. Use "fix: " commit message
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant