It'd be super duper useful if, when doing chapter requirements, there was a "doesn't equal" option. So that if you've got a Time variable, things can be closed off at certain times (let's say at Time = 5) without needing one chapter for Time < 5 and another for Time > 5 -- especially if there's multiple times that the same thing would be closed off! That's just one example, but it would also mean that variables to stop loops wouldn't need to be set beforehand (if you can only go the Gym once, say, then the variable requirement would be Gym =/= True, and the chapter would set Gym to True -- no need to set Gym to False beforehand!) Would super really nice for making things easier, and making a lot more stuff possible to take full advantage of the game system in the website!
I run into this quite a lot myself! In Kami Kurabe, I end up doing a roundabout thing where I add one to the score on the hub chapter each time and add 1000 to it when you're actually in the chapter to close it off in the future. An "if not" statement would make it a lot easier.
Yeah! There's been so many times that it would've been awesome to require no value of a variable, as well as just not one specific value of a variable. So much cool stuff could be done!
Game mode would be immensely improved if it allowed logic gates. It would be difficult to implement, I imagine, but definitely worth the effort.
I agree! But that's probably a different suggestion to make somewhere here -- and I don't think (hope!) it's be too hard to have the "conditions to view" section be >, <, =, and =/=.
I believe =/= uses a logic gate (the NOT gate applied to the = operator), though NOT gates are indeed simpler than AND and OR gates, and would likely be easier to implement. However, OR gates would generally solve the same issue as an =/= operator. Instead of writing Time =/= 5, you can write Time > 5 OR Time < 5.
A "NOT" condition would only serve very specific cases. You still wouldn't be able to check for 10 < x < 20. Thus, there was the idea of having a more flexible way of changing scores that would allow you to precalculate condition variables. (including deleting of specific variables and handling cases when a variable isn't set.) Unfortunately, that might lead to performance problems so it might be better implemented in the next version.
