전격 폭발 스킬을 사용할 때 가속 관문을 통과하도록 하면 사거리와 피해량이 대폭 증가합니다.
적의 공격으로 받는 피해가 클 경우, 무기를 해머로 변환하면 방어력이 향상됩니다.
무기를 되도록 자주 변환하십시오. 무기를 바꿀 때마다 공격력이 강화되며 순간적으로 이동 속도를 증가시킬 수 있습니다.
혜성전설의 비행 효과를 활용해 은하 해일 폭발 범위를 엄청나게 키울 수 있습니다.
혜성전설로 맵 이곳 저곳을 빠르게 이동할 수 있습니다. 이 스킬을 활용해 다른 공격로를 압박하세요.
필요할 경우, 성운의 공명을 아껴뒀다가 근접 챔피언들을 막는 데 활용하세요. 또는, 둔화 효과를 이용해 거리를 유지하며 멀리서 싸울 수도 있습니다.
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 worsened from NaN to NaN. This fall shows that 아우렐리온 솔 helps 제이스 perform not as well in competitive League of Legends games. Yet, the small difference indicates that this performance change is not very impactful.
When 제이스 tries to synergize with 아우렐리온 솔, he sees a small increase in his full damage output. This change could signal that 아우렐리온 솔 supports by providing cover for him to dish out more damage or that his participation also helps extend the round's duration. Similarly, when 제이스 is played together with 아우렐리온 솔 on the same side, he usually scores many fewer killing sprees compared to when he plays alone. This is contrasting evidence that he is worse when playing synergisticly with 아우렐리온 솔.
Additionally, when 제이스 plays with 아우렐리온 솔 on the same team, he typically receives a little more damage than when he fights alone. Taking more damage could indicate that 아우렐리온 솔 does a poor job of protecting 제이스 in teamfights.
There is no ideal companion for 제이스 that will 100% of the time be his ideal ally. Yet, overall, 아우렐리온 솔 is a very bad companion for 제이스. By locking into the same side as 제이스, he decreases their win rate by -4.3% to 43.5%. This proves that there is a terrible bond between 제이스 and 아우렐리온 솔 that allows them to perform not as well together than without each other.
아우렐리온 솔 has a lower difficulty than 제이스. That means you don't need to be cautious when finding 아우렐리온 솔 teammates to go into battle on the same side as, as they will require a lower level of skill to fight well with you.
Fighting together, you should witness an overall large increase in your team’s capability to deal magical damage. Together, these two are able to dish out a surprising amount of magic type damage.
Although, by bringing 제이스 and 아우렐리온 솔 together, you will not be giving your other teammates a great deal of crowd control. Plan to pick other champions on your team that offsets this gap in their playstyle.
Regardless of the ability of your 아우렐리온 솔 ally, you need to focus on maximizing your income, outlasting your enemies, and taking down objectives. If you heed this simple advice, you should do well anyway.
To truly master 제이스 to synergize with 아우렐리온 솔 during both the laning and mid / late game phases of League games, you should keep reading to master a few extra tricks and insights into this champion pairing. If you pay attention to the build and suggestions presented here, you should grow your win rate by a lot.
The best finished items to have in your 제이스 and 아우렐리온 솔 synergy build include 무라마나, 요우무의 유령검, and 밤의 끝자락. When 제이스 used at least these three pieces in his build, he did significantly better as an ally of 아우렐리온 솔 than with most other common builds. In fact, 제이스 had an average winrate of 43.5% helping carry 아우렐리온 솔 with these items in his kit.
To have the highest likelihood of vanquishing your oponents, 제이스 players should equip the 난입, 마나순환 팔찌, 절대 집중, 폭풍의 결집, 비스킷 배달, and 마법의 신발 runes from the 마법 and 영감 rune sets. Out of all the rune combinations players chose for this team composition, this mixture of runes yielded the top win rate. In fact, these runes averaged a 43.5% winrate overall.
By default, tips, statistics, and builds on how to team up 아우렐리온 솔 with 제이스 are presented for all ranked divisions. If you want to filter the statistics and builds to a specific division, you may use the selection menu earlier on the page.