[BUG FIX] Fix regressions which made it nearly impossible to obfuscate scripts without using LuaJIT.#237
Conversation
…Integrity Fix to satisfy safety guardrails Non-LuaJIT clients, and fix 'random' obfuscation failures), also fixed Scientific notation causing a large amount of errors when once again, not using LuaJIT. Prometheus is once again Lua Client Agnostic.
ghost
changed the title
Author
|
please update me on when this is pushed |
ghost
closed this by deleting the head repository
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added
math.log10&loadstringpolyfills to support the NumbersToExpressions integrity fix.Fixes that restore Prometheus to a Client-Agnostic state:
And finally, a new test was added to ensure that there isn't any so called 'random' regressions from NumbersToExpressions again.
It is unfortunate this issue went unnoticed for so long, as I only looked in the Discord today to see multiple people facing the same issue. The new test ensures this won't happen again!