빙하 균열은 강력한 둔화 구역을 남깁니다. 팀간 전투 시 적들을 갈라놓고 다가오는 속도를 늦출 수 있는 위치에 사용하세요.
불굴 스킬을 사용하면 방어력이 약한 아군 앞으로 도약하여 투사체 공격을 막아줄 수 있습니다.
아군과 협동하여 뇌진탕 펀치 중첩을 쌓는 게 좋습니다. 아군에게 표식이 생긴 대상을 기본 공격하라고 알려주세요.
그웬은 신성한 안개 밖에 있는 적에게도 피해를 입힐 수 있습니다. 궁극기 사거리를 활용하면 더욱 효과적입니다.
그웬의 몇몇 스킬은 기본 지속 효과를 다수의 적에게 적용할 수 있으니 무리 지은 적을 노려 피해와 회복 효과를 최대로 높이세요.
늘 기본 공격을 가하세요. 추가 피해를 입히며 그웬의 기본 공격을 강화하거나 여러 스킬을 초기화할 수 있습니다.
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 not as well in competitive LoL rounds. Yet, the small difference shows that this performance change is only marginal.
When 브라움 is an ally to 그웬, he observes a small decrease in his full damage output. This could signal that 그웬 does not provide protection for him to dish out more damage or that her participation also helps extend the round's duration. Similarly, when 브라움 is played together with 그웬 on the same team, he usually scores many fewer killing sprees compared to when he plays on his own. This is contrasting evidence that he is worse when playing synergisticly with 그웬.
Additionally, when 브라움 plays with 그웬 on the same team, he typically takes a little less damage than when he fights alone. Receiving not as much damage may mean that 그웬 does a decent job of covering 브라움 in teamfights.
There is no ideal champion pairing for 브라움 that will 100% of the time be his #1 synergy. Yet, overall, 그웬 is a very bad ally for 브라움. By being on the same team as 브라움, she drops their win rate by -3.2% to 48.2%. This proves that there is an easy to overcome and exploit bond between 브라움 and 그웬 that allows them to perform not as well together than without each other.
그웬 has a greater difficulty than 브라움. That means you need to be very careful when lining up 그웬 teammates to fight alongside, as they will require a greater level of skill to be able to do well with you.
When playing cooperatively, you should expect to see an overall large increase in your team’s capability to tank a lot of damage. When paired, these champs will be able to tank for the rest of their team.
Conversely, by grouping 브라움 and 그웬 together, you probably will not be giving your side a great deal of magic damage. Plan to bring other champions on your team that fills this gap in their potential.
Regardless of your 그웬 ally's skill level, you should focus on increasing your gold income, staying alive by avoiding foolish fights, and clearing objectives. If you follow these simple suggestions, you should do well, regardless.
To learn all of the intricacies of 브라움 in order to pair well with 그웬 during both the laning and mid / late game phases of League of Legends matches, you should keep reading to gather a few extra tips and tricks for this champion pairing. If you listen to the build and tips displayed above, you will grow your win rate significantly.
The most important finished items to build first in your 브라움 and 그웬 synergy build include 지크의 융합, 강철의 솔라리 펜던트, and 태양의 썰매. When 브라움 used at least these three items in his build, he did much better as an ally of 그웬 than with many other common item sets. In fact, 브라움 had an average win rate of 48.2% when playing alongside 그웬 with this build.
To have the highest probability of beating your oponents, 브라움 players should equip the 수호자, 생명의 샘, 뼈 방패, 불굴의 의지, 비스킷 배달, and 우주적 통찰력 runes from the 결의 and 영감 rune sets. Out of all the runes players picked for this team composition, this order of runes yielded the highest win rate. Notably, these runes averaged a 48.2% winrate overall.
By default, tips, stats, and builds on how to team up 그웬 with 브라움 are presented for all ranked divisions. If you would like to scope the statistics and builds to an individual division, you can use the selection menu at the top of this page.