Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] type(nil) is seemingly broken when obfuscating #51

Closed
dragonbane0 opened this issue May 6, 2022 · 4 comments
Closed

[BUG] type(nil) is seemingly broken when obfuscating #51

dragonbane0 opened this issue May 6, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@dragonbane0
Copy link

Describe the bug
As mentioned in #44, I finally tracked down the issue I was having with one of my script functions breaking as soon as Vmify, ProxifyLocals or both are used. Seems the issue is that type(nil) currently produces an error when used. So if you, for example, try to get the type of a table member that is nil, you get a non working script.

Expected behavior
type(nil) should be properly implemented when obfuscating.

To Reproduce
Adding a simple local nilType = type(nil) seems to break the function of my script immediately as soon as obfuscation options are used.

Additional context
Lua 5.1

@dragonbane0 dragonbane0 added the bug Something isn't working label May 6, 2022
@Brohammer5
Copy link
Contributor

Try instead of using type(nil), try just nil or make the variable without value so by default it is nil

@dragonbane0
Copy link
Author

Just nil doesn't produce any issues. For now I can work around it by simply checking if a variable is nil first before trying to check its type, but it's still a bug in the obfuscator right now, so it should be mentioned

@Brohammer5
Copy link
Contributor

Issue seems to be around 340 when ( Beautified)while Obsfucated
This line of code
(Pu .. "rpb")(B[string[(Gu / "A").l(-18003)]])

@levno-710
Copy link
Member

Fixed in upcoming version v0.2

@levno-710 levno-710 added the waiting for release The issue has been fixed, but the fix is not included in the current release. label May 7, 2022
@levno-710 levno-710 reopened this May 15, 2022
@levno-710 levno-710 removed the waiting for release The issue has been fixed, but the fix is not included in the current release. label May 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants