1. I assume you are talking about switch/if statements that fail to find their end position. Quite a difficult bug to fix as there are several ways for switch/if's to end and one switch ending which I can't detect at all.
2. Not a bug. Both are legit ways of calling gotos.
3. Temporary bug in V1.2, I have fixed this but it is not public yet! Also for most arrays you'll be required to define an array type as UE Explorer cannot figure the type out on its own unless it were to link every package in the System folder which it doesn't do.
4. Not a bug. The Unreal Engine compiler treats Enums as constants so at compile time the enums are replaced with their corresponding number.
5. Thanks, didn't notice the accidental () parentheses. I guess I messed this up long ago when I redid some of this code
6. Not a bug. Although definitely an issue. I will fix this whenever I know a solution to it. If you really want to know the original parenthesis you can use "View Tokens" and look for things like BoolVariableToken which is like surrounding a bunch of expressions with () but not always!
Edit: 3, 5, and 6 are fixed in 1.2.2.1
Thanks, feel free to report more!
2. Not a bug. Both are legit ways of calling gotos.
3. Temporary bug in V1.2, I have fixed this but it is not public yet! Also for most arrays you'll be required to define an array type as UE Explorer cannot figure the type out on its own unless it were to link every package in the System folder which it doesn't do.
4. Not a bug. The Unreal Engine compiler treats Enums as constants so at compile time the enums are replaced with their corresponding number.
5. Thanks, didn't notice the accidental () parentheses. I guess I messed this up long ago when I redid some of this code
6. Not a bug. Although definitely an issue. I will fix this whenever I know a solution to it. If you really want to know the original parenthesis you can use "View Tokens" and look for things like BoolVariableToken which is like surrounding a bunch of expressions with () but not always!
Edit: 3, 5, and 6 are fixed in 1.2.2.1
Thanks, feel free to report more!