That seems to be one of the things that triggers it, but is not the only thing. Other potential triggers have been identified above in the thread.
Uh, after all the posts here it seems relatively safe to say that the problem is hero skills trying to summon troops when there’s no free slot on the summoning team.
Leprechaun is just a trigger, not the actual issue. Neither is orbweaver per se.
Summon. Enemy summon. In PvP. It’s when the enemy summons a troop. It’s summoning. Not a specific troop. Not a specific class. Summoning. Summon. It’s summoning.
Hope that helps! Seriously thanks for all you do!
You’ve replied to another post since I’ve made my previous comment please reply to confirm you’ve seen and understand it.
Please check my full disclosure post that was set to invisible, it explains in detail which situations cause this issue. If the team working on the fix is now focusing solely on the Orbweaver class, we’ll just end up with another fix that doesn’t really work.
It’s definitely not only Orb Weaver, here’s my most recent example:
(that’s Bard, just to be super clear, which has a summon chance. And of course there’s a storm active again as well)
We’ll post more updates in the known issues article as well, once we have them from the team
Wow, that is some weapons-grade missing the point.
“Uh, something about Leprechaun spell. Or maybe Orbweaver, or whatever…”
Not one mention of summons, let alone AI trait-triggered summons during the player’s turn without an open spot to receive them, as was so clearly, unambiguously, and repeatedly explained.
No wonder the game is in a state like this.
Hey all,
THANK YOU Jeto for taking the time to help out on the GoW forum, despite being busy with your other responsibilities, and replying so everyone had a reply acknowleding that the team was aware of the issue sooner.
I will try to include some more details here, I may miss something out because I am human, if you have further questions, concerns after reading this, please raise them civilly and I will give you more info - please don’t jump to conclusions. The Help Center article is generic and mentioning specific Troops intentionally, because the majority of players will just want to know what to do to avoid the issue, we also haven’t confirmed the reason it’s locking up yet so don’t want to publish any hypothetical causes. What we do know though is that these Troops are reported as being in the battles being reported, and that’s helpful to the general playerbase.
The programmers are currently looking at a few issues already which may relate to this issue. I can’t tell you specifically which issues are at play here right this moment but it seems to relate to these 2 off the top of my head:
- Summoning may be causing CLIFFY errors for a very small handful of players
- “Pharoah Khafru” issue - or rather the game soft locks, most commonly when Khafru is on the team but not specifically a bug with Khafru himself. We suspect it’s an issue with the timing of the puzzle board resolution
- Orbweaver issue (I’m in a rush so this is a very generic paraphrase sorry!!!)
You’ve all posted good insights into what could be causing this issue, thank you also for the screenshots.
Everything you’ve mentioned has been included in a bug report to the team by Jeto and also connected with these other issues so that anything relating to the puzzle board not resolving can be looked at both as one big picture issue and in smaller detail.
We’re always happy to answer any questions or follow up concerns if we’re able to and haven’t already answered about it, especially if we may have missed something in our prior answers if we’re able to do so. This is a discussion so it’s ok to have some back and forth if some things are not included in the original response ![]()
Is everyone only encountering this issue when playing in a Blood Frenzy region in PvP?
Or have you experienced in different game modes and non-blood frenzy regions as well?
Apologies if someone already mentioned non-blood frenzy and other game modes, there’s a lot of posts here so I just want to be sure I haven’t missed it.
Last update messed with the stats for summoned troop. Bug didn’t exist before the update. Bug existed after the update. Undo the “fix” that will resolve the screen locking bug. Then work on a fix to the summon stats issue that won’t cause the game to lock.
If this is an extension of the other bugs I mentioned, then it existed before 8.2 and basically it’s possible multiple bugs will be resolved by fixing a similar area of the puzzle board resolution.
Removing that fix also requires a client update if I’m correct.
So we may as well just keep working on the core issue(s) to resolve it.
“Orbweaver bug” is really “Summon bug” - anything that causes a summon stacks stats on the enemy’s entire team. PvP only.
This happens even in the citadel wars.
Actually, I believe everybody here would prefer if you would just prevent the issue from showing up. Now™, not Eventually™.
As you should be well aware, you don’t need any client update. For anything but some very exotic corner cases, you just need to:
- Temporarily modify the Familiar trait and Golem Protector talent, either changing the trigger to something that can’t happen on the opponent turn or changing the effect to not summon troops.
- Distribute this change through the in-game update channel, like already happens several times each week for event purposes.
This shouldn’t take an hour, even when allowing for an extended coffee break. Why hasn’t this been done at least a week ago? The community has provided all information needed to handle this fast and efficiently. Have the devs really been informed about this issue or is this gathering dust in some quarterly feedback summary?
Losing PvP battles to this bug is annoying. Losing limited talismans and citadel sigils is MORE annoying. Losing limited talismans and citadels sigils that have been paid for in some way is MORE THAN annoying. Please make this 10th anniversary update feel less like a funeral.
Strictly speaking that is a “workaround” not a “fix” because it avoids the issue rather than fixing its root cause. Still, you’re correct it’s a simple workaround that could technically be issued as an asset update from the server – so long as they’ve actually decided on what to temporarily replace it with.
I lost a citadel battle today due to the summon bug. Khochi was on the other team along with a Stormcaller hero. The screen shook for about 10 seconds, then a troop appeared and the hero had 1000 to all stats, so he used his 1000 magic to immediately destroy me. Not impressed.
Happened in Maraji Expanse with the all so buggy Mana Potion Gems. The annoyances in this game start to easily outweigh the rest of the “fun” to be had. No Orbweaver or Leprechaun or any other weird theories this thread is discussing.
The opponent has Arachnaean Weaver. Weaver’s third trait is a 75% chance to summon Webspinner when an enemy dies. Your fourth troop died, triggering the third trait. It’s exactly the same issue that is being described with Orbweaver. It has to do with summons. Seems that if there are no spots to summon a troop, the game freezes. But if it can summon a troop, it does and the hero gets 1000 to all stats.
Could be arachnean weaver tried to summon a webspinner on death. So, perfectly in line with the things discussed here.
“Weird theories” is how this community gets to the bottom of bugs and is actually what is happening on your screen.


