Vertical Slice #1 #8
Description
Vertical Slice 1
The goal for this slice is to write all the code needed to simulate, damage calc, and effect analyze the battle scenarios with player choices listed below. This will lead to most of the common-case code being written, so finishing this slice will give great insight into what parts of the design should change and how the undesigned parts should function before taking on the whole project.
Scenarios to Build For
Singles
Player_1 = EMPOLEON, DEFIANT, ASSAULT_VEST, FURY_ATTACK
Player_2 = AMPHAROS, STATIC, CHOICE_SPECS, THUNDERBOLT
Doubles
Player_1A = GARDEVOIR, SWEET_VEIL (via trace), CHOICE_SCARF, MOONBLAST (2B)
Player_2A = PANGORO, IRON_FIST, LIFE_ORB, KNOCK_OFF (1B)
Player_1B = DRAGAPULT, INFILTRATOR, FOCUS_SASH, WILL_O_WISP (2A)
Player_2B = RIBOMBEE, SWEET_VEIL, BRIGHT_POWDER, QUIVER_DANCE
Tasks
Entering Data
- Components for
dexentries #9 - Components for
PokemonSide,Battle, etc "classes" #12 - Components for turn-choice #14
- Systems for building needed move, pokemon, weather, etc dex data entities #16
- Systems for adding battle-state properties to a battle state #18
- Utility for creating battle states #20
Starting a Simulation
- Entry points for each of the main functions #23
- Options for choosing the battle format being simulated
- Systems for adding decisions of a battle state to the action queue #25
- Systems for making copies of a battle state #27
- Components for simulation results
Running Actions
- Code path for simulating a turn (TS) #29
- Code path for calculating a move's damage (DC) #31
- Code path for analyzing an effect (EA) #33
- Systems for running a move #35
- Systems for event handling #38
- Systems for ending a turn
All the tasks above, unless marked otherwise, are for the turn simulator because the damage calculator and effect analyzer run on a subset of the turn simulators code