Vi Build Guide by

✔️ How to smash Rocks

2033 59

3,608,821 Views

128 Comments

League of Legends Build Guide Author Fruxo

Vi Build Guide By Updated on

Guide Discussion (128) Reviewed (2) More Vi Guides

New Comment

You need to log in before commenting.

(101) |

please click!

Hey! I'm Katasandra, one of the local Scouts. I have come here to review your guide, you requested one a while ago and I have to test my new template :p Please tell me what you think! I'll try my best to give pointers on what areas you can improve your guide on. I hate just saying 'this isn't good', and I'll try my best to give advice on how I would improve certain things (as if it were my own guide).

How does it work:

I'll go into three 'main' topics: Content, Language/Writing and Coding/Visuals. I believe all three are core ingredients of a guide. Just knowing your champ is not enough. You also have to make sure you can actually convey all this precious knowledge to your readers!

I'll specify these categories as well as some subcategories and for that I'll use the following rating system:

rating system

Content

Due to my limited knowledge about champions other than Lissandra. I'll mainly focus on the presence and explanation of content rather than talking about whether it is viable or not.

>Cheatsheet: Pretty good

Overall solid, but I don't like the control ward monologue within the notes. If you really wish to stress the importance of vision in your notes I'd put it at the end instead of in front the explanations of Oracle & Farsight.

I'm slightly confused by the two possible builds (assassin/bruiser) is this game dependent or is it just preference? There's also a slight mistake in the notes at , it is actually impossible to build if you already have Maw (try it in practice tool).

>Setup (Runes/Items/Summoner spells): Pretty good

About the runes: I'm fairly suspicious that the choice of hunter runes are based on preference rather than game. Nonetheless, if that's the case you should mention it (can even be done at the top where you talk a little about in general).

The distinction between bruiser / assassin build is completely gone in the items section. Even worse, they're all thrown together and the explanations also do not reflect what build they belong to. If I had to point at one thing in your guide and say you have to fix this, it's this.

>Champion (Abilities/Tips&Tricks/Combo's): Godlike

>Gameplay: Godlike

Of course, you could always re-add matchups. But since the rest is so extensive I think it already reached the heights of godlike ^_^.

Code/Visuals

> Execution: Pretty good

It's perfect, except for one section: The items section. Especially in the "Other items" part, the heap of lighter green lines being cut up by the black background gets very heavy on the eyes. Combined with the issue mentioned in the content part above, I think it may be a better idea to revisit the code of this section altogether.

Also good job on the mobile-friendly coding, seems to be working everywhere!

>Cohesion (same coding style used throughout guides): Godlike

>Theme of guide (color scheme): Godlike

Writing/Language

>Spelling/grammar: Godlike

Okay, I didn't read all of it (I can if you wish, just reply in that case). But aside from a few capital letters in the cheatsheet notes I didn't find errors in the parts I read.

>Paragraphs/Sentence length: Pretty good

Your usage of paragraphs is fine, but sometimes sentences stretch towards/slightly go over the limit (which I tend to set at 30 words). In the past I would point all of em out, but it just takes too much time unfortunately. I recommend sifting through your guide sometime and critically look at the long sentences. Ask yourself if they can be split up or whether some parts can be left out.

>Overall writing: Godlike

Overall thoughts

Your guide still holds up very well, good job on keeping it updated and gradually improving it over time! Or rather: managing to keeping it at the same level for a longer time period. I know how hard that can be. Although this review isn't as long as my older ones I hope it's useful to you anyway :D

And (of course ;) ) a very late +Scout. It's deserved.

(33) |

You cannot build Malmortius and Sterak's together because they are both considered Lifeline

(326) |

You have to pay attention to when this review was made, it was a year ago. I am aware that Sterak's and Malmortius cannot be built together as they share the same passive, which was highlighted by this review.

Load more comments (2 more replies) →

(33) |

I was trying to point out this fact to anyone reading the review, in order to clean up any confusion. Really sorry if my comment flustered you! Was just trying to help people from the future (even if the review is very very old) because the review has a really flashy design

(326) |

Which is entirely fine, but as I said this was already highlighted within the review. There's really no need to clear up any confusion as there was none. Due to it being impossible to build them together it shouldn't take too long to check their passives and realise they're the same description and does the same thing.

I appreciate it, but not really necessary.

(326) |

Hey Katasandra! thank you a lot for the review, it's very helpful. :)
I think your new template looks great!

Apart from that, here are a few of my thoughts:

my thoughts

(101) |

Hey Fruxo, thanks for the quick reply! Excited to see what you'll come up with for the items section (eventually). Also thanks for the feedback, I'll continue to use this template for now :p

(87) |

Henlo FRUXO! Ya big cutie you. I saw you requesting a review of your guide on the forum and on Discord, so here I am! These are going to be the things that we are going to be looking through ideally with this review. STRUCTURE: This is basically how you code, place and use code from a tidy and neat viewpoint. CONSISTENCY: Basically how often you switch things up. Some parts might be a mess and others great. INCLUDINGS: These are things that could be added like Runes, Items, Matchups or entire sections. MY CONCERNS: Things that I find not really interesting to apply to a guide or just filler.
This section of ones guide as you know should be both detailed and easy to read without being too overwhelming. You have notes on your runes and your items, it's straight forward, simple and isn't too much of an overwhelming sight like some people have in their guides. Though one thing I would try to add if possible would be your ideal first back choices. While I know you are Vi and playing Jungle with more freedom to extend longer before backing to base, some helpful tips for new players would be great like... Example: if Teemo top builds Blasting Wand he now has access to x5 items where as Recurve Bow locks him into Nashor's Tooth so there is no sense of diversity. Something like... "First Back: Boots and (x) item are ideal." It just gives newer players a sense of priority. Similar to how Teemo "needs" Recurve early game in the jungle to help him clear faster to make it through early game while jungling. It's an optional choice, but I could see this as beneficial to again, new players! That's the only issue I see here in your items section! Overall, very well done on the information provided in this section. It'll be up to you if you decide to make those chances!
As you may know this next section is the "cheat sheet" portion of the guide right below items and runes. You'll want to at the very least put some basic information in here even if you plan on adding a Matchup section, rather than directing everyone to your sections. Same thing with ideal champions that benefit with having Vi on their team. Most people don't want to scroll and look through information, they just want simple brief information now, like "Extreme: Because they are really strong." so they can make the right choices for banning or avoiding this champion into them.
Beautiful. It's a very nice fit for Vi the green fits the theme very well. Everything is coded well and you have a very good structure throughout MOST of the entire guide. (I will go into more detail below so bear with me.) THIS is more of a pet-peeve thing. I like things to connect well. Neatly (OCD) so when I see a box that can be extended more to match with the box right below it width wise, in this case the Flash box, I would recode it to be a little. Doing this would also help space the text and images in the box to not squish together and break flash/smite off from the text. I will add one thing I noticed, you use radius curves on your imagery, but not your icons for items. Unsure if you meant to, but I think it would match the rest of the guide, once again all of this advice is simply my opinions, it might look like poopoo, but I like the curves. THIS part is where the consistency breaks and feels like it doesn't belong. I understand what you were trying to go for, but it would be best to keep the guides theme of green here as well. That is my personal opinion, you can keep it if you wish, but I really liked the green theme and love it when things stay consistent. It feels harsh in this spot. The structure once again, for me, personally breaks up when you reach your route section HERE and onward to the bottom of the guide. I don't like the thrown in reds, yellows, purple/blue (PsiGuard) as you can just easily use imagery or make the text a little bit more bigger / bold. Besides this, I don't see any other problems with structure.
You've got a good guide. In my eyes there really isn't much wrong with it, besides the things I listed above. You have decently good consistency throughout the entire page besides those few spots. I would also like to see change-logs in spoilers as they can get really long and tedious filling up the entire screen for people when the only thing that should be shown would be immediate recent changes, not changes from 2020, with the option to dropdown the rest. Don't punch me! ~Cat
It's not often I bother scouting, as I am a hard nut to crack when it comes to presentation. This is one of the best looking guides I have had the privilege of looking at, it's gentle on the eyes, it's informative and has great use of code & would be the first guide I would look at not because of ones RANK but because of ones effort put into it. You've done good Fruxo.