-
Notifications
You must be signed in to change notification settings - Fork 177
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
[Enhancement] Simple tera usage #178
Comments
On terastallization in general: I started a branch where tera+move was considered for each of the available moves. I lost motivation for that because:
On your particular desire: It might be possible. Every time the PokemonShowdown server asks for a request, there is a can_terastallize flag that gets set on the active Pokemon. You can access this in the battle-bot's find_best_move function with Whatever logic you want to apply can be done so here, but you will need to change the format_decision function as well. Unfortunately, my motivation to work on further terastallization mechanics is not very high - it is a very complex mechanic with long-term consequences that cannot realistically be considered with a low depth search bot such as this project Unrelated potential bugs As always, it is impossible to say without logs - it could be a bug, or it could be the bot working as intended but being really bad. Would need full logs to see the exact state(s) being considered to know for sure. |
might be possible to just add best usage, something like
or
either way i created a fork im gonna see if i can do anything like that |
Can we get something simple like:
then use tera?
Seems like it should be simple enough, but I can't figure out exactly where we would place this code, since it needs access to a lot of different information. I was thinking get_payoff_matrix made sense since it has user_options + opp_options, but tera isnt known as a user option so it seems the only way atm to add it without modifying a few of the classes is in format_message, which doesn't really work.
Unrelated, but some potential bugs:
I did run into an issue where amoongus continually used a poison move against an opponents steel type, dont have logs, so maybe it was predicting a switch every turn, and also blissey using seismic toss continuously vs someone who tera'd into ghost (maybe it didnt know they terad?).
Anyways, great project.
The text was updated successfully, but these errors were encountered: