[karajorma]

-nowarn IIRC but it's generally a really bad idea to use it.

[CP5670]

No, that isn't recognized. I will search around the wiki and see if I can find it.

[edit] The wiki command line says it is -fred_no_warn, but that isn't it either. Simply -no_warn doesn't give any unrecognized option error so that might be it, but it doesn't do anything.

I would like to fix the table "error" but as I said before, it's impossible to do that at the moment. I looked over the debug message again and looks like $Stealth is just not in the debugger's list of valid flags at the end of a ship entry, which is really an issue with the debugger.

[karajorma]

My FAQ says no_warn and I remember checking my facts when I wrote that piece of info. Either the function is broken or has changed its name.

[WMCoolmon]

You're thinking of the FRED command line to stop it from complaining if the player ship is a capship,

Try "-noparseerrors", that will restore lax table parsing. Still, like Goober says it's best to actually fix the problem; fs2_open has some minor order-correction stuff in the parsing code but I wouldn't trust it.

The problem you're having is that there's actually a ":" after "$Stealth" in the code. It should really be a ship flag, and not an extra tag, but for now, if you add the : onto the end of your stealth it should work. If not, post the three entries ($Stealth, entry before, entry after) with the data and that should help it get debugged. If you have any outrageous comments that totally spoil your campaign's ending you can go ahead and remove them.

[CP5670]

That colon seems to have done the trick nicely. Thanks. If it needs the colon though, how come it doesn't complain about the original $Stealth flags for the Pegasus and Ptah?

I was using this stealth feature for the polaris pylons, those framework pieces Dark made that have been around since FS1. These things are generally used in large numbers and I don't want them cluttering up the radar and target list.

[WMCoolmon]

Because they both have the : on the end.

Apparently it's a voltion thing

[Goober5000]

Might be nice to make it more user-friendly though.  What about changing the string check to accept both "$Stealth:" and "$Stealth"?