Bug Fixes Guides

Bug Fixes throws you into fog and grass with a katana and a one-line poem: is honor truly dead. The official description is a key list, not a tutorial. This hub is the missing first hour. Start with Getting Started if you have not dueled yet. Keep controls open while you learn E, Q, and F. Then graduate to how to fight, the armor grind, cinematic mode, the lantern map, hats, mobile play, and Highborn.

The game is live on Roblox, created 9 August 2026 by captainwoodlegs, with help from adeptrblx, tannergombi, aedanluke, and jondecus. Servers hold up to 50 players. Combat is directional melee plus stance changes, not an anime kit. That is why these guides stay mechanical: when to bow, when to pray, when to displace, and when a musket line is a feature instead of a glitch.

How to use this hub

1. New spawn. Getting Started covers PC-only expectations, the fist/katana hotbar, and why mobile users bounce.
2. Hands. Controls is the keybind bible: X, B, E, Q, F, R, =, G.
3. Duel. How to fight turns those keys into cuts that actually land.
4. Look. Armor is the pray loop for kabuto and red plates.
5. Camera. Cinematic mode is the kurosawa chat trick.
6. Field. Lantern map is landmarks when the description names no zones.
7. Brim. Hats is =, the drop-hat prompt, and silhouette language.
8. Phone. Mobile play is the PC-first warning plus the drop-hat clip.
9. Spare sword. Highborn is the 50 Robux wakizashi pass and the shrine one-life copy.
10. Classes. Classes covers samurai, ronin, ninja, and shinobi playstyles mapped to the actual binds.
11. Weapons. Weapons is every tool on the field: katana, fist, wakizashi, musket, and shinobi tools.
12. Advanced combat. Advanced Combat goes past the basics into reads, displacement tricks, and team fight thinking.

Cross-link into systems when a guide is not enough. Stances belong on the tier list and stances. Honor reading belongs on players and honor. Movement quirks including displace sit on movement. Patch context sits on updates.

What these guides will not do

They will not invent a quest log the game does not have. They will not list codes that do not exist. They will not pretend full controller support is finished. The description is explicit: no full console or mobile support yet, and those platforms are intended for people with keyboard attachments. If you are on a phone without a keyboard, you will fight the UI more than other players. Read mobile play before you buy a fake HUD pass. The only listed storefront item is Highborn.

They also will not treat scripts as a tutorial. If you want executor notes, go to scripts and understand the ban risk on a skill-based melee title. Learning R to change stance is the intended power spike.

Pain points we wrote toward

• “What do I press?” The description dumps eight binds with no diagram. Controls and the controls sheet fix that.
• “Why is everyone in a helmet?” They prayed. Armor and the pray tool explain the loop.
• “Is the gun a glitch?” Community videos show musket lines and a shinobi teaser. Read gun teaser and loadouts instead of reporting a musket as a bug.
• “The camera feels like a movie.” That can be the easter egg. Cinematic mode tells you how to turn it on and off.
• “I keep losing despite clicking.” Directional cuts and stance matter more than click speed. How to fight is the page for that bruise.

Video policy on this wiki

Each guide that has a useful public video embeds exactly one YouTube clip in the middle of the article. We do not stack trailers at the bottom. The getting-started page uses a first-impressions session. Armor uses a samurai-armor update clip. Fight uses a gameplay session. If two videos cover the same topic, we keep one page.

Next reads outside Guides

After the tutorials, jump to tier list so your stance choice is not random, then updates so you know whether muskets were a test or a keep. Official links stay on links. The desktop Guides dropdown shows at most eight titles; extra pages including mobile and Highborn collapse into this hub via View all.