Fixes:
- Aggressively specialize lists generated by NbtSerializer.Sequence to fix deserialization of types like UUID which expect a specialized NBT array type (#363, Blodhgarm)
Fixes
- Aggressively specialize lists generated by
NbtSerializer.Sequenceto fix deserialization of types likeUUIDwhich expect a specialized NBT array type (#363, Blodhgarm)
Deal with issues involving recent changes to neos reload listeners changes
Changes
- Tooltip rendering on the owo-ui screen template classes can now be customized by overriding
drawComponentTooltip
Fixes
- owo-ui screens built using the provided template classes no longer stop rendering their tooltip after reinitializing (#314, Blodhgarm)
Changes
- Updated to 1.21.4
- The tooltip of the UI managed by an OwoUIAdapter is no longer drawn directly inside the adapter's render method. Instead, the separate drawTooltip method must be invoked after rendering, allowing tooltips to be rendered definitively after all main UI
Fixes
- owo-ui tooltips in screens with layers should no longer stack with main UI incorrectly
- Endec encoding and decoding of optional fields in NBT has been fixed
Changes
- Updated to 1.21.4
- The tooltip of the UI managed by an
OwoUIAdapteris no longer drawn directly inside the adapter's render method. Instead, the separatedrawTooltipmethod must be invoked after rendering, allowing tooltips to be rendered definitively after all main UI
Fixes
- owo-ui tooltips in screens with layers should no longer stack with main UI incorrectly
- Endec encoding and decoding of optional fields in NBT has been fixed
Update to fix issues where networking would only register within debug environment.
Removes final bit of renderdoc code
Update to 1.21.3 which brings less of a reliance on FFAPI and disabled RenderDoc utility to use neos RenderNurse within the future
Disable RenderDoc Utils to be replaced with Neos RenderNurse
Fix issues with config screens being non existant though mod info screen
Fixes
TextureComponentrendering now works properly again
Fix issues where during a ModLoading error, owolib would be blamed for Shader loading issues due to neos continuation of general asset loading
Changes
- As a consequence of updating the endec library, the signatures of the
field(...)methods on(De)Serializer.Structhave changed to accomodate the new optional flattening methodology. If this causes trouble, contact us and we'll try to help
Fixes
- Optional struct fields should now always encode properly in self-described formats (namely JSON and NBT)
Update version to be consistent with maven
Primarily, this release constitutes the first port of owo-lib to 1.21.2/3. There were however also a number of other changes:
Additions
CodecUtilsnow offers theeitherStructEndec(...)andxorStructEndec(...)methods for creating either/xor endecs which conform to theStructEndecinterface- The endec builder used for serializing owo-config options over the network can now be customized in the
ConfigWrapperconstructor
Changes
- As a consequence of the vanilla changes to item and block registration, the
AutoRegistryContainerAPI is deprecated for the moment and might be (partially) removed in a future release. We're investigating potential alternatives - Which owo-ui components are used for the exclusion areas provided to REI and EMI can now be customized by overriding
BaseOwoHandledScreen#componentsForExclusionAreas()
Fixes
BaseOwoHandledScreen#enableSlot(Slot)no longer incorrectly disables the slot
Fixes issues with Concurrent Modification Exception with FFAPI networking
Initial Release of owo for Neoforge. Yippie!
Changes / Fixes
This release fundamentally changes the implementation used for Endec/Codec interop. Instead of always using EDM as the intermediary format, the framework will now try to determine if a format-appropriate (De)Serializer/DynamicOps implementation is available and use it if so. This means that the serialized representation of all data structures should now be both consistent and preserved correctly when in complex nested scenarios, something we hope will alleviate an entire class of bugs. Most of these are related to serialized EDM which turns out unrepresentable in NBT, but other formats might have been affected too



