Bugs Thread

[camelotcrusade]

Got it. I'll update the entry. Was that fix put in on build 6249?

I'll add the bit about the yellow ball, too.

[ckdamascus]

Originally Posted by camelotcrusade

Got it. I'll update the entry. Was that fix put in on build 6249?

I'll add the bit about the yellow ball, too.

The pacify "not not" fix was in build 6249 surprisingly. Without that, pacify would never do the slightly increased damage.

[ivra]

Some additional information regarding the yellow ball that might or might not be relevant any more...
1) My current game where the yellow ball occurs is 100% 6249. In my first game I did not encounter the yellow ball. That game was started after Patch 1, but mainly played after Patch 2.
2) My graphic card is ATI Radeon HD 5800 Series, version 12.10 (latest available).

Originally Posted by dainbramage

As for the rune, that's more bad/unintuitive map design than a bug. You have to go through from the other side (i.e. facing from creiston mines to greenwort), it's passable even though it doesn't look it. using the arrow keys will probably help.

Thanks! That worked, but it wasn't easy. And yes, I had to use the arrow keys in order to navigate to it.

[Fatt_Shade]

@camelotcrusade
I listed things i found in items.txt that were wrong. Didnt think it really matter if i name them bugs , errors, misses, or developers fu.k up. Fact remains it something that is wrong in game files.
I`ll be sure to list my finds properly in future so dev team know who should read posts : Bug developer team start reading and it says `not really bug...` and they think a OK this is not our job leave it for miss crew. Beacause they all read this forum so often.
Sry to sound bitter camelotcrusade , but i find it seriously disregardful from whole dev studio to have some problem listed on their forum and 1 month and 3 patches later it still is in game (same thing for `If you have questions re .... and some1 will answer it form devs` , bunch serious posts in there with game problems, and no1 bothered to answer them)

[ckdamascus]

Dragon of Chaos dispells properly now (it is fixed in build 6249) as far as I can tell.

[dressar63]

I don't think the Viking Absolute Rage skill works correctly. I have it at lvl 3 for my Viking and it should give
100% crit on counters
50% chance to receive 25% attack bonus on round 2
50% to crit hit dm
However my units do not always crit on counters and I have never had a unit receiving an attack bonus on round 2 (or it is not showing up as an increase in the units attack rating). The increase to crit damage is there though.

[ckdamascus]

Originally Posted by dressar63

I don't think the Viking Absolute Rage skill works correctly. I have it at lvl 3 for my Viking and it should give
100% crit on counters
50% chance to receive 25% attack bonus on round 2
50% to crit hit dm
However my units do not always crit on counters and I have never had a unit receiving an attack bonus on round 2 (or it is not showing up as an increase in the units attack rating). The increase to crit damage is there though.

It works fine.

Nope, 100% of the BASE VALUE of critical hits. A troll's crit chance base value is about 10%to give you an example. I think paladin is 12% or so.

So your "morale buffed" + items paladin with 40% critical chance on hit will counter strike with 40+12% or 52% chance to crit back.

At least that is how I am reading it.

It has a CHANCE to give you a bonus of 25% attack rating on your BASE VALUE and will show up as a status effect (with no visable icon) called "Absolute Rage". It seems to stack twice though if you get hit twice (it only has a chance to give you absolute rage, not a guarntee) and lasts for 2 rounds. It can be dispeled by a skeleton archer's black arrow though.

[camelotcrusade]

Originally Posted by ckdamascus

Dragon of Chaos dispells properly now (it is fixed in build 6249) as far as I can tell.

Thanks, I'll update it!

[ckdamascus]

During the battle with Nilrem (guy you fight for the Staff of Starlight after you beat the 3 altars of power), you will get a random "ai_solver error" pop up if in debug mode.

If you are not in debug mode, this results in a crash to desktop with NO "there was an error with kbwotn.exe". It just magically shows up to the desktop with no error.

Build 6249/6249.