Official forums for BZFlag.org

Just an idea of a flag that has been on my mind for a long time and might be interesting to see, albeit possibly impossible to implement.

Named Disguise, the flag would function similarly to Masquerade, except that the tank would be visible in its real colors through the screen, while the radar would display the masquerading (or should that be, disguising) color; in a sense, it would be the inversion of Masquerade.

A similar type of inversion can be seen with flags like Cloaking and Stealth.

The idea is interesting and I would have implemented it myself some time ago were it not for API limitations in creating custom flags.
This has mostly been resolved in the next major release, although it would not quite support what you are looking for, but this could probably be resolved by adding a new feature.
Still, I would not mind implementing this myself in the future, but this would be after having completed my pending projects.

Additionally this seems to have been suggested previously, but was rejected...
This may have changed in the future, however.

-Zehra

That reason is pretty silly, since by the same logic we shouldn't have Stealth, Invisible Bullet, or Jamming. Really I think a version of MQ that affects radar instead of the HUD would be more useful than the regular MQ, which rarely has any impact on gameplay whatsoever.

A flag like this would probably need to be implemented in the official game and not via a plug-in.

We need to get away from flags like this in general, which involve blindly trusting other users' clients to show (fake) information or to hide information from the user. Flags like Stealth, Cloaking, Masquerade, Jamming, Colorblindness, etc. all depend on this blind trust. Going forward, flags like this should be designed within the limits of what the protocol can enforce. For example, I would like to eventually see the Stealth and Cloaking flag effects combined into one flag (so the server can then just stop sending position updates to other players), and then give the flag some other caveat (for example, a 2-3 second engage/disengage period, with an inability to fire while cloaked).

Why not simply grant the API complete control over flag effects and abilities?
Instead of simply "merging" them which is another word for removal, why not grant a better API instead?
If we can control multiple variables, flags which have been suggested over the years can easily be made and invented.
Additionally, quite a few people have been interested in seeing some new features and it could grant what you would like as well.

-Zehra