그림자 공격은 탈출할 때 유용한 스킬이지만 여러 명을 공격할 때에도 유용하게 사용할 수 있습니다.
적 뒤에 자리를 잡고 녹서스식 외교의 근접 공격을 시도하고 싶을 때 암살자의 길을 사용해 보세요.
전투 전에 미리 공격 대상을 선택해두십시오. 탈론의 모든 스킬을 하나의 대상에 집중시키면 최고의 성과를 거둘 수 있습니다. 스킬을 분산시켜 사용하면 위험한 상황에 처할 수도 있습니다.
프리즘 보호막 사용이 어려운 경우 보호막은 최대 사거리에 도달하면 다시 캐릭터에게 돌아온다는 사실을 참고하십시오. 보호막이 돌아올 때 아군을 맞힐 수 있도록 이동하십시오.
럭스는 시야 밝히기, 범위 둔화 스킬 등 일정한 지역에 영향을 끼치는 데 유리한 챔피언입니다. 적의 돌진 또는 탈출을 막으려면 광휘의 특이점 스킬을 사용하십시오.
광휘의 특이점 스킬은 정찰에도 유용합니다. 수풀로 들어가기 전에 이 스킬을 사용하여 적의 유무를 확인할 수 있습니다.
The 탈론 럭스 synergy stats shown here demonstrate the areas of his gameplay that do better (or worse) when paired with 럭스, compared to his overall stats. Significant differences are areas of focus that highlight how his gameplay changes when paired with this other champion.
Overall, 탈론 sees a very large drop in his KDA (ratio of kills and assists to deaths) when paired with 럭스. His KDA fell from NaN to NaN. This decrease shows that 럭스 helps 탈론 perform worse in competitive LoL rounds. Yet, the small difference shows that this performance change is not very impactful.
When 탈론 is paired with 럭스, he sees a little drop in his total damage dealt. This difference could signal that 럭스 does not support by providing protection for him to deal more damage or that her support also helps increase the game's duration. Similarly, when 탈론 is played with 럭스 on the same side, he usually scores many fewer killing sprees than when he plays without 럭스. This is contrasting evidence that he is worse when playing alongside 럭스.
Moreover, when 탈론 plays with 럭스 on the same side, he on average takes a little more damage than when he plays alone. Receiving more damage may mean that 럭스 does a poor job of covering 탈론 in teamfights.
There is no perfect champion pairing for 탈론 that will no matter what be his #1 teammate. Yet, 럭스 is a below average companion for 탈론. By locking into the same team as 탈론, she drops their win rate by -1.3% to 47.7%. This clearly indicates that there is a bad bond between 탈론 and 럭스 that results in them performing not as well together than alone.
럭스 has a lower difficulty than 탈론. That means you don't need to be very careful when enlisting 럭스 allies to fight alongside, as they will require a relatively low level of skill to be able to do well with you.
When playing on the same side, you should expect to observe an overall large increase in your team’s capability to destroy wih physical damage. When paired, these champions can tear through the other team with a lot of physcial damage.
Conversely, by aligning 탈론 and 럭스 together, you probably will not be giving your side much tankyness. Make sure to bring other champions on your team that neutralizes this hole in their potential.
Regardless of the ability of your 럭스 ally, you need to focus on increasing your gold income, warding to avoid ambushes, and clearing objectives. If you heed this simple advice, you will do well, regardless.
If you would like to truly master 탈론 to pair well with 럭스 during both the laning and mid / late game phases of League of Legends rounds, you should continue reading to pick up some more lessons on this champion pairing. If you use the build and suggestions shown above, you should grow your win rate significantly.
The ideal finished items to build first in your 탈론 and 럭스 synergy build include 요우무의 유령검, 오만, and 불경한 히드라. When 탈론 incorporated at least these three items in his build, he performed much better when fighting alongside 럭스 than with many other common builds. In fact, 탈론 boasted an average winrate of 47.7% when playing alongside 럭스 with these items in his kit.
To have the greatest likelihood of beating your oponents, you should use the 감전, 돌발 일격, 사냥의 증표, 끈질긴 사냥꾼, 절대 집중, and 빛의 망토 runes from the 지배 and 마법 rune sets. Out of all the rune builds that we analyzed for this champion pairing, this order of runes resulted in the best win rate. Notably, these runes averaged a 47.7% winrate overall.
By default, tips, statistics, and builds on how to pair 럭스 with 탈론 are shown for all skill levels, merged. If you want to scope the statistics and builds to a specific rank, you can use the selection menu located earlier on the page.