Active Objects - Flag limits

[nivram]

It would be a nice system, to have MMF2 remind the user that they can not overstep flags.

Marv

[Nifflas]

Oh okay. That makes sense. Thanks.

Although I was thinking what would be a nice feature, is that if you use a number higher than 0-31, for example 32, it should display like this.

Flag 30 is off/on.
Flag 31 is off/on.
Flag 32 (0) is off/on.
Flag 33 (1) is off/on.
etc.
etc.

In the parenthesis you can see which flag goes back to when the number are higher than 31. While at the same time you are using another number of your choosing.

Either that, or use the other idea to help notify us when flag limit is over.

Just a text saying "(0-31)" in the caption is a reasonable solution. I'd be happy if MMF wasn't dumbed down, in every expression the user has to know to stay within the range and, I can't see why flag expressions should provide unreasonable help. Sure, MMF should be beginner friendly, but it has to be sane too - CT have more important tasks to do than to protect every user about every mistake they can possibly make.

I mean, you'll notice something goes wrong anyway when the flags wraps, and if you can't debug on your own to find the cause, that's one area you'll need to practice in either case.

[RickyRombo]

And it's useful to have it wrap, because variables can then define which flag gets turned on/off, no matter what number they are.

I agree with Nifflas, just a small (0-31) in the caption would be enough