Morioh High’s official description explicitly includes making friends and enemies, forming relationships, and interacting with NPCs. It does not publish a complete NPC directory, universal affection meter, or guaranteed dialogue reward. Use the interaction the current client shows, then judge the visible response before assuming hidden progress.
Start one clear interaction
Approach a character until the current prompt appears. Identify whether the target is an NPC or another player before acting. Read the name, role, objective marker, or interaction label that the game provides.
On PC, current community control guides report holding C for a voice or dialogue prompt. The available options can depend on distance and context. If C does nothing, check the visible prompt rather than repeatedly pressing it. On mobile and controller, use the on-screen interaction control.
Choose one clear request or response. Wait for the reply, animation, objective change, or menu update. Starting several interactions quickly makes it difficult to tell which choice produced the result.
Separate visible relationship changes from roleplay
Friendship, rivalry, and roleplay can be meaningful even when no number appears. Record what the game actually confirms: a label, new option, objective, status, item, or other visible change. Do not convert a friendly line into invented relationship points.
Likewise, a negative reply does not prove a permanent enemy state. It may be contextual dialogue, a failed request, a cooldown, or the current character’s behavior. Repeat only when the interface permits and the interaction remains appropriate.
If the game exposes a relationship panel, use its exact labels and date your observation. No stable first-party table was verified for point thresholds or rewards, so a copied fan value should not override the live screen.
Use the prompt as your decision map
Conversation
Read before choosing
Identify who is speaking, what is being asked, and whether the option affects an objective.
Confirm: visible reply or state change.
Request
Ask for one specific action
Use the option presented by the client and wait for acceptance, refusal, or another prompt.
Confirm: do not assume silence means success.
Relationship
Track only exposed status
Use an actual label, panel, or changed option if present.
Unknown: hidden totals or universal thresholds.
Player interaction
Respect consent and platform rules
Another player is not an NPC. Accept refusal and avoid pressure, harassment, or private-information requests.
This method keeps a story interaction useful without promising a mechanical outcome the interface does not show.
Connect NPCs to classes and clubs carefully
A teacher or club character may direct you toward a room, seat, activity, or membership screen. Follow that visible objective. The Classes Guide explains how to confirm the room and lesson prompt, while the Clubs Guide explains why membership warnings matter.
Do not assume every teacher shares the same consequence system or that every club NPC changes relationships. Community reports mention consequences for witnessed fighting, but exact NPC detection, detention, or penalty rules need live verification.
When an NPC appears linked to Stand acquisition, keep the route separate from social progress. A delinquent fight, Occult case, or Arrow use does not automatically document a relationship system.
Troubleshoot a missing or frozen prompt
Move out of range and approach once more. Close chat, settings, and other overlays. Confirm that the objective targets this character and that another dialogue is not active.
If the NPC is absent, check the current room, time or objective state shown by the game. Do not invent a schedule. Another server may reflect a recent update, but rejoin only once before seeking current help.
If dialogue freezes, wait briefly for server response, then close the interaction through the visible control. Record the character, location, objective, device, date, and last displayed line when reporting the issue. Remove other players’ usernames and private chat.
Handle other players differently from NPCs
The official description’s friends and enemies language also supports social play, but another player controls their own participation. Ask before a planned duel, group activity, or extended roleplay. Stop when they decline or leave.
Never request a password, session cookie, authenticator code, payment, or off-platform personal information. Do not trust a player who claims that account access is required to change a relationship, grant a Stand, or activate a code.
Use Roblox’s privacy, block, and report tools when needed. A relationship mechanic does not override platform safety.
Keep a useful interaction note
Record the NPC or role shown, location landmark, objective, prompt, chosen option, exact visible result, and date. This provides enough context to compare an update while avoiding a speculative “likes” score.
If another source reports a threshold, look for a current full interaction sequence and live panel before using it. Repeated claims without direct current evidence remain community reports.
NPC and relationship questions
Are relationships an official feature?
Yes. The official Roblox description explicitly mentions forming relationships. It does not define a universal point system or reward table.
How do I talk on PC?
Holding C is the current community-reported voice or dialogue prompt input. Use the live prompt and available options because context can change the action.
Where is the complete NPC list?
No sufficiently current first-party directory was verified. Follow objective markers and character labels in the current client rather than using an invented list.
Does every conversation give relationship progress?
No such universal rule was verified. Look for a visible status, objective, option, or response before claiming progress.