So, while I was asking about how headers change the font, I got to thinking. How many [sup] (or [sub], either works) brackets would it take to roughly replicate each header size as regular RPG text? I don't know who would even care about this, but if you want something that isn't unicode and breaks on certain devices, this might be for you.

It does have some issues, though. The text doesn't like to wrap, and will turn into a garbled mess once it reaches the other end of the post/reply box. Also, it doesn't like enter gaps/multiple lines of text in general, so you'll have to input the coding per line of text to try and "get around" the previous issue. Maybe someone can improve on this, idk.

Testing font. This is a message.
0 [sup] = Regular RPG font size (without header).

===

Testing font. This is a message.

4 [sup] = normal RPG font size (with header [h1]).

===

Testing font. This is a message.

3 [sup] = normal RPG font size (with header [h2])

===

Testing font. This is a message.

2 [sup] = normal RPG font size (with header [h3]).

@Kuro
If you put the [h1] on the outside of the sup(s), it doesn't have the overlapping issue for longer text. It does, however, have bigger line spacing than regular text. And you might want to alternate sups and subs so that it doesn't displace it weirdly on the page.

_{^{Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean dui turpis, porta vitae commodo sit amet, facilisis nec lacus. Integer malesuada leo eget diam tristique, et egestas lacus fermentum. Nullam porttitor, justo non commodo dapibus, nulla est fermentum enim, sed consectetur diam tortor vel tortor. Sed dapibus nibh justo, id tristique lectus porta a. Proin porttitor feugiat ipsum ac porttitor. Praesent nec cursus ante, tincidunt euismod elit. Sed eget finibus odio.}}

vs.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean dui turpis, porta vitae commodo sit amet, facilisis nec lacus. Integer malesuada leo eget diam tristique, et egestas lacus fermentum. Nullam porttitor, justo non commodo dapibus, nulla est fermentum enim, sed consectetur diam tortor vel tortor. Sed dapibus nibh justo, id tristique lectus porta a. Proin porttitor feugiat ipsum ac porttitor. Praesent nec cursus ante, tincidunt euismod elit. Sed eget finibus odio.

Also, it looks better with an H3 as opposed to an H1 - almost usable, even :)

_{^{Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean dui turpis, porta vitae commodo sit amet, facilisis nec lacus. Integer malesuada leo eget diam tristique, et egestas lacus fermentum. Nullam porttitor, justo non commodo dapibus, nulla est fermentum enim, sed consectetur diam tortor vel tortor. Sed dapibus nibh justo, id tristique lectus porta a. Proin porttitor feugiat ipsum ac porttitor. Praesent nec cursus ante, tincidunt euismod elit. Sed eget finibus odio.}}