Nostrademous / Dota2-FullOverwrite

Work in progress for a full-overwrite Dota 2 bot framework
GNU General Public License v3.0
97 stars 40 forks source link

fix laning #191

Closed Keithenneu closed 7 years ago

Keithenneu commented 7 years ago

Our safe lane is dying a lot. Most of it comes from over aggression / bad positioning. They also miss a few easy last hits.

Not saying that it's all bad, but I think it really needs an update.

This is mostly from observing a CM/PA safe lane. should be true for other lanes and combinations. Loosely ordered by severity.

I'm also planning some risk assessment for lanes. Might help with the positioning later on.

Nostrademous commented 7 years ago

I implemented some fixes to address some of these. working on smarter in-lane harassment currently.

Nostrademous commented 7 years ago

okay, I just pushed changes that do a lot of the above.

Currently I forced hero selection to only 5 heroes that have proper nukeDamage calculations implemented. Works great. Give it a go.

Keithenneu commented 7 years ago

Aw yeah, much better!

Just more edge cases I noticed (I'm kinda abusing the issue tracker as a public note pad ath this point..):

Nostrademous commented 7 years ago

CM does use frostbite if above a certain % mana threshold on nearby "weakest" enemy (providing the non-weakest enemy is not standing in the way, and the distance from her current position is less than Frostbite CastRange + small delta).

Nostrademous commented 7 years ago

That code used to exist in the utils.HarassEnemy() ... but I commented it out or scrapped it b/c it didn't belong there as it wasn't a harassment. I need to re-create it as part of the "fight" mode.

Nostrademous commented 7 years ago

Yeah, I know... it was hard enough getting them to not go past the tower... bots and understanding positioning is a hard problem. We need a generic solution that will tie into your map-wide orientation.