You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
When running an Expression2 script with @strict enabled, an undefined variable (Tut_Warning) causes a Wiremod internal error instead of a proper E2 error. This behavior is unexpected, as @strict should catch undefined variables and throw an E2 error, not a Wiremod-level error.
The issue occurs specifically when @strict is enabled.
The variable Tut_Warning is never defined, which should trigger an E2 error instead of hard wiremod error
The error seems to propagate to the Wiremod level, causing an internal error instead of being caught by the E2 runtime.
Even worse, it's feeding the variable into the printColor function which is invoking the error. Being able to feed functions types they shouldn't be allowed to take poses a huge security concern, although it seems it might only occur for undefined types which default to number.
Description:
When running an Expression2 script with @strict enabled, an undefined variable (Tut_Warning) causes a Wiremod internal error instead of a proper E2 error. This behavior is unexpected, as @strict should catch undefined variables and throw an E2 error, not a Wiremod-level error.
Code:
Error Message:
The text was updated successfully, but these errors were encountered: