Skip to main content

Character Reviews

Character review is NarutoVerse's moderation layer for profiles. It lets a server decide which character fields matter enough to require staff approval before the character is treated as ready for ordinary roleplay.

The default Balanced and Strict rulesets require approval. Freeform does not require it by default, but a server can still enable approval explicitly.

What gets reviewed​

The server chooses which fields are review-sensitive. Available reviewable fields include core identity, lore and power information such as:

  • name and age;
  • village, clan and rank;
  • specialization and chakra natures;
  • stats;
  • jutsus and abilities;
  • kekkei genkai;
  • appearance and history;
  • affiliation;
  • OC/canon type and source canon character;
  • avatar.

Casual fields such as pronouns, likes, dislikes, goals and notes can also be included if the server wants them covered by review.

Review outcomes​

An authorized reviewer can generally resolve a submission in three ways:

Approve​

The submitted state is accepted and the character can move forward under the server's policy.

Request changes​

Use this when the character is fundamentally acceptable but needs a fix. A good change request explains what must change and why so the user does not have to guess.

Reject​

Use rejection when the submitted character should not be approved in its current form and a normal change request is not the appropriate outcome.

tip

Use request changes for fixable problems. Rejection should not become a vague substitute for telling the user what needs correction.

Self-review protection​

Normal reviewers cannot approve their own submission. This avoids a simple conflict of interest.

An administrator can only use the exceptional force path with an explicit reason, so the override is recorded instead of silently bypassing review rules.

What happens after an approved character is edited​

Review-sensitive edits can legitimately return the character to review. This is intentional: changing a major field such as stats, jutsus or lore after approval should not bypass the same policy that applied to the original submission.

A casual field can be treated differently depending on the server's configured review field list.

Reviewing efficiently​

A useful review order is:

  1. Confirm the character type is allowed (OC/canon/both).
  2. Check the active ruleset limits.
  3. Check stat/jutsu budgets.
  4. Check canon uniqueness when applicable.
  5. Review server-specific lore/power requirements.
  6. Leave one clear decision/reason.

Reviews and scenes​

Approval changes the source character state. It does not silently rewrite a character snapshot already frozen inside an active scene. That separation protects continuity.

Common mistakes​

  • Approving only from the displayed name/avatar without checking the configured review fields.
  • Treating webhook messages as proof that the character was approved; proxy eligibility and review state are separate checks.
  • Rejecting a fixable profile without explaining what needs to change.
  • Assuming an approved profile can make unlimited review-sensitive edits without another review.