specify key requirements
This commit is contained in:
parent
2d72f4e86d
commit
6c07144978
@ -9,7 +9,7 @@ lastmod: "2025-05-01T18:47:58-05:00"
|
||||
|
||||
`declare function MV_ENC_FUNC<A..., R...>(vmFunction: (A...) -> R..., encryptKey: string, decryptKey: string): (A...) -> R...`
|
||||
|
||||
will virtualize and encrypt the passed function constant with the provided `encryptKey`. Then `decryptKey` is evaluated at runtime to grab the key.
|
||||
will virtualize and encrypt the passed function constant with the provided `encryptKey`. Then `decryptKey` is evaluated at runtime to grab the key. There are no restrictions on the length or the allowed characters of the keys, only that they are the same.
|
||||
|
||||
## Valid Usage
|
||||
```lua
|
||||
|
@ -9,7 +9,7 @@ lastmod: "2025-05-01T18:47:58-05:00"
|
||||
|
||||
`declare function MV_ENC_STR(str: string, encryptKey: string, decryptKey: string): string`
|
||||
|
||||
will encrypt the passed string constant with the provided `encryptKey`. Then `decryptKey` is evaluated at runtime to grab the key.
|
||||
will encrypt the passed string constant with the provided `encryptKey`. Then `decryptKey` is evaluated at runtime to grab the key. There are no restrictions on the length or the allowed characters of the keys, only that they are the same.
|
||||
|
||||
## Valid Usage
|
||||
```lua
|
||||
|
Loading…
x
Reference in New Issue
Block a user