I have a bad habit after any Elden Ring update: I apply the file, check the title screen, and then open the weapon board as if the rows might be out of date. Most weeks that reflex is harmless. This time it would have been a waste. On 20 October 2026, Bandai Namco Europe published patch notes for version 1.17.2 and said, plainly, "This patch brings bug fixes to ELDEN RING. No additional content is included." I still write the official version on the board. I do not take that sentence as a prompt to reshuffle anything.
I keep the board in the browser on Tierlist, on a saved S-through-D layout I already use for weapons I actually carry. The useful work, after a bugfix-only patch, is not a new ranking. It is a short label that tells next month's me I already read the notes and chose to leave the tiles alone.
The notes I actually read
The European notes list a small set of fixes, and I will not turn them into a balance argument they do not make. There was a display bug with the Gold Tattoo Chest when Hide Helmet was enabled, visible in the status menu. There was a left-hand graphics bug if you used the Repeating Crossbow skill in the left hand while holding Leontiel's Greatsword in the right. Credits text was corrected. Piquebone Arrows and Fletched Piquebone Arrows could apply status buildup incorrectly in a specific procedure. On PlayStation 4 and PlayStation 5, network features also received a security enhancement. After the update, the title screen should show App Ver. 1.17.2 and Regulation Ver. 1.17.3 on PlayStation, Xbox, and Steam. The update is required for online play. That is the whole official story I am using here (Elden Ring patch notes, version 1.17.2).
The Japanese news page for the same 20 October update adds one detail the European post does not: ELDEN RING Tarnished Edition on Nintendo Switch 2 is listed with App Ver. 1.17.2 and Regulation Ver. 1.17.4, and a later note about that edition was added on 12 November 2026 at 19:00. I write whichever pair my platform actually shows. I do not invent a 1.17 weapon-damage list, and I do not treat a later platform note as a secret rebalance.
What the official tray is showing me
When I open the official unranked tray on the Elden Ring weapon tier list, the first tiles are names, not verdicts. The contact sheet in front of me starts Academy Glintstone Staff, Alabaster Lord's Sword, Albinauric Bow, Albinauric Staff, then Ancient Meteoric Ore Greatsword, Ansbach's Longbow, Antspur Rapier, Anvil Hammer. Further along are Arbalest, Astrologer's Staff, Axe of Godfrey, Axe of Godrick, Azur's Glintstone Staff, Backhand Blade, Bandit's Curved Sword, and the Banished Knight's Greatsword and Halberd. The lower row in that first set still includes Barbed Staff-Spear, Bastard's Stars, Bastard Sword, Battle Axe, Battle Hammer, Beast-Repellent Torch, and Beast Claw. Those are official template tiles. They were official template tiles before this patch, and they are still official template tiles after it.
A status-menu display bug does not tell me whether Antspur Rapier belongs one row higher. A left-hand graphics fix around Leontiel's Greatsword does not tell me what to do with Bastard Sword or Battle Axe. An arrow that was applying status buildup incorrectly in a specific procedure is a reason to be glad the procedure was fixed. It is not a reason to rebuild a poison or bleed column I had already settled. I can be glad the credits are spelled correctly and still refuse to perform a ceremonial rerank.
The only edit I make
What I actually type is short. On the board title, or in a line I will see when I reopen the file, I write the date I read the notes and the official pair: App Ver. 1.17.2, Regulation Ver. 1.17.3 — or 1.17.4 if I am on Tarnished Edition. Sometimes I add "bugfix only, no additional content," borrowed from the official wording, so I do not later invent a memory that this was a combat patch. I do not add a new S-row headline. I do not drag Academy Glintstone Staff next to Azur's Glintstone Staff just because they share a naming pattern in the tray. The tray order is a catalog order. It is not a hint.
This is the part I have to remind myself of, because a blank evening after a patch feels like I should "do something" with a ranking. If the notes did not change the weapons, the honest action is inaction. Writing the version is how I make that inaction visible. Without the label, a still board and a neglected board look the same in a screenshot. With the label, the still board is a decision.
A second board I do not use as a consolation prize
I am not going to spend the leftover energy on a second game as a way to make the evening feel productive. This week I also have an Arknights board open, because the official Monster Hunter collaboration is mid-window. A Games Press release dated 17 November 2026 calls the event Thunder in the Azure Dream and describes two stage phases, Hunting the Azure Thunder and Treading on Dreams, with limited operators named Violet Mizutsune Orchid and Zinogre S Catapult, plus a free 1-star operator, Rhodes Island Recon (ARKNIGHTS x MONSTER HUNTER Opens). I have not finished that event, I have not pulled the limited operators, and I am writing this on 20 November 2026, before the second phase opens. A mid-event scout name is not a placement. I can open the Arknights tier list later in the week and still leave last month's rows alone. The two boards stay two boards. The weapon label I wrote tonight does not migrate onto an operator row.
Field notes, then, for the next bugfix-only patch: read the official notes first, and stop at what they actually claim. Write the App and Regulation versions your title screen shows. Leave the tiles where they are. Do not promote a graphics fix or a status-buildup correction into a meta shift. Do not fill the quiet with a ceremonial reshuffle, and do not spend the same evening forcing a limited event name onto a second board just so the session feels finished. If a later patch does add content or change combat, that will be a different morning, with different notes. This one already told me there was no additional content. The version on the board is enough.

Top comments (0)