Are the backer beta testers under NDA?  I'm wondering how they missed it or if it wasn't present in the tested version.

There's pretty much no way we would've caught it, given that the trigger seems to be related to both areas saved and loaded in, and time spent playing for the changes to mount up enough to be noticeable - like Tanred said, we had a three map section slice of the game to play around with.  Given that it took me over 30 hours to notice anything was up with my PC in the actual game...

 

Which is probably the same reason Obsidian didn't catch it in their QA; I gather playing the game through "normally" for a week or so isn't as much a part of the testing process as playing certain content to check for specific problems, going by what others have said about this.

Where is fix ???????????????????? This is an outrage!!!!!!! One week and still unplayable game!!! Obsidian took money and can't produce fix for so simple duplication stat bug. I will never never buy again original game from Obsidian. Next time at most, only PB.

I wouldn't be surprised if this bug was actually introduced in the day one patch. Sensuki played a reviewer copy and apparently never saw it (an he's exactly the sort of player who would notice it).

If you don't save/load as much and it only happens once or twice it's gonna be pretty tough to notice it. Especially if defenses are affected.

 

Most people started noticing because of the absurd 100 int or something.

Great game and all but yeah, I got this too. With Grieving Mother. Gonna take a bit of a break from playing now and wait for the patch.

 

Still doesn´t diminish what a great game it is though.

Great game and all but yeah, I got this too. With Grieving Mother. Gonna take a bit of a break from playing now and wait for the patch.

 

Still doesn´t diminish what a great game it is though.

 

I agree, and also taking a break, reluctantly.  The bug affected me via the Drinking Horn.   My druid has 38 INT...

This has grown to a rather big topic, so I'll just ask: Is there any way to prevent this from happening at the moment ?

 

I enjoy the challenge on Hard, not too much but not too easy. The problem is, I noticed fairly late that Eder has 114 deflection, so hoping for a way to avoid it so I can start a fresh game

This has grown to a rather big topic, so I'll just ask: Is there any way to prevent this from happening at the moment ?

 

I enjoy the challenge on Hard, not too much but not too easy. The problem is, I noticed fairly late that Eder has 114 deflection, so hoping for a way to avoid it so I can start a fresh game

You have to try not to save and reload in any of the areas where you can recruit a party member.

If the area has a building you can go inside and save there, for example.

This has grown to a rather big topic, so I'll just ask: Is there any way to prevent this from happening at the moment ?

 

I enjoy the challenge on Hard, not too much but not too easy. The problem is, I noticed fairly late that Eder has 114 deflection, so hoping for a way to avoid it so I can start a fresh game

This bug can be prevented if you do not save load on companion home maps (where you recruited them from)

 

This has grown to a rather big topic, so I'll just ask: Is there any way to prevent this from happening at the moment ?

 

I enjoy the challenge on Hard, not too much but not too easy. The problem is, I noticed fairly late that Eder has 114 deflection, so hoping for a way to avoid it so I can start a fresh game

You have to try not to save and reload in any of the areas where you can recruit a party member.

If the area has a building you can go inside and save there, for example.

 

+1

 

But I also want to add that you should be careful when equipping new item with stats bonuses. Some of them can lead to stat stacking even without saving/loading within said areas.

Best advice is to check your characters stats consistently and create new saves instead of overwriting older ones. Always keep the option to load an older one when your current savegame shows some irregularities. The only other option is to wait for the patch.

Shouldn't removing all of a characters equipment every time you save help? If there's no stat boosting items, then no stat boosts?

 

Can this happen even on companions made by you?

Can this happen even on companions made by you?

It's not about the companion, it's about the location, I think.

For anyone that missed it, the fix for this issue is in 1.03 coming out (hopefully) tomorrow.

 

http://steamcommunity.com/app/291650/discussions/0/618458030654783671/

Oh wow, thank you for letting me know !

 

Now I can start playing again, deleted all my saves and avoided starting fresh before the patch, but if I can atleast avoid this bug, and the inventory bug, it should be fine

Can someone explain this to me as I've fallen foul of it and want to restart. For example, it is just the literal map that your can't save in or is it also locations inside that map (so for Eder and Aloth, is it fine to save in the Black Hound Inn or Temple of Eothas without encountering that bug - or as they're locations accessible from the Gilded Vale map are they off limits too)?

 

I guess if it's the latter maybe I'll just wait until the patch as there's no way I could do the Temple of Eothas without a save.

 

EDIT: Nevermind, I just tested it myself. I guess for anyone who didn't know it's literally only the map itself, internal locations are fine to save in (so saving in the Black Hound in is okay for Eder and Aloth but saving outdoors in the Gilded Vale is not). I guess this was already covered somewhere in the thread, but I couldn't be bothered to trawl through pages to find out.

Edited April 3, 201510 yr by Jojobobo

[...]  it is just the literal map that your can't save in or is it also locations inside that map (so for Eder and Aloth, is it fine to save in the Black Hound Inn or Temple of Eothas without encountering that bug - or as they're locations accessible from the Gilded Vale map are they off limits too)? [...]

 

See:

 

For everyone who's same as dumb as me:

 

When it's called you shouldn't save within the areas where you've recruited your companions, it doesn't mean you also shouldn't save in their sub-areas.

So if you want to save e.g. within Gilded Vale just enter a sub-area (e.g. Black Hound) and feel free to save without increasing stats.

 

Maybe for everyone else this was already a trivial conclusion, but I thought I couldn't save within the entire areas including sub-areas.  

Well, the point is that the concept of "sub area" is wrong.

If there is a transition, then it's a completely separated new area.

Can someone explain this to me as I've fallen foul of it and want to restart. For example, it is just the literal map that your can't save in or is it also locations inside that map (so for Eder and Aloth, is it fine to save in the Black Hound Inn or Temple of Eothas without encountering that bug - or as they're locations accessible from the Gilded Vale map are they off limits too)?

 

I guess if it's the latter maybe I'll just wait until the patch as there's no way I could do the Temple of Eothas without a save.

 

EDIT: Nevermind, I just tested it myself. I guess for anyone who didn't know it's literally only the map itself, internal locations are fine to save in (so saving in the Black Hound in is okay for Eder and Aloth but saving outdoors in the Gilded Vale is not). I guess this was already covered somewhere in the thread, but I couldn't be bothered to trawl through pages to find out.

Patch will come out today if nothing went wrong during the last stage of QA.

Patch 1.03 seem to prevent this bug from occurring again when save/load in a recruiting area, and retroactively fix attributes, defenses, AOE, and Healing Bonus.

 

As patch 1.03 doesn't retroactively fix endurance and health, the workaround is still applicable.

 

http://forum.cheatengine.org/viewtopic.php?t=580596

 

Latest CT file (credit to tfigment, but corrected by me): https://www.dropbox.com/s/8zh5l024c8mhvle/PillarsOfEternity_1.0.3_figment_v10_corrected_and_add_end_bonus_v2.CT?dl=0