You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current JSON parser supports using // to make the comments; however, because the // syntax isn't supported in all JSON parsers, most people prefer using a "__comment" key (As in, "__comment": "...").
Currently, this causes an error when used in InControl configuration files
Example:
[
{
"__comment": "Example: Prevent enderman from spawning in the overworld for some reason that might not be obvious",
"dimension": "minecraft:overworld",
"mob": "minecraft:enderman",
"result": "deny"
}
]
This change would only apply to keys prefixed with one or two underscores, so other invalid keys would still raise errors
Example:
[
{
"mob": "minecraft:zombie",
"comment": "This will raise an error since it's not prefixed with an underscore",
"__comment_1": "Someone in the process of balancing may add __ to the start of a key to temporarily comment it out",
"__healthmultiply": 4,
"healthmultiply": 3,
"__comment_2": "Because 'when' is misspelled here, you'll still get an error because it doesn't have two underscores to prefix it, this change won't affect that""wehn": "onjoin"
}
]
The text was updated successfully, but these errors were encountered:
The current JSON parser supports using
//
to make the comments; however, because the//
syntax isn't supported in all JSON parsers, most people prefer using a"__comment"
key (As in,"__comment": "..."
).Currently, this causes an error when used in InControl configuration files
Example:
This change would only apply to keys prefixed with one or two underscores, so other invalid keys would still raise errors
Example:
The text was updated successfully, but these errors were encountered: