FrozenLib

• Added Fire Types.
  • Fire Types control the amount of damage an entity will take and the textures to use while on fire.
  • A data-driven registry is used to create Fire Types:
    • blocks: An ID, a list of IDs, or a tag of Blocks that correspond to the Fire Type. (e.g., Fire and Campfire)
    • damage: The amount of damage the Fire Type will inflict.
    • spreads_from_zombie: Whether the Fire Type can be spread from Zombie attacks.
    • spreads_from_ignite_enchantments: Whether the Fire Type can be spread from Enchantments that ignite entities.
    • replaceable: Whether this Fire Type can be overriden by another upon contact.
    • texture_0: The first Fire overlay texture.
    • texture_1: The second Fire overlay texture, also used in first-person view.
• Added the frozenlib:default_fire_blocks Block Tag, containing the Fire and Campfire blocks by default.
• Added the frozenlib:soul_fire_blocks Block Tag, which is empty by default.

• Added the itemToPatternMappings method to DecoratedPotPatternRegistryEntrypoint.
  • Removed SherdRegistry.
• Added the frozenlib:scares_piglin Entity Type tag.
• Added the frozenlib:blazes Entity Type tag.
• Added the frozenlib:hoglins Entity Type tag.
• Added the frozenlib:ghost_like Entity Type tag.
• Fixed a critical issue that prevented DataFixing from working as intended.
• Cleaned up the implementation of multiple DataFixer helpers.

• Fixed a critical issue that prevented DataFixing from working as intended.
• Cleaned up the implementation of multiple DataFixer helpers.

• Restored modmenu-specific features.

• Restored modmenu-specific features.

• Fixed the structure_upgrade command.

Server Textures

• ServerTextures now support .jpeg files!
  • Files ending in .mcphoto will also be treated as .jpeg files.
  • All methods pertaining to finding files for ServerTextures will no longer work if a file extension is included in the fileName parameter.
    • Instead, an automatic search has been added which looks for matching file names, ending in the .png, .jpeg, and .mcphoto extensions respectively.
    • When a match is found, it will be read.
• FileTransferPackets now require a list of file extensions for requests.
  • This lets modders request files that could have a different file extension (e.g., photos ending in .png or .jpeg.)
  • Transfers are untouched, and still require the file extension to be part of the fileName parameter.
    • Please refrain from using the fileExtensions parameter when sending transfers, only use it for requests.
• Updated the whitelisted file extensions for file requests and transfers.
  • .png, .jpeg, .mcphoto, .json.
• Fixed a bug that could occur when running a dedicated server from the same directory a client is running from, which is connected to the dedicated server.
  • ServerTextures would continuously request their texture file while the server would continuously send it, resulting in the file being constantly rewritten and never read as a texture.
• Added BuiltInBlockModelRegistry, helping modders register their own built-in Block models.

Added the brand new Config V2!

The goal of Config V2 is to substantially improve performance, memory usage, and network usage overall, while maintaining FrozenLib's unique config features.

Multiple issues that would result in players being kicked, crashing, or experiencing lag have all been fixed.

Config Entries

• Contain an id, Entry Type, default value, and properties.
• The id is used for naming the Entry.
  • Entry names can be anything you'd like, with / being used as a way to "nest" entries.
  • For example, "test/sectionA/1" and "test/sectionA/2" would both be encoded to and parsed from an array in the config file, namely "sectionA".
  • However, an Entry with the id "test/sectionB/1" would be nested in its own array, "sectionB".
  • Nesting can occur recursively.
  • Do note that giving an Entry the same name as a nest array will cause issues, please avoid doing so.
• The Entry Type is a new class, providing a Codec and Stream Codec for the Entry to use.
  • Config entries are now encoded and decoded with codecs, opposed to writing present data to a file and hoping the encode/decode will return the anticipated result.
  • As a result of this, it is now possible to use much more complex classes in configs without issues.
  • Stream codecs are now used for config syncing, instead of sending the entire config file over the network.
    • This both significantly improves network performance and also cuts down on packet sizes tremendously, eliminating an edge-case that could kick players.
• The default value is of course, the default value the Entry will use when unchanged.
• Entry properties contain a few fields to control the behavior of an Entry.
  • The syncable field determines whether the Entry is able to sync between clients and servers.
  • The modifiable field determines whether the config modification system can be used on the Entry.
  • The comment field provides an optional comment that can be saved alongside the Entry.
    • Depending on the file type used, this will be saved either as:
      • An array containing the Entry's value and the comment.
      • A comment, not affecting the file's structure.
  • The visibilityPredicate field is optional, and determines whether the entry will be accessible in the config screen (only implemented for Cloth Config).
  • The textSupplier field is optional, and determines what text should be used for the entry's values in the config screen (only implemented for Cloth Config).
  • The requireRestart field is optional, and determines whether the entry will prompt Cloth Config's restart screen.

Config Data

• Config Data provides the base id for all config entries, as well as the file path to save the config file to.
• Config Entries are created using an existing Config Data instance.
  • This is done to ensure Entries can be saved to their respective files, and won't get mixed up or lost.
• Config Settings are provided, determining what file type to use for the config.

• ServerTextures now support .jpeg files!
  • Files ending in .mcphoto will also be treated as .jpeg files.
  • All methods pertaining to finding files for ServerTextures will no longer work if a file extension is included in the fileName parameter.
    • Instead, an automatic search has been added which looks for matching file names, ending in the .png, .jpeg, and .mcphoto extensions respectively.
    • When a match is found, it will be read.
• FileTransferPackets now require a list of file extensions for requests.
  • This lets modders request files that could have a different file extension (e.g., photos ending in .png or .jpeg.)
  • Transfers are untouched, and still require the file extension to be part of the fileName parameter.
    • Please refrain from using the fileExtensions parameter when sending transfers, only use it for requests.
• Updated the whitelisted file extensions for file requests and transfers.
  • .png, .jpeg, .mcphoto, .json.
• Fixed a bug that could occur when running a dedicated server from the same directory a client is running from, which is connected to the dedicated server.
  • ServerTextures would continuously request their texture file while the server would continuously send it, resulting in the file being constantly rewritten and never read as a texture.
• Added BuiltInBlockModelRegistry, helping modders register their own built-in Block models.

• ServerTextures now support .jpeg files!
  • Files ending in .mcphoto will also be treated as .jpeg files.
  • All methods pertaining to finding files for ServerTextures will no longer work if a file extension is included in the fileName parameter.
    • Instead, an automatic search has been added which looks for matching file names, ending in the .png, .jpeg, and .mcphoto extensions respectively.
    • When a match is found, it will be read.
• FileTransferPackets now require a list of file extensions for requests.
  • This lets modders request files that could have a different file extension (e.g., photos ending in .png or .jpeg.)
  • Transfers are untouched, and still require the file extension to be part of the fileName parameter.
    • Please refrain from using the fileExtensions parameter when sending transfers, only use it for requests.
• Updated the whitelisted file extensions for file requests and transfers.
  • .png, .jpeg, .mcphoto, .json.
• Fixed a bug that could occur when running a dedicated server from the same directory a client is running from, which is connected to the dedicated server.
  • ServerTextures would continuously request their texture file while the server would continuously send it, resulting in the file being constantly rewritten and never read as a texture.
• Added BuiltInBlockModelRegistry, helping modders register their own built-in Block models.

• ServerTextures now support .jpeg files!
  • Files ending in .mcphoto will also be treated as .jpeg files.
  • All methods pertaining to finding files for ServerTextures will no longer work if a file extension is included in the fileName parameter.
    • Instead, an automatic search has been added which looks for matching file names, ending in the .png, .jpeg, and .mcphoto extensions respectively.
    • When a match is found, it will be read.
• FileTransferPackets now require a list of file extensions for requests.
  • This lets modders request files that could have a different file extension (e.g., photos ending in .png or .jpeg.)
  • Transfers are untouched, and still require the file extension to be part of the fileName parameter.
    • Please refrain from using the fileExtensions parameter when sending transfers, only use it for requests.
• Updated the whitelisted file extensions for file requests and transfers.
  • .png, .jpeg, .mcphoto, .json.
• Fixed a bug that could occur when running a dedicated server from the same directory a client is running from, which is connected to the dedicated server.
  • ServerTextures would continuously request their texture file while the server would continuously send it, resulting in the file being constantly rewritten and never read as a texture.
• Added BuiltInBlockModelRegistry, helping modders register their own built-in Block models.

• ServerTextures now support .jpeg files!
  • Files ending in .mcphoto will also be treated as .jpeg files.
  • All methods pertaining to finding files for ServerTextures will no longer work if a file extension is included in the fileName parameter.
    • Instead, an automatic search has been added which looks for matching file names, ending in the .png, .jpeg, and .mcphoto extensions respectively.
    • When a match is found, it will be read.
• FileTransferPackets now require a list of file extensions for requests.
  • This lets modders request files that could have a different file extension (e.g., photos ending in .png or .jpeg.)
  • Transfers are untouched, and still require the file extension to be part of the fileName parameter.
    • Please refrain from using the fileExtensions parameter when sending transfers, only use it for requests.
• Updated the whitelisted file extensions for file requests and transfers.
  • .png, .jpeg, .mcphoto, .json.
• Fixed a bug that could occur when running a dedicated server from the same directory a client is running from, which is connected to the dedicated server.
  • ServerTextures would continuously request their texture file while the server would continuously send it, resulting in the file being constantly rewritten and never read as a texture.

Added the brand new Config V2!

The goal of Config V2 is to substantially improve performance, memory usage, and network usage overall, while maintaining FrozenLib's unique config features.

Multiple issues that would result in players being kicked, crashing, or experiencing lag have all been fixed.

Config Entries

• Contain an id, Entry Type, default value, and properties.
• The id is used for naming the Entry.
  • Entry names can be anything you'd like, with / being used as a way to "nest" entries.
  • For example, "test/sectionA/1" and "test/sectionA/2" would both be encoded to and parsed from an array in the config file, namely "sectionA".
  • However, an Entry with the id "test/sectionB/1" would be nested in its own array, "sectionB".
  • Nesting can occur recursively.
  • Do note that giving an Entry the same name as a nest array will cause issues, please avoid doing so.
• The Entry Type is a new class, providing a Codec and Stream Codec for the Entry to use.
  • Config entries are now encoded and decoded with codecs, opposed to writing present data to a file and hoping the encode/decode will return the anticipated result.
  • As a result of this, it is now possible to use much more complex classes in configs without issues.
  • Stream codecs are now used for config syncing, instead of sending the entire config file over the network.
    • This both significantly improves network performance and also cuts down on packet sizes tremendously, eliminating an edge-case that could kick players.
• The default value is of course, the default value the Entry will use when unchanged.
• Entry properties contain a few fields to control the behavior of an Entry.
  • The syncable field determines whether the Entry is able to sync between clients and servers.
  • The modifiable field determines whether the config modification system can be used on the Entry.
  • The comment field provides an optional comment that can be saved alongside the Entry.
    • Depending on the file type used, this will be saved either as:
      • An array containing the Entry's value and the comment.
      • A comment, not affecting the file's structure.
  • The visibilityPredicate field is optional, and determines whether the entry will be accessible in the config screen (only implemented for Cloth Config).
  • The textSupplier field is optional, and determines what text should be used for the entry's values in the config screen (only implemented for Cloth Config).
  • The requireRestart field is optional, and determines whether the entry will prompt Cloth Config's restart screen.

Config Data

• Config Data provides the base id for all config entries, as well as the file path to save the config file to.
• Config Entries are created using an existing Config Data instance.
  • This is done to ensure Entries can be saved to their respective files, and won't get mixed up or lost.
• Config Settings are provided, determining what file type to use for the config.

Added the brand new Config V2!

The goal of Config V2 is to substantially improve performance, memory usage, and network usage overall, while maintaining FrozenLib's unique config features.

Multiple issues that would result in players being kicked, crashing, or experiencing lag have all been fixed.

Config Entries

• Contain an id, Entry Type, default value, and properties.
• The id is used for naming the Entry.
  • Entry names can be anything you'd like, with / being used as a way to "nest" entries.
  • For example, "test/sectionA/1" and "test/sectionA/2" would both be encoded to and parsed from an array in the config file, namely "sectionA".
  • However, an Entry with the id "test/sectionB/1" would be nested in its own array, "sectionB".
  • Nesting can occur recursively.
  • Do note that giving an Entry the same name as a nest array will cause issues, please avoid doing so.
• The Entry Type is a new class, providing a Codec and Stream Codec for the Entry to use.
  • Config entries are now encoded and decoded with codecs, opposed to writing present data to a file and hoping the encode/decode will return the anticipated result.
  • As a result of this, it is now possible to use much more complex classes in configs without issues.
  • Stream codecs are now used for config syncing, instead of sending the entire config file over the network.
    • This both significantly improves network performance and also cuts down on packet sizes tremendously, eliminating an edge-case that could kick players.
• The default value is of course, the default value the Entry will use when unchanged.
• Entry properties contain a few fields to control the behavior of an Entry.
  • The syncable field determines whether the Entry is able to sync between clients and servers.
  • The modifiable field determines whether the config modification system can be used on the Entry.
  • The comment field provides an optional comment that can be saved alongside the Entry.
    • Depending on the file type used, this will be saved either as:
      • An array containing the Entry's value and the comment.
      • A comment, not affecting the file's structure.
  • The visibilityPredicate field is optional, and determines whether the entry will be accessible in the config screen (only implemented for Cloth Config).
  • The textSupplier field is optional, and determines what text should be used for the entry's values in the config screen (only implemented for Cloth Config).
  • The requireRestart field is optional, and determines whether the entry will prompt Cloth Config's restart screen.

Config Data

• Config Data provides the base id for all config entries, as well as the file path to save the config file to.
• Config Entries are created using an existing Config Data instance.
  • This is done to ensure Entries can be saved to their respective files, and won't get mixed up or lost.
• Config Settings are provided, determining what file type to use for the config.

Added the brand new Config V2!

The goal of Config V2 is to substantially improve performance, memory usage, and network usage overall, while maintaining FrozenLib's unique config features.

Multiple issues that would result in players being kicked, crashing, or experiencing lag have all been fixed.

Config Entries

• Contain an id, Entry Type, default value, and properties.
• The id is used for naming the Entry.
  • Entry names can be anything you'd like, with / being used as a way to "nest" entries.
  • For example, "test/sectionA/1" and "test/sectionA/2" would both be encoded to and parsed from an array in the config file, namely "sectionA".
  • However, an Entry with the id "test/sectionB/1" would be nested in its own array, "sectionB".
  • Nesting can occur recursively.
  • Do note that giving an Entry the same name as a nest array will cause issues, please avoid doing so.
• The Entry Type is a new class, providing a Codec and Stream Codec for the Entry to use.
  • Config entries are now encoded and decoded with codecs, opposed to writing present data to a file and hoping the encode/decode will return the anticipated result.
  • As a result of this, it is now possible to use much more complex classes in configs without issues.
  • Stream codecs are now used for config syncing, instead of sending the entire config file over the network.
    • This both significantly improves network performance and also cuts down on packet sizes tremendously, eliminating an edge-case that could kick players.
• The default value is of course, the default value the Entry will use when unchanged.
• Entry properties contain a few fields to control the behavior of an Entry.
  • The syncable field determines whether the Entry is able to sync between clients and servers.
  • The modifiable field determines whether the config modification system can be used on the Entry.
  • The comment field provides an optional comment that can be saved alongside the Entry.
    • Depending on the file type used, this will be saved either as:
      • An array containing the Entry's value and the comment.
      • A comment, not affecting the file's structure.
  • The visibilityPredicate field is optional, and determines whether the entry will be accessible in the config screen (only implemented for Cloth Config).
  • The textSupplier field is optional, and determines what text should be used for the entry's values in the config screen (only implemented for Cloth Config).
  • The requireRestart field is optional, and determines whether the entry will prompt Cloth Config's restart screen.

Config Data

• Config Data provides the base id for all config entries, as well as the file path to save the config file to.
• Config Entries are created using an existing Config Data instance.
  • This is done to ensure Entries can be saved to their respective files, and won't get mixed up or lost.
• Config Settings are provided, determining what file type to use for the config.

• Added pushable Block Entities!
  • Blocks within the frozenlib:has_pushable_block_entity block tag that have a Block Entity will now be pushable.
  • The models of Block Entities will render whilst being pushed.
  • Please note this feature cannot be considered stable, so do not expect to be able to add just any Block to the tag without possible side-effects.

• Added pushable Block Entities!
  • Blocks within the frozenlib:has_pushable_block_entity block tag that have a Block Entity will now be pushable.
  • The models of Block Entities will render whilst being pushed.
  • Please note this feature cannot be considered stable, so do not expect to be able to add just any Block to the tag without possible side-effects.

• Added pushable Block Entities!
  • Blocks within the frozenlib:has_pushable_block_entity block tag that have a Block Entity will now be pushable.
  • The models of Block Entities will render whilst being pushed.
  • Please note this feature cannot be considered stable, so do not expect to be able to add just any Block to the tag without possible side-effects.

• Added pushable Block Entities!
  • Blocks within the frozenlib:has_pushable_block_entity block tag that have a Block Entity will now be pushable.
  • The models of Block Entities will render whilst being pushed.
  • Please note this feature cannot be considered stable, so do not expect to be able to add just any Block to the tag without possible side-effects.

• Added pushable Block Entities!
  • Blocks within the frozenlib:has_pushable_block_entity block tag that have a Block Entity will now be pushable.
  • The models of Block Entities will render whilst being pushed.
  • Please note this feature cannot be considered stable, so do not expect to be able to add just any Block to the tag without possible side-effects.