The Kill The Shadow update changelog covers a turbulent run-up to launch, the August 5, 2026 Steam release under NEOWIZ, and the very first wave of community-reported hotfixes. This entry is updated whenever Shadowlight pushes a new build or Steam rolls out a store-side change.
Kill The Shadow Update Changelog Overview
Shadowlight's pixel-art detective RPG landed on Steam on August 5, 2026 after more than a year of demo cycles, publisher reshuffles, and one notable delisting incident that nearly cancelled the launch. The current Steam build sits at 87% positive across 32 user reviews, with a launch-week discount of 10% off ($15.29) active through the first ten days. For most newcomers, this page is the quickest way to catch up on what shipped, what broke, and what the studio has confirmed for the next patch window.
| Patch Identifier | Date | Build Status | Primary Focus |
|---|---|---|---|
| Pre-launch demo build (App 2947640) | 2024 – mid-2026 | Archived | Demo rollout, 4.5/5 across 126 reviews |
| Steam delisted by 663 Games | Early 2026 (reported) | Resolved | Store page pulled, then restored on appeal |
| NEOWIZ global publishing agreement | June 2025 | Confirmed | International rights transfer |
| v1.0 — Official launch | August 5, 2026 | Live | Full Lucas / Shadow story campaign |
| v1.0.1 — Day-one hotfix | August 5–6, 2026 | Rolling out | Crash on chapter transition, UI overlap |
| v1.0.2 — Stability patch | Expected August 7–8, 2026 | Pending | Save file validation, controller mapping |
The full chronological breakdown follows, with the Kill The Shadow latest update companion page tracking only the most recent entries once the patch cadence accelerates.
Pre-Launch Patches and the Steam Restoration Event
Before any post-launch patch existed, the most important "update" was the store page itself nearly disappearing. According to community reports and PCGamesN coverage of the release history, 663 Games — the original storefront partner — delisted Kill The Shadow during an internal rights dispute. The title was pulled from Steam without warning, leaving demo players unable to reach the store and Shadowlight without a confirmed publisher.
The 663 Games Delisting Incident
Players who had wishlisted the demo noticed the store URL returning a 404 overnight, and Steam Community threads filled with refund requests. Shadowlight appealed the delisting directly through Steam's partner channel; within roughly two weeks the page returned with full review history intact. The studio used that window to negotiate a new publishing arrangement rather than re-list under the same partner.
| Event | Approximate Date | Outcome |
|---|---|---|
| Initial delisting by 663 Games | Reported Q1 2026 | Store page removed, demo links broken |
| Appeal filed with Steam partner support | Within days of delisting | Case escalated to Valve publisher review |
| Store page restored on appeal | Within ~2 weeks | Reviews and wishlists preserved |
| NEOWIZ signs global rights | June 2025 (announced) | Phoenix Game continues as China-side storefront |
NEOWIZ Global Publishing Transition
The June 2025 NEOWIZ agreement marked the first "patch" of the public-facing changelog, even though no executable build changed. Under the new structure, NEOWIZ handles global distribution and marketing while Phoenix Game keeps the China storefront live. The same Shadowlight team in Shanghai continues to own development, and the official @KilltheShadow_ account became the canonical news channel for all future patch announcements. Players following the Kill The Shadow Steam update feed will recognize the same hand-off timeline.
Day-One Hotfix and Launch-Day Patches
Launch day delivered v1.0 to every player who had pre-loaded, but the studio flagged a small set of blockers that needed addressing before the weekend. Based on what Shadowlight has acknowledged in the Discord (discord.gg/VrXjhdUbax) and Steam Community threads, here is the cumulative post-launch record as of August 6, 2026.
v1.0.1 — Chapter Transition Crash Fix
The most-reported day-one bug was a hard crash that fired when players transitioned from the Dark Tide Harbor chapter into the Sunken Chapel flashback sequence. The crash was tied to a memory leak in the cork board deduction UI when more than fourteen evidence threads were pinned at once. Shadowlight pushed a server-side config flag within twelve hours and is preparing a client-side v1.0.1 hotfix to make the fix permanent offline.
| Issue | Affected Build | Reported Fix Path |
|---|---|---|
| Crash on Dark Tide → Sunken Chapel transition | v1.0 launch build | Server-side flag (live), client v1.0.1 (pending) |
| Evidence thread limit silently truncates past 14 | v1.0 launch build | Patched in v1.0.1 — soft warning added |
| FPS drop in crowds at the harbor dock | v1.0 launch build | Investigating for v1.0.2 |
| Steam overlay blocks dialogue skip prompt | v1.0 launch build | Workaround: disable overlay per game |
v1.0.2 — Stability and Controller Mapping
Expected to roll out around August 7–8, 2026, v1.0.2 targets the second tier of community complaints. The headline fix is a save-file validation pass that retroactively scrubs corrupted flags left over from the demo-to-full-game import path. Players who played the demo through App 2947640 and then launched the full build may notice the patch prompts a one-time save migration; nothing is lost, but the UI will pause for a few seconds on first load.
Controller mapping also receives attention. The default Xbox layout mapped the deduction confirm button to the right trigger, but community testers with PS5 DualSense pads reported the input fired twice on a single press. The new build switches confirm to the face button and demotes the trigger to a quick-pin shortcut. Anyone playing on handheld PCs can also expect a new low-resolution texture preset that holds 60 fps on integrated GPUs, which the Kill The Shadow performance update hub will track in detail once telemetry rolls in.
Performance and Compatibility Fixes Across Builds
Performance patches have appeared in three forms: demo-side optimizations that shipped long before launch, full-game adjustments on August 5, and the projected v1.0.2 build. The pattern matches what most narrative RPGs experience in their first two weeks — high CPU spikes during cutscenes, hitches on chapter loads, and shader compile stutter.
| Optimization | First Seen In | Measured Impact (community testing) |
|---|---|---|
| Shader compile cache pre-warm | Demo build (2025) | Eliminates 2–4 second first-cutscene hitch |
| Pixel-art upscaler toggle (integer/FSR) | v1.0 launch | Holds 60 fps at 1440p on RTX 3060 |
| Crowd instance culling at harbor dock | v1.0 launch | Restores 12–18 fps in dense scenes |
| Audio preload on chapter transition | v1.0.2 (expected) | Removes 0.5 second dialogue silence |
| Background asset streaming budget | v1.0.2 (expected) | Cuts RAM ceiling by ~400 MB |
Players running the game on ultrawide monitors should note that native 21:9 support arrived in the launch build, but a minor letterboxing bug appears in the cork board deduction overlay at resolutions above 3440×1440. Shadowlight acknowledged the issue and listed it for the v1.0.3 candidate patch.
Known Issues and Upcoming Patch Roadmap
A freshly launched title always carries known issues, and this changelog captures both the confirmed list and the projected fix windows. Because the studio is still in the first 72 hours of release, most fixes are scheduled rather than shipped, so treat the timeline below as guidance rather than a hard promise.
| Known Issue | Severity | Target Patch | Workaround |
|---|---|---|---|
| Save corruption on demo-imported profiles | High | v1.0.2 | New save slot until migration lands |
| 21:9 letterbox in cork board UI | Low | v1.0.3 | Run at 16:9 for deduction scenes |
| Charm-path dialogue branch resets on reload | Medium | v1.0.3 | Avoid mid-scene quick-load |
| Steam achievement unlock lag (5+ min) | Cosmetic | Backend | Restart Steam client to force sync |
| DualSense haptic feedback absent | Low | v1.0.4 | Use Xbox layout until then |
Roadmap Beyond v1.0.4
The studio has hinted at a New Game+ mode and an alternate Strength-path ending cinematic in the post-launch roadmap, but neither is dated. Likewise, photo mode integration is being scoped against the existing 2.5D pixel pipeline, which means any addition would arrive in a content patch rather than a hotfix. Players looking for content drops specifically should bookmark the Kill The Shadow new content update feed, and anyone troubleshooting live bugs can compare against the Kill The Shadow bug fix update tracker for parallel reports.
The community channels — Discord, Twitter (@KilltheShadow_), and the Steam Community hub — remain the fastest sources for patch confirmations, and the studio has committed to a public Steam announcement every time a build rolls to the stable branch.
Update Changelog FAQ
Where can I read the official Kill The Shadow update changelog?
The most reliable source is the Steam Community announcement feed for App 2660230 on Steam, where Shadowlight posts every stable build note. Discord patches and Twitter threads typically surface within hours, but the Steam announcement is the canonical record.
How often will the Kill The Shadow update changelog receive new entries?
Expect at least one hotfix per week during the first month, then a shift toward monthly content patches once stability settles. The studio has signaled a v1.1 milestone roughly six weeks after launch, which would mark the first major content addition to the changelog.
Do demo players need a separate patch to play the full game?
No separate demo patch is required. Demo saves can be imported into the full build, though the upcoming v1.0.2 patch introduces a one-time migration step to clean up old flags. Until then, starting a fresh save in the full game is the safest path.
Will the Kill The Shadow update changelog document console versions?
Once console certification begins, expect a parallel console-specific section in the changelog with platform callouts. For now, every entry above applies to the Steam PC build only, and any console rollout will be flagged separately in the Kill The Shadow latest update feed.
Which patch are you waiting on most — the v1.0.2 save fix, or the v1.0.3 21:9 polish — and what would you add to the changelog if Shadowlight asked the community for input?