Combat
Combat is the D Tier default fighting style that every player starts with in Sailor Piece. It provides basic punches and kicks with minimal damage output and no special mechanics.
How to Obtain
Automatically unlocked — all new players begin with Combat equipped.
Abilities
| Move | Key | Description |
|---|---|---|
| Basic Punch | Z | Standard melee attack with low damage |
| Kick | X | Simple kick attack |
Stats
| Stat | Value |
|---|---|
| Rarity | Common |
| Tier | D (Ranked #18 of 18 Melee Specs) |
| Stat Priority | Any |
Strengths
- No requirements to unlock — available immediately
- Functional for the earliest levels of gameplay
Weaknesses
- Lowest damage output of all fighting styles
- No special mechanics, AoE, or crowd control
- Should be replaced as soon as the player reaches Shibuya Station (Level 3000+)
Tips
- Replace Combat with Gojo or Cursed Vessel as soon as you reach Shibuya Station
- Combat is only a placeholder — do not invest resources into optimizing it
Source guardrails
This page is kept as player guidance for Sailor Piece. When exact values, hidden rates, damage numbers, drop chances, or prices are not directly verified by the listed sources, treat them as legacy guide context rather than confirmed current facts.
Bloxpedia Hub does not recommend scripts, executors, mod menus, or downloadable reward tools for this game. Use official Roblox data, visible public source reports, and recently checked code status before spending rare resources.
Player-use checklist
Use this Combat page as a live decision aid, not as a permanent claim that every old value, reward, or tier-list opinion is still current. First identify the exact problem: codes, beginner route, unit choice, resource spending, boss pressure, trade safety, or source confidence. Then check whether the page sources actually support the claim you are about to act on.
For Sailor Piece, the safest next step is usually the one that removes the current blocker with the least risk. If a code is uncertain, keep it pending. If a build claim depends on a changing unit, trait, pet, fruit, or reward, check the source date before spending resources. If a mode or route fails, change one decision at a time so you can see what fixed the run.
Source and safety check
Do not treat Discord invite pages, general chat, copied screenshots, old code lists, value screenshots, or short videos as final proof. Exact rates, hidden values, current rewards, and update-specific mechanics need a readable source. Reject scripts, executors, mod menus, account checks, cookie requests, browser extensions, downloads, QR scans, and Discord token requests even when they promise faster progress.