1. Tables are completely fixed™. Half a dozen other glitches are fixed. I've requested that fonts be enabled, but that's my stretch goal—people use weird unicode anyway, so we might as well unify it under a feature to prevent it from breaking on unsupported devices.

This is the table I've been working on, but I'm not sure if it's because I crammed a lot of cells into the table or maybe it's the sizing addition I made? Still weird that I have that giant gap at the start, I left a few spaces in the table for some slots that need to be filled but the space is there even when I take out the spaces in the code.

Edit: after a little testing, looks like the space increases with each row added.

Hey, resident Table Experimenter here! The space has nothing to do with either of those things @Hero – fortunately it's kind of a simple fix.

Basically when you add spaces/hit the enter key for good code hygeine, spacing out your raw code for a table, that break is reflected at the top of the table. (Because, uhhhhh BBCode). Since what you've done is press the enter key at least once after every row, and I presume you have a lot of rows, all of those breaks have jumped to the top resulting in a huge gap.

To fix this, you should be able to join up all of the[row]and[/row]tags so that they're sitting in the same line with no spaces between them – like[/row][row].

As an example in a simpler table, this:

[table]
[row]
[cell]Header[/cell][cell]Header[/cell]
[/row]
[row]
[cell]Don't[/cell][cell]Open[/cell]
[/row]
[row]
[cell]Dead[/cell][cell]Inside[/cell]
[/row]
[/table]

Produces this:


While this one, with the[row]tags joined end-to-end:

[table][row]
[cell]Header[/cell][cell]Header[/cell]
[/row][row]
[cell]Don't[/cell][cell]Open[/cell]
[/row][row]
[cell]Dead[/cell][cell]Inside[/cell][/row]
[/table]

Produces this:

Like I mentioned in the post, the table fix is an upcoming update, not already active.

Like I mentioned in the post, the table fix is an upcoming update, not already active.

I was teasing, haha, sorry if I didn't make that clear.

@Roach I'll get it fixing that sooner than later, thank you!

@HeroYes, I had the same problem. Important thing is to make sure there is no spaces between the code parts (cell, row, table, etc.) like so...



Yes, it makes things kind of disorganized if you have to edit it. But look at the raw version of this post. If you create the lines in the correct spots, you won't have any problems.

@BrokenPromise Oh I fixed it earlier today, but thank you, now I know for the future since I left some spaces for organizational purposes (i.e. I'll leave this space so I know to edit in X character later) and clearly that is no bueno.

@BrokenPromise

This is really impressive. Well done!