[feature] Being Able To Export Metatables

[5m1Ly]

I created this post in addition to this bug report.

[lua] auto reset of metamethods when exporting table

The problem Like many of us know we can create exports for a resource and call these within an other resource. This way you can easly share functionallity across resources without having to rewrite logic. This is very usefull in many cases, there is only one problem i’m constantly figthing with, this is exporting the metamethods of a table in lua. Metatables in lua are tables that contain a set of functionallity (also called metamethods), which are used to define the opperational logic of a tab…

Current State

So as shown in the bug report that i made a while back. I’ts not possible to export a MetaTable, according to d-bubble this is because MetaTables don’t exist in JavaScript and C#, just like Classes that don’t exist in Lua.

Feature Request

So this topic was created to ask if it would be possible to do a language check, meaning that if you export a MetaTable in a Lua file and that call this export in the Lua file that the MetaTable remains and otherwise it becomes an Array or Object Notation.

[xander1998]

I have a small workaround for this. If you load the class as a script you can set the data sent over the export and add the meta tables back on the data after it is passed.