This guide has not yet been updated for the current season. Please keep this in mind while reading. You can see the most recently updated guides on the browse guides page
This build has been archived by the author. They are no longer supporting nor updating this build and it may have become outdated. As such, voting and commenting have been disabled and it no longer appears in regular search results. We recommend you check out our other Builds
Vote received! Would you like to let the author know their guide helped you and leave them a message?
Howdy there, guidecrafter! My name is TormentedTurnip, or DrPaco, and I'd like to help you improve the look of your guides by teaching you how to use something referred to as "BBCoding."
Proper formatting is essential for a guide to be considered good. BBCoding might not technically be necessary, but it's a great tool for formatting your guide, and even the simplest of codes make it easy to emphasize important material. Let's face it: most of us have the attention spans of a goldfish. And even if someone does manage to muster through an entire guide without BBCoding, they won't be able to retain every single tidbit of information they learned. It's therefore best to give salience and vividness to the most important information, and there's no better way to do that than with BBCoding.
I won't explain every single possible code you can use - hell, there are probably some I still don't even know about. But what I've written here should help get you on your feet and may still be useful even if you're pretty familiar with BBCoding.
If, after reading through the guide, the concept seems too confusing or time consuming to be worth your effort, please at least check through the sections that provide ready-made templates of coding used in some of the top rated guides on this site, which were given to me by the publishers themselves. Feel free to use them to improve your guide's presentation, as it will be nothing short of flattery to those you've used it from.
Also please note that none of the templates throughout this guide are actually cut off. If you highlight text from either the bottom-up or top-down, it will still include anything that has been visually separated from the page. You will also have to insert vertical spaces (pressing the enter key x amount of times) where you see fit.
And if you haven't already, make sure to check out my guide to guidecrafting before publishing your guide. As important/helpful as BBCoding is, it will end up being useless if the foundation of the guide itself is broken.
As mentioned previously, BBCoding, even more than it's used to make a guide pretty, is helpful for giving salience and vividness to its most important information. Extremely simple coding can be applied by highlighting the desired text and pressing any of the buttons that head the text box.
That said, it's better to learn how to enter codes by individual characters rather than "quick-buttons." Every single code is surrounded by brackets, which look like [ and ]. The first one is an opening bracket, and the second one is a closing bracket, which are used to surround the desired coding. You need a set of both brackets at the start of the code, and a set of both brackets (with a slash mark) to signify the end of the code. In visual terms, it will look like this: [code]coded material[/code].
If you want a statement to look like this, for example, then you simply have to enter in the following characters:
[i]If you want a statement to look like this,[/i]
Now that you have a rudimentary understanding of how to start and end a code, let me give you a short list of some of the more basic codes along with their effects:
[i]italicized[/i]
[b]bolded[/b]
[u]underlined[/u]
[color=yellow]colored yellow[/color] - color chart & color creator
[font=Monotype Corsiva]altered font[/font] - no list available :,(
[left]aligned left[/left]
|
[center]centered[/center]
|
[right]aligned right[/right]
|
Probably the most important feature of BBCoding that you should take advantage of is coding for items in the database. Instead of drowning the readers in a sea of text that will likely become outdated as the game is patched, database coding allows them to hover their cursor over an item, skill, or active to see a pop-up box that displays their descriptions.
A prime example for this is in your section explaining how to use a god's skills. Let's compare a section that hasn't used database coding with one that has:
In my eyes, simple coding is just using one code to format something. But fortunately, you can do much more with coding than that! It reasons to be, then, that advanced coding is combining individual codes for multiple effects. A simple form of advanced coding, for example, would be combining both a color and the underline code, to achieve something like this.
There are multiple ways to code this, but I prefer having coding "consume" another. The above code, for example, was entered as: [color=cyan][u]like this[/u][/color]. As you can see, the underlining code began after the color code, but was also the first to end. The same result could be achieved by closing them off in any order (such as [color=cyan][u]like this[/color][/u]), but I feel it's harder to upkeep, especially when using multiple codes.
Another form of advanced coding is the actual customization of codes. Say, for example, that the size of a picture you desire is either too large or small to be practical. Instead of using the default [img][/img] code, you'll have to set the image equal to your desired dimensions. Let's say the image is typically 500x600 pixels, but you want it to be a fair bit smaller (say, 167x200 pixels). You'll need to use the coding:
[img width=167 height=200][/img].
When customizing dimensions, make sure to change them proportionally. Modifying 500x600 pixels to 100x350 pixels, for example, would drastically alter its appearance. To find a picture's dimensions, simply right-click the image and select "Image Properties..." A new window will open, displaying, among other things, its dimensions.
So, to modify this image to one-eighth of its original dimensions, you would change its default dimensions of 1440x1080 to 180x135. The coding would therefore change from [img]image url[/img] to
[img width=180 height=135]image url[/img]
Before I leave you with ready-made templates, I'd like to provide a few links to some guides that deal with more specific BBCoding.
If you've any experience in BBCoding at all, you might notice how there's been a severe lack of explanation on columns. Well, that's because there's so much about columns that you could write an entire guide on them. In fact, several people have! I highly recommend checking out both Icecreamy's guide to columns and Jordenito's guide to columns, as they're a tremendously useful formatting tool.
There are also come codes listed here that I haven't gone over because they've already been explained fairly well. It won't take much time out of your day; it's pretty short and concise.
If the twelve colors in the color wheel heading the content box don't quite do it for you, here are both a color chart and a color "creator".
The templates in the following sections may seem rather unwieldy; if you end up staring at them with a blank face, use these simple ones I made. Just replace any capitalized text with the content you desire.
This guy!
This is useful for giving an quick overview of a god's strengths and weaknesses while also allowing potential for expansion.
![]() |
[The] Anti-Peeler. Excellent AoE heals. Excellent sustain and burst. Ability to prevent and/or remove crowd control. |
![]() |
![]() |
High Skill Floor. No leap or dash. No true ultimate. No hard crowd control. |
![]() |
![]() |
PRO'S PRO'S PRO'S PRO'S PRO'S PRO'S PRO'S PRO'S PRO'S |
![]() |
![]() |
CON'S CON'S CON'S CON'S CON'S CON'S CON'S CON'S CON'S |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
I, personally, think Piederman's Ao Kuang guide is the cleanest comprehensive guide on the site and certainly deserves its position as one of the most highly rated guides here. He has unfortunately ceased his activity on Smitefire, so I believe we should make use of all the effort he put into his guide, giving his influence a lasting contribution to this site. In case he does one day make a triumphant return, it'd be great if you'd give him a +Rep and credit him for using his coding.
A word of warning, though. The templates provided here might be slightly off from Piederman's actual guide because, even though he did send me the coding, it was unfortunately inaccessible when I finally got around to writing the templates. But I made sure to inspect the elements and convert the majority of the html to BBCoding, so it should be pretty similar.
This is, in my opinion, the best skill explanation section I have ever seen. He doesn't go extremely in-depth with the skills, but the formatting and presentation for them is stellar. This is my most highly recommended template if you can manage to create gifs for the skills.
Graceful Winds |
Whenever people hear the name Ao Kuang, his passive should clearly be what first comes to mind. What it does is that it gives you an additional magical power equal to 5% of your total mana, which is why he is mostly built with mana items. In the late game with my builds you have around 2700 mana, which gives you around 135 additional magical power. |
Squall |
A very useful ability not just for you, but for your teammates as well as it'll help melee gods stick to their target a lot easier. Never use this on minions or for poking. It'll just eat up all your mana before you know it, and leaving you without any major results as well. Use this and Slither to keep your ![]() |
Slither |
This ability is superb when you realize you're in the wrong spot of a team fight and need to get out of there, or to quickly catch up with an fleeing enemy. It's also a very strong ability if you use it together with Squall to keep ![]() |
Tornadoes |
The main ability of Ao Kuang. This brings forth huge tornado with a wide area of effect range that adds a massive damage over time effect on enemies within it. The damage over time effect also refreshes if an enemy remains, or steps back into it. This ability is used for out-zoning Assassins and Hunters from team fights, or to keep them from feeling out of one. |
Spirit's Tempest |
This is Ao Kuangs ultimate. It can be breath-taking if used properly, but its also very difficult to hit with; as well as making a very distinctive sound upon activation. Use it only if you know that it will hit; otherwise use it defensively, or else you'll be drawing a lot of attention to you. It works really well with Ares's ![]() ![]() |
![]() Agni DIFFICULTY VERY HIGH ![]() ![]() ![]() ![]() Path of Flame ![]() |
![]() ![]()
Tips and Tricks
Avoid standing behind your minions, and don't stand next to them at all once he's level 5 or more. This will only give him a straight advantage to poke you down. Remember to move unpredictably to make it harder for him to successfully hit you with any of his abilities, but mainly for his ![]() |
Subzero008 SubShallot is definitely one of the best guidewriters on this site; he has published more guides than anyone else without forsaking quality for quantity. He's probably got the best organization out of anyone, both within each guide and how well they're all integrated together. Even if you don't use his coding, I recommend you simulate how his guides are structured. And if you do use his coding, make sure to +Rep and give him credit.
This is useful for starting your guide with a bang - it will help provide a short and sweet overview of the god your guide is about.
Playing ArtemisIf I had to describe Artemis with one word, it would be unforgiving. Artemis is a difficult goddess to play. She has a set of clearly defined and easily exploitable weaknesses while having few strengths compared to other carries such as Apollo or Neith. Her main strength is the absurd amounts of damage she can inflict late game, but her reliance on basic attacks is also a weakness. With no escape, any mistakes in positioning will be severely punished, and missing shots will decrease your damage output significantly. In short, you cannot afford to make a single mistake. You must have perfect positioning, perfect accuracy, and perfect foresight. If you can master these three, you have mastered Artemis. |
|
Jordenito Jojobanito has published multiple works, and you can really see how his coding skills have developed with each guide. If you want your guide to have a great format, definitely ask him for help. He also typically leaves great reviews. And if you use any of his codes, make sure to +Rep and give him credit.
This is great for displaying a god's common combo(s), while also giving you the option to go more in-depth about it.
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() ![]() |
![]() ![]() |
Sanguis is the author of the top rated Ymir guide here. And even more importantly, he's the one that converted MOBAfire's skillsequence coding into a format Smitefire can use. In addition, he's just generally a very kind and helpful member of the community. Make sure to +Rep and credit him if you use his coding.
I recommend using this code to head you skill explanations section, as it really helps to show the general priority of the god's spell leveling orders.
1
![]() |
2
![]() |
3
![]() |
4
![]() |
5
![]() |
6
![]() |
7
![]() |
8
![]() |
9
![]() |
10
![]() |
11
![]() |
12
![]() |
13
![]() |
14
![]() |
15
![]() |
16
![]() |
17
![]() |
18
![]() |
19
![]() |
20
![]() |
1
![]() |
2
path of flame |
3
![]() |
4
![]() |
5
![]() |
6
![]() |
7
![]() |
8
path of flame |
9
![]() |
10
![]() |
11
path of flame |
12
path of flame |
13
![]() |
14
path of flame |
15
![]() |
16
![]() |
17
![]() |
18
![]() |
19
![]() |
20
![]() |
BestMinionEver BestMelonEver, or Marki, is the author of one of the top rated guides on the site, with several other solid guides under his belt. Both he and Subzero could be considered the site's Jungling mentors, and he's graced me with some coding from his comprehensive guide to Ne Zha. Please give him a +Rep and credit him if you use his coding in your guide.
Beginner build (jungle)![]() ![]() |
Advanced build (jungle)![]() ![]() |
Early snowball build![]() ![]() |
My current build![]() ![]() |
|
|
Well, I hope this guide was helpful to you. I really would like to see guidemakers make use of the templates that multiple prominent authors have provided, using the time they will have saved to focus on the content of their guides. Best of luck to you, and feel free to PM me with any questions or help regarding BBCoding.
When I began writing my first guide in June of 2013, I hadn't an inkling of what BBCoding was. Although I didn't use it as a reference for this guide, Jhoijhoi certainly helped get me on my feet with her Getting Started guide.
A big thank you to Icecreamy and Jordenito for their guides to columns. I would not have even considered making this guide if I were going to explain columns. *Shudder*
Huge props to Piederman, Subzero008, Jordenito, Sanguis, and BestMinionEver for lending me their codes to be used as templates.
There are also many others who have, to a lesser but non-negligible extent, influenced my works. Thanks for being active, ya'll.
And finally, let's not forget the editors, veterans, moderator, and administrators who keep the database current!
SMITEFire is the place to find the perfect build guide to take your game to the next level. Learn how to play a new god, or fine tune your favorite SMITE gods’s build and strategy.
Copyright © 2019 SMITEFire | All Rights Reserved
I'm planning on maing a columns guide...
YAY :D
<3 u if you make it