< DBFZ
Android 17 | |
---|---|
Play-style | Rushdown, Rekka, Mix-up |
Team Role | Point, Mid |
Overview
"Let's have some fun. This is a game, after all." | |
Lore: | Android 18's younger twin brother. Forcibly turned into a cyborg alongside his sister by Dr. Gero for the purpose of destroying Son Goku, he rebelled and killed Dr Gero with little effort. Despite being free from the doctor's demands, both 17 and 18, along with the reactivated Android 16, continued in their task in killing Son Goku just for the entertainment. 17 was then absorbed by Imperfect Cell, but was later revived by Shenron after Cell's defeat. With Goku gone and the world at peace for the time, Android 17 became a park ranger in order to preserve nature and wildlife. Many years later, 17 finds himself with the Z Fighters again after being recruited by Son Goku to join in the Tournament of Power as one of Universe 7's strongest warriors, with 17 ultimately winning the tournament as the last remaining fighter. |
Playstyle
Android 17 Android 17 operates as a speed-type character who can throw out many special moves with follow-up inputs, as well as punish moves with his barrier.
Pros
Cons
- Rekkas/multi-inputs, cross-ups and 4 lows give him a plethora of mixup options and damage.
- Has good stagger pressure with his normals and anti-air options with his rekkas.
- Above average solo damage in the right scenarios.
- Good meter gain when utilizing ki blasts.
- Multiple ToD routes with the right assists and an even more amazing meter gain in sparking.
- Barrier Explosion is a reversal, meaning Frame 1 invincible.
- Acrobatic Assault allows him to have extra mobility with a little mix-up potential, and can also extend combos.
- Nice corner carry with M rekka inputs.
- Fast assist with multiple applications, being defensive and offensive at the same time.
- More technical than other characters, which requires a higher level of execution and solid conditioning for his tactics.
- His options in the air are very limited and his acrobatic assault only works in specific situations.
- A lot of his strings or mix-ups are not real.
- Most of his normals are poor in horizontal range.
- Struggles a lot in neutral without assists except in a 1v1 situation.
Normal Moves
5L
5L | Template:AttackDataHeader-DBFZ |
---|
5M
5M | Template:AttackDataHeader-DBFZ |
---|
5H
5H | Template:AttackDataHeader-DBFZ |
---|
5S
5S | Template:AttackDataHeader-DBFZ |
---|
2L
2L | Template:AttackDataHeader-DBFZ |
---|
2M
2M | Template:AttackDataHeader-DBFZ |
---|
2H
2H | Template:AttackDataHeader-DBFZ |
---|
6M
6M | Template:AttackDataHeader-DBFZ |
---|
3H
3H Sliding Sweep |
Template:AttackDataHeader-DBFZ |
---|
j.L
j.L | Template:AttackDataHeader-DBFZ |
---|
j.M
j.M | Template:AttackDataHeader-DBFZ |
---|
j.H
j.H | Template:AttackDataHeader-DBFZ |
---|
j.S
j.S | Template:AttackDataHeader-DBFZ |
---|
j.2H
j.2H | Template:AttackDataHeader-DBFZ |
---|
Special Moves
Accel Driver
Accel Driver 236L/M/H |
Template:AttackDataHeader-DBFZ |
---|
Finishing Driver
Finishing Driver 214L/M/H |
Template:AttackDataHeader-DBFZ |
---|
Driver Follow-Ups
Driver Follow-Ups Any button after a "Driver" attack |
Template:AttackDataHeader-DBFZ |
---|
Acrobatic Assault
Acrobatic Assault 236S or 214S (Air OK) |
Template:AttackDataHeader-DBFZ |
---|
Power Blitz Charge
Power Blitz Charge 22S |
Template:AttackDataHeader-DBFZ |
---|
Power Blitz
Power Blitz 22S after Charge (Air OK) |
Template:AttackDataHeader-DBFZ |
---|
Z Assists
Assist A
Reverse Gear Assist A |
Template:AttackDataHeader-DBFZ |
---|
Assist B
Power Blitz Charge Assist B |
Template:AttackDataHeader-DBFZ |
---|
Assist C
Accel Driver Assist C |
Template:AttackDataHeader-DBFZ |
---|
Super Moves
Endgame
Endgame 236L+M |
Template:AttackDataHeader-DBFZ |
---|
Barrier Explosion
Barrier Explosion 236H+S (Air OK) |
Template:AttackDataHeader-DBFZ |
---|
Super Electric Strike
Super Electric Strike 214L+M or 214H+S (Air OK) |
Template:AttackDataHeader-DBFZ |
---|
To edit frame data, edit values in DBFZ/Android 17/Data. Be sure to update both the
move
and the move Full
sections. One is shown on the character page, while the other is shown on the frame data page.