FLAG

FLAGs, or "bitflags" are, according to the Modmaker's Guide:

A way to store "bits" of info. Used for various options that can only be turned on or off. In Weird World Quest System a bitflag line usually starts with the FLAG command followed by a list of properties you wish to turn on.

So the FLAG command shows up all over the place in .ini files. You'll find FLAGs in races, weapons, stars, you name it. It's usually very early on in a file, but the exact placement depends on what type of file you're looking at.

Here's a list of FLAGS, sorted by the type of file they tend to appear in:

Category or File Type	Legal Flags
(hull).ini files and thus ships with those hulls	antigravity asleep board capture damocles dead foldspace nododge nofighters nosabotage nosysdamage novaprot protector ramshield regensystems spacehulk teleport
(item).ini files (See also weapon DATA blocks, below)	combat hypervision life loot nogen nomulti nosell nothief nowish structural tech unique
Particle effects Often in items / weapons Also appear on starmap and combat	fadein fadeout relative rotoffs slowdown trail worldtime zoomin zoomout
(planet).ini files	homeworld invisible noitems norename
Quests (start of (quest).ini files)	ally always event gamemsg mainquest never tutorial
Quest STAR blocks	existing faraway nearby offmap protect
Races / (race).ini files	always blowup friendly hometrade hostile never random shroud simulator trader unknown
(star).ini files	binary1 binary2 blhole nonova rare variable
weapons DATA blocks	burst continuous homing instakill instant lightning nocollision repeat shootable soundonce spin spiral stretch

Mixing FLAGs from the "wrong" types of files is largely untested. It could give fun results, but also might cause crashes. Please test and document thoroughly, in case the problems don't manifest immediately.

P.S.: If anyone can think of any flags I've missed, please point them out. It's a big list, and was tricky to compile and sort.