The Guide Guide

[[Poni]Octavia]

This page exists for those of you who want to become guide authors, but are perhaps a little intimidated by the amount of effort required into creating a high quality teaching resource. I'm also making this in the hopes of us getting not just a higher quantity of guides, but also a higher quality of them. The sections of this guide are mostly not in a chronological order, so you can think of this as a reference page or manual to guide making; you don't need to read the previous sections for the other sections to make sense.

________________________________


The Guide To Making Guides || The Guide Guide

Table Of Contents

1. Introduction & Table of Contents
2. First Things First
3. Editing
   
   • Editors
   • Layout
   • BBCode
   
   
4. Content
   
   • Justification
   • Feedback
   • Quantity
   
   
5. Grammar
6. Media
   
   • Pratice Mode Tools
   • Images
   • Animations
   
   
7. FAQ
8. Credits

________________________________


First Things First

This may seem like a relatively obvious thing, but you need to make sure you have a good understanding of exactly what your topic is. If you're going to be sharing your knowledge with people, make sure it is good knowledge. If you don't have that knowledge, perhaps it is not the best idea for you to be attempting to tutor others on the the subject. This doesn't mean that you need to have some arbitrary level of PSR / MMR to display your prowess, but it does help to have sufficient support from successful experience; the experience doesn't have to be yours, but if you want your guide to have credibility it should be able to be endorsed by people who are successful on a practical level.

Once you've got that out of the way, the first thing you should ever do when you are planning on writing a guide is to make a Table of Contents. If you ever looked at any of my drafts as they were in development, there was an always almost complete Table of Contents before any actual content even existed. Having an outlined Table of Contents helps you get a good feel for where you should be writing what. It's very easy to briefly cover every single topic in your guide in a few paragraphs, and then you end up somewhat repeating yourself excessively by going over the same topics twice under a different header; repetition for the sake of emphasis is perfectly reasonable, just make sure you're making concious efforts to maintain fluency and structure in your guide.

Remember that writing a good, high quality guide will take a reasonably large amount of time. I would estimate that for most people, a really good premium quality guide would take up to 10 hours to create. Along with that, once the guide is created it is your responsibility to maintain its accuracy with the release of new patches.

Also I strongly believe if you are not going to put the effort into updating your guide for new patches, then don't bother writing it in the first place. The amount of out of date guides we have already is ridiculous.

This isn't much of a problem with gameplay guides, but for hero guides this is a big issue due to the constant changes being made. If you can't continue updating your guides for some reason such as if you are planning on quitting HoN, it would be really cool if you could give permission for somebody else to repost and continue updating your guide. There are a number of really good guides that have been chucked into the archive due to being outdated, when only half an hour's work could bring them up to scratch.

________________________________


Editing

This section will explain the things you need to do to maintain a neat looking guide. Most of the things in here are largely my own opinion, but I believe most people can agree with the way these things will improve the quality of your guide.

Editors

You have to have something to edit your information with. For most people, using the editor on the forums is sufficient. The benefits of the forum's editor is there are a few buttons which can automatically add a few BBCodes for you. There is also the added bonus of the forum editor having a What You See Is What You Get editor for any modern browser that isn't Chrome. While this may seem like a good convinience for most people, I really implore that you do not use the What You See Is What You Get editor on the forums. The main reason for this is that you end up with extremely messy code, and that the default colour for the forums is not white. This means that if you change the color of your font and then try to change it back to white (because you can't just type '[/color]') you will end up with random parts of your article having slightly different colours for your content. This also applies to resetting any variable back to default, as you end up with extremely messy code.

Here's an exerpt from a_cloth's Predator Guide:

Wait till he ults then use Stone  Hide [/SIZE][/COLOR][/COLOR][/SIZE][/COLOR][/SIZE][/COLOR][/COLOR][/COLOR][/SIZE][/COLOR][/COLOR][COLOR=Red][COLOR=White][SIZE=5][COLOR=Red][COLOR=White][COLOR=Red][SIZE=2][COLOR=White][SIZE=5][COLOR=Red][COLOR=White][SIZE=2](Removing  the Root)[/SIZE][/COLOR][/COLOR][/SIZE][/COLOR][/SIZE][/COLOR][/COLOR][/COLOR][/SIZE][/COLOR][/COLOR][COLOR=Red][COLOR=White][SIZE=5][COLOR=Red][COLOR=White][COLOR=Red][SIZE=2][COLOR=White][SIZE=5][COLOR=Red][COLOR=White][SIZE=2] and  chase - an example of debuff removal

Which when interpreted will look like:

Wait till he ults then use Stone Hide (Removing the root) and chase - an example of debuff removal

Messy code is extremely difficult to deal with. The WYSIWYG editor makes messy code and creates a lot of problems that aren't easily dealt with. For simplicity's sake, don't use it (please!).

One of the biggest things that will piss the living poop out of you with server side editors is if you've written a huge update to your post and then something bad happens. Maybe the forum server dies, you got a power cut, your computer BSODs out of nowehere, your internet dies or your modem is thrown to the floor by your cat; anything can happen that could cause you to lose your work. If you use a client side editor and periodically hit the CTRL+S button, you should be able to avoid losing much of your work in any of the previously mentioned events. With that covered, editing your guides on the forum also has the issue of being inside of the tiny forum box. This wastes horizontal space on anybody's computer with a width greater than 600 pixels. This is a minor thing, but it nags me to the point where I'd rather edit something with a program that works entirely client side.

So if you're not using the editor on the forums, what can you use? Well, pretty much anything. You could use Microsoft Word, Open Office, Notepad or even Wordpad. It doesn't really matter, but a spellchecker of some kind can certainly help. Personally I use Notepad++ due to it not wasting any of my screen's space with bloat, the fact that it has tabbed file management and it re-opens everything you had opened last when you closed it.

Layout

Creating a layout that is both unique and readable is one of the biggest challenges that people face when creating guides. There is a lot of room for flexibility regarding this topic, but I would strongly recommend that you follow this list of guidelines to create a readable post.

• Think of a colour scheme that suits the content in your guide. Colours make your guide prettier, and in combination with a good distribution of images will make your guide easier on the eyes and more than just a giant wall of text.
• Maintain consistency with your layout. If you are using size 5 "Lucida Sans Unicode" for all of your sub-section titles, don't throw a sub-section title in with size 5 Verdana for no reason.
• Indent all of your body text. Nothing is more ugly than guides that don't indent their body text (See: LegoPirate's Swiftblade guide).
• Do not center body text or lists. Centering body text and lists is really difficult to read as the first letter of each point on the list / sentence is in a different spot. A lot of people for some reason think this looks nice, it doesn't. Please stop centering your body text and lists.
• Sections of your guide should be easily distinguishable from quick scroll throughs. Make sure your titles are clear and dissimilar from the rest of the content. This is easily accomplished by putting the titles on a different indent, and giving them a different font, size and/or colour. Readers should be able to see when a section begins and when a section ends just by scrolling through.

The forum has a relatively decent variety of fonts to use. I highly suggest that you stick with the default font for your content. Changing the style of the font for the body content in your guide to something slightly more obfuscated than the default is really quite obnoxious; you don't need a unique font for your content to make it look nice. For titles, I would suggest either Lucida Sans Unicode, Frutiger or Arial Black. If you want monospaced font, use Lucida Console. For a comical font, use Comic Sans. As far as fonts are concerned, it is very important that you don't over-do it. Like stated earlier, the default font is absolutely fine for any of the body content. For reference, here is a list of all of the fonts you can use in the forums.

BBCode

A complete list of all of the BBCode's usable on the Heroes of Newerth forums is located at http://forums.heroesofnewerth.com/misc.php?do=bbcode.

Bold, Italics and Underline

http://forums.heroesofnewerth.com/mi...o=bbcode#basic
These are your standard emphasis mark-up codes. Different types of emphasis work for differen't people, just don't overuse it. If you emphasise everything then nothing will actually be emphasised.

Colour

http://forums.heroesofnewerth.com/mi...o=bbcode#color
Colours help give flavour and theme to your guide. In Heroes of Newerth, red, blue and green represent strength, intelligence and agility respectively. Remaining consistent with colours is important so that your guide looks orderly, well constructed and has a distinct theme.

Size

http://forums.heroesofnewerth.com/mi...do=bbcode#size
Different sized fonts allow you to make certain things stick out or remain subtly in the background. The default size is 2. The maximum size is 7. Small notes can be written with smaller fonts and titles should be written in larger fonts. Subtitles can be made slightly smaller than titles to distinguish the two from each other.

Size 1
Size 2
Size 3
Size 4
Size 5
Size 6
Size 7
Default

Font

http://forums.heroesofnewerth.com/mi...do=bbcode#font
Different styles of font, like colour, give theme to your guide. I highly recommend maintaining the default font for all of your body content, as it is simple and easy to read. Using a fancy font for your content only takes away from your guides readability at the cost of fanciness. Remember that the main point of your guide is to present information, not to impress the reader with your cool looking fonts. I don't want to have to squint to read your content.

I won't personally give you any feedback on your guide's content if you insist on using an unbearable font for your content.

Alignment

http://forums.heroesofnewerth.com/mi...o=bbcode#align
Alignment allows you to place certain blocks of information in a different location to others. This is where a lot of people can really mess guides up, specifically regarding centering of text. Most of your guide should be left aligned because that is how every single piece of published English writing is ever written and it is how most people are used to reading. Center aligned stuff spread around your guide for no reason does not add any substance to your layout, it just makes it harder to read. Right aligned things will barely ever appear in anything aside from notes that you want put off to the side.

Indenting

http://forums.heroesofnewerth.com/mi...=bbcode#indent
Indents are good for separating different blocks of writing from each other. Good use of indenting will give good pacing to your layout and make different sections easily distinguishable from each other. Indents inside of indents make double idents.

Lists

http://forums.heroesofnewerth.com/mi...do=bbcode#list
If you use a list inside of a list you will get an indented list (See: Table of Contents). Numbered lists are good for skill builds, bulleted lists are good for notes and alphabetical lists are good for optional things, i.e., do a or b.

Spoilers

http://forums.heroesofnewerth.com/mi...bbcode#spoiler
Spoilers are one of the most useful tools for your guide formatting, because they allow you to add a lot of extra detail to your guide without compromising the brevity of it. People who don't want to read the specifics can skip through without scrolling through pages of fluff and get to the real important stuff. So, what should you put in spoilers you ask? Skill descriptions, item descriptions / tooltips and anything else that isn't necessary. I would advise against using spoilers on images; if your images are taking up so much space that you need to spoiler them you should consider making them smaller or getting rid of some of them. You can fit a lot of information in one image.

Conserving your vertical space helps keep your guide concise, so do so diligently.

________________________________


Content

Content is the reason you're writing the guide, and good content is what will make or break your writing. It won't matter how pretty your formatting looks if you don't have anything worth reading inside of it. Good content requires more than just knowledge, however. It is remarkably difficult to write down in understandable and brief terms all of the experience you need to express. Opinions on things can change pretty easily, and the chronology of your guide can easily mess up; it is important that you can root out any contradictions in your guide.

If at any point in your guide you find yourself writing something that you don't quite agree with, do not simply ignore it or throw it in your guide haphazardly. Misinformation will only degrade the overall quality of your guide. If you are unsure about a certain aspect of your topic, you should have very generalised information such that it can interpreted more broadly and not be so definitive, or you should be analysing and asking for as much feedback as possible on the topic at hand. You will almost surely find yourself learning new things as you write your guide, since knowing everything about your topic is highly unlikely.

As the guide author, you may feel as though you are the most knowledgeable person on your topic. Remember that the only thing distinguishing your guide's information from anybody elses is that it is the first post in the thread and has neat formatting to make it look prettier. You can dress up poop as much as you want, it's still going to be poop. Yes, you do have full creative control over your guide, but if you want a highly acclaimed guide it needs to be largely agreed upon as being accurate.

Justification

If you have an opinion on something, back it up with logic and reasoning. The tournaments you've won or your reputation is not sufficient evidence.

This quote may be a little hard to really indentify with accurately at first, since it seems awfully demanding of you to present accurate logic to a subjective decision. 'Theory craft' in this game does not go awfully far; there's only so much that you can truly understand by merely thinking about the game. Creating indisputable logic for decisions you make in this game is extraordinarily difficult, and I don't expect anyone to be able to do so (nor have I seen a single post from anybody ever doing so). Evidence of theory crafting being horribly wrong can be seen by early beta posts regarding Helm of the Black Legion (See: http://forums.heroesofnewerth.com/sh...ad.php?t=19991 and http://forums.heroesofnewerth.com/sh...ad.php?t=30203). Both Fenald and Glorify had theory crafted 'logic' and in game experience to justify their opinions, but in the end as the game developed people began to realise that Helm of the Black Legion was in fact an incredibly strong item.

The most important things to cover with your justifications is that it directly relates to the rest of your guide and does not contradict playstyles. Making a Glacius guide telling people to build a tonne of fancy luxury items while focusing your entire gameplay section around wards does not make sense. If your hero has multiple play styles (Hammerstorm, Voodoo Jester, Slither) then you should have multiple sections for each play style. You don't need walls of text and math explaining why one thing is better than another, math can't compare two different things very easily. The most important justification for your opinions is that people agree with them. It doesn't matter how much theory, in game evidence and math you present—if everyone says you're wrong it's likely that you are.

Being right in theory craft is hard, and saying something is wrong is generally a bad idea since this game is very flexible. Most things can work, and item / skill build choices generally don't have as large of an impact on the game as actual gameplay choices (which is why good players like n0tail can go bottle first mid and succeed). This is extremely important when it comes to Boot choices for heroes. On well over half the hero pool, you can buy either Ghost Marchers or Steamboots and be successful; boot choice is very largely up to personal taste. You cannot compare apples to oranges, and the strength of Movement Speed can never be compared logically to the strength of bonus Stats and Attack Speed.

Feedback

When you write and publish a guide publicly it is going to receive feedback, and whether you like it or not, some of this feedback is going to be people disagreeing with you. Some people may be less constructive with their criticism than others, but what is important with this is that you consider the ideas in every single bit of feedback you receive. The means are irrelevant, what is important is the point being made. If you have people telling you that something is wrong and you refuse to acknowledge that, then your guide will not be at the highest standard possible. A guide is a collaborative work of a number of ideas, with you being the final composer.

Just because someone disagrees with you does not make them a troll. Most of the people who give feedback to your guide are being honest with their opinions; what those opinions are does not change the intent of them. You should respect feedback. Feedback is what allows you to see how people view your ideas. Feedback gives you the opportunity to improve your content and learn new things. If your ideas are viewed poorly, then you know that something needs to be changed. You must at all costs remain modest with your work. If you can't accept that something you have written is wrong, then it will be wrong forever.

Quantity

Only write as much as you need to.

________________________________


Grammar

If you use bad grammar in your writing it will make it look sloppy. Sloppy is bad, and bad is not good.

Read each and every one of these comics by TheOatMeal.

• http://theoatmeal.com/comics/apostrophe
• http://theoatmeal.com/comics/misspelling
• http://theoatmeal.com/comics/semicolon (Note: using conjunctions with semi-colons is acceptable in the same way that starting sentences with conjunctions is.)
• http://theoatmeal.com/comics/ie

Would / Could / Should have

Would of - Wrong
Would have - Right!

This error occurs because the phonetic sound for would've (contraction of would have) sounds like "would of". Would/Could/Should of does not make any sense. The definition of 'of' is shown at http://www.thefreedictionary.com/of. None of those definitions even partially resemble the meaning of 'have'.

I may add more to this, but this covers most of the basics. Remember to be conscious of sentence structure and to avoid run-on sentences.

[[Poni]Octavia]

________________________________


Media

Practice Mode Tools

All of the codes in here are activated by inputting them into the console, which you can open by pressing CTRL+F8 in game.

Recording Replays

replayrecordstart replayname.honreplay
replayrecordstop

Recording replays is good for creating a scene and then capturing it later. This way you can avoid having to do the mouse clicks while recording and can focus on the video angle you want to shoot at. It's also useful because you can pause the replay whereas you can't pause real time practice mode (although you can set the time scale extremely low). You can view the replays by clicking on the Local Replays icon in the top-left corner of the HoN interface.

Camera Manipulation

Zooming in and out can be done with the scroll-wheel, however there are default minimum and maximum values for the zoom range. To change these use:

g_camdistancemax value
g_camdistancemin value

The default value for the max camera distance value is 1650. These variables need to be changed if you want to take screenshots / videoes at extremely zoomed in or out distances. If you zoom out further than the draw distance, you will need to increase it with:

scene_farClip value

The value for scene_farClip should generally be about 1000 higher than g_camdistancemax.

To rotate the camera, hold the \ key and move the mouse around. To reset it back to the default position press backspace.

Game Speed

host_timescale value

The value is a multiplier of the normal game speed. Having obscenely high values won't give real-time increases to the game speed because of the way the engine works, so you can't get much higher than about 5x speed. Decimal values give reduced game speed (e.g., .1 will make it 10 times slower).

Images

Any decent guide is going to be required to have images in it to separate all the walls of text from each other (much unlike this guide, which I doubt anyone would read entirely in one sitting) and to give visual displays of things. Taking images is very simple. You can either hit the print screen button and save an image to your clipboard or you can press F5 and save an image to ~/Heroes of Newerth/game/screenshots. Note that this directory is different to the one that has all the game files in it, this is the directory that has your replays and other personal settings saved in it. Saving something to the clipboard is generally a bad idea because as soon as you copy something else you lose your image. If you want to take multiple images in a row then you'll need to use F5, because the basic clipboard can only have 1 thing on it at a time.

Once you have an image from the game, you'll probably need to add some sort of anotations. If you've never done anything with image editing before, stick with Paint. If you've used more complicated programs then feel free to use them. If you're using paint you lack the feature of layers, so it would be a good idea to save backups of your original images before you started editing them.

To get your image on the internet, I suggest you upload it to http://www.tinypic.com. Tinypic doesn't have bandwidth limits and images don't expire, so you won't have to worry about your images randomly disappearing.

Animations

Making .gif animations for your guide can add a lot more than images. If you want to show off execution of a skill then an animation is the best way to do it.

You'll need to use a few 3rd party applications to do this, and some of them are licensed software (meaning that I can't tell you specifically where you can download them for free) and they mostly only run on Windows. The programs I use are:

• FRAPS - Proprietary
• Sony Vegas Pro 9.0 - Proprietary
• GIMP - Open source & free

Step 1

You need to record your footage with FRAPS. Your settings for FRAPS should look like the following.

The important things that are changed from default are:

• Frame rate is set to 10 - This is because that is the frame rate GIMP likes to make animations at
• Video capture key is changed - The default button F9 opens up a diagnostics window in HoN, which makes your recordings look clumsy
• Half size - Your gifs aren't going to be high quality so there's no need for a full size recording.
• Hide mouse cursor for obvious reason.

Once you have recorded the footage with FRAPS you need to throw it into a Non-Linear Editing Program to make into an image sequence. I'm going to be using Sony Vegas for this tutorial.

Step 2

Open Sony Vegas Pro and start a new project with the following video settings:

The important thing is that the frame rate is set to 10, and that the resolution is set quite low, you don't want the filesize of your animation exceeding 5mb.

Import the footage with this button:

Drag it onto the video track and clip off the bits you don't want. It's a good idea to make sure the length of your animation is short, if it goes for too long (more than 10 seconds) the filesize will be way too big. Once your storyboard looks the way you want it to go to File -> Render As and you will get the save as dialog box. Under "Save as type" choose "Image Sequence", this will save your video as a series of images. Note: this will make a large amount of files, I'd suggest that you make a folder somewhere specifically for these files because you will be getting 1 file per frame. Once that is done you will have an image sequence for your animation, and you will now proceed to make your animation with GIMP.

Step 3

Open up GIMP and select File -> Open as layers. Highlight every single one of the images in your image sequence and click open. You should have a full image sequence of every one of your frames now loaded into GIMP. Go File -> Save as and you'll get this little dialog box (if gif isn't already selected, select it from the drop down menu):

Once you click save you'll get this dialog box, which should be filled in like so:

Followed by:

Once you click save, your animation should be saved and ready to be uploaded. Like with images, use http://www.tinypic.com to upload them. The filesize limit is 5mb, so make sure your animation's filesize doesn't exceed that.

________________________________


FAQ

What are the requirements for a Premium Guide

To meet the minimum requirements for consideration, your guide should contain the following (where applicable):

• Detailed descriptions of the hero's skills, including what your skills do, hero build order, how/when to effectively use your skills, how they interact with team dynamics, and how they scale early/mid/late game.
• Detailed descriptions of item builds on your hero. What items are most effective on the hero. Different build options (e.g. carry vs support build). Early/Mid/Late game items. How your items interact with team dynamics. Cost of items.
• Hero role - How do you play the hero in a lane. How do you jungle the hero. Should you be farming? Ganking? Supporting? What the role of the hero is early/mid/late game. How does this hero interact with team dynamics.
• Strengths and Weaknesses of the hero. Which heroes are you strong/weak against. What type of overall team strategy best suits this hero (e.g. push strat, turtle strat).
• Links to a replay of you demonstrating the effectiveness of your guide in a non -EM game.
• Screen shots of abilities (e.g. Pestilence's stun with an MS Paint circle highlighting the AOE)

Gameplay guides have less structure, but should be appropriately comprehensive to thoroughly describe the topic.

These things are required of a Premium Guide, however these things do not make a Premium Guide. Your guide must be of outstanding quality and be generally well accepted to be considered of Premium quality. If you would like to recommend a guide to be Premium send a PM to Drasha.

________________________________


Credits

• Myself (a.k.a. RogerDodger)

Thanks for reading this guide. Any feedback is appreciated. If you would like to request feedback on one of your own guides post in this thread and I'll get around to it when I can, a full analysis of a guide can sometimes take me around an hour (depending on how big your guide is), so don't expect it to be immediate.

[Drasha]

I highly recommend this guide to any one trying to write a premium guide. Odds are if you submit your guide you are going to be linked to this thread any ways.

[[S2]ElementUser]

There's one called d_drawareaaffectors too.

This one shows most affectors' AoE (doesn't show zero-duration affectors, non-linear affectors or projectile touch radii)

[[BWR]mega_manuel]

I tried my best but im not a good writer, can you please tell me tips so i can get people to read it and use it?

[[GM]Okuu]

Read it, might try and start writing a little guide for fun, then focus, gather, and write a more serious one that I'll PM Drasha

Thx Roger

[[TOPS]SlowKing]

Read it and it made me want to write a guide myself it was so impressive.

On a side note, there is a spelling error in this paragraph under step 2 of Animations:

Drag it onto the video track and clip off the bits you don't want. It's a good idea to make sure the length of your animation is short, if it goes for too long (more than 10 seconds) the filesize will be way too big. Once your storyboard looks the way you want it to go to File -> Render As and you will get the save as dialog box. Under "Save as type" choose "Image Sequence", this will save your video as a series of images. Note: this will make a large amount of files, I'd suggest that you make a folder somewhere specifically for these files because you will be getting 1 file per frame. Once that is done you will have an image sequence for you animation, and you will now proceed to make your animation with GIMP.

[[S2]ElementUser]

Fixed his typo

[[E]Marach]

another typo you can fix under the 'Animation' section (2x):
Proprietry -> Proprietary

[[MsG1]ObeseSheep]

Great guide. I need help through. I want to use tiny pic. But when I try to make an account, it tells me to make a photobucket accout. I have one. So then I login to my photobucket. Then when I try to make a tinypic account, it just sends me back to photobucket. So then I tried loggin into tinypic with my bucket account and it doesn't work. AAAAAAAAGR

I want to reduce the size of my images (they are f in' HUGE, page can take long time to load.). I don't want to do all that work only to have imageshack screw me. I want tinypic ARRGRGGRGRG.

[[Poni]Octavia]

You don't need to login to tinypic. Just upload an image.

The only issue with the site is that some of the ads have audio.

[[MsG1]ObeseSheep]

You don't need to login to tinypic. Just upload an image.

The only issue with the site is that some of the ads have audio.

Not the only SMALL issue. I don't want to upload up to 30 images one by one. =( Pls help.

[[Poni]Octavia]

I don't know of any image hosting services that let you upload multiple images for free + unlimited bandwidth. That stuff is normally where they start charging .

Just gonna have to do it the tedious way I reckon.

[[MsG1]ObeseSheep]

I don't know of any image hosting services that let you upload multiple images for free + unlimited bandwidth. That stuff is normally where they start charging .

Just gonna have to do it the tedious way I reckon.

AAAAAAAAAARGGGGggg.... =( Thanks anyway. q.q

[[E]Marach]

I don't know of any image hosting services that let you upload multiple images for free + unlimited bandwidth. That stuff is normally where they start charging .

Just gonna have to do it the tedious way I reckon.

haven't tried it myself, but heard good things about:
http://imagevenue.com/
&
http://www.imgplace.com/

they both should support multiple file upload.

[[S2]ElementUser]

I've used imageshack for a long time and they haven't charged me anything yet

[Jezu]

^ Same, although also used tinypic, but mainly imageshack

[[MsG1]ObeseSheep]

Image Shack is us only.

You organize your hero guides differently than I do. For each skill, you give the facts then talk about how to use them. Same with items.
Fact
Usage
Skill
Usage
Item
Usage
I do it in sections.
Items
ALL ITEMS.
Then usage.
Etc.

What do you think?

[Jezu]

Image Shack is us only.

Im EU and I use it for free...

[[MsG1]ObeseSheep]

Im EU and I use it for free...

I heard that it's only US. My bad.