How is this a bug report, or even a bug in the first place?
Again, this has been discussed many times and nothing implies that serialization somehow retains metatables, and implementing any such functionality is non-trivial (as other scripting runtimes would not even know the concept of ‘metatables’).
- Exports does not return metatable attached to the table · Issue #802 · citizenfx/fivem · GitHub (comments)
- [HELP] Resources can't share objects - #11 by nta
- Exporting a class between two resources - #5 by nta
One of these posts also discusses an easy workaround to ‘export’ a class-like object using wrappers/closures, and it would be possible fine to make code to automate such exports.
I’ll in fact directly cite a relevant part from a post nearby: