빙하 균열은 강력한 둔화 구역을 남깁니다. 팀간 전투 시 적들을 갈라놓고 다가오는 속도를 늦출 수 있는 위치에 사용하세요.
불굴 스킬을 사용하면 방어력이 약한 아군 앞으로 도약하여 투사체 공격을 막아줄 수 있습니다.
아군과 협동하여 뇌진탕 펀치 중첩을 쌓는 게 좋습니다. 아군에게 표식이 생긴 대상을 기본 공격하라고 알려주세요.
대회전은 탈출 수단으로도 사용할 수 있습니다.
게임 후반에는 지진, 몸 말아 웅크리기 스킬을 활용하여 포탑을 손쉽게 파괴할 수 있습니다. 팀 전투에서 제대로 활약할 수 없다면 팀과 별도로 행동하여 포탑을 공략하는 것도 좋은 생각입니다.
아군의 포탑 근처에 있는 적 챔피언에게 도발을 사용하면 포탑이 해당 챔피언을 공격합니다.
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 negative change shows that 람머스 helps 브라움 perform worse in ranked League of Legends games. Yet, the small difference shows that this performance change is not very impactful.
When 브라움 tries to synergize with 람머스, he sees a little increase in his complete damage dealt. This change may signal that 람머스 supports by providing cover for him to dish out more damage or that his allyship also helps extend the game's duration. Similarly, when 브라움 is played with 람머스 on the same team, 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 side, he on average takes a little more damage than when he fights alone. Getting dealt more damage could indicate that 람머스 does a poor job of protecting 브라움 during teamfights.
There is no universally accepted best companion for 브라움 that will 100% of the time be his #1 ally. Yet, overall, 람머스 is a good companion for 브라움. By locking into the same side as 브라움, he increases their win rate by 1.7% to 53.1%. This shows that there is a good bond between 브라움 and 람머스 that allows them to perform better together than alone.
람머스 has a greater difficulty than 브라움. That means 브라움 players must be cautious when arranging 람머스 teammates to go into battle on the same side as, as they will require a greater level of skill to fight well with you.
Working alongside, you should expect to witness an overall large increase in your team’s ability to soak up damage. Combined, these champions might be able to provide enough cover for their team's carries.
Conversely, by pairing 브라움 and 람머스 together, you may not be granting your other teammates enough AD. We recommend you bring other champs on your team that helps cover this relative disparity in their potential.
Regardless of your 람머스 ally's skill level, you need to focus on increasing your income, outlasting your enemies, and taking down objectives. If you follow these simple suggestions, you will do well anyway.
If you would like to learn all of the intricacies of 브라움 in order to work well with 람머스 during both the lane and mid / late game phases of League rounds, you should keep reading to gather some more tricks and insights into this champion pairing. If you pay attention to the build and tips shown here, you will grow your win rate by a lot.
The most important items to have in your 브라움 and 람머스 synergy build include 지크의 융합, 강철의 솔라리 펜던트, and 태양의 썰매. When 브라움 included at least these three pieces in his build, he did significantly better when fighting alongside 람머스 than with most other typical item sets. In fact, 브라움 had an average winrate of 53.1% when playing alongside 람머스 with this build.
To have the highest probability of coming out on top against your oponents, you should take the 수호자, 생명의 샘, 뼈 방패, 불굴의 의지, 비스킷 배달, and 우주적 통찰력 runes from the 결의 and 영감 rune sets. Out of all the rune combinations that we analyzed for this team composition, this mixture of runes resulted in the best win rate. In fact, these runes averaged a 53.1% winrate overall.
By default, tips, stats, and builds on how to synergize 람머스 with 브라움 are displayed for all skill levels combined. To filter the statistics and builds to a distinct rank, you can use the selection menu located earlier on the page.