Thread:FishTank/@comment-28362064-20160602124631/@comment-4522253-20160602142613

It's fine, coming to me directly. :-)

This is not an Infobox, and so the same rules do not apply. This is what we'd call a data table.

So, let me mention first that in terms of portability there are three things that you're doing here that you'll want to avoid for making it work on every platform: you're constructing a table from a template, you're using three templates to do it, and you're using colspan. I understand the convenience on doing it that way, but you'll actually be a little better of doing it in an actual wikitable (and in this case putting it into 4 wikitables would solve this problem you're having entirely). The balance is that readers will be able to see it better, even if it's on a smaller device or browser. I have no doubt that many players would appreciate bring able to reference information like this inside their phones during gameplay; if they're using that phone in portrait rotation, a table fixed to be that wide (especially with many row entries) will be cumbersome and uncomfortable to use.

It's very tempting to want to have the information all in one table, but that's also what is causing your final column problem. It is definitely caused by the fixed table layout running out of space. Your gut reaction is likely to be to tell me that the single table is absolutely imperative (and that it must be done in Templates), and I wouldn't blame you for doing so. But as you came to me for the advice, I'm still going to suggest you try breaking it up a little and seeing if that doesn't solve more problems than it creates.