v4.1.4

Version 4.1.4:

Updated to 1.18.2

see full changelog here

v4.1.3

Version 4.1.3:

Additions

• Added mod icons

Fixes

• Fixed chunk components serialization

see full changelog here

v4.1.2

Version 4.1.1:

Fixes
Fixed modded ComponentProvider subclasses (as in, custom entities) on newer loom versions

see full changelog here

v4.1.1

Version 4.1.1:

Fixes
Fixed modded ComponentProvider subclasses (as in, custom entities) on newer loom versions

see full changelog here

v4.1.0

Version 4.1.0:

Now available on modrinth!

Changes

• Changed the maven group from io.github.onyxstudios.Cardinal-Components-API to dev.onyxstudios.cardinal-components-api

Fixes

• Fixed curseforge upload

see full changelog here

v4.0.1

Version 4.0.1:

Fixes

• Fixed cardinal-components-chunk crashing at launch
• Fixed components not being saved when bucketing entities

see full changelog here

v4.0.0

Version 4.0.0:

Updated to 1.18

Removed

• Removed serializable item components
  • Item components must now save all their data in the stack NBT
  • Consider switching to API Lookup API where possible
• Removed the cardinal-components-util module
  • According to Github no one ever used it, but if you did, and you see no currently available alternative, please open an issue

see full changelog here

v4.0.0-alpha.1+21w37a

Version 4.0.0:

Alpha 1

Updated to 21w37a

Removed

• Removed serializable item components
  • Item components must now save all their data in the stack NBT
  • Consider switching to API Lookup API where possible
• Removed the cardinal-components-util module
  • According to Github no one ever used it, but if you did and you see no currently available alternative, please open an issue

see full changelog here

v3.1.1

Version 3.1.1:

Fixes

• Fixed explicit component ordering being ignored during registration

Changes

• Deprecated the cardinal-components-util module for future removal

see full changelog here

v3.1.0

Version 3.1.0:

Additions

• Added an experimental way to order entity and BE components through Registration#after(ComponentKey)
  • This allows mods to ensure components are deserialized/synchronized/ticked in the right order if needed
  • Components that are not ordered through this mechanism will keep their registration ordering

see full changelog here