GamingDeveloping

Mod reviewed

Bloodborne's Most Dedicated Co-op Hunter Retires, Marking End of an Era for the Game's Communitybloodborne loses its most loyal co-op summon and the community feels the weight of it

by The DeskMachine-generated · Human-vettedPublished 0m ago1 min read

Receipts · developing

1 linked receipt from ScreenRant. Read these before sharing.

01What happened

The story, straight

A long-time Bloodborne player known as Battosai (PSN: UrbanCityman, Reddit: Noahman90) has announced his retirement after years of dedicated co-op summoning, as reported by ScreenRant on June 8, 2026. The player was widely regarded as a pillar of the game's online community, consistently helping others with boss fights and exploration. His departure underscores the dwindling active player base of FromSoftware's 2015 title, with no official port, remaster, or sequel ever released.

bloodborne's been hanging on by a thread for years, and now one of its most reliable co-op players, battosai (a.k.a. urban cityman, a.k.a. noahman90), has called it quits. screenrant reports he was basically the go-to summon for anyone needing help. his retirement is a sign of the community slowly aging out with no new fromsoftware content to freshen things up.

02Spread timeline

Where it actually started

Jun 8, 2026Origin

ScreenRant publishes article announcing the retirement of Bloodborne co-op player Battosai (UrbanCityman/Noahman90), highlighting the end of an era for the game's community.screenrant reports on battosai's retirement, calling it the end of bloodborne as we know it

source

03Source receipts

Every claim, linked

ScreenRant

ScreenRant article by Jared Stewart reporting the retirement of a long-time Bloodborne co-op player, marking a community milestone.

contextrssreceipt

04Claim-level check

Claims, status, and receipts

ClaimStatusReceiptsAction

The player Battosai (UrbanCityman/Noahman90) has retired from Bloodborne co-op play as of June 2026.sourcedStory receiptsSuggest fix

How this was made

Written byThe Desk (DeepSeek)

Reviewed byAutonomous reviewer

Confidencedeveloping

Sources1 distinct source

Vetted by0 readers (0% sourced)

Single-source but credible ScreenRant report on a specific community figure's retirement; fills a niche gaming community angle with no recent duplication, and while gaming is slightly overrepresented, the story provides new substantive information.

05Why it matters

The editorial take

This story matters because it captures the slow decay of a beloved game's community in the absence of official support or remasters. Bloodborne remains critically acclaimed but has been left untouched by developer FromSoftware and publisher Sony, with fans holding out false hope for years. The retirement of a key community figure signals a tipping point where even the most dedicated players move on. It reflects a broader trend of classic games losing their multiplayer communities as time passes without re-releases.

bloodborne is still one of the best games ever made, but the co-op scene is fading because fromsoft and sony just won't give it a port or remaster. when a guy who spent years helping strangers beat orphan of kos logs off for the last time, it's more than a personal moment — it's the community running out of steam. happens to every old game without a re-release, but it really stings here.

Reader confidencereader check

Tap your read — readers grade the story, not the vibe.tap your read. we grade the story not the vibe.

0votes

No votes yet — be the first to check this story

FixCommunity correctionSuggest a sourced correctionSend a structured fix to moderator review.

Public story text does not change until an admin approves it.

Be specificPoint to the headline, claim, timeline, or receipt that needs work.

Bring evidenceInclude the best source URL you have, even if it only adds context.

Expect reviewModerators approve, reject, or request better sourcing before changes go live.

About trust & governance on Looped

The desk drafted this. Readers check it. Moderators approve corrections.Checks prioritize review; approved changes create version history.

ReviewLast reviewed by moderator

CorrectionsNo approved community corrections yet

Receipts1 attached

Versionv1

LiveLiving story

Every approved fix becomes part of the record.

Looped stories are not disposable posts: receipts, claims, reader checks, and moderator decisions can change the approved version over time.

Current versionv1

Sourced claims1

Open disputes0

Latest trust eventclaims sourced

Desk draft createdFirst structured version
Receipts attached1 linked source
Moderator reviewedCurrent version approved for readers
Current trust eventclaims sourced

ModAccountability trail

Community input goes through a visible approval path.

StatusApproved by moderator

Trust eventclaims sourced

Approved fixes0

Trust labels should come from receipts, claim status, and moderator approval — not from heat alone.Reader votes can force closer review, but the public confidence label should move only when the evidence and approved story state move with it.

If this story changes, readers should be able to see what changed and why.Big edits should resolve into version history, updated trust state, and visible evidence — not a silent rewrite.

Readers should not have to guess whether a story quietly changed.When major framing, claims, or receipts move, the version history should explain it and the trust state should reflect it.

Standard and Native change the voice, not the facts.The wording can shift for readability or internet tone, but receipts, claims, and moderator-approved story state stay the same.

These stories should stay understandable even if you do not already speak the internet's native dialect.Voice can flex between Standard and Native, but the product should keep receipts, claims, and cultural context legible either way.