Skip to content

fix(kernel): update custom uint32 entity values - #174

Merged
nick2781 merged 2 commits into
mainfrom
fix/entity-custom-uint32
Oct 27, 2026
Merged

nick2781 merged 2 commits into
mainfrom
fix/entity-custom-uint32

Conversation

@nick2781

Copy link
Copy Markdown
Member

The public entity custom-uint32 setter always returned false, so fields could be created/read but never updated through their matching API.

Look up the existing field, reject missing or differently typed values without mutation, and call the existing unsigned storage setter for valid uint32 fields. Public signatures and layout remain unchanged. Update the Kernel reference in both languages.

Validation:

  • The new public-entity test failed on the unchanged stub, then passed with the fix.
  • Debug, Release and AddressSanitizer/UndefinedBehaviorSanitizer runs passed: 12 cases / 510 assertions each. Leak detection was disabled.
  • Actual Kernel/EntityOperations dynamic libraries verified 0 → UINT32_MAX → 0 on four players and preserved an existing signed value after rejection.
  • 157 policy tests, clang-format 18 and Nimbus passed; affected canonical HTML and Markdown were checked.

The branch is normally synchronized with accepted main #172. No other placeholder API, schema, serializer or ownership behavior is changed. Hosted checks remain separate from these local results.

@nick2781
nick2781 added this pull request to the merge queue Oct 27, 2026
Merged via the queue into main with commit ebacf07 Oct 27, 2026
6 checks passed
@nick2781
nick2781 deleted the fix/entity-custom-uint32 branch October 27, 2026 03:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant