Skip to main content
Pocket RivalsPocket Rivals
Season 8

Author profile

Pocket Rivals Editorial Team

The public byline for Pocket Rivals guide pages, role hubs, hero editorial modules, and ranked queue advice.

Site-written guides and ranked tool notes

Editorial focus

Practical ranked context for everyday queues

This byline is used where Pocket Rivals adds original recommendations on top of official Marvel Rivals source context. It does not claim official affiliation, professional coaching status, hidden statistics access, or guaranteed ranked outcomes.

Bronze-to-Platinum ranked decision-making

Role fundamentals and practical hero swaps

Official-source context translated into next-queue actions

Privacy-conscious Match Analysis guidance

Byline model

What this author label means today

Pocket Rivals Editorial Team is the public label for site-written pages, not a claim that the project has a staffed newsroom.

The site owner remains responsible for shipped copy, source choices, AI-assisted drafts, code changes, and review decisions.

The byline is used on original Pocket Rivals guidance: guides, role hubs, hero editorial modules, examples, and ranked tool notes.

A named operator or stable pseudonym should replace or strengthen this label after that public asset is available.

Review checklist

What this byline is responsible for

  • Separate official Marvel Rivals facts from Pocket Rivals recommendations.
  • Keep patch-sensitive advice dated and update it after relevant official changes.
  • Prefer concrete examples, role tradeoffs, and next-fight actions over broad filler.
  • Avoid claims of affiliation, hidden win-rate access, or guaranteed ranked outcomes.

Source boundaries

What the byline can and cannot claim

  • Official Marvel Rivals pages are used for roster, role, team-up, event, patch, and source-link facts.
  • Pocket Rivals advice is the independent layer that translates those facts into lower-rank queue decisions.
  • Pages should not claim hidden live win-rate access, official approval, professional coaching credentials, or guaranteed outcomes.
  • AI assistance may support drafting and maintenance, but visible pages should remain accountable to the site owner and editorial policy.
Read methodology

Correction readiness

What a useful correction should include

  • Correction requests should identify the page URL, the claim that may be wrong, and the official source or observed behavior that supports the correction.
  • Privacy or removal requests should avoid adding private data to public match notes and should wait for the real public contact channel before sending sensitive details.
  • Patch-sensitive pages should be rechecked when official balance, roster, event, or tool behavior changes.
  • Until the public contact channel is available, the Contact page remains the source of truth for support status.
Contact status

Read the work

Pages carrying this editorial model

Ranked GuidesRole GuidesHero LibraryDaily Digest