Fix: Monster tokens throw Polyglot errors #529
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Whenever you select a monster token with the Polyglot mod enabled, it emits at least one console error telling you that it can't find the actor's languages because
system.languages.valueis undefined. As far as I know it's basically harmless, but depending on what I'm doing it can spit hundreds or thousands of bright red error messages that make debugging a pain.This quick fix eliminates the spam by placing an empty array where Polyglot expects to find it: first by moving the template.json definition for the languages field from the PC actor type into the common template shared by both, then adding migration code to correct the behavior for old monsters.