Giganticus Lupicus path 4

Giganticus Lupicus path 4

in Fractals, Dungeons & Raids

Posted by: Malediktus.9250

Malediktus.9250

So we tried to do Path 4 twice, once about 2 weeks ago and once today. But giganticus lupicus didnt wake up, no matter what we did. Whats up with this?

1st person worldwide to reach 35,000 achievement points.

Giganticus Lupicus path 4

in Fractals, Dungeons & Raids

Posted by: Sina.9208

Sina.9208

We fought Lupicus twice alrdy on path4 and yet the encounter this problem. (on the other hand there is that kitten npc that always gets grubbed at phase change)

Giganticus Lupicus path 4

in Fractals, Dungeons & Raids

Posted by: swiftpaw.6397

swiftpaw.6397

Did path 2 and 3 yesterday and today no issues, perhaps you can try those instead for now, I have heard from a few people that path 4 is an issue of late due to the Halloween patch.

Grandmaster Forum Mind Brain
|-Swiftpaw Sharpclaw [DnT]-|

Giganticus Lupicus path 4

in Fractals, Dungeons & Raids

Posted by: Malediktus.9250

Malediktus.9250

I only encountered this problem on path 4 so far, but its pretty annoying since I want to finish my Dungeon Master title. Its hard enough to motivate people for path 4 already, but if its bugged they loose motivation even more…

1st person worldwide to reach 35,000 achievement points.

Giganticus Lupicus path 4

in Fractals, Dungeons & Raids

Posted by: RoRo.8270

RoRo.8270

Don’t bother with path 4 along with this bug and the bloodstone bugging out its not worth the time

Giganticus Lupicus path 4

in Fractals, Dungeons & Raids

Posted by: Malediktus.9250

Malediktus.9250

But I want that title :/
I dont care how long or difficult it is, as long as its completeable.

1st person worldwide to reach 35,000 achievement points.

Giganticus Lupicus path 4

in Fractals, Dungeons & Raids

Posted by: Kevin.2176

Kevin.2176

Did path path 2, 3, 4 yesterday with no issues at all.

However I did encounter the dreaded Giganticus being superfriendly bug before on path 4. It doesn’t seem like this is patch related, as we had this same bug maybe 3+ weeks ago.