getShowInWiki feature

[FranticFairy]

Currently, we have a getShowInEditor feature, and it's quite useful. However, it would be nice to have something similar exist for the in-game wiki.

When making a total overhaul mod or something similar, the wiki still remains clogged with vanilla units when you view a CO's Affected Unit's or a unit's weapontable. It would be nice if we could set things (CO's, Units, Terrains, Buildings) to not show up on the wiki, seperate of whether they show up in the map editor or not.

Uses for this would be:

• Vanilla units that are not relevant in a mod (Because they're no longer buildable and can't interact with new units)
• Terrain types that are not relevant in a mod (Because they've been hidden from the editor)
• Units that exist to support a mod mechanic, but are otherwise identical to a different, identical-looking unit (Something I intend to do to make loadouts/upgrades work better in my mod; add duplicates of existing units that come pre-equipped with an upgrade to make the Upgrade/De-Upgrade process cleaner and to work in AI support of sorts)

[Robosturm]

Probably won't happen. It's a nice to have thing

[Lymia]

Would you be against a PR to implement this, or just not interested in implementing it yourself?

[FranticFairy]

Probably won't happen. It's a nice to have thing

In that case, I'd really like to push for #1864, because this mess of modded and vanilla units is genuinely a pain to look through to quick-check what something can attack. It's totally reasonable for a player to look at this, see unit that they think is from the mod, and make a mistake on whether it can or cannot attack something. All of the underlined units are vanilla and so irrelevant and I'd really like to not see them in this (and other) screens.

[Robosturm]

If I'm against something.
I write down why.
This is more a niche feauture which I don't want to invest time in.
PR's are always accebtable unless they decrease performance