View Full Version : 100% hit and block still possible O.o ?!?!?
ChainHeart
07-15-2006, 07:00 PM
ok, sry dont have any s/s ~_~ didnt think this would happen.
F_A told me to post this up anyways :p .
here is what happened, my opponent's archer had -60 in blocking, and i shot at the archer in the front to kill it, but it blocked !!!! :confused: is this a bug ?
this is my theory - that the % is not a whole number so the game rounded it up, the hit was suppose to be 99.9% ... and F_A just got a 0.1 % block on me.
Does that make sense? or is that just a game error...:dry: I NEED TO KNOW
some1udontknow
07-15-2006, 07:07 PM
That is just there saying that it should have a -60 percent of blocking. But it is just a little guide for you to get a idea to attack or not. And i've had far worse than that, and hit them. I shot a Pyro, in the front with -112 blocking, and it killed it.
Maverik07
07-15-2006, 07:14 PM
ouch, that sucks
Enjoi
07-15-2006, 07:27 PM
That is just there saying that it should have a -60 percent of blocking. But it is just a little guide for you to get a idea to attack or not. And i've had far worse than that, and hit them. I shot a Pyro, in the front with -112 blocking, and it killed it.
Do you mean +112?
R.I.P
07-15-2006, 07:29 PM
weird
Forest_Archer
07-15-2006, 07:37 PM
Ah ahm so lucka!
[/scottish accent?]
ChainHeart
07-15-2006, 07:50 PM
-_- so the numbers are NOT EXACT?
=/ and once my opponent's pyro blocked an attack and the blocking went to -190. :dry:
can the blocking ever exceed 200+/-?
plusminus
07-15-2006, 10:26 PM
I think the lowest a blocking adjustement can go is a knight blocking from the side on a 99% chance of hit. He'd have to be -79 to begin with, the block would take him down another 120, putting him at -199. Of course as soon as the turn ended he'd be at -179. The other extreme, a witch blocking from the side at 99% chance of hit, would be (-19) + (-180) = -199, again. In fact, I'm too lazy to do the math for all the units, but I think anyone blocking from the side on 99% will have it work out to -199%, give or take 1% from rounding.
In the other direction, I think the most you should go is +99, possible on anyone that gets hit from the front on a 1% chance.
Of course, getting a block on 100% hit (or more) could change all that. :/ And so back to your original question, it sounds like it's just a bug, but I could see how it would be a rounding oversight (which is still a bug really, but a different kind than some random glitch). The numbers are supposed to be exact, but glitches happen. Either way it probably happens very very infrequently.
VAMP7
07-15-2006, 10:43 PM
http://img85.imageshack.us/img85/7269/untitled28ob3.jpg
ChainHeart
07-15-2006, 10:53 PM
o.0 wow...
i think there is a glitch in the blocking system...i remember a grey game i had when i was down to my last knight, i had 70+ in blocking or something over 70.
in this situation shouldn't the knight block any attacks on the side as well as the front? instead i lost due to a side attack.
*in a normal situation knight has a 60% chance of being hit...and 70 blocking should cover it, with + to spare...yet i got hit... explainations?
Batosi
07-15-2006, 10:57 PM
Lol blocking system is still the same guys but now people can have alittle better clue on there hit rate! This game is still nothing but luck, I had a dude that shot my archer and he only had 1% and killed it. Also I killed a knight with only 3% to hit and I killed it. Game is still about luck, dont take it to heart! :P
uniquinous
07-15-2006, 11:00 PM
Perhaps I'm completely off on this, but nowhere next to the -198 do I see a percent sign. It's a numeric qualifier, and not a 100% guarunteed definite - treat it that way at the least.
monkus
07-15-2006, 11:06 PM
o.0 wow...
i think there is a glitch in the blocking system...i remember a grey game i had when i was down to my last knight, i had 70+ in blocking or something over 70.
in this situation shouldn't the knight block any attacks on the side as well as the front? instead i lost due to a side attack.
*in a normal situation knight has a 60% chance of being hit...and 70 blocking should cover it, with + to spare...yet i got hit... explainations?
Okay, here's where most of you are off (except uni):
The blocking #s are modifiers to the unit's actual blocking stat.
For example:
Give a knight +30 and his blocking becomes 110. That means 110% of blocking front shots, 55% blocking side shots.
Treat the unit as if his/her blocking number was modified.
Maverik07
07-15-2006, 11:21 PM
o.0 wow...
i think there is a glitch in the blocking system...i remember a grey game i had when i was down to my last knight, i had 70+ in blocking or something over 70.
in this situation shouldn't the knight block any attacks on the side as well as the front? instead i lost due to a side attack.
*in a normal situation knight has a 60% chance of being hit...and 70 blocking should cover it, with + to spare...yet i got hit... explainations?
look at monkus' reply, so he normally has 80% blocking + 70 is 150, and with the side shot u divide by half = 75% chance to block, so ur opponent had one in four to hit
plusminus
07-15-2006, 11:36 PM
Perhaps I'm completely off on this, but nowhere next to the -198 do I see a percent sign. It's a numeric qualifier, and not a 100% guarunteed definite - treat it that way at the least.
You're completely off ;)
If a scout has -60 or lower and you aim at him (click the orange square but not the red), it will show your chance to hit as being 100%. Similarily if he had +40 or more and you aim from the front, it will say 0%.
monkus
07-16-2006, 12:05 AM
You're completely off ;)
If a scout has -60 or lower and you aim at him (click the orange square but not the red), it will show your chance to hit as being 100%. Similarily if he had +40 or more and you aim from the front, it will say 0%.
I think we had a mistranslation here or something.
Oh well. I think it's clear that you just add/subtract the modifier to the unit's original blocking #, and you have the new temporary blocking percentage, half for sides.
gryph89
07-16-2006, 12:25 AM
Perhaps I'm completely off on this, but nowhere next to the -198 do I see a percent sign. It's a numeric qualifier, and not a 100% guarunteed definite - treat it that way at the least.
Ya, but even if the numbers make up a percentage. I see it stupid to display those numbers if the variable rounds up. Those numbers output the blocking % on hit and miss (I think. . .) So if it rounds up (Only guess. . .) What's the point of even having those numbers there in the first place? To provide a basic concept on how screwed you are if your going to attack or defend?
The AIDS Virus
07-16-2006, 01:44 AM
Ya, but even if the numbers make up a percentage. I see it stupid to display those numbers if the variable rounds up. Those numbers output the blocking % on hit and miss (I think. . .) So if it rounds up (Only guess. . .) What's the point of even having those numbers there in the first place? To provide a basic concept on how screwed you are if your going to attack or defend?
Uniqnubs post was the most accurate. It's only a modifier, no matter what there is a chance you can hit. I hit BD's scout the other night when it had like 120 with the modifier. I shot up front and hit.
Personally, I don't look at the modifiers because they ruin my game. I'm sure jeffrey will post here in a bit with an exact quote of why this happens anyway.
Fallin_Demon
07-17-2006, 12:35 AM
Lol blocking system is still the same guys but now people can have alittle better clue on there hit rate! This game is still nothing but luck, I had a dude that shot my archer and he only had 1% and killed it. Also I killed a knight with only 3% to hit and I killed it. Game is still about luck, dont take it to heart! :P
You wanna talk about luck, now I ahve seen it all....
This guy I played today got 3 REALLY lucky blocks. First he gets a scout side block at a 97% hit chance, then he gets a knight side block at a 93% chance and RIGHT after that he got a 99% scout side block. I was to a point that I felt lucky his cleric didn't get a back block..:dry:
vBulletin® v3.8.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.