Morioh High uses familiar Roblox movement plus separate combat and Stand actions. The PC map below is repeated across current community guides, but it is not a first-party permanent key sheet. Verify each action against the live HUD, especially after an update or when a specific Stand changes the prompt.
PC control lookup
Normal combat
Left mouse
Reported light attack input.
Check: range, recovery, and whether a menu is open.
Stand active
Right mouse
Reported Stand barrage input.
Check: summon state, target range, cooldown, and meter.
Defense
F
Reported block input. Current coverage describes the guard as frontal.
Movement
Q
Reported dash input for repositioning or escape.
Targeting
Ctrl
Reported lock-on toggle. Release it when target tracking harms your route.
Menu
M
Reported side-menu input, including access toward Settings and Codes.
Stand skill
X
Reported Stand skill input. The actual effect depends on the current kit.
Stand state
Z
Reported summon or withdrawal input.
Voice prompt
Hold C
Reported voice or dialogue prompt input. Read the options shown before choosing.
Standard Roblox movement, camera, jump, and chat behavior can still depend on your client settings. This guide does not overwrite the prompts shown by Roblox or the game.
Test the normal controls first
Move to a low-risk area and make sure chat or a menu is not capturing the keyboard. Test movement and camera, then left mouse, F, Q, and Ctrl one at a time. Watch the character and UI rather than pressing several keys quickly.
For block, face the threat and look for current feedback. For dash, observe the direction and ending position. For lock-on, note which target is selected and how the camera changes. Toggle it off before testing free movement again.
Open the menu with M and identify the current labels. Community code guides report a Settings then Codes route, but the interface can be rearranged. Follow the visible menu rather than clicking an old screenshot’s coordinates.
Test the Stand controls second
Press Z once and confirm whether the Stand appears and the meter becomes active. Do not assume a failed summon means Z is wrong; the bar may be depleted or the character may be in a state that blocks summoning.
With the Stand active and a safe target available, test right mouse once. Then test X once. Observe range, startup, recovery, cooldown, and meter change. Press Z to withdraw before reaching zero.
The exact action on X and the behavior of a barrage depend on the Stand. The Stands List identifies documented kits but intentionally avoids inventing a move sheet where current evidence is incomplete.
Use controls as decisions, not a combo string
Left mouse is useful when the target is within the normal attack’s range and the recovery is acceptable. F is useful when you face a readable threat. Q is useful when changing position solves the problem. Ctrl is useful when stable tracking is more important than free camera movement.
Right mouse and X are useful only when the Stand is active, the resource is available, and the target or situation fits the action. Z is both an access input and a resource-management input because withdrawing can preserve meter.
This decision map remains helpful after balance changes. Memorizing a long key sequence without understanding its first safe opening does not.
Mobile and controller guidance
No sufficiently consistent current mobile or controller map was verified for this page. Do not translate the PC keys into guessed button names. Use the on-screen controls or Roblox device mapping presented by the current client.
On touch, identify the menu, attack, defense, movement, targeting, summon, and Stand-skill icons before entering combat. Test them individually in the same order as the PC route. If an icon disappears, check summon state, meter, context, and whether another panel is open.
On controller, use the live prompts and Roblox settings. If the game exposes remapping, confirm the saved mapping after leaving the menu. When sharing a control correction, specify the controller and platform.
Troubleshoot an input that does nothing
Close chat, text fields, settings, and other overlays. Confirm the game window has focus. Test the input once, then check for a cooldown, stun, safe-zone restriction, empty Stand bar, or missing summon state.
If several controls fail together, rejoin once after confirming Roblox service status. Do not repeatedly reinstall the client or run an unofficial repair tool. A recent update may also change a prompt while an older server retains previous behavior.
If only one Stand action fails, compare it with another action from the same kit and reproduce the condition. Report the date, platform, Stand, input, meter state, and visible response without sharing private account information.
Build a personal quick card
Write the six actions you actually need: normal attack, block, dash, targeting, summon or withdraw, and one Stand action. Practise those until you can choose them without looking away from the target. Add menu and voice controls when school or social activities require them.
Keep the quick card action-based rather than key-only. “F: face and block” is more useful than “F” because it remembers the reported frontal requirement. “Z: withdraw before zero” connects the input to the meter decision.
Control questions
What key summons a Stand?
Z is the current community-reported PC input for summoning or withdrawing. Verify the live prompt and meter state.
How do I block?
F is the reported PC input. Face the incoming threat because current coverage describes frontal defense.
What does C do?
Holding C is reported to open a voice or dialogue prompt. Read the live options and release or select as the interface instructs.
Why is there no mobile key table?
The current evidence is not consistent enough for a reliable fixed map. Use the actual touch controls rather than guessed translations from PC.