You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the end of the 10th turn is reached in a battle, currently the program will be surprised that it's wiped out with non-zero lives and throw out a warning and keep going. While the current operation doesn't break anything, it could be optimized to avoid throwing this warning if a simple for loop were added that increments a counter the turn counter every time the Fight symbol gets detected. That way, it can be prepared for no "Catch / Don't Catch" menu popping up on Turn 10, and the program can safely switch to the next mode without a warning in conjunction with the detection of the black screen.
I do think it's important to leave the current black screen detection in to end the run, because if for some freak reason if the Fight symbol gets detected an eleventh time (which won't happen), this setup should handle a case like that to keep fighting anyway since no black screen would have been detected at that point.
The text was updated successfully, but these errors were encountered:
We might be able to add a turn counter when we start using the battle text to learn more about stat changes et cetera. We would have to account for 2-turn moves and Outrage/Petal Dance since they take multiple turns but only show the "Fight" symbol once.
If the end of the 10th turn is reached in a battle, currently the program will be surprised that it's wiped out with non-zero lives and throw out a warning and keep going. While the current operation doesn't break anything, it could be optimized to avoid throwing this warning if a simple for loop were added that increments a counter the turn counter every time the Fight symbol gets detected. That way, it can be prepared for no "Catch / Don't Catch" menu popping up on Turn 10, and the program can safely switch to the next mode without a warning in conjunction with the detection of the black screen.
I do think it's important to leave the current black screen detection in to end the run, because if for some freak reason if the Fight symbol gets detected an eleventh time (which won't happen), this setup should handle a case like that to keep fighting anyway since no black screen would have been detected at that point.
The text was updated successfully, but these errors were encountered: