Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Twitch Plays Pokémon X: Coordinate Proposal
- ===========================================
- Single Battles
- ==============
- Main objective: don't hit an Item or a Pokémon.
- This is fairly easy on the right half of the screen, because the gaps between Items line up better with the gaps between Pokémon. The sweet spot is a good 8 pixels high.
- On the left half, the gaps overlap less, reducing the sweet spot to 3 pixels high. This is within the touch screen tolerance, so there is a risk of hitting an Item or Pokémon even with a coordinate in the sweet spot.
- To decrease the risk, I aim one pixel away from the bottom right corner of the Item button. Theoretically speaking, there is a 75% chance of avoiding the Item button and 25% chance of hitting it (if the deviation is to the top right). I'm not sure if there are ways to improve this, or if the reasoning is actually justified by the hardware workings. For example, if the deviation is always the same for a given coordinate, then the reasoning is flawed: the coordinate either hits or doesn't hit the Item button.
- att1: 157,60
- - 25% chance of hitting Item 1
- http://mattiasbuelens.github.io/tpp-coords/?x+bf1234-bp*,bq*;157,60@bf#bf
- att2: 319,64
- http://mattiasbuelens.github.io/tpp-coords/?x+bf1234-bp*,bq*;319,64@bf#bf
- att3: 157,120
- - 25% chance of hitting Item 3
- http://mattiasbuelens.github.io/tpp-coords/?x+bf1234-bp*,bq*;157,120@bf#bf
- att4: 319,124
- http://mattiasbuelens.github.io/tpp-coords/?x+bf1234-bp*,bq*;319,124@bf#bf
- mega: 140,180
- - 25% chance of hitting Item 5
- http://mattiasbuelens.github.io/tpp-coords/?x+bfm-bbbpr,bdab,bfjk,bg*,bp*,bq*,btabc;157,180@bf#bf
- Multi Battles
- =============
- Main objective: don't hit an Ally, Item or Pokémon.
- Secondary objective: don't hit an Item or Pokémon.
- Tertiary objective: hit a Foe.
- The Foe buttons are vertically aligned with the Attack 1 and Attack 2 buttons. It is impossible to hit a Foe with Attack 3 or 4. Therefore, we should prefer top row attacks in Multi battles.
- Another problem with bottom row attacks is that the Ally buttons of Double and Triple battles combined cover the whole screen width. This renders most of the button areas of Attack 3 and 4 unusable and leads to a lot of unwanted overlap on the remaining areas. Therefore, we cannot use the same set of coordinates for both Double battles and Triple battles. Fortunately, only two coordinates actually differ.
- att1: 120,60
- + hits Foe 1 in Double Battle
- + hits Foe 2 in Triple Battle
- - 50% chance of hitting Item 1
- http://mattiasbuelens.github.io/tpp-coords/?x+bd12,bf1234,bt123-bdab,bp*,bq*,btabc;120,60@bf#bf
- att2: 200,64
- + hits Foe 2 in Double Battle
- + hits Foe 2 in Triple Battle
- http://mattiasbuelens.github.io/tpp-coords/?x+bd12,bf1234,bt123-bdab,bp*,bq*,btabc;200,64@bf#bf
- att3: 157,120
- + Same as general Attack 3 coordinate.
- http://mattiasbuelens.github.io/tpp-coords/?x+bd12,bf1234-bdab,bp*,bq*;157,120@bf#bd
- att4: 319,124
- + Same as general Attack 4 coordinate.
- http://mattiasbuelens.github.io/tpp-coords/?x+bd12,bf1234-bdab,bp*,bq*;319,124@bf#bd
- In Triple battles only, use these coordinates for Attack 3 and 4 instead:
- att3: 105,120
- - 50% chance of hitting Item 3
- http://mattiasbuelens.github.io/tpp-coords/?x+bf1234,bt123-bp*,bq*,btabc;105,120@bf#bt
- att4: 214,124
- http://mattiasbuelens.github.io/tpp-coords/?x+bf1234,bt123-bp*,bq*,btabc;214,124@bf#bt
- Switching
- =========
- Main objective: hit Pokémon both in Battle and Overworld screens.
- Secondary objective: don't hit an Item, Summary, Restore or Check moves.
- Tertiary objective: hit Switch.
- We can abuse the gap between Item buttons to hit a Pokémon and Switch. Unfortunately, the gap is rather small and it's hard to guarantee both hitting the Pokémon and *not* the item.
- poke1: 1,1 (alternative 1)
- - does not hit Switch
- http://mattiasbuelens.github.io/tpp-coords/?x+bp123456,bss,op123456-bq*,bsmrw;1,1@bp#bss
- poke1: 157,50 (alternative 2)
- + hits Switch
- - 50% chance of hitting Item 1
- http://mattiasbuelens.github.io/tpp-coords/?x+bp123456,bss,op123456-bq*,bsmrw;157,50@bp#bss
- poke2: 162,50
- + hits Switch
- - 50% chance of hitting Item 2
- http://mattiasbuelens.github.io/tpp-coords/?x+bp123456,bss,op123456-bq*,bsmrw;162,50@bp#bss
- poke3: 157,100
- + hits Switch
- - 50% chance of hitting Item 3
- http://mattiasbuelens.github.io/tpp-coords/?x+bp123456,bss,op123456-bq*,bsmrw;157,100@bp#bss
- poke4: 162,100
- + hits Switch
- - 50% chance of hitting Item 4
- http://mattiasbuelens.github.io/tpp-coords/?x+bp123456,bss,op123456-bq*,bsmrw;162,100@bp#bss
- poke5: 157,150
- - does not hit Switch
- - 50% chance of hitting Item 5
- http://mattiasbuelens.github.io/tpp-coords/?x+bp123456,bss,op123456-bq*,bsmrw;157,150@bp#bss
- poke6: 162,150
- - does not hit Switch
- - 50% chance of hitting Item 6
- http://mattiasbuelens.github.io/tpp-coords/?x+bp123456,bss,op123456-bq*,bsmrw;162,150@bp#bss
- Alternatively, we change the objective to reduce overlap in Overworld screens rather than in Battle screens. We'll probably need these coordinates more in the Overworld for operations (TM teaching, party re-ordering,...) rather than in Battle for switching. It might be better to optimize for Overworld usage and allow more overlap with Battle screens.
Advertisement
Add Comment
Please, Sign In to add comment
