I had no problem killing the swarms with alchemist fire. You need more than 6 though. Later you can just kill them with your weapons if those have elemental enchantments.
Can owlbears do aoe fire or acid damage, though? Because otherwise they won't be able to damage a swarm. Of course the swarm will likely be unable to damage the owlbear unless they roll a 20, but still...The world already belongs to the owlbears, we just live in it.
Do Cleave or AE melee attacks destroy swarms? I had a couple of swarms at end of Chapter 3 which I just auto-attacked to death. But didn't notice who it was who did the attacks.
you've also got that everburning torch, no?I had no problem killing the swarms with alchemist fire. You need more than 6 though. Later you can just kill them with your weapons if those have elemental enchantments.
Oh I agree it would've still been buggy, but they might have been able to polish out gamebreakers or get to the current level of polish where the early game is pretty smooth.More like 3-6 months. They've been playing catch-up with genuinely game-breaking bugs since release, and the game is, compared to what it could've been, completely unpolished. Because the core is so strong, it's not immediately noticeable in the way it would be in some other games for sure, but there's ultimately no way to tell for sure (other than Owlcat saying it) just how much better things could've been if the game had not been forced out the door. Some things (especially of narrative nature) were likely irrevocably damaged by it, and I wouldn't be surprised if there are bugs or issues that will likely never be fixed because doing so would break some core functionality or something.Because it's good!So big patch is in two weeks, and the game actually enters "finishable without Shadenaut's workarounds" status, proving that the game was buggy enough it really shouldn't have been released, but was somehow dramatically financially successful anyway.
It's barely buggy up until Armag's now, which is a lot of time. Playing like a normal person instead of a frothing-at-the-mouth obsessive like me or some of the others in this thread means you probably wouldn't get to the real bugs unti December.
(But yes they should've delayed release by least a month)
No way would a single month have been enough. I refuse to believe it.
They needed 2 months for bug fixes, 1 month for ironing out balance/mechanics numbers (especially later chapters and overall kingdom management) and then preferrably another 2 months just to do it all again in a final smoothing pass that focused on various smaller bugs like broken domains/ class mechanics/feats and made sure things like itemization were smooth and inclooosive.
3 months for essential things a further 2 months to get things nice and buttoned down. I am not sure why they just didn't sell it as Early Access it would have been in a far more comprehensive state than most Early Access steam games.
I did it so:Got teleport for my monk and tried to steal lich treasures early...
This shout spell is seriously broken and should be removed. Even with invisibility up his summons see me and lich just casted it in my general direction and it's all over.![]()
What does power equal? +8 racial bonus to Listen checks.I did it so:Got teleport for my monk and tried to steal lich treasures early...
This shout spell is seriously broken and should be removed. Even with invisibility up his summons see me and lich just casted it in my general direction and it's all over.![]()
dimension door into the room to the left on a spot where the lich doesn't aggro
dimension door to the chest->loot
spellrecall
dimension door back the same way
The lich did aggro on the way back probably because I didn't hit the exact right spot, but I just teleported out of the room
Oh I agree it would've still been buggy, but they might have been able to polish out gamebreakers or get to the current level of polish where the early game is pretty smooth.More like 3-6 months. They've been playing catch-up with genuinely game-breaking bugs since release, and the game is, compared to what it could've been, completely unpolished. Because the core is so strong, it's not immediately noticeable in the way it would be in some other games for sure, but there's ultimately no way to tell for sure (other than Owlcat saying it) just how much better things could've been if the game had not been forced out the door. Some things (especially of narrative nature) were likely irrevocably damaged by it, and I wouldn't be surprised if there are bugs or issues that will likely never be fixed because doing so would break some core functionality or something.Because it's good!So big patch is in two weeks, and the game actually enters "finishable without Shadenaut's workarounds" status, proving that the game was buggy enough it really shouldn't have been released, but was somehow dramatically financially successful anyway.
It's barely buggy up until Armag's now, which is a lot of time. Playing like a normal person instead of a frothing-at-the-mouth obsessive like me or some of the others in this thread means you probably wouldn't get to the real bugs unti December.
(But yes they should've delayed release by least a month)
No way would a single month have been enough. I refuse to believe it.
They needed 2 months for bug fixes, 1 month for ironing out balance/mechanics numbers (especially later chapters and overall kingdom management) and then preferrably another 2 months just to do it all again in a final smoothing pass that focused on various smaller bugs like broken domains/ class mechanics/feats and made sure things like itemization were smooth and inclooosive.
3 months for essential things a further 2 months to get things nice and buttoned down. I am not sure why they just didn't sell it as Early Access it would have been in a far more comprehensive state than most Early Access steam games.
There is no balance, this is Pathfinder. It's all a total shitshow, that's why it's fun.
Well they are mix of great games and some epic shit. They were publishers of Kingdom come and Metro games.Most likely the published didn't expected the game to make a return on investment and decided to push it out the doors. 2-3 months would have polished the game and fixed most of the patches,for the cut contend it would have needed maybe 6 month total.
Meh who knows, I have heard bad things about Deep Silver.
when a game have a lot of different possible combination bug ramp up.Bitches, Obsidians and other devs should have inured you to the buggy state of released games. Why the hell do you complain about it now?
Fallout2, Fallout NewVegas, Fallout Tactics, Baldur Gates (oh god~), Arcanum...
Great games come with boatload of bugs, it's like a requirement.
The HBS game has the same problem, with complaints from users that their graphics cards have been compromised because of the heat. It definitely seems to be a Unity problem if this game is also exhibiting the same behaviour.I installed a new cooling system recently to mitigate the blowtorch effect this game has on your video card whenever you open a menu. It worked, but now I'm starting to see the video card temp creep up again after the latest patch (about a third higher than they were before the patch). So I realise this is a Unity specific problem - but I don't suppose Owlcat are in a position to ever do anything about it?.
I can play much more demanding games without this level of stress being applied to the card. And it is just on the menu - as the temps drop as soon as they're closed.
the fixes even show this quite wellwhen a game have a lot of different possible combination bug ramp up.
for a simple reason: nobody can QA 40 millions of different combinations and triggers.
One of the arguments to convince Jaethal not to sacrifice her daughter during the "Reveal My Destiny" quest was missing if the player chose to "destroy Urgathoa ritual" while talking with Taneka during Jaethal's "Chase My Shadow" quest. Resolution: fixed. If this argument is the decisive one for those players who tried to convince Jaethal, failed and then chose "attack Jaethal" instead, the quest result will be changed. Jaethal will appear at the critical point at the House at the Edge of Times area and act as if she was convinced to let go of her evil ways.
It does, and yeah, it's a Unity thing. I can hear all the fans go wild when I run PF:K.The HBS game has the same problem, with complaints from users that their graphics cards have been compromised because of the heat. It definitely seems to be a Unity problem if this game is also exhibiting the same behaviour.I installed a new cooling system recently to mitigate the blowtorch effect this game has on your video card whenever you open a menu. It worked, but now I'm starting to see the video card temp creep up again after the latest patch (about a third higher than they were before the patch). So I realise this is a Unity specific problem - but I don't suppose Owlcat are in a position to ever do anything about it?.
I can play much more demanding games without this level of stress being applied to the card. And it is just on the menu - as the temps drop as soon as they're closed.