Tanred

Aloth has a level 1 aoe spell that can practically one shot them. It requires proper positioning though.

I too find the hard mode to be relatively easy, hope it will pick itself up in Act II. My main concern is overlevelling the content - I am quite surprised that gaining early levels happened so fast. I have not been to yet and my party is almost at level 5. I will probably restart it on PotD and as soon as possible hire adventurers up to a full party to slow down the levelling speed.

Obsidian, thank you:)

Yeah, I see it now - I failed to realize that the 0,8x speed is actually negative. Must be a bug then.

I am not sure this is a bug - because of stacking rules. See here: http://forums.obsidian.net/topic/70763-do-afflictions-stack-on-enemies/?p=1577278

. This is derivative work, fanart (built using copyrightable parts of an IP) is owned by Obsidian Entertainment. This might be not entirely true - while the original author has the right to control the integrity of their original IP and their commercial interests, they do not automatically acquire "ownership" rights to the derivative work. The author of the derivative work has usually the full protection of copyright.

@OP: Those are really well done, keep up the good job!" And don't let the comments on the watermarks stop you from creating more art and posting it here.

Wounding Shot stays persistent too (even after resting). I haven't done any thorough testing though, so there might be more.

Update: it appears that this bug is caused by Priest's spell "Suppress Affliction"

I can't proc it for some reason. I have been testing it for a while (attacking another party character) and all crits were caused by regular rolls - no hit to crit conversion. I was expecting that it works the same way as the Hearth Orlan Minor Threat ability, when the combat log shows the conversion (Hit-[Minor Threat]->Crit). EDIT: Nevermind, I have just found that the Dirty Fighting ability activates only in combat state, so testing it by fighting another party character is pointless.

I have to disagree on this. Because clipping and engagement are currently working as designed, what Sensuki did is a legitimate party according to the rules of the game world. He is not exploiting a bug or an unintentional behavior from the game. A party of 6 fighters cheesing their way through every encounter using disengagement attacks is not only legit, but also the most powerful combination you can possibly have within PoE's rules. If you give it up, you are deliberately crippling yourself in combat / shooting yourself in the foot by going for a vastly inferior build/party for the sake of roleplaying. Which is perfectly legit, mind you—but if the most powerful party you can legitimately have is something you'd actively avoid because it detracts from your fun, that's poor game design. After playing the latest build, I noticed the clipping changes removed one of the most glaring issues - pathfinding, which now works way better both in and out of combat. This is something much more important than an occasional disengagement attack that you can possibly do from time to time due to the clipping/engagement bug (which I believe will be fixed anyway). And I think that the exploit did not show an unintentional behaviour - it requires some effort to pile up your characters this way, especially in a normal combat scenario when you are attacked on sight (I tried it). This "tactic" would be even irrational sometimes - for example when facing AoE or ranged enemies or with a different party composition - so I can't agree it is that powerful as you claim to be. In my opinion the overall gameplay experience is much more better now.

Prepared chants and titles are replaced by randomly generated undeletable chants with blank icons in the chants editor.

Fortunately, this exploit does not happen in a normal game, unless you really push yourself and probably only when you are going to attack a neutral party. I take it you don't like engagement or noclipping, but using this exploit as an argument is not the best idea. It shows how no clipping can mess the game up. There is no "argument"; he's showing off an exploit. I meant that if you want to point out broken mechanics, it is better to argue it with real game situations rather than a nonaccidental exploit.

Fortunately, this exploit does not happen in a normal game, unless you really push yourself and probably only when you are going to attack a neutral party. I take it you don't like engagement or noclipping, but using this exploit as an argument is not the best idea.

Some obsolete effects do not clear up from the effects tooltip/character sheet after their expiration.

Just to chime in, I have been playing the latest build for several hours and despite few minor bugs I am really enjoying it and looking forward to the release. It seems to be ready now.

Yes, the enemy spell auto-pause triggers on certain player spells - it has always been like that and I reported it as a bug when the first beta build was released.

Yeah, shame it has not been implemented.

Just a quick info: no changes to auto-pauses in the latest beta build. Auto-pause when a player controlled character casts a spell is still missing and the auto-pause when an enemy casts a spell is buggy - sometimes it triggers, sometimes it does not.

Yes, I wholeheartedly agree.

Only on enemy cast, unfortunately.

One of the most important auto-pause options in the Infinity Engine games was the one which triggers when a player controlled character casts a spell. Yet, it has not been implemented into PoE. I mentioned it here on forums quite a few times when the beta was released thinking it was an oversight on developers part (given that there is an auto-pause option when an enemy cast spell and many others, imo less useful, auto-pauses). I checked the last beta build and to my surprise, it is still not there. So my question is, will this ever be implemented? And if not, what was the reason to it?

Excellent.

Auto-pause remains bugged. Auto-pause option when a player controlled character casts an ability is still missing. Description of the issue: http://forums.obsidian.net/topic/68285-v278-auto-pause-spell-cast-not-consistent/

Spot on.