Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DefendLane #192

Open
1 of 3 tasks
Nostrademous opened this issue Mar 28, 2017 · 8 comments
Open
1 of 3 tasks

DefendLane #192

Nostrademous opened this issue Mar 28, 2017 · 8 comments

Comments

@Nostrademous
Copy link
Owner

Nostrademous commented Mar 28, 2017

  • Don't use TP if we can walk there (I saw Lina that was by safe-lane jungle shrine, TP to mid, to defend it. She could have walked there in the amount of time it took to TP, approx.

  • Once we arrive, bots are too weary to engage against stronger enemy defense and just hang back and let the tower fall, need to fix this (either don't defend if we won't contest, or bring more firepower and contest). We should not use pure # of heroes as an estimate who to TP

  • Once we decide to defend, we should probably push the wave out until 0.5 lane-amount is reached (to the river) before going back to do something else like farming/laning/pushing (unless it is very important, like we can get a kill or are needed in a team-fight)

@Keithenneu
Copy link
Contributor

I agree to most of it, just some notes:

  1. yeah. also, support should tp, not carries (unless necessary)
  2. We should simply use the same determination we use for fighting. stalling the push is an option as well.
  3. Ideally, that shold happen by itself, as they want to push, or farm the lane. We don't want to keep several core heroes busy just and only because a tower got pushed.

@Keithenneu
Copy link
Contributor

BTW, I'll tinker with global map considerations for a few more days (I feel like we need a game plan, and stuff like that. Killing a tower because we happen to be there is nice. But I feel like we need some Blood-Lust in the game.)
If that goes horribly wrong I'll go back to bug fixing / improving stuff.

@Keithenneu
Copy link
Contributor

Oh, and for 1. and 2.: The push detection is broken atm. number of heroes in 1200 range around the tower won't cut it. Improving that should stabilize the fight determination results.

@Keithenneu
Copy link
Contributor

The bot's perception range is way to low in general. That's another thing I'm trying to take on in the map stuff.

@Nostrademous
Copy link
Owner Author

One other thing... we are still very bad about defense in our own base.

@Keithenneu
Copy link
Contributor

Yeah, we just cant predict pushes at this time. And defending base with just the guys that happen to be around isn't going to work.

@Nostrademous
Copy link
Owner Author

Checked in a change where we actually "move towards" the tower we are to defend if we are too far away from it... we were just standing there at times in "defendlane" mode and far from tower.

@Riveon
Copy link

Riveon commented May 19, 2017

Another issue is that sometimes they TP to a tower when it isn't safe to do so. E.g. Viper and CM tp'd to the bottom tier 2 tower where there was an enemy Jugg bot (and another bot). Viper immediately retreated (meaning there was no point in Tping there instead of the tier 3 tower. (CM stayed in by herself and died.)
This doesn't happen nearly as much as with the default bots though thankfully lol.

And yeah I've seen them TP to the ancient to defend when they're in the fountain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants