In short, the goal of this new template is to remove the notes portion from the template protection of the main body so that regular users can expand them as needed. (This also has the benefit of preventing every page with the table body from being affected just to change the notes.)
As its primary type is one of the glitch types, which do not have any weaknesses or resistances, this glitch Pokémon has the same weaknesses and resistances as a pure Normal-type Pokémon.
First off, {{TypeEffectiveness}} has a number of parameters that tell you what happens in a previous generation. I think these are pointless. Just make a separate table for that generation.
Offensive type changes in some generation ([X]-type moves were [Y]×)
flying=ironballiv (Iron Ball used to negate the Flying type, so effectiveness depended on the secondary type; but since Gen V, Iron Ball just makes Ground-type moves do 1×.)
I also think maybe there are some inconsitencies in what goes into some notes.
Wonder Guard mentions what happens if it gets Soaked. But none of the type immunity notes mention Soak. (By which I mainly mean, the type immunity will go away. Of course, most other effectiveness values would change too.)
A bunch of the Ability notes have a "maybe" option (if the Ability in question is not the Pokemon's sole Ability), but that text only mentions the new effectiveness and completely ignores all the caveats (bypass Abilities, suppressive moves) that the "yes" option mentions.
Final general comment: a lot of the current template's note parameter names are fairly cryptic. Like why does "helditem" remove the held item case... Or why does ghost need a "fightingonly" case? So a minor goal of changing up this template is also to make things a little easier to understand.
Altered effectiveness overview
Type immunities
The form caveat to item-transfer negation only applies to certain Pokemon currently, but new games could easily introduce new forms that are similar.
And none of the non-form item "counters" are accounted for in the current template...
Ghost is annoying because the "ghost=fightingonly" parameter is just for Pokestar Studios' Majin, who has Wonder Guard (meaning Normal effectiveness doesn't change just because the Ghost immunity is nullified). Honestly...if this format of TypeEffectiveness is adopted, I'd say Majin's Wonder Guard-specific note should just be typed out—it doesn't need to be part of any generic template. (FWIW...Wonder Guard itself is also further bypassable/suppressible, as below.)
Iron Ball is damn weird... In Gen IV, it acts like you kinda expect: if the Pokemon has Flying type, then that now has no effect on how damage is calculated (so if the Pokemon is also Fire-type, it takes 2x damage from Ground moves). But since Gen V, if the Pokemon has Flying type and is not under another grounding effect, it takes 1x damage from Ground-type moves; if it has Flying type and is under another grounding effect, or if it doesn't have Flying type, then it takes normal damage.
