Is there any performance or memory bonus to using a boolean over a number?

So like if my character is running, I set ISRunning to True or 1?

I only say this because I started off using numbers for my game, and I want to switch but this means I have to go through every instance that I have used a number instead of a boolean (i have many more than just running conditions).

And now I can't figure out how to so whether IsRunning is true for conditions. "Is Instance Boolean Set" seems to not work

I've read that blog post, but didn't find anything specifically on booleans vs variables. But if you say it doesnt matter, I believe you guys! I wanted to use a boolean, but whenever I try to check if the condition is true or not (I'm guessing "Is Instance Boolean Set" is asking if it is true) it doesn't work. I think i'll stick with a 0 or 1, even though I'll be having around 6 or more instance variables per character.

I often use string variables, while less efficient than numbers and booleans, they're much more readable and the difference is really negligible. Variables aren't no bottlenecks and won't be for decades to come, unless you use some weird code such as huge nested loops.

I agree that boolean would be easier to debug, but for me, I have to use a bunch of state checks. I have one for isattacking that will not only let you know if an attack animation is playing but also the power of the attack to see who's attack will win if two players attacks both collide. (0 is not attacking, 1 or more means is attacking, a higher is attacking will win). I also have some for sidecharge, upcharge, downcharge, isblocking, isrunning, is jumping and a few more to come. This will be replicated for up to four players on screen at once. But maybe using one string as a player state indicator would be beneficial... either way thanks so much for all the help everyone!! :)