XLua's MMF Functions not working in a built application

[Ibis]

I'm having an issue where once I actually build my application, a lot of scripts involving XLua break (particularly, any references to functions within MMF2 events can't be called). These work fine when I run the application as a test from inside MMF2.

I'd assume this is because of MMF2 not being able to locate the packages, but the .exe is in the same folder as the .mfa.

The following is included at the start of the "auto" script:

package.cpath = "./?.dll;./ext/?.dll"

require "mmfi"

but I get the impression I'm missing something really obvious.

E: specifically, the error says "attempt to call upvalue 'MMFFunction' (a nil value)

[Pixelthief]

Try taking the actual mmfi.dll and putting it in the same folder as your project, or a subfolder.
You should find mmfi.dll at your /multimedia fusion 2/dev/lib/mmfi.dll folder, along with any other prepackaged libraries

[Ibis]

It is there, nothing changes, which is why I'm baffled.

My other guess would be that I'm doing something wrong with the MMF Functions themselves but I haven't figured out what.

[Ibis]

Actually, it turns out that the script was confused every time I referred to an alterable value by its "MMF2 name" and not just mmf.ALT_A, etc.

Most of the MMF functions seem to work fine now too so I'm not sure why it was breaking those?

[Pixelthief]

When xlua encounters an error, it throws an error call and usually ceases to work from that point on, you expect everything else to fall apart unless you reset that instance. Some things might work, but those that depended on a failed script won't, its like that
You would benefit greatly by putting a debug string object somewhere in your frame, and using this simple line of code. This way whenever lua throws an error, it will become visible and tell you what line that error occurred on
You'll notice that if a script has syntax errors in it, it will throw an error when you try to load it