BattleAction.hitStepMoveHitLoop [Functionality]

[aed3]

The main idea here is for the code to better handle how random events will work. This comes down to how the number of hits is calculated and how accuracy is used to determine if a move hits.

Some other aspects of the function to change/improve:

• Since only one hit per battle state can be handled at once and handling hits can generate other random events
  • (Probably a component that holds the hit number that's decremented every time a hit finishes and is removed when the value reaches 0)
• There are many "keep track of this for this one scenario" parts of the function that should be moved to only be run when that scenario is in play
• The many generation specific part should be broken out into separate functions, particularly away from the universal parts

[aed3]

There's nothing too complicated about this function that requires a design doc to resolve. The only part that required more thought, handling multihit moves, was solved when writing the description. The more fleshed-out version of the solution:

• A component HitCount will be added to the active move's entity with the total number of hits and the current hit number (starts at 1)
• An active move will only be handled if the HitCount component is present
• Once a hit is finished being handled, the current hit number is incremented and, if the hit number is greater than the total number of hits, the component is deleted