Loading...
Loading...
Week One Report (April 17, 2026) - Version 3 vs Version 4
May 8, 2026, 08:59 AM
Applied Title Case to body headings
May 19, 2026, 03:48 PM
Embedded launch-window screenshot (2026-05-19)
11Overview22On April 17, 2026, TiMi Studio Group published a first-week production team report (制作组首周汇报) for Honor of Kings: World, timed to coincide with the mobile client going live. The report is titled 'A progress report about change' and is the first post-launch transparency document of its kind for the title. It contains both an acknowledgement of launch-window problems and a set of firm, season-pinned commitments to fix them.45The report matters for two reasons. It is the first time the production team attached specific season labels (S1, S2) to individual feature commitments rather than using generic 'post-launch' phrasing. It is also the first time the team publicly framed the launch as having 'defects' and 'presumptuous assumptions', rather than defending the design choices that drove the most-cited complaints.67What the Report Acknowledges89The opening of the report is an unusual direct apology. The team states that they were very inexperienced (非常缺乏经验) in transitioning from a tightly scoped MOBA development context to a full open-world release. They admit that the early-game experience had many defects (很多缺陷), and that several launch-build design choices had been made with presumptuous assumptions (自以为是的想当然) about player tolerance.1011The specific launch-build misses named in the report are listed below. These are the items that the team accepted responsibility for, rather than the broader reception complaints captured in the Launch Reception article.1213Unskippable cinematics: the team wanted to deliver a complete story presentation and did not anticipate that players would want to control the pacing. This was the single highest-volume complaint surfaced through the official feedback channels on day one.Missing minimap: the team had designed the world with layered cavern regions and assumed players would adapt to spatial navigation cues in place of a traditional minimap. The assumption was wrong.Keybinding bug: the custom keybinding feature shipped in the launch build contained a bug that interfered with combat execution inputs, severe enough that the team pulled the feature rather than hot-patch it in place.Shader compilation stutter: the first-run shader compile caused noticeable stalls. The launch build's preheat strategy was insufficient.PvP cheating: hacking and other unfair-play reports surfaced in the first week. The team committed to an intensified anti-cheat push without attaching a specific fix window.1415What Shipped Within the First Week1617The report quantifies the first-week delivery as more than one hundred and thirty (130+) distinct bug tickets resolved between April 10 and April 17. A portion of these are visible to players and a portion are server-side or telemetry-only fixes.1819Animation skip function: shipped as a same-day patch after launch. Prior to the patch, only the opening 'Battle of the World's End' prologue had a skip option. After the patch, all story cinematics inside quests can be skipped.April 11 hotfix: a no-downtime 380 KB PC hotfix that tuned two Primal Flow Resonance breakthrough challenges, rewrote the Blade of Destruction parry challenge, optimised shader preheat, and fixed a controller vibration settings bug. Details in the April 11 Hotfix article.Server-wide 648-yuan login bundle: distributed on April 17 to celebrate the dual-client launch. Contents in the Dual-Client Launch Event article.2021Commitments Beyond the First Week2223The report pins three specific commitments to named seasons. This was the first appearance of season-labelled commitments in TiMi's post-launch communication.2425Minimap - S1 Season: in active development. The implementation has to integrate with the world-streaming system that handles the layered cavern regions, so the fix is a season-break feature rather than a mid-season patch.Keyboard and mouse custom keybinding - S1 Season: the feature will return after the launch-build bug has been resolved and verified.Gamepad custom keybinding - S2 Season: flagged as needing more runway than the keyboard path. Ships one season after the keyboard and mouse fix.2627The report also confirms a sustained rapid-response iteration mechanism (快速响应迭代), in which each individual piece of player feedback routes directly into the next patch's scheduling rather than into a quarterly planning cycle.2829Community Reception of the Report3031Community reception to the Week One Report was visibly split. On one side, the concrete ship-list and the season-pinned commitments were welcomed by player commenters on the main community forums as a clear upgrade over the vague 'post-launch' phrasing used in the April 11 day-one Q&A. On the other side, a counter-current of commentary argued that the items promised for S1 had also been raised during the February 2026 Zhengming Test and that acting on them now meant the fixes had taken weeks rather than days.3233The community aggregate player score, which had stabilised at 6.9 out of 10 by April 12, had not meaningfully moved by April 17. Launch-window sentiment on the visual presentation, cosmetic-only monetisation, and combat feel remained positive. Sentiment on progression pacing, minimap absence, and early-game quest friction remained negative pending the S1 fixes.3435Related Articles3637Day One Patch documents the April 10 and April 11 fix sequence. April 11 Hotfix covers the first-week mid-patch. Dual-Client Launch Event documents the April 17 login bundle. Launch Reception captures the wider community sentiment picture. Content Roadmap lists every roadmap commitment, including the S1 and S2 items from this report.
