Luraph Compatibility Guide
MoonVeil provides a compatibility layer to support users which already use Luraph’s suite of Macros.
Many of Luraph’s macros do features or optimizations that are already built into MoonVeil. Though MoonVeil will still accept scripts which try to use these macros, they will have no effect. Below is a table of compatibility between Luraph and MoonVeil.
| Luraph Macro | MoonVeil Alias | Description |
|---|---|---|
LPH_ENCFUNC | MV_ENC_FUNC | Virtualizes and encrypts functions |
LPH_ENCSTR | MV_NO_OP | Not applicable |
LPH_ENCNUM | MV_NO_OP | Not applicable |
LPH_CRASH | MV_CRASH | Crashes the VM |
LPH_NO_VIRTUALIZE | MV_OMIT | Omits a function from all obfuscation steps |
LPH_JIT | MV_NO_OP | MoonVeil provides built-in optimizations |
LPH_JIT_MAX | MV_NO_OP | MoonVeil provides built-in optimizations |
LPH_NO_UPVALUES | MV_NO_OP | Not applicable |
LPH_LINE | MV_LINE | Current line number |
LPH_OBFUSCATED | MV_OBFUSCATED | Detects obfuscation |
MV_NO_OP isn’t user accessible, and is only used to provide source compatibility.A minor difference between Luraph and MoonVeil is that MoonVeil does not automatically virtualize your script (outside of the Virtualize Script option). Instead, you can selectively virtualize blocks using the MV_VM or MV_ENC_FUNC macros. This gives you much more control over the obfuscation process, enabling you to have much better performance.
Though you can use Luraph’s macros in MoonVeil, MoonVeil additionally provides many other macros which are not available in Luraph.