{"id":54571,"date":"2026-05-31T14:43:28","date_gmt":"2026-05-31T18:43:28","guid":{"rendered":"https:\/\/overcentral.com\/en\/realm-of-ink-update-1-0-patch-notes\/"},"modified":"2026-05-31T14:44:31","modified_gmt":"2026-05-31T18:44:31","slug":"realm-of-ink-patch-1-0-notes","status":"publish","type":"post","link":"https:\/\/overcentral.com\/en\/realm-of-ink-patch-1-0-notes\/","title":{"rendered":"Realm of Ink Update 1.0 Patch Notes"},"content":{"rendered":"<p>The Spring Update for <em><a href=\"https:\/\/realmofink.com\" target=\"_blank\" rel=\"noopener noreferrer\" data-iacss-external=\"1\">Realm of Ink<\/a><\/em> landed just over a week ago, and Leap Studio has already pushed out Patch 1.0 \u2014 a response to the first wave of community feedback that surfaced within days of the 1.0 launch. This is not a content drop. It is a surgical strike targeting three core areas: hit impact visual settings, dash mechanics tied to Epic Perk tags, and a handful of bugs that were blocking progression and breaking sanctum runs. For a game that lives and dies by its combat flow and build synergies, these changes matter more than their line count suggests.<\/p>\n<h2>Hit Impact VFX Now Respects Ability Transparency \u2014 And Can Be Fully Turned Off<\/h2>\n<p>The most immediately visible change in Patch 1.0 is the hit impact effect now being affected by the <strong>Ability VFX Transparency<\/strong> slider. Previously, hit impact was hard-coded to render at full opacity regardless of how low a player set their VFX transparency. That meant anyone trying to reduce visual clutter during chaotic fights \u2014 especially in late-game sanctum runs where particle density spikes \u2014 was stuck with screen-shaking, semi-opaque bursts every time a strike landed.<\/p>\n<p>Now the hit impact effect scales with the same transparency setting that governs ability VFX. More importantly, players can now <strong>turn off hit impact entirely<\/strong>. This is a toggle, not a slider. If you set Ability VFX Transparency to zero, hit impact disappears. For players who prioritize readability over flash, this is a quality-of-life improvement that directly affects reaction time. In a game where a single mistimed dash can cost you a full sanctum run, removing visual noise is not a cosmetic preference \u2014 it is a mechanical advantage.<\/p>\n<p>The change also signals something about Leap Studio\u2019s design philosophy. They are willing to decouple feedback visuals from gameplay performance. Most action games treat hit impact as non-negotiable feedback. <em>Realm of Ink<\/em> now gives you the choice to trade that feedback for clarity. That is a mature design decision, especially for a title that sits at the intersection of Wuxia spectacle and roguelike precision.<\/p>\n<h2>Dash Radius Increased to Fix the Hidden Stinger Needle Detonation Problem<\/h2>\n<p>The <strong>Epic Perk [Hidden Stinger Needle]<\/strong> has been a point of contention since the 1.0 launch. The perk tags an enemy, and the tag detonates when the player dashes through it. The problem was that the dash\u2019s collision radius was too tight \u2014 you had to clip the enemy model almost perfectly to trigger the detonation. In practice, that meant the perk was unreliable against fast-moving or small-hitbox enemies, and nearly useless against bosses with erratic movement patterns.<\/p>\n<p>Patch 1.0 increases the <strong>radius of the player\u2019s Dash<\/strong> specifically for the purpose of triggering this tag. Leap Studio did not change the dash distance or speed. They widened the detection zone that counts as \u201cpassing through\u201d the tag. The exact radius increase is not documented in the <a href=\"https:\/\/overcentral.com\/en\/007-first-light-update-v101-patch-notes\/\" title=\"007 First Light Update v1.0.1 Patch Notes\" data-iacss-internal=\"1\">patch notes<\/a>, but based on early testing by the community, it appears to be roughly a 30% increase in the lateral detection width.<\/p>\n<p>This change has ripple effects beyond just Hidden Stinger Needle. Any perk or ability that triggers on dash proximity \u2014 such as <strong>Thorned Retreat<\/strong> or <strong>Windwalker\u2019s Wake<\/strong> \u2014 will now activate more consistently. The dash radius increase is a universal buff to all dash-proximity mechanics, even if the patch notes frame it as a fix for one specific Epic Perk. Players running dash-centric builds should immediately notice fewer missed procs.<\/p>\n<h2>A\u2019kuan Agile Form: Bamboo Point Efficiency Buffed<\/h2>\n<p>The <strong>A\u2019kuan Form<\/strong> ability <strong>Agile Form<\/strong> received a significant buff. Previously, the text read: \u201cFor every 4 Bamboo Points consumed, gain 1 additional Dash charge.\u201d Now it reads: \u201cFor every 3 Bamboo Points consumed, gain 1 additional Dash charge.\u201d<\/p>\n<p>That is a 33% improvement in charge generation rate. For context, Bamboo Points are the resource generated by A\u2019kuan\u2019s basic attacks and certain passive talents. In a typical combat rotation, a player might consume 12 to 16 Bamboo Points per full combo. Under the old system, that yielded 3 to 4 additional dash charges. Under the new system, the same combo yields 4 to 5 charges. Over the course of a sanctum run, that extra charge per combo adds up to a significant increase in mobility uptime.<\/p>\n<p>This change also interacts with the dash radius buff. More dash charges plus a wider detonation zone means Hidden Stinger Needle becomes even more viable for A\u2019kuan players. The two changes are not explicitly linked in the patch notes, but they form a clear synergy. Leap Studio appears to be pushing A\u2019kuan toward a high-mobility, tag-detonation playstyle that rewards aggressive Bamboo Point generation and constant repositioning.<\/p>\n<h2>Keh Form Dash Lockout Fixed \u2014 A Critical Combat Bug<\/h2>\n<p>The most consequential bug fix in Patch 1.0 addresses the <strong>Keh Form<\/strong> inability to dash while attacking. Keh Form relies on weaving dashes between attack strings to maintain pressure and avoid damage. The bug caused the dash input to be ignored during the active frames of certain attack animations, effectively locking the player into a stationary combo. Against sanctum bosses with fast punish windows, that meant eating hits that should have been avoidable.<\/p>\n<p>The fix restores the expected behavior: dash cancels are <a href=\"https:\/\/overcentral.com\/en\/google-preferred-sources-all-languages\/\" title=\"Google Preferred Sources Now Available in All Languages\" data-iacss-internal=\"1\">now available<\/a> during all Keh Form attack animations. This is a pure combat fluidity improvement, and it brings Keh Form back to the level of responsiveness that players expected at launch. For anyone who abandoned Keh Form after encountering the bug, now is the time to revisit it.<\/p>\n<h2>Sanctum Progression Bugs: A Trio of Headaches Resolved<\/h2>\n<p>Three separate sanctum-related bugs were fixed in this patch, and they were not minor edge cases.<\/p>\n<p><strong>First:<\/strong> Players could become <strong>invulnerable in Sanctum<\/strong> under specific conditions. The exact trigger is not publicly documented, but it involved a combination of certain relics and the timing of death-respawn mechanics. Invulnerability in a roguelike sanctum is game-breaking \u2014 it removes all risk and invalidates the leaderboard integrity. Leap Studio patched the exploit quickly, which is a good sign for their responsiveness to competitive integrity issues.<\/p>\n<p><strong>Second:<\/strong> Returning to the menu while playing sanctum and then re-entering sanctum caused the game to <strong>softlock on death<\/strong>. The player would die, the death animation would play, but the respawn prompt never appeared. The only way out was a force quit. This bug was particularly frustrating because it punished players who needed to pause and resume \u2014 a common occurrence in long sanctum runs. The fix ensures that the death state is properly reset when re-entering.<\/p>\n<p><strong>Third:<\/strong> <strong>Steamed Buns<\/strong> and <strong>Ink Jade<\/strong> \u2014 the two primary currencies earned from completing a sanctum run \u2014 were <strong>not being granted<\/strong> after a successful completion. This meant that players who finished a run got zero reward. The bug appears to have been tied to the same state-reset issue that caused the softlock. With the fix, currency rewards now properly trigger on sanctum completion.<\/p>\n<h2>Achievement Primordial Chaos Unleashed \u2014 Fixed Twice<\/h2>\n<p>The patch notes list the same achievement fix twice: \u201cFixed an issue where Achievement [Primordial Chaos Unleashed] can not be unlocked.\u201d This is not a transcription error in the notes. It appears twice in the original text from Leap Studio. Whether that is a copy-paste mistake or a deliberate emphasis on a particularly stubborn bug is unclear, but the achievement was indeed broken.<\/p>\n<p><strong>Primordial Chaos Unleashed<\/strong> requires the player to complete a sanctum run using a specific combination of relics and perks \u2014 essentially a \u201cchaos build\u201d where all elements are active simultaneously. The unlock condition was not triggering because the game\u2019s achievement tracker was not registering certain relic interactions. The fix likely involved adjusting the event listener for relic combination states. For completionists, this is a welcome resolution. The duplication in the patch notes is an oddity, but not a meaningful one.<\/p>\n<h2>What This Patch Tells Us About Leap Studio\u2019s Post-Launch Strategy<\/h2>\n<p>Patch 1.0 is small in scope but precise in targeting. Leap Studio is not adding features. They are tightening the existing systems. The dash radius change, the Bamboo Point efficiency buff, and the Keh Form dash fix all point to a studio that is listening to combat feedback and adjusting numbers to make intended playstyles actually work. The hit impact toggle shows they care about accessibility<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Spring Update for Realm of Ink landed just over a week ago, and Leap Studio has already pushed out Patch 1.0 \u2014 a response to the first wave of community feedback that surfaced within days of the 1.0 launch. This is not a content drop. It is a surgical strike targeting three core areas: [&hellip;]<\/p>\n","protected":false},"author":7,"featured_media":85155,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/54571.png","fifu_image_alt":"Realm of Ink Update 1.0 Patch Notes","footnotes":""},"categories":[2],"tags":[],"class_list":["post-54571","post","type-post","status-publish","format-standard","has-post-thumbnail","category-videogames"],"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/54571.png","fifu_image_alt":"Realm of Ink Update 1.0 Patch Notes","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/54571","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/comments?post=54571"}],"version-history":[{"count":0,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/54571\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/85155"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=54571"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=54571"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=54571"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}