-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Bot Strength increase option (cheat?) #104
Comments
I think Bane is not bad? BTW, I have downloaded source code directly from this repo, how can I test in my solo bot mode with this? |
You can check out this page to start a local game: https://github.com/adamqqqplay/dota2ai#play-offline |
I have already checked that guide. |
No, although this script is called "Ranked Matchmaking AI", it cannot be used for ranked matchmaking. It's just that at the beginning, we hope that this script can achieve the feeling of ranked matchmaking.
In this case, the If you see the bot's name ending in |
Thanks for your guidance. |
Hi, can anyone help with the CPU is not picking all heroes? |
@keanesnow98 In fact, not all heroes are supported, maybe 10 to 20 heroes, such as the Invoker you mentioned. There are also some heroes who are not included in the hero pool because they are too weak. As for more heroes, you can enter the name of the hero you want the Bot to choose in the game chat box (/all for enemy), so that the Bot will choose it according to your requirements. |
Thanks again, @adamqqqplay I will try that way. |
Is it possible bots could get more gold/XP via some option? I'd like bots to cheat as it's pretty easy to play versus them at this point.
Yesterday I saw the situation when Bane solo laning while his teammates were fighting, got his lvl8 when all the others were 11+
My personal list of bots strength is below.
The list of pleasantly strong:
The list of just strong bots:
The list of Medium difficulty:
Something is really wrong with these guys (I've seen them playing much better):
The text was updated successfully, but these errors were encountered: