This build has been archived and is for historical display only

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 take a look at this author's other builds.

Not Updated For Current Season

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

So you want to write a guide? [Preliminary Release]

12 0

9,014 Views

27 Comments

Build Guide By Updated on

Guide Discussion (27) More Guides


General	Starting Out	Content Of A Guide

Introduction	Qualification	Cheatsheet	Guide Content	Going Beyond
Closing Words	Editing	Visuals	Guide Body

Hello everyone! I am Katasandra, your local & table or code in general enthusiast. If you don't know me yet, that doesn't matter. Today I'm here to help you, I have for you a guide on...

Writing A Guide

Back when I started writing my guide I used a few short guide-like writups around the site. Each of those told me a little, but in the end I still felt like something was lacking. I will be repeating (some of) the information in these guides and also try to explain some things I haven't seen. So in this guide I will share my view on how to write a guide & compile an collection of the snippets on this topic that are scattered around the site.

Sources I used

Perhaps you don't trust me entirely yet... Maybe I'm a madman that has no clue on how to actually write a guide! But rest assured, I won a few Guide Contests and write reviews for guides around the site. I know the guide stuff ;)

If you have a different view than me, or you if you disagree at some points, that's totally okay. Please share your view & reasoning in the comments. I'm curious to hear others' thoughts!

Disclaimer

This is a Preliminary Release, in other words: my guide isn't done yet. However, I'm unsure what exactly I'm missing... Since that all depends on me getting an idea who knows how long that'll take, so I decided to release the guide!
Feedback is appreciated a lot. Whether you are new writer, or seasoned author, all opinions are welcome!

Before writing a guide, are you eligible & credible?

Eligibility

I know, I know, everyone can make a MFN account and make a guide, buuut.

Don't bother writing guides when you're below level 30 or writing about builds/champions you don't have (a lot of) experience on. You might think you know a lot, but trust me, unless you are the next faker, you don't. You can only teach people things if you know it better than they do, if you don't you'll be wasting your and their time.

Credibility

As an author you also need to supply some credibility, such as your rank or mastery. Truth is that many people will look at this, regardless of what you put in your guide. In any case, make sure you really know what you're about.

As a general rule of thumb, you should be at least gold+. Simple reason for this is that about half the playerbase is below that & half is above that. Usually explaining things to people on a higher level than you tends to have little success. It's like a high schooler explaining something to a university student.

I'm aware of the existence of the normal games unranked gang. You can make guides too! It's just that you have to put some extra effort in to make sure your information is correct.

Having a high rank/lots of mastery does not mean that your guide will automatically be good. Quite the opposite, some of the worst guides on this site are from challenger/grandmaster players... And vice versa, there are also some very good unranked/low elo guides!

Necessity

Let's say you want to write a guide. Now, what is it what you offer that the dozen existing ones yes there are that many do not? If you cannot offer anything different from the other authors then you might as well not bother writing a guide.

Do not write a guide if there are (multiple) guides that already say the exact same thing as you would say!

If there is something different, you'll still have to be careful. If the only difference is that you take a different secondary tree you could comment on the already existing guide & ask the author what they think of that. Perhaps the author does not agree with you, then you can go decide to go ahead and tell the world that your secondary tree is the superior one. But do so in a respectful way...

Streamers are a group who get to evade this one, as they have an additional goal: promoting their stream. Some of their guides may not have original content and still receive high ratings. If you're not a streamer and you're aiming high, then you got to outdo these guides.

Perhaps you are still not buying it, you are truly passionate about your champion and really want to create a guide. Then you can create it, even though many others exist. The key to getting on top of the rest: constant improvement and longevity. The longer your guide exist, the more likely it is the rack up votes & views and get on the top! If it's good.

This is entirely about editing on PC

Although there are editor tutorials flying around I cannot find an updated one :(
So here is my attempt at explaining the bits and pieces of the editor. If you're not interested I suggest you use the sidebar TOC to skip to the next section.

Once you click "create a guide" at the top of the page, you'll end up on the basic setup interface. On the right is perhaps the most important part of the guide editor.

The page you're on is highlighted. There are a total of five tabs:
1. Basic Setup Interface where you can edit the title, guide type, champion as well as C2V and prime settings.

2. Build Options Here you make the cheatsheet.

3. Guide Chapters All the content in the guide body goes in here.

4. Help Some BBCode help as well as some ideas on what topics you can put in your guide and generic tips & do's and don't for guide.

5. General Rules & Guidelines Exactly as the name says. Make sure to check it out as there are rules concerning guides as well!

You can only access the 2nd and 3rd tabs after filling out the Basic Setup.

There are also a couple of other buttons, these all have to do with saving / proofreading and publishing your work.

1. Save saves your guide, make sure to use it regularly so that you do not lose your work.

2. Preview opens your guide using all the saved content, only you can see this. Make sure to use this regularly to check what your writing & code looks like.

3. Preview Mobile does the same, except it shows how mobile users will see your guide.

4. Publish will publish the previewed version to the public. Don't publish WIP guides. This is just tilting and can damage your rating.

5. Next lets you go to the next part of the interface. However you can also click on the individual tabs, so you can pretty much ignore this button.

Basic Setup

This interface is quite straightforward to use.

Put anything in the title bar you can edit later.
Select the category (if you're making a champion guide, make sure you do not select General)
Select the champion
Select the guide skin (This displays on the chapter header & in the search results)

Once you've done this you should be able to proceed to the Build Options & Guide Chapters. There are also additional options (Comment to vote & Prime settings), but you don't have to bother with these.

Build Options

This works quite intuitive as well. I recommend just clicking on everything & trying out what it does. You can easily check how it looks by Saving & clicking Preview. Only Build Title right below the character counter will not have a visible result. You can actually select your champion multiple times in the Basic Setup, if you do so you'll see two icons in Build Options:

→

You can edit either of these builds by clicking the respective icon. If you enter a build title (or no build title) it'll look like this in the guide:

This can be super helpful if you got item builds that go with specific rune pages or something of that sort.

Guide Chapters

This is actually not so straightforward as the rest. Let's start with the bar at the top:

The Character Counter keeps track of the characters in the guide. If your guide has more than 3k characters then it can be found as a guide in the search results. Once you pass 15k characters you'll get the in-depth tag as well. The notes in your cheat sheet count too!

Then there is the Chapters Header. If you select Show, you'll see this kind of banner (at the top of the guide):

If you select Hide, you obviously will not see it. Fade Chapters Header, ironically, does nothing with the actual Chapters Header. It will basically fade the bottom half of the Header Images of the chapters, I'll get to that later.

Last, but not least, there is this box:

Chapter Title is basically the title of the chapter. All the names of the chapters will appear in the sidebar TOC, which you'll see to the right/below.

At Title you can select Show you want to show the Chapter Title in the guide body (or on the Header Image).

Then there is the Header Image URL. If you have banners, it is often convenient to put the URLs here. However, if your banners are not the right size, or you don't want the "TOP" marks on your banner (like in this guide) you can just put them in the text as well!

Coming back to the Fade Chapters Header, it fades the bottom of all the Header Images. I enabled the option in this guide. I actually think it looks awful so I recommend disabling it.

Returning to your Draft

Of course, you'll not be able to finish your guide in one go. Guide writing can take a couple of days, a few weeks or even months. You can easily return to your guide by going into your profile and selecting the following:

You can also select Draft Only, but I prefer selecting All because that's the only way to make my coding draft show up >:(. Then just click on your guide. Somewhere at the top you'll find a couple of buttons (they may be slightly different):

Select Edit and tada! You have returned to the editor.

Onto how you should tackle the Cheatsheet aka Build Options. But first something that comes before the cheatsheet.

Guide Title

The title is the very, very first thing people will see. It's all up to you, you can put anything from quotes to nifty word plays these are obviously the best >:) in the title. But there are some things you should avoid:

Making it longer that 60 characters - it cuts off once you hit publish
Adding tags such as patch or in-depth - they show beneath the title anyway, it's pointless
Adding your name - your name shows below the title too
ALL CAPS - LET ME SHOUT THIS CLICKBAIT GUIDE TITLE YES YOU WANT IT

If you don't the title yet like me, just enter something and continue. You can always change it later!

Cheatsheet

Every guide begins with a cheatsheet. One could mistake this for some dumb, silly, simple thing, but it's far from that. This might be the only thing that many of the people that open your guide will see. Therefore it is the 'face' of a guide. A cheatsheet:

Will entice your readers and catch their interest.
Quickly shows what to build.
Functions without the rest of the guide.
Is concise.

Yes, a cheatsheet can do/have all those things! But how do you make such a thing? I got a few pointers and warnings for you.

Content

The Summoners & Skill Sequence are the most straightforward. Just add all your options. Threats & Synergies are completely optional, if these get lengthy it's often better to put them in the guide body.

The Runes and Items are trickier. I'll explain those in a bit!

Notes

Notes, notes, notes! A cheat sheet with no notes cannot exist. When there are multiple options you should explain when to choose what in the notes. Do NOT add WHY xxx is good (this should be explained in the main body!). Explaining "why" makes notes unnecessarily long and a tragedy to read wall of text D:, remember the purpose of a cheat sheet: quickly show what to build!

Titles

You can utilize the titles of rune pages, summoner spells & item blocks to explain your choices. For example if you take vs assassins. Instead of calling the page "Exhaust" and putting "vs assassins" in the notes, you should call the page "vs assassins" and leave the notes altogether. You can explain a surprising amount of stuff this way.

Runes

Here you should list the standard/viable rune page(s). Try to make a rune pages for each keystone. There should be like 6 rune pages max, if there is more you're either playing an extremely versatile champ or you're including meme pages.

Do not make new pages where you swap this or that minor rune. Just put that in the notes! This often results in wayy too many rune pages.

It is optional to create pages where you swap secondary trees, but you sometimes you can mention these secondary trees in the notes as well.

Now it's time for the items! Instead of throwing all of these together you group them into little blocks.

Starting Items

List the starting item(s). If there are multiple choices you can either make separate blocks or put them in one block. Trinket is not necessary (but hey, everyone adds it), unless it is red trinket.

First Base

This one is optional, I noticed that things can get very complicated very quickly if you have a lot of options. This defies the purpose of the cheatsheet (e.g. quickly show what to build). If you have a small amount of choices, it is alright. But if you got more you should consider talking about this in just the items section.

Mythics/Core items

You can make a separate block for mythics, explaining when to go what. You can also choose to make groups highlighting builds that combine with specific mythics. If there are any items you always build (Core items), then you should also make a separate block for those.

Boots

You can make a separate block containing boots, you can put one in core items. But you can also put them in a block with situational items. Boots are very flexible.

Situational Items

The advanced pitfall. Do NOT heap all of the situational items in ONE block. Try to split them up in groups. You can always determine some kind of structure! Think of Offensive - Defensive, Armor - MR or even situational - super situational.

Consumables

This is more of a "tradition", you basically throw potions, elixirs and control wards in here. Some people also add trinket, it is up to you.

X Rune Page Build

Sometimes a certain build corresponds with a certain runepage. You can easily match these by going to
Basic Setup --> 4. Champions --> Select the champion your guide is about (for a 2nd time) --> Build options --> Select the second one. Here you can enter your magnificent runes + items combo, just make sure to give it a title. If you wish to delete it for some reason, you can right click the champion icon in Basic Setup (Make sure to delete the right one). It isn't possible to adjust the order of these builds.

And then it's time forrr some examples! I'll include some images but make sure to check the guides out as well for the notes! Tauricus' MF Guide Spoiler: Click to view My Lissandra Guide Spoiler: Click to view Looking for more...
Then there are also two pitfalls regarding the build itself. The first one is build variety. A build without situational choices does not exist. If it doesn't have these it's probably just bad. Then there is not explaining in legible ways. For example if you list a build with 5 items + boots & a loose block with a bunch of situational items, but do not explain which items you can swap for situational items.

There are lots and lots of topics to talk about, but let's start at the beginning!

What do you put in a guide?

There are some basic topics, which every guide should have:

Introduction
Pros/Cons
Summoners
Runes
Items
Abilities Explanation
Skill Sequence
Gameplay Information
Conclusion

Then there are also some topics to avoid:

Lore
Skin tier lists or other talk about skins
Champion changes (Patch notes)
Excessive self promotion YT & Stream are OK, but don't add non LoL related things.

This is simply not information people are looking for in guides. They're "filler" topics and serve no use.

If you've covered all the necessary chapters, you can get creative and add chapters such as:

Matchups
Role related gameplay (e.g. Jungle Paths)
General Skills
Advanced Champion Mechanics

Chapter Order

Of course, you cannot put the chapters in some random order. A logical order is:

Introduction → Pros/Cons → Abilities / Skill Sequence / Summoners / Runes → Items → Gameplay → Conclusion

Your guide should always start with some kind of introduction. Introduce yourself, show your credibility and enthusiasm. It's just like presenting, you don't hop into your story & end it with(out) telling who you are.

Next up are the pros/cons. This is basically an introduction to your champion. Here your readers can figure out whether this is the champ for them and/or what to expect.

Then we enter a grey area... These four chapters can be put in a lot of different orders. For example, I prefer to group the chapters about the kit and the setup chapters (which includes items), so I put it in the order listed above.

The items come very close to gameplay, you basically purchase them in-game. Therefore they should be close to the actual gameplay chapter.

Once the setup and kit explanation is done, it is time for the gameplay. Once you start expanding your guide you should be careful of the order of topics in this chapter. Try to keep it chronological.

The placement of additional sections that are not pure gameplay such as combo's & advanced champion mechanics is up to you. Make sure to keep it logical though, don't talk about combo's before talking about abilities.

∞

Finally, the guide should end with a conclusion. Thank your readers, give credit to people/guides that help you out and wave goodbye.

In some guides you'll also see a changelog, this always comes last, usually in a spoiler. Readers rarely want to see this and it's mostly for the author to keep track of changes.

It's time for a breakdown of the different components of a guide and what you should look to put in them!

Introduction

I already kind of said it in the part about chapter order... It's basically to "start' the guide without suddenly getting into the thick of it. At the same time you can assess your credibility by mentioning your rank (please link your profile), mastery or in other ways. ~~winrates of your smurf account~~.

Pros/Cons

This is essentially the introduction of your champion. In my opinion this should be an objective list of a champions strengths & weaknesses. You can add additional explanation of these qualities where you can mention their effects or what causes them.

Sometimes these pros/cons are not so objective, it depends on you and how you want to write it. If you're really enthusiastic and want to sell your champ, then I recommend making a Why play X (sub)section.

Abilities & Skill Sequence

These two often come together as they're very closely related. The Skill Sequence is easiest. What is the skill sequence and why? If there are multiple possibilities: when do you choose each & why?

Abilities are a little harder. Copying their descriptions is optional. Anyone can go over to lolwiki and read what they do. If you do put them in your guide, be careful as it is extremely easy to forget to update numbers.

What this section should actually entail is a breakdown of how abilities are used, how they synergize with other abilities and other neat tips and tricks. This is what people are looking for!

Summoners, Runes and Items

These sections come down to the same things:

	1.	What are the options
	2.	When do you choose them
	3.*	Why do you choose them
1. & 2. are the most important. "Why" some choices are good usually speaks for itself, but "when" you actually take them can be difficult to guess.

Do not explain why X choice is bad and why you don't take it, especially clearly unviable choices. The only exception is when you don't take a very common option.

Then there are also the niche options. You have to make sure you tested all the content you put in your guide. This is not the place to theorycraft. If you come up with niche options, but you never ever build them do not include them

Last but not least, the content of your cheatsheet should match the content in your guide and vice versa. You cannot leave cheatsheet content unexplained in any scenario.

Gameplay

This is perhaps the most important part of a guide. Anyone can find builds and skillsets on stat sites. But you cannot find gameplay information. A few questions that could look to answer in this section.

What is your goal in the laning phase / mid game / late game?
What do you do to accomplish this goal?
What do you have to watch out for?
How do you want to fight?

Basically at least the bare minimum of knowledge required to play a game with X champion.

Conclusion

All beginnings must have an end... Including your guide. It also gives you the opportunity to thank your readers & give credit where credit is due.

If you've seen multiple Mobafire guides you also have noticed that there can be large differences between them. Not only in terms of content, but also how they look. But before getting all into visuals, I want to mention a more important subject.

Writing

Honestly, sometimes guides with nice visuals fall on their face just because they are filled with spelling & grammar mistakes. Run your guide through a spelling check, you can easily do this in Microsoft Word, in Google Docs, or even in your Browser if you tell it to check for English. Utilize Google to research grammar or ask others to check your guide for these mistakes. Not being a native speaker is not an excuse for heaps of mistakes. They just look bad and can turn readers away from your guide.

Then there are two subjects that rarely get attention Sentence Length and Paragraphs. To demonstrate the effect of both of those, there's a spoiler below. The first one has the original text and in the second one I merged the paragraphs and made some sentences a little longer.

Original

Modified

As a rule of thumb you should make your sentences no longer than 25 words. If they get longer you're probably trying to talk about too many subjects at once!

Paragraphs are a little harder than sentences. Usually they encompass a single subject (or single bits of a subject) and they help cutting up the text. It's beyond the scope of the guide to talk about this, so here are a few helpful links: 1. 2. And well, Google exists...

BBCode

If you copy paste some bits of the code showcased here, it might not result in the same thing as I show. I added some widths here and there to limit the size of things. This is not shown in code so it cannot confuse you...

The rest of visuals is BBCode. This is also explained in a lot of other places, but I'll put all the corresponding code and such in spoilers.

This is essentially all about formatting, you want to avoid big walls of text. However, be careful. Sometimes authors leave important pieces of information out because they want to avoid these walls since they look bad. To quote a friend of mine:

It's not the fault of the wall of text, it's the fault of lack of aesthetics

And he's right! You can transform even the ugliest wall of the text in something that looks nice, with ~~tables~~ BBCode.

Text Effects

The most well-known and most used Text-Effect are wiki links:

[[world ender]]

→

You can link abilities, champions, items and a lot more directly from the site database. I recommend using them whenever you write down champion names/runes etc. They can have quite an impact on the text!

Other Text Effect Codes

All these effects concern changing the text in some way. Avoid overusing them! Do not randomly color or bold entire paragraphs. They quickly make your reader eyesore and tired. You may think that it makes your text look "fancy" or "nicer to read" but it really does not. If you're not convinced, I wrote a blog post about this topic too.

Images & Icons

These two help a lot breaking up text & giving your guide a nice look. Icons are often used in items, runes & summoner spell sections and images can basically be used everywhere. Either just as a flavor addition in the form of fanart, but also to support your explanation with images of certain scenarios.

Icons are added using [icon=salvation size=20]:
Let's say you wanted 's ability instead, you can easily achieve that by doing [icon=salvation ability size=20]:

You can also add borders to these icons [icon=salvation size=20 border="2px solid blue"]: . 2px defines the thickness of the border change it to 20 hehe and blue is obviously the color. Hexcodes work too!

Images basically work the same way. You obtain a direct image link and add it between [img][/img brackets. Then you (again) can add some things to the brackets, check the spoiler!

Bracket tags

Gifs & Vids

Like images, these can really spice up your guide. Adding them can be easy or difficult, depending how you look at it. There are two 'methods':

Embed: [embed]https://www.youtube.com/watch?v=qakuk-1pA6A[/embed]

Webm: [webm url=https://thumbs.gfycat.com/KindheartedWhimsicalArgali-mobile.mp4]

You'll always have to upload your clip to some 3rd party site. Then you have to obtain a direct link (right click & select Copy Source URL). Once you've done that you have to fiddle a bit with the methods, most clips tend to work with only 1 method. For instance YT vids can only be added using the embed method and GFYcat Gifs can only be added with the webm method. Try messing around with both.

You can again add tags to this code. Changing size is done (again) with width= and/or height=. If you utilize the webm method you can also make the clips autoplay or loop by adding the words to the code:
[webm url=https://thumbs.gfycat.com/KindheartedWhimsicalArgali-mobile.mp4 autoplay loop]

Tables & Columns

These two are basically necessary if you wish to format your guide well. Since their function is a tad to complicated to explain here, there are a few guides that can help you out if you want to know how these work:

Common Pitfalls

There are also some common pitfalls regarding BBCoding and how it is utilized. Most of these by solved by viewing your guide through the eyes of a reader.

1. Clean > Fancy

Do not aim for the fanciest guide right at the start of your journey. These are often guides that overuse text effects, have extraordinarily large images . They totally forget that although these things look sparkly and fluffy, it doesn't really make your readers happy.

It often takes a lot of time and effort to reach great results.

2. Lack Of A Theme

All the very good looking guides have one thing in common: they all have a particular color scheme/coding style they adhere to, which remains the same throughout the guide. This again is a pitfall of many authors who try to make their guide look fancy: they slap many colors/coding styles together, but it just doesn't fit together. Make sure you adjust the colors of any templates you use and also make sure you have a cohesive color scheme.

Quoting an Jovy, an artist & creator of clean & neat guides: artist:

Choose a color scheme before you start anything and stick to it

Of course, if you're just starting out with guide writing you may still be trying to figure out how to write stuff. However, once you get a little more used to it, you should definitely start looking out for this one! If you're looking for cohesive colors, check out this site.

3. Lack of Structure

This is more or less tied to the content of your guide. In some cases people tend to list their chapters in very strange orders. It's kind of a no-brainer, but it still happens a lot (pros & cons at the bottom of the guide, anyone?...). Although this doesn't affect the content of the guide itself. Weird chapter orders WILL confuse your readers.

This also goes beyond the chapter order. Once your guide gets larger and larger, you should start thinking about subchapters. And you give these subchapters headers. Imagine you expand your village to a major sized town. You'll need more signs to explain where you are right? The same is true for guides, having headers that indicate what you're talking about will make life so, so much easier for your readers.

Custom Images & Banners

One thing you'll see in many guide is banners. These just help so much breaking up text in the guide and don't look as boring as the usual chapter header. Most of the time people make these themselves using programs such as Photoscape, Photoshop or Krita. When you do end up making these yourself, be careful with the font you choose. Make sure it fits with the theme of your guide and that it supports all the characters you plan to use.

You can also spice up other things like item images, rune images, whatever your imagination leads you to! If you have the ability to do this, it can yield great results. If you do not have that ability like me, there are still other ways to achieve good results!

What do you know about your champion that others don't, but should know?

Perhaps you wondered why all those things I listed in the Guide Content were supposed to be in the guide: it's because they are needed for the question up here. This can be exploited on many different levels:

For people who never played the champion
For people who casually play the champion
For people that main the champion

Obviously, you need to be on the next 'level' to explain the former. There is a good reason why some of the very best guides on this site are made by onetricks...

And that's also how you can take your guide to the next level guide contest level. Once all the necessary subjects are covered, authors often expand into gameplay knowledge. Champion specific gameplay knowledge > generic gameplay knowledge. Take for example roaming, there are a lot of generic conditions attached to this. However it makes a significant difference whether you are playing or ... There are lots and lots of video's and guides to be found on these general subjects, but few on how to utilize them on specific champions!

Then there are specific ability caveats. Take 's , how many of you think it's "just pressing R"? Let me tell you, it is not. And I actively try to show that in my guide. These are bits of information are worth a lot. Do not fall into the trap of immediately thinking "But this is something you'll learn once you start playing games with the champion". Guides are a way to transfer your knowledge to others, this is part of that knowledge!

If you genuinely don't know what to add anymore: There is a Guide Review Application Thread and there are also some other review shops, where you can ask for feedback. You can also look at other guides contest winning ones are usually a good bet. Or you can just play the game and pay attention to what you're actually doing, perhaps you'll get an idea ;)

Keep in mind what it is all about though: What do you know about your champion that others don't, but should know?

Relevancy

When going beyond, it is important to keep relevancy in mind. Any advanced topics might no longer be relevant due to League of Legends being a non-static game. After you create your guide, you need to maintain it. If you do not it'll just become outdated after a while or some topics won't make sense anymore. A few things you will have to keep track of:

Champion buffs/nerfs (Ability numbers, playstyle changes)
Item & Rune changes (buffs, nerfs, removals)following the meta
Other changes (New champions & mechanics)

What can also help a lot is to watch high elo VODs of people playing your champion if it's off-meta this will be a bit hard. You can find these for example on LeagueOfGraphs, Youtube or even through the client. These can also be a great help for finding new content or checking whether you know as much as you think you do!

We have reached the end of my guide on how to write a guide! Thanks a lot to you, my dear reader, for being here with me :) Hopefully I managed to tell you a thing or two about writing guides and good luck with writing them yourself!

As is custom, a special thanks to a few peeps:

Thanks to Silverman43 for explaining how to make gradients art isn't my thing I rather stick to tables.

Thanks to Maintained for pointing out some common mistakes.

Thanks to TheBlueImperial for ~~nagging about bad ADCs~~ being there as a friend.

Besides that, if you wonder about another topic that isn't covered here or anywhere else, let me know! If you think anything is lacking, just comment or something, I cannot add things if I don't know they're missing!

Changelog