Pillars of Eternity Game-Breaking Bug Alert

Pillars of Eternity Game-Breaking Bug Alert

Details on the bug and steps you can take to avoid it.

Pillars of Eternity

A game-breaking bug has reared its ugly head in the recently launched Pillars of Eternity, available for Linux, Windows, and Mac systems. The bug is triggered by double-clicking an item to equip it to your character, which in turn removes all passive, racial, and permanent buffs forever. The short answer to keeping all your buffs safe and sound would be to not double-click the item to equip, but instead drag and drop the item into a slot on the inventory screen.

So what are you to do if you've encountered the bug? You can load up an old save of the game and head about your merry way, but without any of the progress made between the time of that save and the triggering of the bug. That's obviously not ideal, but an Obsidian developer has stated that they "have a fix for [the bug] and [are] trying to make it retroactive, so it will fix any save games that have this problem."

If a member of your party has come in contact with the bug, you can remove them from the party and then add them back again, which seems to work as a solution.

Meanwhile, there is some good news to revel in. According to Polygon, "others report that though passive buffs do not show up, they appear to still be present and working."

Source: Polygon, via Obsidian

Permalink

Nice to know that an Obsidian bug is still considered newsworthy.

Well, it IS an Obsidian game...

Soviet Heavy:
Nice to know that an Obsidian bug is still considered newsworthy.

It is a hell of a bug though. Nothing wrong with a PSA about it for players.

Yup, definitely appreciate the heads up.. I wonder if I have any gear I've done that with... *ponders*

captchas: 6 feet of snow - Yes... thank you for the reminder... /GLARE

Alright who had Monday 30th in the Obsidian new release game breaking bug discovery sweepstake? Come on and claim your prize :P

Still have yet to even get pass the title screen as I am having to reinstall everything on my pc and my laptop sadly cannot run the game above 10 fps. Setime this week I will get play it and hopefully a patch is released by then.

It's weird that the game includes a console but no commands to fix this sort of thing. You could usually fix even the most oppressive bugs in TES games using console commands if you knew what to do.

Wouldn't be an Obsidian game without the bugs!

My question is thus, even considering obsidians shit tier level of bug checking, HOW THE FUCK did they miss something like this? It's the most basic command in a RPG.If someone played for more that 10 minutes they would have equipt a new piece of gear and found this bug. Did they manage to get it to launch without crashing or instantly frying your hard drive and label it a success?

Oh, that's got to suck for those whose buffs completely disappeared, and aren't just invisible.

The last really game breaking bug for me was at the last few missions of Oblivion's Thieves' Guild questline. It was the bug where the quest givers disappears yet the arrow points to the chair he should be in. (I'm sure some readers are now getting flashbacks to hard work lost.) Unfortunately, I was playing the 360 version and clearing the system cache didn't help. I think I did get a save from way back to work, though. I'm glad I go with PC versions of Bethesda games now.

snekadid:
My question is thus, even considering obsidians shit tier level of bug checking, HOW THE FUCK did they miss something like this? It's the most basic command in a RPG.If someone played for more that 10 minutes they would have equipt a new piece of gear and found this bug. Did they manage to get it to launch without crashing or instantly frying your hard drive and label it a success?

My guess is that the Day One patch caused the bug. It wasn't an issue in the backer beta, from what I hear, and also the rest of the game is really well polished. Aside from some scrolling issues when you have multiple item description popups and one time when half of a certain character's voice acting got eaten somehow, I haven't encountered any bugs in 20+ hours of game time. Shit is downright stable compared to KOTOR 2, NWN 2, Alpha Protocol, or any Bethesda game. Better than a lot of AAA releases last year, let me tell you.

That's a nasty bug, no question. But my understanding of the term "game-breaking" is that it, well, breaks the game- i.e., after the bug is tripped, it is no longer possible to progress. An NPC who needs to do something to advance the plot won't do that thing. A door that must be passed to advance fails to open. An item necessary to complete a plot-central quest won't spawn. Etc.

This bug is a pain in the ass, and sure, I can see why players might not want to proceed after that bug was tripped, if they couldn't find a way around it, and Obsie should definitely fix it tout suite. But it isn't "game-breaking".

(Sorry to be "that guy", but it's true.)

a great game nonetheless

Soviet Heavy:
Nice to know that an Obsidian bug is still considered newsworthy.

At this point I assumed people knew bugs were just par for the course with Obsidian games. But given the nature of this one, a PSA (of sorts) might not be a bad idea.

snekadid:
My question is thus, even considering obsidians shit tier level of bug checking, HOW THE FUCK did they miss something like this? It's the most basic command in a RPG.If someone played for more that 10 minutes they would have equipt a new piece of gear and found this bug. Did they manage to get it to launch without crashing or instantly frying your hard drive and label it a success?

The game is actually surprisingly bug-free save for this one and a few other minor glitches. Personally I've yet to have run into a single problem playing in over 15 hours of gameplay.

Meanwhile since this wasn't actually a problem in the earlier beta releases the safe bet is that this glitch was introduced in the day 1 patch, so it's not like it's something that's been hanging out for a while now. Should be fixed soon as well.

And Man:
Wouldn't be an Obsidian game without the bugs!

There's bugs and then there's broken, this issue falls in the latter. If a basic ability of the game doesn't work it's faulty and if I had of bought this I would have returned it for a full refund. Fuck developers who can't be bothered to finish a game before release.

Callate:
That's a nasty bug, no question. But my understanding of the term "game-breaking" is that it, well, breaks the game- i.e., after the bug is tripped, it is no longer possible to progress. An NPC who needs to do something to advance the plot won't do that thing. A door that must be passed to advance fails to open. An item necessary to complete a plot-central quest won't spawn. Etc.

It breaks a core function/feature in the game, it's game breaking. A bug doesn't have to stop you from advancing to break something important. That would be like saying a GTA bug that stops you from getting into a car outside of missions isn't game breaking. Sure you can get around but since driving is a core feature most would agree it's game breaking.

That's Obsidian quality for you. I read a lot about items that when equip permanently bork your character. I guess they still don't do QA, but on the other hand the game at least seems to have all it's content included, so there is that. I will not be surprised to find out they had to cut the ending and several locations, though.

Wait, wait, wait. It's definitely annoying but it hardly breaks the game. I played like 20 hours without noticing. It makes combat a little harder than it should have been, but doesn't stop any progression and the racials aren't super powerful anyhow.

Also, any Obsidian game has to have at least one major bug lurking, let's hope this was it.

Fingers crossed I get that hotfix sooner than later. I'd really like to know for sure, beyond a shadow of a doubt, that all my passives still exist as a thing. I'm pretty sure I lost a level 1 spell per rest from my wizard and priest because of this bug; would like to know if I was just dreaming of a magical five casts per rest (swoon) or if it actually used to be a thing. Oh, and all my elf passives.

For all the "OMG BUGZ LOL OBSIDIAN" hate, the game has been very enjoyable with only one other major hiccup: the can't-load-Raedric's-Hold-after-exiting bug, which is thankfully fixable client-side by (I kid you not) viewing the .savegame file via 7Zip, WinRAR, etc. and deleting the Raedric's interior content. A hassle, sure, but all my progress was saved and I could get back to good ol' fashioned Infinity Engine-style beatdowns of sellswords.

snekadid:
My question is thus, even considering obsidians shit tier level of bug checking, HOW THE FUCK did they miss something like this? It's the most basic command in a RPG.If someone played for more that 10 minutes they would have equipt a new piece of gear and found this bug. Did they manage to get it to launch without crashing or instantly frying your hard drive and label it a success?

It might not have shown up on their systems.

Just a heads up: if you aren't already affected by the bug, this mod will disable double-clicking while in inventory so that you don't accidentally trigger it. It's not a fix, but it should do as a workaround until the game gets patched.

snekadid:
If someone played for more that 10 minutes they would have equipt a new piece of gear and found this bug.

Nah, the bug only occurs if you double-click to equip something when you don't have an open slot for it. That's exactly the sort of bug that tends to sneak through, on account of the fact that you'd never intentionally do it in normal gameplay.

Still better than a Bethesda release though. Obsidian has been doing better now that they aren't being rushed to make games by publishers.

Thorn14:
Well, it IS an Obsidian game...

Soviet Heavy:
Nice to know that an Obsidian bug is still considered newsworthy.

It is a hell of a bug though. Nothing wrong with a PSA about it for players.

except there's an easy fix that only results in your companions gaining an extra level, and they are in the process of issuing a patch. So far there are only 2 game breaking bugs, remarkably few for any sort of RPG at release, with the other being a CTD.

I take it the character sheet display for the buffs disappears as well? Am I correct in understanding that? It's not just a backend thing? Because I can't remember if I've double clicked to equip anything yet, or just dropped it on the character doll.

This must have affected me. My pale elf druid definitely had his racial bonus for a bit, but it disappeared two days ago. So he's lost his 10 DR to fire and freeze, it's annoying but not the end of the world. It's definitely not game breaking...I'm up to level 7, just finished Dyrford village and I'm managing just fine.

Thanks for the heads up all the same. I hope there's a bug fix for it...altho unless it's retroactive or there's a dev console command to fix it, I won't get it back this playthru.

Only other bug I've encountered is the ranger debuff from when their pet dies in combat, persisting even after the pet gets up again.

Supahewok:

snekadid:
My question is thus, even considering obsidians shit tier level of bug checking, HOW THE FUCK did they miss something like this? It's the most basic command in a RPG.If someone played for more that 10 minutes they would have equipt a new piece of gear and found this bug. Did they manage to get it to launch without crashing or instantly frying your hard drive and label it a success?

My guess is that the Day One patch caused the bug. It wasn't an issue in the backer beta, from what I hear, and also the rest of the game is really well polished. Aside from some scrolling issues when you have multiple item description popups and one time when half of a certain character's voice acting got eaten somehow, I haven't encountered any bugs in 20+ hours of game time. Shit is downright stable compared to KOTOR 2, NWN 2, Alpha Protocol, or any Bethesda game. Better than a lot of AAA releases last year, let me tell you.

Not true, I don't recall any game breaking bugs in Dishonored. O you missed New vegas, the Obsidian game with more game breaking bugs still existing than Skyrim had at launch.

God... why did you have to list those games.... The only one I have fond memories of playing are alpha protocol which was very bug free during my play through. Kotor 2 ended in the mandolorian camp when my character put on light speed shoes and would teleport into walls making progression impossible. NWN 2..... AHAHAHAHAH....no.... got better with community patches but that shit doesn't work with just the obsidian patches.

You probably shouldn't compare anything to last year unless you're insulting it, as saying something was better than a game last year is like saying it took more than 30 minutes to give you a tumor. Its not praise, its just saying its better than a kick to the balls.

If you missed it, I don't have a very high opinion of Obsidian, not because they make bad games but because they release broken games and then never fix them. Half their games need community patches to be considered stable. It drives me insane as the ONLY time I ever found that acceptable was when vampire the Masquerade: BloodLines did it and that's only because Troika flat out died and wasn't able to patch it, Obsidian still being alive doesn't get that excuse.

Pyrian:

snekadid:
If someone played for more that 10 minutes they would have equipt a new piece of gear and found this bug.

Nah, the bug only occurs if you double-click to equip something when you don't have an open slot for it. That's exactly the sort of bug that tends to sneak through, on account of the fact that you'd never intentionally do it in normal gameplay.

...What? you mean, you, during the course of normal gameplay, would never double click a piece of gear to equipt it when the slots already filled? You mean you would never replace old gear with better gear? I'm not mocking you so much as confused as to your meaning since what you just said sounds exactly like how game play in a RPG works. Or were you being sarcastic, because that would make more sense.

A fan made fix is already out on the nexus, but ofc who would check modding sites when the game was made using Unity which is famous for giving the middle finger to modders:
http://www.nexusmods.com/pillarsofeternity/mods/11/?

A side effect - You can't split stacks of items in inventory since it's made by double clicking.

NoShoes:
Blah Blah Blah

[b][a href='/news/view/140282-Pillars-of-Eternity-Game-Breaking-Bug-Alert' target='_self']Permalink

Hyperbole much? This bug is in no way game breaking and I doubt many wouldn't even notice if they had it.

Poor Obsidian, I've dropped over 30h into PoE and haven't seen a single bug yet. It is literally the least buggy game I have ever played and yet they still get flak over one bug.

Supahewok:

snekadid:
My question is thus, even considering obsidians shit tier level of bug checking, HOW THE FUCK did they miss something like this? It's the most basic command in a RPG.If someone played for more that 10 minutes they would have equipt a new piece of gear and found this bug. Did they manage to get it to launch without crashing or instantly frying your hard drive and label it a success?

My guess is that the Day One patch caused the bug. It wasn't an issue in the backer beta, from what I hear, and also the rest of the game is really well polished. Aside from some scrolling issues when you have multiple item description popups and one time when half of a certain character's voice acting got eaten somehow, I haven't encountered any bugs in 20+ hours of game time. Shit is downright stable compared to KOTOR 2, NWN 2, Alpha Protocol, or any Bethesda game. Better than a lot of AAA releases last year, let me tell you.

Agreed. Smooth as silk, beautiful as anything and more fun than I ever hoped it would be. Man....I SO hope this is the start of a new golden era for RPGs.

snekadid:
My question is thus, even considering obsidians shit tier level of bug checking, HOW THE FUCK did they miss something like this? It's the most basic command in a RPG.If someone played for more that 10 minutes they would have equipt a new piece of gear and found this bug. Did they manage to get it to launch without crashing or instantly frying your hard drive and label it a success?

I bet it's rather easy, seeing as I've double clicked hundreds of times and never once encountered this bug. How are you supposed to catch a bug no one reports? Besides, the game is really, really well polished all in all.

Obsidian does fantastic work. I don't have this game yet but I have yet to be truly disappointed by any of their games so I'll get it sooner or later.

This looks like the kind of thing that must have come out in a day one patch. I'm sure they will get it fixed. It's not like they are the only dev to have bugs at launch. They simply get ragged on for it more.

I read this and imidiatly load up my game in fear of having done just this, only to realise that durning my now 40 hours played I have not a single time double-clicked an item to equip it. How that is possible considering I do this in nearly any other game is beyond me, I just drag and drop itmes for no apperent reason. So yeah, all my characters have all their stats still. Pehw...

Only bug I've seen so far is that my tank apperently has the "blind" status, but does not have any penalties for it (as in no hit to his accuracy), and as far as I can see he's doing just fine. Sort of just shrugged it off pritending he lost his eyesight somewhere along the way, but somehow learned to just sense the world around him instead. I think it was when he tried to pet the fox companion because he just can't resist it and it scratched his eyes out.
Edèr don't need eyes, he's just too awesome.

Obsidian games have more killer bugs than Starship Troopers.

I'm actually downloading it right now, but maybe I'll wait for a few patches before I play it. I have Bloodborne to keep me busy right now anyway.

After I heard about the bug from a friend I realized I'd been dragging and dropping the entire time and thus was not affected

 

Reply to Thread

Posting on this forum is disabled.