Yup I can atest to this problem existing - I lost two games in a row, wondering why I couldn't do any damage to health. So I played through a third game (also lost) where I fought every battle in-game. Not a single attack from any archer unit or bow-equipped hero does any damage at all - all attacks results in a miss.

In these combats, melee combat appears to work as per normal.

Sov and archers always miss with the shortbow. I also noticed that my earth elemental stone rain ability is missing all targets however I've only tried to use it about 6 or 7 times so far.

I'm having the same issues.  Bows are definitely broken.  Tried with several unit types and enemies.  Same result every time "MISS"...

I'm having the same problem, happening with catapults as well.

Just verifying that bows no longer do damage in my new game either.  Ran into a bandit party.  Bandit's bow did not cause any damage to my party.  I later equipped my Sovereign and 7 NPC's with cedar longbows.  Despite 16+ attacks per round, no damage.  Defenders had 0, 1 or 2 defense (i.e. minimal).

This is with the patch that was uploaded tonight (Friday).  With 1.08xx (the previous one), bows were causing huge amounts of damage.  One extreme to the other.  I miss the 1.07 bows...

I am liking the speedier combat though.

I'm starting to wonder if there is any serious testing at all . I still have high hopes from the game, as i have since beta but really... they're still missing this sort of thing completely?? Maybe we should have a patch once a fortnight or so, get some actual testing done. I imagine this so-called 'hot-fix' didn't go through QA. That's really, really not a good idea...

Same here. Just tried to start a new game and ran into this.

This and the vanishing mana seem to be the most serious issues introduced with the latest patch. Hopefully we can get a hotfix for the hotfix!

Good work on finding a root cause.  I haven't done any modding before, but this seems like a good time to learn enough to fix this small bug.

Thanks for the info!

I'm not so sure that is a math error. The two lines of code are attempting to mimic the min/max effects placed on spells and in the case of the bow that is 0 to AttackValue.  My guess would be the change in "combat" code is testing for a zero value and going auto miss but is not set up to understand min/max. I would be interested to see if the code works if the MIN (note MINE) value was first to be calculated therefore passing the maxvalue as the old "value" parameter.

Either way SD will be on top of it. Now if we could just get the worldnames and unitmnames files capable of mod override I"ll be a happy camper.

This thread should read, 1.08b blows 100%!

Who's doing the QA for this project, JoWoo productions?

I'm still waiting for Elemental Version 2.0, because the way things are going, I don't think version 1.1 will do it!

Data tweaks alone are mostly harmless, IMO.

It's code changes that don't maintain compatibility with old data that are problem. Like for example when num_shards field out of blue became real number of shards instead of shards+1. Sure you can change damage formula in XML files to match it, but it breaks old saves (since they rely on old XML data).

Also, I really don't see a reason why creature abilities or things like ranged bow attacks needed new min/max value tags. They should have kept old ones, with old code in place to properly interpret them just as in 1.07 or earlier. And only spells should have been tweaked with new values. That way, changing spells wouldn't make it possible to break something else.

hunh?!?!!

so max value is multiplied by "-1" and the min by "-0.1". that's kind of screwy as it seems like the only way you could get a the thing to do damage is if your attack was actually supposed to not do damage.

(negative times a negative equals a positive and all that)

so how i'm reading it is taht any time the units base attack value is positive, that calculation would invert the value into a miss.

shouldn't it be max =1 and min =0.1?

The new min/max thing lets you mimic multi die roles, which is essentially what people have been asking for. Instead of just implementing it for spells only, extending it to weapons is a great boon in my view. If they didn't, you'd get people asking why they can't just use the same system for weapons. Of course doing it without testing the results and end up breaking stuff doesn't look so good, but that's what happens when you are trying to rush out a fix for something else...