v1.10.6
Full Changelog: v1.10.5...v1.10.6
perf/refactor: value-based IDs for better change handling
Before, instance IDs were stored as a simple [key] = value
on the instance, now it uses an “id” key with ClassLib.SetValue
to allow easier
ID change catches
I first planned to create proxies for __index
and __nexindex
metamethods on the instance metatable, but after some thought I came to the conclusion that it would consume more by catching changes this way
The upside is that scripters have more control over ID overrides, which can be useful in (very) special use cases
The downside is that scripters can cause chaos if they call object:SetValue("id", something)
without knowing what they're doing