Skip to main content
Pocket RivalsSeason 9 · July 10 patch live
Pocket Rivals
Season 9

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

Author relay

Read the byline as a transparency layer

The author profile explains what the editorial label means, where it appears, and what standards it is meant to uphold.

  1. 01BylineUnderstand the author labelThe byline marks site-written ranked judgement, not official affiliation or hidden data access.
  2. 02CoverageSee where the judgement appearsCoverage links show the pages where Pocket Rivals adds practical context beyond raw source facts.
  3. 03ReviewCheck what the byline is responsible forThe profile documents review focus, source boundaries, and when the trust pages should change.

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

Coverage map

Where this byline is most visible

The author label appears where Pocket Rivals adds judgement or structure beyond raw official facts. These pages are the clearest examples of that editorial work.

Daily DigestTurns official patch, event, and balance windows into short queue reads with dates and source limits.Hero LibraryConnects official hero details to counters, role context, practical ranked reads, and source-review notes.Ranked GuidesExplains repeatable Bronze-to-Platinum problems such as target focus, resets, support duos, and objective timing.Coach ExamplesShows privacy-safe match notes and the kind of next-fight coaching the Match Analysis workflow should produce.

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 Lennon supplies that asset.

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.

Review cadence

What gets checked, and when

Fast review

Patch notes, balance posts, new heroes, official team-ups, and Daily Digest entries should be checked when official source windows change.

Regular review

Hero reads, counters, builds, role hubs, and team-comp pages should be revisited when the current ranked advice stops matching the patch context.

Policy review

Trust pages should change when Pocket Rivals adds a public contact channel, operator detail, new data provider, AI workflow, or ad behavior.

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