AndreaColombo

The game had a number of sound files for NPCs that were never hooked up and never played. Among them, comments on your progression restoring Caed Nua; guess that's what Aloth's remark is (barks for clicking repeatedly on a character and for friendly fire were hooked up in 3.0.) Perhaps firing it every time you visit the stronghold is a bit too often?

More like ... inaccurate? 30 was always the maximum base Accuracy, and all of my characters display their base Accuracy correctly in the breakdown (but that's after starting afresh post 3.0.) With older saves I get 5 more base Accuracy than I should for each character, but not 15.

Unfortunately I have already overwritten that save If nobody else can provide one, I'll try to load an older save and get to that point over weekend. From there, reproducing the issue is very easy.

Many of the fixes I would call pretty major, actually

bump for visibility

Spending a talent point is a cost. And the difference in power level is negligible anyway.

Nah, those aren't really coming into it itt

Typos here plz: https://forums.obsidian.net/topic/77064-translation-errors-missing-translations-english/page-6?do=findComment&comment=1783305

It probably will. Scaling ups the ante by 33% (if PotD is any indication, the ante is enemies' Accuracy and Defenses.)

Psychic Backlash leaves that square. I could repro 100% of the times when fighting the bounty in Cilant Lis; Durance would get hit by Psychic Backlash systematically when trying to cast Painful Interdiction and the icon would stick after the battle ended. Saving and reloading would turn the icon into a white box.

Very old bug. Don't think it'll be fixed at this point

https://forums.obsidian.net/topic/85094-px2-31-enemies-like-to-slaughter-innocent-people-instead-of-me/ Probably the same issue; allegiances seem to be broken in this build.

^ think he meant Clear Out.

http://forums.obsidian.net/topic/84990-survival-racial-accuracy-bonus-bug/?do=findComment&comment=1785833

Probably the same issue as you're having with the pet. Textures are working fine for me on these spells.

It's a proc from one of your items; probably one of the newer ones which is missing a string for its proc name. Are you wearing the Glittering Gloves (or however they are called)?

Siphoning Image is also pretty kick-ass.

Interesting. I checked Edér's character sheet, and under "Binding Rope" is only says "+2 Constitution, (Suppressed)" (basically there's no name for the Stuck proc). Removing the helmet (which grants retaliation) removes the suppression as well. Putting the helmet back on keeps the effect going, but the helmet's Retaliation is suppressed. So the belt needs to be equipped first, before any other piece of equipment that has a retaliatory proc (being it the classic retaliation, or a status proc like Lavender Wreath's); this way, the Stuck proc will work, but the other will be suppressed. EDIT: Saving and loading will restore the suppression on the belt's proc and take it away from the other item's. Clearly a bug; hope it's already fixed in 3.02

Bump for visibility; would like to confirm whether the item works at all and, if it does, whether it works as intended

Bump for visibility. Hopefully it's not a global issue but just to confirm.

Same issue in this thread.

I know a number of bugs of this very nature have already been reported, and hopefully fixing one will fix the problem globally. However, for the sake of completeness and because this time the bug has gone far enough to make me post about it, here's another example of "mixed-up alliances". SAVED GAME: link OUTPUT LOG: link REPRO STEPS: Load the attached saved game. Select the party and walk downward; you'll run into a bounty almost immediately. Observe that part of the soldiers that are supposed to fight you do, in fact, not; rather, the run in the opposite direction and start killing all innocent bystanders in the map. If you follow them, engage them, and hit them they will disengage and keep going for the innocents (one of whom is a quest giver and of course you can't have the quest if they kill her.) This happened to me in other areas as well—enemies fighting innocents or other enemies—so it looks like 3.0 broke some part of the code that handle creature allegiances.

That's likely an unintended side effect of some other code change they made. I doubt they went out of their way and wasted development time to remove a feature that was harmless at best.

That's a pretty reasonable response, but if somebody can jury rig a fix as quickly as they did - as evident from those links - then it stands to reason that the devs can find a solution too without an insurmountable effort. Development time is a precious thing. We do not know how long it took the IE Mod maintainers to develop their solution, and we do not know whether it is completely bug free. Obsidian never officially supported the use of the console anyway; I'd rather they focus on fixing gameplay bugs for these last few patches, especially if this feature can be had via mods.

The IE Mod makes it available as of the latest version.