• Hello!

    I would like to separate bug fixes from champion changes (such as nerf and buffs) on patch notes pages. This would improve the clarity of patch note pages. The champion changes are clearly the most important thing to see when you click on a patch note page. Most people don't want to see the random bug fixes and are just going to scroll down to see the next champion change.

    The bug fixes are minor changes basically impactless on most players' experience, this is why they should be separated from the champion changes and should be hidden by default (using a tabber for example).

    What are you thoughts about this?

      Loading editor
    • I would like to see an example. Can you create one in your userspace?

        Loading editor
    • User:Tylobic/Patch_notes_-_Sandbox Here my example with the patch V6.14, the bug fixes are at the bottom of the page.

        Loading editor
    • So, what do you think about it ?

        Loading editor
    • {{Question}}Question Question

      {{Support}}Support

      Support
      {{Neutral}}Neutral Neutral
      {{Oppose}}Oppose Oppose
        Loading editor
    • Support

      Support —10/10 m8 really why were the bugs on the same part as champion adjustments anyways
        Loading editor
    • Neutral

      Neutral — I read the whole patch notes anyway, so I do not care.
        Loading editor
    • Support

      Support — it would take literally ten more seconds to make and it's neat user friendliness.
        Loading editor
    • Neutral

      Neutral — Echoing Ninjamask's comment, I read all the patchnotes so it doesn't make any difference to me.
        Loading editor
    • Oppose

      Oppose — While perhaps more could be done to make bug fixes more distinct from balance changes, I think it might not be ideal to separate bug fixes from balance changes in the patch notes, since I feel it's likely users are going to be going to the same place to read about the same information ("Did my champion get improved?").

      With that said, I think the only way we'll really get a feel of this is with a proper experiment, so I'd be up for a temporary Support

      Support — just to see what two separate changelogs would feel to go through on the main space. As much as there might be a potential downside in splitting information that should be unified, there's a much larger potential benefit in user-friendly information delivery, so even if I disagree with the proposition, I think it's worth trying out for the next few patch cycles, or the next one at the very least.
        Loading editor
    • Support

      Support — It's a good idea in my opinion. I myself, and probably a lot of other people care more about the balancing types of changes to the champions. Though, i don't see why it has to be hidden by default. It is a change in the patch notes that might make a difference ingame, albeit i myself might not pay too much attention to it.
        Loading editor
    • Alright you guys seems to be 50/50 on this one, so we are going to apply this to the next patch note and see if there is any feedback from the wiki community about this change in the presentation of patch notes.

        Loading editor
    • Oppose

      Oppose — tl;dr Bug fixes vary in size, quantity, and documentation. Sometimes they're important enough to include with any numerical or functional changes. Consistency is important.

      There's also a fuzzy line between bug fixing and quality of life - there are frequent? reddit posts & similar about how X champion has Y bugs that affect their playability. For instance, do you remember how Azir/Previous_Versions has been criticized on and off since release as buggy and unplayable? How would he have been received if those bug fixes weren't clearly documented and disseminated?

      Regarding bug fixes that relate to the functionality of champions and their abilities, both the change itself and the documentation can affect that champion's performance and perception on the broader scale of the game.

      Sure, minor visual fixes and corrections of unintended interactions are small, but they're pretty important to maintain consistency within a page. More broadly, such a change would further divide older & newer patch notes, and even more relevantly, this suggested separation of content would make changes less visible to anyone who cares or might care.

      The current organization also makes it simpler to directly transfer sections from the patch notes to individual patch histories, which should be worth considering as the current de facto maintainer of patch notes (@Tylobic).

        Loading editor
    • You made a point. Patch notes to come won't be changed in term of organisation of content.

        Loading editor
    • an anonymous contributor
        Loading editor
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message