This is mostly for the sake of the NeoLemmix Introduction Pack, and is supported for postview texts purely on the basis of "it would be extra work to specifically not allow it there, compared to just allowing it on both sides".
But yeah - IchoTolot wants to mention what hotkeys are in the intro texts. Fair enough - but the issue is that there are multiple default hotkey setups one can choose from, as well as the possibility of custom hotkeys. This means that any hard-written text is not guaranteed to be correct.
Therefore, here's a feature that will help with that!
As an example, I can have the following in an NXLV file:
$PRETEXT
LINE Back skip: [HOTKEY:SKIP-]
LINE Forward skip: [HOTKEY:SKIP+]
LINE Pause: [HOTKEY:PAUSE]
LINE Fart: [HOTKEY:FART]
LINE Back One: [HOTKEY:SKIP:-1]
LINE To Shrugger: [HOTKEY:SPECIAL_SKIP:NEXTSHRUG]
$END
"SKIP-" and "SKIP+" are special values that will list any fixed-duration (ie: not the "to next shrugger" etc) backwards or forwards skip key respectively, regardless of duration. Aside from those two special cases, the key words are exactly the same as in the hotkey INI file in the "Settings" directory. The text outside of the [ ] brackets is just interpreted as normal text, just like it currently is.
The result of the above is as shown in the attached screenshot. Obviously - intended use case would be similar to this, with a dedicated line to list hotkeys. The actual text body would simply mention "hotkeys exist" or something. This avoids the need to either write text that can adapt to any number of hotkeys, or write code that somehow determines just a single one of the various options to display.
Not shown in screenshot: If a function has no hotkey assigned, the placeholder will be replaced with {No Hotkey Assigned}.