Jump to content

Atrik

Community Members
  • Posts

    291
  • Joined

  • Days Won

    11

Atrik last won the day on August 24

Atrik had the most liked content!

6 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Atrik's Achievements

Triplicarius

Triplicarius (5/14)

211

Reputation

  1. It's less prevalent thanks to the melee re-balance, but in some cases it's still very important, and will 'force' you to snipe even if you would rather not doing it, your example with hans is one, another is when enemy has pikes, or even just if you have archers. I don't think it would be possible to avoid either: 1. accepting sniping as game mechanic (I don't like it) even with workaround this would still give a big fighting efficiency boost to players sniping. 2. introducing a feature that replace alt-clicking for sniping by a less spammy one (in this case, this thread wouldn't have to exist).
  2. I'm ofc not talking about removing the ability to make a single unit attack, but rather to add a feature to make sniping less spamy. In my opinion too much workaround are considered when any fun micro feature could just make a great fix for this spamy meta. Example of feature I suggested in another workaround tweaking by @real_tabasco_sauce:
  3. Just fix sniping... Any game mechanic that is about clicking fast fast is not interesting, and subjected to create unbalances if anyone has 'gaming' mouses/drivers with click multipliers or anything.
  4. I also think that champ cav shouldn't be nerfed too much, just having more viable counters is needed.
  5. Besides the hurdle of having to find the good limit to population of allowed units, I don't think it is fun to make a limit on any unit. Champs are a great way to 'coil up' and invest some economic advantage. The problem is the lack of counter options and their efficiency against specifically: melee champ cavs spam. As I said above, even champ spears are meh... not that good of a counter. In short, investing in champ cav is too safe, because of the lack of counters and the amazing versatility of cavalry. Hence the suggestions to nerf capture rate, and increase counters.
  6. As chrstgr said, they get slaughtered even when you have a big number's advantage. In some cases where i had a bunch of spears champs from sparta or athen (note that they require special, costly buildings to make compared to champ cav), they merly counter the champ cav. They deal x2.5 but champ cav have x2 hp (when they have the buff hp), it's just not fair counter. Spears should slaughter cavs, not the other way around. They already have mobility they can use at their advantage.
  7. Yes exactly, when 100+ cs spears get slaughtered by cavs it's just non-sens. You would think you are playing counter and therefor, even if you can't kill the cavs (because of their mobility), they also can't just run into your spears and kill all, but that's what they do actually.
  8. If you need a reason to nerf cavalry capture rate you could also say that it's not as convenient to raid a buildings with cavalry. As for swords vs spears, of course against infantry, swords are better. But spears are still the 'alpha' cav as they would counter other cavs, and do pretty much well against infantry in the same time.
  9. Champ spear cav is just more available and is also the champ cav for the civilsations who have buffed champ cavs; such as Persians, Seleucid and to a lesser extent Gauls. I guess champs cavs are really just slightly too good of an option too often, because of the mobility and strength, and capture rate. The problem really is that the critical mass of a champ spam being unstoppable is reached too early. If some suggest that they should cost 2 pop, I think it would be too much of a nerf. Spears could have increased counter damage (restore it to x3 in com mod as an example, no idea why it was brought down to x2.5) and maybe cost slightly increased, like 100metal instead of 80. Also all cavs could have 50% only of the capture rate of their equivalent infantry.
  10. If the prepare time is reset every time a unit receive a order like halt, target, or move by itself, as I I think it is, then it's the main delay during witch overshoots occurs.
  11. I've tested for pikemen and crossbows and both overshoot cav running away. Pikes still hit in the wind and the cav far away takes the hit. Again not complaining about it, this is better then if the pike would never land a hit, but if your patch impact performance for no effects, then I don't understand the point. Maybe limit the range check for only the units that have the slowest attacking units (crossbow and pikes aren't included).
  12. I guess it's not going to kill performances but since most players agree performances is the priority, I guess @real_tabasco_sauce should not add it to community mod. It's only making any differences for bolts and catas. For all others units, there isn't anything changed about overshooting (witch is also good for playability). Part of the overshooting was due to unit taking into account target movement and will still be added to unit range, therefor extending overall max range. This is unaffected by the patch. The other part of when unit is targeting a unit moving away and getting out of range is also, from my tests, unchanged. Only bolts and catas might interrupt their attack if the target move away early enough.
  13. No it's only poison, fire cavalry are decent units to take down buildings thanks to fire damage.
  14. Try to add this within <Resistance><Entity> <ApplyStatus> <Burning> <Duration>0.0</Duration> <BlockChance>1</BlockChance> </Burning> </ApplyStatus>
×
×
  • Create New...