---

---

1. Let's atart with a simple table:
   
   Units, come in.

   Sitrep, over.

   ...

   Alpha

   Ready, over.

   Bravo

   Ready, over.

   Charlie

   Delta

   Ready, over.

   ...
   The code looks like this: [Table] [Tr] [Th]Units, come in.[/th] [th]Sitrep, over.[/th] [Th]...[/th] [/tr] [Tr] [Td]Alpha[/td] [td]Ready, over.[/td] [/tr] [Tr] [Td]Bravo[/td] [td]Ready, over.[/td] [/tr] [Tr] [Td]Charlie[/td] [/tr] [Tr] [Td]Delta[/td] [td]Ready, over.[/td] [td]...[/td] [/tr] [/table]
   • The tags are read by Steam in order of their appearance.
     
     
   • The [tr][/tr] tells Steam to add a row while the [th][/th] or [/td][/td] tells Steam to add a column.
     
     
   • The size of the column box per row will always fit the first row columns. If there are three columns, then at every row, you need to put the same number of columns.
     
     Otherwise, you can see your table having that odd potrusion ('...') as shown above.
   
   
2. But let's say you don't have a neat symmetrical table to make. You need a flexible table so let's make an assymetrical table via creating multiple columns below the same row:
   
   Sitrep?

   Alpha

   Bravo

   Charlie
   The code looks like this: [Table] [Tr] [Th]Sitrep?[/th] [/tr] [Tr] [Tr] [Th]Alpha[/th] [Th]Bravo[/th] [Th]Charlie[/th] [/tr] [/tr] [/table]
   • By chaining the [tr] within each other before any other tags, Steam is reading it as a trench within a trench.
     
     Ergo, the second [tr] creates the second row of the table and the [tr] after the second tells Steam to create a row within this second row.
     
     
   • The [td][/td] tag will not bold your text in the cell while the [th][/th] tag will bold automatically.
     
     As such, it is redundant to bold a text between the [th][/th] tag.
   
   
3. Now let's see if we can add multiple rows beside the same column:
   
   Sitrep?

   Report?

   Alpha

   Bravo

   Charlie
   The code looks like this: [Table] [Tr] [Th]Sitrep?[/th] [Td]Report?[/td] [Tr] [th]Alpha[/th] [/tr] [Tr] [th]Bravo[/th] [/tr] [Tr] [th]Charlie[/th] [/tr] [/tr] [/table]
   • Next principle: Steam not only reads the tags in order but it reads them in a fixed sequence of rows followed columns.
     
     Basically, when you use the [table] tag, it tells Steam to begin a table. Then, the first [tr] tag tells Steam to add a row. Steam will read this as the first row in the table.
     
     As long as you do not close this row with a [/tr] tag, Steam will read any further starting tags as being in the first row.
     
     
   • So, as you can see, I did not close the first [tr]. When I add the [th] tag, Steam reads it as forming the first column in the first row.
     
     If I add another [tr] right after closing the [th] with a [/th], it tells Steam that the first colum is finished but since the very first [tr] has not been closed yet, Steam will see the new [tr] as being the starting of a row in the next column in this first row.
     
     
   • In short, Steam will always see where you close your tags and until the main trench/row tag has been closed, it will assume subsequent new row tags after closing any column tags to be a part of the next column.
     
     
   • Additionally, you will notice that the [td][/td] draws text differently than the [th][/th] tag. The text is drawn in the center rather than from the top respectively.
     
     Keep in mind when adding rows within cells as this will mess up the alignment (unless this is a look you are going for).
   
   
4. Now we try to combine the above two theories to make a larger assymetrical table:
   
   Units, come in.

   Report status, over.

   Alpha here, standing by.

   Bravo engaging!

   Charlie, requesting assistance!
   The code looks like this: [Table] [Tr] [th][h2]Units, come in.[/h2][/th] [/tr] [Tr] [Tr] [Td]Report status, over.[/td] [Tr] [Td]Alpha here, [u]standing by[/u].[/td] [/tr] [Tr] [Td][h3]Bravo engaging![/h3][/td] [/tr] [tr] [Td]Charlie, [b][i]requesting assistance![/i][/b][/td] [/tr] [/tr] [/tr] [/table]

Ever wonder how I did it?

---

Is the same as:

"Well this is just wonderful."

---

You think to yourself as you march down a lowly path of dirt & gravel, moving past sullen or grim-faced people, some in chains, others pulling them.

As you approach a bunker of what must undoubtedly be bomb proof to its maximum strength, you glance aside to corpses lying on the ground, headshot wounds to the forehead visibly bleeding.

Originally posted by Your thoughts:

"He's been busy."

You wince and quickly brush past the guardsman on duty, a crisp salute the only greeting shared between the two of you.

Why was he in here though?

They say the man who resides inside is nothing more than a madman who voluntered for this job. Others say he was put here to get him away from everyone who were neither insane nor condemned. Still others share the rumour that he was put here by mistake, an error of paperwork or a clerk's misfiling.

Whether he was in here by will, by force or by pure chance, none of it changes the fact that you are here, about to meet him.

Originally posted by Your thoughts:

"Well, I have this thing troubling me.
Maybe he has some advice?"