ESOCommunity

true, I changed my tactics hotkeys and don't know how to alt-d, and it happened to me twice if I recall correctly that I used it undeliberately during the game
and how can that change the meta wtf, maybe just stop abusing this, which should be fine?

iCourt wrote:

[Armag] diarouga wrote:Eh? No lol.
I think that you were told to not remove explorer hotkeys to fix alt d, but if you can fix the azzy bug, do it, it's a serious issue.

I was told not to fix cover mode from Ryan cause it could change meta.

What??? I can't believe he said that lol. It's possibly the most abusable bug in the game. How are you meant to deal with an explorer who has 2000 HP, 60% RR, 33 area damages and who's as fast as war wagons?
Oh, and he revives instantly if you kill him.

Anyway, Ryan deleted his ESOC account and left the patch team some months ago, so even if he said that, it doesn't really matter.

It did cause he still had admin rights to everything. If you want it fixed we can discuss solutions. Again keep in mind all this would need to happen on a major release patch.

On a related ote, can someone confirm that cover mode halves the opponent range amage rather applying 50% rr to the covered unit?

Garja wrote:On a related ote, can someone confirm that cover mode halves the opponent range amage rather applying 50% rr to the covered unit?

CON. FIRMED.

Garja wrote:On a related ote, can someone confirm that cover mode halves the opponent range amage rather applying 50% rr to the covered unit?

Hum, didn't know.
It's like 55% rr then, right?

I hope ep team will give Icourt full permission to fix more bugs in the future. That way we will have almost bug free game, and new players will have more motives to use the patch. Everyone likes bugfixes....

I just really, really want Agra fort hotkeys please.

I thought we just added them. Didn't we!?

[Armag] diarouga wrote:

Garja wrote:On a related ote, can someone confirm that cover mode halves the opponent range amage rather applying 50% rr to the covered unit?

Hum, didn't know.
It's like 55% rr then, right?

If the unit in question also has 10% ranged resistance, it is exactly like 55%, yes.

What if the 10% rr applies to the base damaged and then cover mode halves the result of that?

Garja wrote:What if the 10% rr applies to the base damaged and then cover mode halves the result of that?

The other way seems more logic but if I'm not mistaken it's the same:
x0.9x0.5 or x0.5x0.9
Still 55% at the end.

For calculations featuring only division and multiplication, order of execution is irrelevant.

zoom wrote:For calculations featuring only division and multiplication, order of execution is irrelevant.

Teach us!

What I meant is base damage halved + 10% rr. For example for 100 base damage:
100 - (100*10%) - 100/2 = 40
This is 60% of course. Is it possible that the cover mode works this way?

Garja wrote:What I meant is base damage halved + 10% rr. For example for 100 base damage:
100 - (100*10%) - 100/2 = 40
This is 60% of course. Is it possible that the cover mode works this way?

Oh.
Aoe is very dumb so it's not impossible.

Garja wrote:What if the 10% rr applies to the base damaged and then cover mode halves the result of that?

Garja wrote:What I meant is base damage halved + 10% rr. For example for 100 base damage:
100 - (100*10%) - 100/2 = 40
This is 60% of course. Is it possible that the cover mode works this way?

Unless I'm mistaken the above quotes are in contradiction of eachother. Nevertheless, this is how cover-mode damage-reduction works and should satisfy your inquiry: First all modifiers are applied – then damage (if ranged) is halved.

Ye I worded it wrong in the first post.
Anyway, are you 100% sure of your cover mode formula? Did you test it by yourself or did you read it somewhere?

[Armag] diarouga wrote:

zoom wrote:For calculations featuring only division and multiplication, order of execution is irrelevant.

Teach us!

I have much to teach French younglings, but teaching those who are both omnipotent and omniscient is a tall order to be sure.

Garja wrote:Ye I worded it wrong in the first post.
Anyway, are you 100% sure of your cover mode formula? Did you test it by yourself or did you read it somewhere?

I tested it in game with Blunderbuss Settlers shooting Fortress-Age Konsha Yamabushi, using whole-number common denominators. I wouldn't say that makes me 100% sure.

Ye seems to be 55% in total.

Atomiswave wrote:I hope ep team will give Icourt full permission to fix more bugs in the future. That way we will have almost bug free game, and new players will have more motives to use the patch. Everyone likes bugfixes....

Not possible to have a bug free game so long as hotkeys are available. They single handily cause about 90%+ of the major bugs found through out the history of this games life span.

iCourt wrote:

Atomiswave wrote:I hope ep team will give Icourt full permission to fix more bugs in the future. That way we will have almost bug free game, and new players will have more motives to use the patch. Everyone likes bugfixes....

Not possible to have a bug free game so long as hotkeys are available. They single handily cause about 90%+ of the major bugs found through out the history of this games life span.

If someone is skilled enough, much can be done with injecting code in exe. I don't know if it is possible with 3, but in AOE II famous userpatch works in similar fashion. It may be the only way to fix those hard coded bugs in game engine...

Missionary bounties are not updated in accordance with the cost decrease of the unit.

Did you update "TEAM Musketeer/Grenadier Hitpoints" to affect Janissaries?

- Aztec "2 war hut age up" description is now always in English, regardless of your ingame language. In a previous version of the patchi it used to be correctly displayed in user own language and with correct number of war huts (2).
- Somehow the resqued village from treasure (in the Painted Desert treasure set atleast) speaks english even if you are playing a native civ.
- The gatherer limit for each berry bush doesn't seem to work.