Blox Fruits races currently need a seven-race hub for Human, Rabbit, Shark, Angel, Ghoul, Cyborg and Draco. Each race page should explain how to obtain it, base passive, V2, V3, V4, gears, best fruits, best builds, weaknesses and change history.
Race index
The Blox Fruits races cluster starts with Human, Rabbit, Shark, Angel, Ghoul, Cyborg and Draco. A race page should not be only a name and a table; players need requirements, version effects and practical build context.
| Race | Detail page focus |
|---|---|
| Human | General use, damage windows and beginner clarity. |
| Rabbit | Movement, chase potential and escape value. |
| Shark | Survivability, water safety and defensive use. |
| Angel | Mobility, support value and V4 context. |
| Ghoul | Unlock route, sustain and night-related details. |
| Cyborg | Unlock route, energy and utility details. |
| Draco | Current status, requirements and source verification. |
Version structure
Each Blox Fruits races page should separate V1, V2, V3 and V4. The V4 section especially needs requirements, gears, ability effects, best fruits, best fighting styles, weaknesses and source records.
Version separation matters because players often search for one upgrade step, not the entire race. A V2 requirement page should answer what to do next; a V4 page should explain trial requirements, gear choices and what still needs testing.
Use-case guides
Good supporting pages include race tier list, best race for PvP, best race for grinding, best race for Buddha, how to change race and Race V4 Guide. They should publish after the methodology and version data are complete.
Comparison standard
The race tier list should not rank races with one universal score. It should compare PvP, grinding, mobility, survivability, Buddha synergy, fruit-main builds and mobile play separately. That gives Blox Fruits races a practical reason to exist beyond a roster list.