Common Errors

Extra (trailing) commas

Trailing commas occur whenever a comma is added after a piece of code that has nothing following, in which JSONS are unable to read the rest of the code and throw errors out. Some examples of trailing commas include:

To fix trailing commas, a good start is to copy what you have added/edited and paste it into https://jsonlint.com/. The tool checks if there are any fancy characters (non-ASCII), trailing commas, or missing commas, then directs you and what to remove/add.

Missing commas

Missing commas occur whenever a comma separating two "keys-values" is deleted or left off, leaving the JSON unable to fully read the code. Some examples include:

To fix missing commas, a good start is to copy what you have added/edited and paste it into https://jsonlint.com/. As previously mentioned, the tool checks if there is any issues within the JSON, and notifies if there is any.

Non-ASCII characters

Non-ASCII characters (characters not in the American Standard Code for Information Interchange) are often due to fancy quotation marks (“”) or misplaced characters. Some examples include:

To fix or identify non-ASCII characters, a good place to start is to copy what you have added/edited and paste it into https://jsonlint.com/. As previously mentioned, the tool checks if there are any issues within the JSON, and notifies if there is any.

Error2

With the creation of a pronoun system, all new events going into the official developmental version of ClanGen should be pronoun and verb tagged beforehand, just to make the transition smoother. If, while editing or adding new thoughts to any of the jsons, you boot up the game and notice your thought shows "error2" in place of a pronoun or verb, then there was a misspelling or mis-formatting of the code.

Pronoun tags

Pronoun tags are the code replacements for singular they/them within the text, as it sets up a framework for custom pronouns to be used instead of ClanGen relying on being gender neutral within the text. The pronouns are represented by {PRONOUN/cat/pronoun}, with cat representing any acronym that can be replaced by a cats name (m_c, r_c, p_l, s_c, etc) and pronoun representing the type of pronouns used (subjective, objective, possessive, etc). If the code was to get messed up in any way (IE misspelling subjective, or doing r_l), then it creates an error2 message within the thought.

The best ways to fix this is to first, double check that all the pronouns are properly tagged and rely on copy and pasting the actual filled out versions of the code, or to copy and paste your code into ClanGen Pronoun Tag Tester (cgen-tools.github.io), which will show if the thought has an error in the tagging and makes sense given different pronouns

Verb tags

Verb tags, much similar to pronoun tags, serve to procedurally change verbs to match a cat's chosen pronoun. In ClanGen, they/them is used both singular and plural, thus the text uses verbs that make sense grammatically (are instead of is, were instead of was, or have instead of has), however custom pronouns will need their specific verbs. Consequently, verbs that need to be changed when pronouns are changed, are replaced with {VERB/cat/plural/singular}; cat representing any acronym that can be replaced by a cats name (m_c, r_c, p_l, etc) while plural/singular represent the versions of the verb.

The best ways to fix this is to first, double check that all the pronouns are properly tagged and rely on copy and pasting the actual filled out versions of the code ( {VERB/cat/plural/singular} ), or to copy and paste your code into ClanGen Pronoun Tag Tester (cgen-tools.github.io), which will show if the thought has an error in the tagging and makes sense given different pronouns