Proxy Scopes
Scopes let you use different characters in different parts of the same server without constantly changing one global selection.
NarutoVerse resolves normal proxy selections from the most specific scope to the broadest:
Thread
↓
Channel
↓
Category
↓
Server
The first valid selection found wins.
Why scopes are useful
Imagine that your server has:
- a general RP category where you usually play Kakashi;
- a mission channel where you play Yamato;
- a private scene thread where you play an OC.
With scopes, you can keep all three selections at the same time. Sending a message in the private thread uses the thread selection; leaving that thread falls back to the channel/category/server selection that applies there.
Scene threads are different
When a thread belongs to a NarutoVerse scene, the scene participant's snapshot is the stable identity for that scene. This prevents a later global selection change from rewriting who you entered the scene as.
Enabled scopes vs character selections
Two separate ideas are easy to confuse:
- Server configuration scopes decide where NarutoVerse is allowed to operate.
- Your proxy selection scopes decide which character should speak there.
Having a character selected does not enable NarutoVerse in a channel that the server has not configured for RP.
Excluded scopes
Server administrators can explicitly exclude configured channels/categories. Exclusions take priority over the general enabled scope check.
Use a thread-level selection when you are participating in multiple simultaneous RP threads. It keeps each conversation stable without forcing you to change the character used elsewhere.
Troubleshooting precedence
If the “wrong” character speaks, check from most specific to broadest:
- Is this a scene snapshot?
- Is there a thread selection?
- Is there a channel selection?
- Is there a category selection?
- What is selected at server scope?
Do not start by deleting the broadest selection; a more specific one may be the real cause.