Skip to content
Powered by Pagefind
English
Rogue Blight Support

Rogue Blight Known Issues and Fixes

Track Rogue Blight save, performance, display, controller, and localization issues with versioned official fixes and report labels.

9/8/2026 1.00.08 Editorial Team Last updated: 9/8/2026 4 min read

Evidence status: Mixed—official fixes and clearly separated community reports. Last checked: September 8, 2026.

What did patch 1.00.08 fix or change?

AreaOfficial changeWhat it meansStatus
Save / black screenThe developer fixed a corruption case that could show a black screen after loading.Affected saves are expected to recover and place the character in the Sanctuary.Officially fixed
Final Boss performanceObject pooling was enabled for projectiles.The patch is intended to eliminate summon-related lag spikes.Official optimization
Tide Root performanceObject pooling was enabled for projectiles.The patch is intended to eliminate summon-related lag spikes.Official optimization
BrightnessMaximum brightness can be raised by an additional 25%.Players who found the game too dark have a wider setting range.Official change
Localization and UIMultiple language, spacing, parsing, camera, and wrapping issues were corrected.Recheck the issue on 1.00.08 before reporting it as current.Official change

“Intended to eliminate” reflects the developer’s patch note. It is not our independent performance benchmark.

Which earlier fixes still matter?

VersionSelected official changeCurrent interpretation
1.00.05Fixed a Freeze-plus-Stun case that could leave the player unable to move.Older reports are outdated until reproduced on 1.00.08.
1.00.06Fixed missing-character boxes in several languages and other translation issues.Language reports should include the current build and language.
1.00.07Fixed Blacksmith and Shop UI scaling on ultrawide displays and adjusted starting gear bonuses.Old screenshots and starting-loadout advice may no longer apply.

Which issues are only community reported?

Steam Community threads mention the following topics. A report does not prove a universal defect, root cause, or solution.

Report clusterEvidence stateUseful details to capture
Save slot visible but unable to loadCommunity reported; compare with 1.00.08Version, operating system, black-screen behavior, and recovery result
Blurry resolution or ultrawide behaviorCommunity reported; some UI was fixed in 1.00.07Resolution, display mode, aspect ratio, UI scale, and screenshot
PlayStation prompts or remappingCommunity reported; native support was previously listed as plannedController model, connection, Steam Input state, and build
Steam Deck text or controlsCommunity reportedSteamOS version, game build, layout, and focused screenshot
Potion, boss-death, or progression behaviorCommunity reportedExact steps, expected result, observed result, and save state

What low-risk checks can you try first?

  1. Confirm that Steam installed the newest public build and restart the game.
  2. Preserve a backup of any save data you can safely access before experimenting.
  3. Record the version, operating system, display or controller model, and exact steps.
  4. Reproduce the issue once with the smallest safe change possible.
  5. Report it through the Steam Community or official Discord with that evidence.

These are general diagnostics, not guaranteed fixes. This page does not recommend deleting saves, editing files, or installing third-party tools.

What is not verified yet?

  • Whether every save affected before 1.00.08 recovers successfully.
  • Measured frame-time improvements for the Final Boss or Tide Root.
  • A release date for native PlayStation controller support.
  • Universal fixes for remaining controller, display, Steam Deck, or progression reports.

Sources

Related Articles

Was this helpful?