진압을 사용하면 강력한 적 방어 담당을 약화시키거나 아군이 공격을 집중할 수 있는 대상으로 만들 수 있습니다.
트런들은 얼음 왕국에서 싸울 때 가장 유리합니다. 적들을 해당 지역으로 유인하십시오.
깨물기는 적의 공격력을 낮출 수 있습니다. 적 물리 공격수를 목표로 하는 게 좋습니다.
쓰레쉬의 랜턴을 사용할 때에는 원활한 의사소통이 필수입니다. 아군에게 어떻게 쓸 것인지 알려 주세요.
사형 선고와 사슬 채찍은 순서와 관계 없이 연계하여 시전하면 강력한 위력을 발휘합니다.
쓰레쉬는 직접 처치하지 않은 영혼도 흡수할 수 있습니다. 사망 일보직전의 대상 근처에 있으면 영혼 흡수 효율이 극대화됩니다.
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 decreased from NaN to NaN. This fall shows that 쓰레쉬 helps 트런들 perform not as well in competitive League matches. Yet, the small difference demonstrates that this performance change is not very impactful.
When 트런들 plays on the same team as 쓰레쉬, he sees a small increase in his full damage dealt. This change could signal that 쓰레쉬 helps provide protection for him to dish out more damage or that his participation also helps extend the match's duration. Similarly, when 트런들 is played together with 쓰레쉬 on the same side, he usually scores many fewer killing sprees compared to when he plays without 쓰레쉬. This is contrasting evidence that he is worse when playing alongside 쓰레쉬.
Additionally, when 트런들 plays with 쓰레쉬 on the same side, he often takes a little less damage than when he fights alone. Receiving not as much damage may mean that 쓰레쉬 does a decent job of protecting 트런들 during teamfights.
There is no perfect companion for 트런들 that will always be his ideal ally. Yet, 쓰레쉬 is a not very good companion for 트런들. By playing on the same side as 트런들, he decreases their win rate by -2.0% to 50.7%. This clearly indicates that there is a bad strategic relationship between 트런들 and 쓰레쉬 that results in them performing worse together than alone.
쓰레쉬 has a greater difficulty than 트런들. That means you should be very careful when finding 쓰레쉬 teammates to play with, as they will require a greater level of skill to be able to work well with you.
When playing on the same side, 트런들 players should expect to see an overall large increase in your team’s capacity to support your allies. When paired, these champions will help their other teammates secure a victory.
In contrast, by bringing 트런들 and 쓰레쉬 together, you will not be granting your other teammates very much magic damage. Plan to bring other champs on your team that fills this relative disparity in their kit.
Regardless of your 쓰레쉬 ally's ability, you should focus on maximizing your gold income, staying alive by avoiding foolish fights, and taking down objectives. If you do this, you will do well, regardless.
To truly master 트런들 in order to work well with 쓰레쉬 during both the early game and mid / late game phases of League of Legends, you should keep reading to master additional tricks and insights into this champion pairing. If you pay attention to the build and suggestions shown above, you will grow your win rate by a lot.
The most important items to have in your 트런들 and 쓰레쉬 synergy build include 삼위일체, 선체파괴자, and 거대한 히드라. When 트런들 incorporated at least these three finished items in his build, he did a lot better when fighting alongside 쓰레쉬 than with most other commonly used item sets. In fact, 트런들 had an average win rate of 50.7% helping carry 쓰레쉬 with these items in his kit.
To have the greatest chance of coming out on top against your oponents, you should use the 치명적 속도, 승전보, 전설: 민첩함, 최후의 일격, 쾌속 접근, and 마법의 신발 runes from the 정밀 and 영감 rune sets. Of all the rune builds players picked for this champion pairing, this sequence of runes yielded the top win rate. In fact, these runes provided a 50.7% winrate overall.
If you need to view 트런들 with 쓰레쉬 collaboration tips and stats for a a specific player tier, please choose one from the selection menu displayed above. If viewing for the first time, the statistics and strategies shown are computed using all rounds with data with these champions.