5.1blueprint greater node has a bug?

Hey there @I_love_Miku39! Welcome to the community! I’m unable to replicate the issue itself on 5.1.1. Is the value changing in other parts of the execution or in another location during the same tick? The Stop and watch debugging tool can sometimes be a bit misleading. I do recommend placing a breakpoint and printing the bool and the values it compared as Everynone mentioned, this will give a more definitive idea of what’s going on under the hood.

1 Like