Старайтесь комбинировать Нескончаемую погоню с Пронзающим светом - это позволит вам резко увеличить урон по цели.
Взрыв Обжигающего пламени имеет форму звезды. Старайтесь использовать его так, чтобы лучи задевали вражеских чемпионов.
Благодаря умению Стрелок света, Люциан получает больше пользы от силы атаки, чем от скорости атаки.
Во время Отстрела вы не можете менять направление стрельбы. Выбирайте правильный момент!
The stat comparisons shown on this page highlight several vital Люциан versus Сетт matchup stats that can help us grasp the distinctions between this set of champions. Люциан’s KDA ratio ([kills + assists] / deaths) of NaN is better than Сетт’s KDA ratio of NaN, highlighting that Люциан may be more central to his team's team fighting potential than Сетт..
Люциан usually has a slightly larger longest kill spree than his foe does. Typically, he takes less damage than Сетт. This often reflects different amounts of tankyness, but it can also imply that the champion with increased HP has less agility and thus is unable to escape further harm when poked or engaged.
Both League of Legends champs are great. Both have their pros and cons. In the game's current meta, Люциан usually loses when playing against Сетт, with a 48.6% win rate. Thus, Люциан makes a poor counter to Сетт.
While Люциан does have a lower win rate than Сетт, when on opposite teams, Люциан also has a much greater learning curve that makes him a more difficult champion to pick up and master. You should be careful when picking Люциан into Сетт.
Additionally, Люциан has almost no amount of CC and other utility, a similar amount to Сетт. This makes her just as valuable during teamfights, especially when fighting champions with a lot of burst damage.
While there isn't a single best champion overall in League of Legends, in Люциан vs Сетт matchups, Сетт is the better champ with a lower win rate, more champion depth, and a similar amount of utility to help out your allies during teamfights.
Люциан is a somewhat poor counter to Сетт. Make sure you focus your tactics on maximizing your CS and taking out objectives. If you are able to do that, you should be able to stand on your own as Люциан against Сетт.
If you would like to learn all of the intricacies of Люциан to counter Сетт during both the early game and mid / late game phases of League of Legends, you should continue reading to learn a few extra tricks and insights into this matchup. If you pay attention to the build and tips presented here, you will grow your win rate by a lot and be closer to League of Legends pro players.
Люциан often picks up a similar amount of CS compared to Сетт. Champs who typically don't earn many minion kills typically don't have to have much CS to be effective, such as supports. These kinds of champions are able to scale well off of their abilities and first items alone. Yet, champs with large amounts of CS, such as hyper-carries, typically need several high cost items to be effective. In either case, try to do better than the values shown on this page to do well.
The ideal items to use in your Люциан versus Сетт build consist of Ангел-хранитель, Убийца кракенов, and Быстрые клинки Навори. When Люциан bought at least these three pieces in his build, he performed a lot better against Сетт than with many other typical item sets. In fact, Люциан boasted an average winrate of 48.6% when playing against Сетт with this build.
To have the best probability of annihilating Сетт as Люциан, you should equip the Решительное наступление, Присутствие духа, Легенда: родословная, Удар милосердия, Магическая обувь, and Доставка печенья runes from the Точность and Вдохновение rune sets. Out of all the rune builds players used for Люциан vs Сетт counters, this sequence of runes resulted in the highest win rate. Moreover, these runes provided a 48.6% win rate overall.
By default, tips, stats, and builds on how to beat Сетт as Люциан are given for all skill levels combined. If you would like to narrow the stats and builds to an individual rank, you may use the selection menu located earlier on the page.