The last cutscene in 4.7 landed like a dropped stone: sudden, heavy, and leaving a widening circle of gossip. You felt the chill—forums buzzing, streamers rewinding the same frame. I watched it play out and kept asking the same thing: who actually killed Luxbane?
On Reddit and YouTube the final frame ignited debate — HSR Luxbane: Everything New Revealed in Version 4.7
I’m going to walk you through what changed in 4.7, what the game finally confirmed, and where the biggest holes still yaw. You’ll get what Hoyoverse put on the table, how the Intelligentsia Guild lore fits, and why the Trailblazer’s presence raises hard questions. Read fast—this one rewires the campaign’s stakes.
On official logs and guild reports, the name Luxbane appears as a single, ominous entry — Who is Lord Ravager Luxbane in Honkai Star Rail?
The patch didn’t give us a biography. Instead, it dropped a verdict: Luxbane is one of the Lord Ravagers — the Emanators of Destruction — and in HSR it carries the terrifying sobriquet Sun Devourer.
I treat lore like evidence. The Intelligentsia Guild files attribute Luxbane with extinguishing roughly one-third of the stars in the Yvanna Chain over 300 years. That’s not mythic flourish; that’s system-level annihilation.
In practical terms, Luxbane isn’t a single body in the human sense. It’s described as an indescribable mass that eclipses suns. Luxbane is a sun-swallowing god. Some analysts on YouTube and Reddit point at Leviathan remnants as a likely origin — a dead lineage reborn as a cosmic hazard rather than a person.

Who is Luxbane in Honkai Star Rail?
Short answer: a Lord Ravager — a cosmic-level threat framed as a natural catastrophe rather than a character with a conscience. If you want the long answer, I’d study the Yvanna Chain casualty reports and the Aeon catalog entries in Planarcadia’s sealed archives.
On livestreams, fans rewound the Oroboros scene a dozen times — Lord Ravager Luxbane’s connection to Oroboros and Voracity
You probably caught Aeon Aha’s line: Luxbane had been stalking Oroboros, the Aeon of Voracity. Oroboros is dead in the present timeline, but its remains are sealed in Planarcadia, and 4.7 staged a near-fusion of Oroboros with the Path of Elation and Aha’s body.
The narrative inference is simple: each Lord Ravager has a target. Luxbane’s interest in Oroboros points toward Voracity as its assignment, but the script refuses to pin Luxbane down as a single-minded hitman. The sequence plays more like tectonic plates sliding: forces converge, then detonate.
That’s where your theorycrafting tools — lore wikis, Discord databases, and YouTube breakdowns — matter. Cross-reference in-game journals with community-run databases and you’ll see the pattern: Luxbane’s encounters are cataloged as cosmic events, not one-on-one duels.
Did the Trailblazer really kill Luxbane?
The game’s twist is surgical. You and I both saw the final log: Luxbane’s remains, trauma consistent with external penetration. The Trailblazer is physically present fighting the Oroboros-Aha amalgam, yet the report names someone appearing as the Trailblazer in the Yvanna Sector as Luxbane’s killer.
That contradiction is the whole story beat. The simplest explanation is an impostor or a future self. We already witnessed an Aeon of Finality who matches the Trailblazer’s silhouette. The person who felled Luxbane was not the Trailblazer you control today; they were a version of them that became something else. A future Trailblazer moved as a blade of finality across the void.

On the final mission log, the corpse report was blunt — Is HSR Luxbane dead?
The in-game forensic note is explicit: Luxbane is confirmed dead. The cause reads as penetrating trauma, not entropy or decay, which implies a directed attack rather than passive collapse.
That leads to two practical implications for you and me. First, a Lord Ravager can be eliminated — the lore moves from inevitability to contingency. Second, whoever killed Luxbane has power and intent strong enough to operate at cosmos scale. That changes future bookkeeping: factions like Planarcadia, the Aeons, and Trailblazer variants now become candidates for direct confrontation.

Is Luxbane dead?
Yes — the game labels Luxbane as dead in 4.7. The mystery isn’t the death itself; it’s the identity of the killer and the mechanics that allowed a Trailblazer-shaped agent to be in two places at once.
If you follow creators on YouTube or comb the threads on Reddit and the HSR Discord, you’ll see two camps: one that treats the event as proof of time-folding or future selves, and another that suspects a copy, proxy, or new faction. I lean toward a future-Aeon angle, but I’m listening to every plausible counterargument.
For now, 4.7 rewrites the score: Lord Ravagers are vulnerable, the Trailblazer’s timeline is now a weapon and a question, and Hoyoverse just handed the community an unsolved file to argue over. Who else could wear the Trailblazer’s face and why would they strike Luxbane first?