You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TechHog edited this page May 21, 2026
·
12 revisions
Below is a list of known discrepancies between frostbyte and Roblox (excluding things that aren't planned or have yet to be implemented).
Please remember that frostbyte aims to strike a balance between a 1:1 clone and a complete redesign. The goal of this project is not to end up looking like a client decompilation, having exact underlying internal behavior, and all that really matters is that the Luau environment functions the same.
Note: If an item is checked, it means there are no plans to change it.
registry tables aren't 1:1 (we have more probably and the keys are all strings in frostbyte)
instancelookup table's key in the registry is not a function pointer (see above)
DataType member functions are cached in frostbyte (static function are cached in both)
Unsure items: (I am unsure as to whether we should change these things)
RunService BindToRenderStep functions in frostbyte have custom error messages regardless of whether the task scheduler has resumed the thread (basically, error"hi" in Roblox emits custom error message while task.wait();error"hi" does not, whereas in frostbyte both instances emit the custom error message)