Earthbreaker support doesn't take in account the +1 totem from Vaal Ancestral Warchief
Hello,
I found a bug with the new Earthbreaker support gem and the number of maximum totems. Here are 2 cases which confirmed that this is bugged. Case 1 For example, if I use : - Ancestral Warchief + multiple totem support - Earthbreaker + consecrated path (without multiple totem support) - Ancestral Bound passive - Vaal ancestral warchief In this case, everything seemed fine. I could summon 2 Ancestral Warchief totems + 2 Earthbreaker + Consecrated Path (summoning them 1 by 1). When I summon my 2x Vaal Ancestral Warchief totems I get a total of 5 totems because it adds +1 max totem. Now, if instead I use these gems : - Ancestral Warchief WITHOUT multiple totem support - Earthbreaker + Consecrated Path + multiple totem support - Ancestral Bound passive - Vaal ancestral warchief In this case, I should also have 4 max totems + 1 totem when using Vaal Ancestral Warchief. But this doesn't work, when using Vaal Ancestral Warchief, one of my totems is being replaced and I have a maximum of 4 totems instead of 5 during the vaal skill. Case 2 Now, if instead I use these gems : - Ancestral Warchief + multiple totem support - Earthbreaker + Consecrated Path + multiple totem support - Ancestral Bound passive - Vaal ancestral warchief I this case, if I summon 4 Consecrated Path totems and use Vaal Ancestral Warchief, it removes of of my totem (it doesnt take in account the +1 max totem) However, Ancestral Warchief seems to work properly. I can summon 4 Ancestral Warchief totems + 1 Vaal Ancestral Warchief totem. By the way, why can't we have a totem of 6 totems when using 2 multiple totem support on 2 different skills ? (this seems intended and I don't know why) Last bumped on Dec 9, 2021, 3:13:08 PM
This thread has been automatically archived. Replies are disabled.
|
![]() |
+1
I'm having the same issue as what bubuche described in Case 1 |
![]() |
Can confirm that this is still not fixed. How can we get this prioritized? Mathil1 is about to play this build, so hopefully will get more attention on this.
|
![]() |
![]() |