Cyanide

Cyanide Initial Release

Full feature list:

World Generation Data Pack Error Improvements

• Append the file to each error message. (at: file "data/cyanide/blah/blah.json")
• Append the source datapack to each error message (at: data pack blah.zip)
• Group and categorize errors by registry.
• Several improvements for error recovery:
  • If an error occurs during a single registry parsing, don't abort parsing others.
  • Record all errors that occur parsing a single registry, not just the first one.
• Optional fields, in some cases, will error if a value is present, but invalid. Example:

``` In a biome json, the following is a valid temperature modifier. It is the same as using a temperature modifier of 'none'. In Cyanide, this would error.

"temperature_modifier": "hocus pocus!" ```

• Improvements for select codecs, which now report trace information to identify where in the file an error occurred.
  • Features in biomes identify both the index in the list, and the index as a generation step.
  • Other fields such as carvers, surface_builder, etc. in biomes will be traced in error messages.
• Removed the Feature: Not a JSON Object log messages. These are now upgraded to full errors.
• Some fields, such as biome categories, temperature modifiers, and precipitations, have slightly improved error messages and will also show the range of valid values. Example:

Unknown category name: not_a_category, expected one of [none, taiga, extreme_hills, jungle, mesa, plains, savanna, icy, the_end, beach, forest, ocean, desert, river, swamp, mushroom, nether, underground] at: file "data/cyanide/worldgen/biome/invalid_category.json" at: data pack test_data_pack.zip

• Improvements for log messages for invalid loot tables and recipes:
  • Stack traces are not printed to the log.
  • Offending file names are identified and printed instead.
• The "Loaded X Recipe(s)" log message is now accurate.