Broken Masquerade is weird

Broken Masquerade is supposed to be a trope, but in practice it reads more like an index. It's written in a self-demonstrating style that lists several "subtropes", each followed by a list of work titles. Should it be completely rewritten?

That looks like an ancient relic from the early days of the site when stuff like that could fly a little more. I'd suggest a full rewrite and moving the in-line examples to an actual section down below.

Should I add it to Tropes Needing TRS, or go straight to the TRS Queue? Its problems are so apparent that it won't take long to write an OP.

Edited by NitroIndigo on Oct 14th 2022 at 1:57:17 PM

Is it actually being misused though, or could it's issues be fixed with just the Trope Description Improvement Drive?

Good point.

The TDID seems like a fine way to go for rewriting it. The examples will still need to moved to a proper section and context added as well.

From when the page had a failed TRS a decade ago:

I do think it's intended to be an actual trope, about a person learning about some sort of hidden truth, but it's heavily obscured by the self-demonstrating description, long and elaborate list of different types of truths that can be revealed, and lack of example section. I'd be inclined to take it back to TRS for a rename at minimum; I see the name and think it refers to the act of revealing the Masquerade to everyone, with The Unmasqued World referring to the status quo after the Masquerade is broken. The page also seems to be broader than the name implies, with only one of the "pills" referring to the Masquerade; some of the others may still fall under the Masquerade trope, but the first and last are hidden only from the protagonist. Since only "signature" examples are listed I might also want to run it back through the Launch Pad for an actual example list to turn it into a real trope.

But the page is pretty healthily linked around the wiki, so a usage check would be necessary to determine if any of that is needed or if the Description Improvement Drive, and crosslinking of existing examples on work pages, can solve the problem.