Very frequently the beast in the ice will not spawn but consume the resource why ?
7 Likes
What? I ran a bunch of Beast earlier.
Consume resource? No, he will kick your butt if you aren’t ready to fight him.
Not sure what you are even talking about.
Worked fine yesterday. I had plenty mats from underctiy and did 20 or more. All worked.
1 Like
Yeah not sure. Makes zero sense, then you have someone like their post.
Who are these people?
Had the same thing happening yesterday.
Happened to me and my group 2-3 times already. It consumes the mats but doesn’t spawn and you can’t launch a new one. You need to go out of the dungeon and reset it.
1 Like
Confirmed happened in all the teams I played with tonight multiple times.
Only happened to me when spamming “summoning” quickly one after another…
After i tried to do it slower, never experienced issue after.
I don’t think it is frequently, but it has happened to me too, a couple of times in groups.
You need to wait until the frozen corpses respawn before summoning him again.
2 Likes
Had it happen twice tonight…
Maybe its the same issue like having with the tenents of akarat. Im pretty sure turning of Crossplay will fix most problems. But if you play on consoles turning of x-play will result in lonelyness. I did it once and saw not a single player. Even at the blacksmiths in the city. 
I did a couple of beast solo runs too yesterday evening. No problems.
1time each ~8 summons it s bugged and you have to reset dungeon. I don t know how much time is required to fix this bug though. Many weeks 
Saves you the time of killing boss just to vendor trash drops by just taking you matts. Clever design by the devs if you ask me!
I solo’d the Beast yesterday 10 times in a row in T3 HC. Now, I’m back to farming mats so I can do it again… sign… But it sounds like there might be a timing issue after defeating it if you try resummoning them again too quickly. I wasn’t in a hurry though… just a lazy Thursday afternoon boss slaughtering session.
1 Like
if you search in the bugs section you’ll find a bug report on this. please add your details there.
New patch notes just went up and this is being fixed on Tuesday.