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

What are You Working On? #171

Closed
Nostrademous opened this issue Mar 15, 2017 · 8 comments
Closed

What are You Working On? #171

Nostrademous opened this issue Mar 15, 2017 · 8 comments
Labels

Comments

@Nostrademous
Copy link
Owner

To avoid me working on the same thing "you" are working on, can you tell me what you are doing?

My plan is to start knocking out all the listed "bug" and "enhancements" that are not "spoken for" in the Issue Tracker, and adding new heroes when my brain gets fried.

@Keithenneu
Copy link
Contributor

I'm working on gobal stuff, namely better push detection/response, better pushing. Also info about lanes that need help, be it to either survive or get a kill.
First goal is proper team wide pushing, like finding a lane to push, gathering in front of the base, and kill the tower.
I have some RL stuff coming up, so it won't be to soon.

@Nostrademous
Copy link
Owner Author

Cool, FYI, I started using the convention of bot.variableName to save bot-specific persistent information rather than setHeroVar() and getHeroVar(). It is "faster", and easier to access (you have it anywhere you call GetBot()). Eventually I will change out all our set/getHeroVar() to it, but not rushing that aspect.

@Nostrademous
Copy link
Owner Author

Checked in Legion Commander (didn't checkin the updated hero_selection.lua to not mess others up). It's a Jungling LC

@Nostrademous
Copy link
Owner Author

Checked in ported Venomancer semi-support

@Nostrademous
Copy link
Owner Author

Nostrademous commented Mar 17, 2017

In my next push I've added two new utility functions for team-fight logic:

InTeamFight(bot, range) - returns a list of allies that are in a "fight" mode within "range" from "bot", will include the unit asking the question is they are fighting already

GetScariestEnemy(bot, range, bConsiderMagicImmune) - returns the most dangerous enemy within "range" that is not already crowd controlled ( check utility.IsUnitCrowdControlled() for what it considers ) or "nil". Optional boolean flag can be passed (defaults to "false" if not supplied) to tell the function to include currently magic immune targets ( for things like Abyssal Blade use, Necro's Ult, etc)

@Nostrademous
Copy link
Owner Author

I should have Spirit Breaker offlane build committed tonight.

@Nostrademous
Copy link
Owner Author

SB is in and taking names... fun to watch him... still needs a little work for breaking charge when used as a retreat mechanic early (rather than let him finish it).

Fighting is much better now... we don't just stand there and fight.

Implemented "Use*()" functions for all usable items. Only Eul's is largely flashed out though.

@Nostrademous
Copy link
Owner Author

image

Bots getting much stronger.

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

No branches or pull requests

2 participants