In the last post I covered a series of basic codes. In this post I'll be covering some tools that are often used as ways of organizing your posts or your character sheets. Much of these codes you've likely already seen in the character sheet example formats, and if those formats have given you any confusion hopefully this will help to better explain it.
There are many times you might uses lists in your posts. It's seen most commonly on various applications for lists of stats, equipment, or similar items. It can also be seen in jutsu when stats or effects may need to be listed. Now this is how the list may appear:
- Option One
- Option Two
- Option Three
But the way it is coded looks like this:
[list][*]Option One[*]Option Two[*]Option Three[/list]
Or it can also look like this:
[list][*]Option One
[*]Option Two
[*]Option Three[/list]
This coding is a bit more complicated than others simply because it has at least three elements to it. It has the starting tag of [list] and it has the ending tag of [/list]. But in addition it has in the middle the [*]. This middle item simple translates into the dot in the list. If you'd rather a numbered list you can change the starting code to [list=1] and it'll number the options for you instead and look like this:
- Option One
- Option Two
- Option Three
As with all things, don't forget that if you start something, you have to end it as well.
Quotes are usually assumed to just be quotes of what someone has said, but quote boxes have a surprising amount of uses. They can be used to quote techniques in a post (so can spoilers which will be mentioned later), they can be used to organize character sheets as well, to separate one thing from an entire paragraph.
Quote:Here is what a quote box looks like.
A simple quote box is what you see above, to code it, it is literally a start and end and looks like this:
[quote]Here is what a quote box looks like.[/quote]
You can also label a quote box.
Naruto:Here is a quote box with a name.
In order to give a quote box a name such as above, the coding simply looks like this:
[quote=Naruto]Here is a quote box with a name.[/quote]
Now tables are where things can get a little complicated. There are several elements to a table that can go wrong. When setting up a table you need to know how many cells (downward separation) you want in it, if you want to title it, and if you want a title line to label each cell with. If that confused you, then you might agree with me, this is where it can get a little complicated. To start with, here is what a table might look like:
Sample Table |
---|
Label One | Label Two |
---|
Sample Content | Sample Content |
The complete coding for this is: [table=2, Sample Table, 1]Label One[c]Label Two[c]Sample Content[c]Sample Content[/table]
Now to break it down, table=2 tells you how many cells you want. 'Sample Table' is the table title. And the '1' shows that you want one label line. Now bear with me, because that is just the starting code to this table. To follow up with something simple, to end the coding you simply need the [/table] line. In order to separate cells we use the [c] coding. Within these cells you can use color changes, font changes, bold, italics, centers, anything you really like.
But remember, using all those combined is where even I get myself in trouble. Finding the error in a complicated code can feel impossible. Be patient, if you have an issue just look at it one piece at a time and remember... if you start a code, you must end it.
One last note on tables. Between [c] codes you need to have both the start and the end of your other codes. If you want three cells side by side of the same text color, they won't carry from one cell into the next without creating errors.
And on a note personal to our current site and hosting site for NSRP... some people like to organize their character sheets with a single cell table, making the starting code a [table=1]. Sadly this will not work here and will just present with a serious error. This is an issue the owner of our site is aware of but so far no resolution has been found.
Now back to something relatively simple, how to display an image using BBcoding. Displaying an image is just as simple as bolding text. It has a start code and an end code, only in this case you're going to put a link to an image in the middle of them in order to display it. For an example I'll use one of my own custom avatar images I used some time ago.
The above is coded as: [img]https://imgur.com/IjBgvG6.jpg[/img][/nocode
The coding of course starts with [nocode][img] and ends with [/img]. In the middle is the link to the image displayed above. As with all other codes, don't forget that whatever you start, you must also finish. Codes have a start, and have an end.
There may come a time where you want to link to a particular word or text. Again as an example I will use something of my own, one of my character sheet links to demonstrate how to link to text. When you link text it will look something like this:
Meiyo Souta
The coding that resulted in the above, looks like this: [url=https://www.narutosaigen.com/forums/viewtopic.php?f=87&t=8340527]Meiyo Souta[/url]
The starting coding is similar to using colors on text in that the start code has to define something. With color text we had to define the color, with links we have to define the destination. So the starting code is [url=Link] though Link would be replaced with the url or link that you want the text to lead to and the end would be [/url]. Between these two are the words you want the link to display as.
Naturally, remember to end any code you start to avoid errors.
Spoilers! They aren't just for movies anymore! Okay but joking aside, spoilers are a very simple mechanism that you also probably saw on the example character sheet formats. You can name them just like you can with quotes, or you can use them simply with just a start and an end. Below you can see an unnamed spoiler example:
This is done with the following coding: [spoiler]Content[/spoiler]
If you wish to name your spoiler you can code it as: [spoiler=Bob]Content[/spoiler]
Which will cause it to display as the following:
As with every other section, just don't forget whatever coding you start, you also need to end in order to avoid errors.