What? I can see the requirements for both, but I don't see any real explanation. It seems very condensed to me and doesn't really answer the general question "How to I make a beam/flak weapon?"
Technically that is not what the weapons.tbl article is about. It is about listing and explaining the options that can be set in the table file. Tutorials as to how to make new weapons would go elsewhere.
Like
http://www.hard-light.net/wiki/index.php/Tutorial_-_Beam_Weapons (old page, could or rather should be updated)
Should this be a section before the "Weapons Table" format?
'Weapons Table' could be removed, it seems to be an empty section
+nocreate
This appears to be grouped OK along with the "$Name:" entry, but there's no visible difference between it and higher grouping.
Which is related to the later issue you listed regarding why certain options are 'hidden' from the menu list.
Missing info?
I thought it was polite not to write there anything if did not know how that option could be used
Inconsistent style.
True and i think it might be better to give examples as if they had been written in table file instead of just entires. However then we get to the issue of to represent them. While < pre> text is possible it should be noted that it easily breaks things (also it does not wrap around making it rather difficult to handle), < code> is another possibility but it renders (IIRC) the background of text with black in wiki (background color), < tt> would give similar font but without undue effects, perhaps with template to render nice box around the text or something?
I'm guessing that the required table is armor.tbl?
That it is.
Homing has several suboptions, but are not accessible via the main menu.
IIRC original issue revolved around the headers of different levels, that is the difference between upper and lower level header did not seem to be clear enough. But if that is not seen a problem then they could be organized into true headers (and end up in the menu).
