녹서스의 단두대를 사용하기 전에 공격을 많이 적중시킬수록 더 큰 피해를 입힙니다. 녹서스의 힘 효과를 활용하여 피해량을 극대화하세요.
다리우스는 생존력을 강화할 때 큰 혜택을 볼 수 있습니다. 교전을 오래 끌수록 위력도 커집니다.
학살은 강력한 견제기입니다. 사거리 끝에서 적을 가격하면 효과가 극대화됩니다.
생물 분해 광선을 사용할 때는 이 스킬을 끊을 수 있는 스킬을 가진 챔피언이 많으므로 매우 주의하셔야 합니다.
플라즈마 분열을 대각선으로 발사해 최대 사거리에서 갈라지게 하면 최초 투사체의 사거리 밖에 있는 적을 맞힐 수 있습니다. 대신 후퇴하기는 더 까다롭습니다.
공격로 대치 단계에서 공허 균열을 사용하면 미니언을 처치하면서 적 챔피언에게 유기물 분해 중첩까지 쌓을 수 있습니다. 그 다음 다른 스킬을 연계하세요.
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 large worsening in his KDA (ratio of kills and assists to deaths) when paired with 벨코즈. His KDA worsened from NaN to NaN. This worsening shows that 벨코즈 helps 다리우스 perform poorer in ranked League of Legends matches. Yet, the small difference demonstrates that this performance change is only marginal.
When 다리우스 tries to synergize with 벨코즈, he gets a small increase in his full damage output. This may indicate that 벨코즈 supports by providing cover for him to dish out more damage or that his presence on the team also helps extend the match's duration. Similarly, when 다리우스 is played alongside 벨코즈 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 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 perfect synergy for 다리우스 that will 100% of the time be his best ally. Yet, overall, 벨코즈 is a pretty good teammate for 다리우스. By playing on the same team as 다리우스, he raises their win rate by 1.4% to 50.6%. This clearly indicates that there is a good bond between 다리우스 and 벨코즈 that allows them to perform stronger together than alone.
벨코즈 has a much greater difficulty compared to 다리우스. That means you need to be cautious when finding 벨코즈 teammates to play with, as they will require a much greater level of skill to work well with you.
When playing on the same side, you should expect to witness an overall large increase in your team’s ability to deal physical damage. Combined, these champs should be able to take down targets with auto-attacks and other AD damage abilities.
Although, by grouping 다리우스 and 벨코즈 together, you will not be granting your team enough utility. Make sure to bring other champions on your team that fills this disparity in this pairing's capabilities.
Regardless of the ability of your 벨코즈 teammate, you should focus on increasing your income, staying alive by avoiding foolish fights, and clearing objectives. If you follow these simple suggestions, you should do well anyway.
To learn all of the intricacies of 다리우스 in order to synergize with 벨코즈 during both the lane and mid / late game phases of League, you should keep reading to master additional lessons on this champion pairing. If you mind the build and tips displayed here, you will increase your win rate by a lot.
The top items to have in your 다리우스 and 벨코즈 synergy build include 스테락의 도전, 망자의 갑옷, and 갈라진 하늘. When 다리우스 included at least these three pieces in his build, he performed much better as an ally of 벨코즈 than with many other typical item sets. In fact, 다리우스 had an average win rate of 50.6% helping carry 벨코즈 with this build.
To have the highest chance of annihilating your oponents, 다리우스 players should use the 정복자, 승전보, 전설: 민첩함, 최후의 저항, 뼈 방패, and 불굴의 의지 runes from the 정밀 and 결의 rune sets. Of all the rune combinations we have analyed for this team composition, this composite of runes yielded the top win rate. Notably, these runes gave a 50.6% win rate overall.
By default, tips, statistics, and builds on how to team up 벨코즈 with 다리우스 are shown for all skill levels combined. If you would like to scope the stats and builds to a specific rank, you should use the selection menu earlier on the page.