v5.4.0

Version 5.4.0:

Updated to 1.20.3

see full changelog here

v5.3.0

Version 5.3.0:

Updated to 1.20.2

Additions

• Added load- and unload-aware components as an experimental feature
  • This can be used to implement advanced initialization and cleanup 🧽

Changes

• Deprecated the utils package in cardinal-components-block as it is now virtually unusable

see full changelog here

v5.2.2

Version 5.2.2:

Fixed chunk components being lost during deserialization (thanks to Stuff-Stuffs !)

see full changelog [here](https://github.com//Cardinal Components Api/blob/5.2.2/changelog.md "Changelog")

v5.2.1

Version 5.2.1:

Fixed compatibility with full 1.20 release

see full changelog here

v5.1.0

Version 5.1.0:

Updated to MC 1.19.3

see full changelog here

v5.0.2

Version 5.0.2:

• Fix world components not synchronizing on load

see full changelog here

v5.0.1

Version 5.0.1:

Fixes

• Fixed components ticking only on subclasses of the block entities they were declared for
  (e.g. if a ticking component got attached to ChestBlockEntity, it would only tick on TrappedChestBlockEntity)

see full changelog here

v5.0.0

Version 5.0.0:

Updated to MC 1.19

Additions

• Component providers now expose the ComponentAccess interface through Loom's interface injection
  • ComponentAccess adds getComponent as an alternative to ComponentKey#get, and syncComponent as an alternative to ComponentKey#sync
  • It is now recommended to use e.g. entity.getComponent(KEY) instead of KEY.get(entity), as this enforces type checking

see full changelog here

v4.2.0

Version 4.2.0:

Additions

• Players can now set the log-deserialization-warnings option to toggle warnings when a component fails to be resolved
  (typically due to mods being removed)

Mod Compatibility

• Fixed incompatibility with Immersive Portals

see full changelog here

v5.0.0-beta.1

Version 5.0.0:

Updated to MC 1.19

Additions

• Component providers now expose the ComponentAccess interface through Loom's interface injection
  • ComponentAccess adds getComponent as an alternative to ComponentKey#get, and syncComponent as an alternative to ComponentKey#sync
  • It is now recommended to use e.g. entity.getComponent(KEY) instead of KEY.get(entity), as this enforces type checking

see full changelog here