Greetings Summoners!
With every new patch Riot introduces to balance out champions and items there are some unforeseen issues that creep up and cause disruption during gameplay. We have noticed that these issues which eventually get fixed clutter up the subreddit immediately following the patch.
We want to avoid this by having a single Megathread which will be posted after every patch so that you guys can report the various issues in one place. This allows Riot to easily keep track of the bugs by providing a central hub and also allows other users to confirm that they might have encountered.
Note only bugs caused by the 13.22 Patch should be reported below.
Prerequisites to be noted before reporting a bug
- A bug will ideally be accompanied with a screenshot or a video. This provides credibility to your report.
- Steps to recreate the bugs should be submitted if possible. This helps Rioters recreate the bug and helps them find the cause behind it.
- The bug must have been caused by the latest patch.
Format when reporting a bug: When reporting a bug, please provide as much information as you can about your computer.
• Server: The server you encountered the bug (NA, EUW, EUNE, TR, RU, BR, LAS, LAN etc)
• Type of Bug: Client Bug, In Game Bug etc
• Description: Describe what was the bug that occurred.
• Video / Screenshot: Insert screenshot (F12 in game) or Video of the bug occurring.
• Steps to reproduce: Provide the steps necessary if someone else had to reproduce the bug.
• Expected result: What should have been the result when you follow the steps mentioned above.
• Observed result: What was the result you obtained when you followed the steps mentioned above?
• Reproduction rate: If you try to recreate the bug how successful are you in causing it to occur? (1/10: Occurs once every 10 tries, 5/10: Occurs 5 times out of 10, 10/10: Happens every single time)
• System specs: Processor, Video card, Ram, HDD/SSD, everything you can provide, even drivers.
Example Bug:
• Server: EUW
• Type of Bug: In-Game Bug etc
• Description: Zed’s R (Death Mark) does not apply secondary damage
• Insert Video / Screenshot of the incident
• Reproduction rate: 2/10 (happened 2 out of 10 times)
• Steps to reproduce:
Launch a game after selecting Zed as your champion. Attempt to use Death Mark. Observe the result.
• Expected result: The damage should apply after a short delay, amplified by damage dealt during the effect.
• Observed result: The damage will not apply properly.
• System Specs: Intel i5 Processor, Windows 7, Nvidia Graphics card (insert model number) etc.
If you don’t know how to format comments on Reddit click here
- **Server:**
- **Type of Bug:**
- **Description:**
- **Video / Screenshot:**
- **Steps to reproduce:**
- **Expected result:**
- **Observed result:**
- **Reproduction rate:**
- **System specs:**
Copy paste the above code and fill in your details.
From this Megathread the list of bugs will not be summarized and put up in the main body of the thread, however, note that many Rioters are going through every single comment so don’t worry if you post the 1500th or 3000th comment, every reply will be read over the next few days.
- **Server:** NA
- **Type of Bug:** in game bug
- **Description:** Neeko W passive auto isn’t always becoming a “non projectile” with Guinsoo’s
- **Video / Screenshot:** https://medal.tv/games/league-of-legends/clips/1CKNFmLf6quTVM/d1337w4UDvSP?invite=cr-MSxvcVcsNTc0OTc1MDIs
- **Steps to reproduce:** Buy guinsoos on neeko, stack guinsoos and keep autoing
- **Expected result:** Attacks with the bonus damage should also be “non projectile” attacks, but only attacks that are made when fully stacked turn into non projectiles.
- **Observed result:** Not all passive attacks turn into non projectiles but still give you the damage and move speed.
In the ability description on the wiki it says attacks that the damage and non projectile stipulation are the same, based on that this should be a bug and not a guinsoo interaction.
- **Reproduction rate:** 100%
- **System specs:** AMD ryzen 7 3800x, Nvidia geforce GTX 1660 super, 16gb of ram.
- Server: All
- Type of Bug: In-game bug
- Description: The latest patch removed the ‘Berserking’ loss of control bar from under the summoner name while under the effect of Briar’s W. The loss of control bar was very precise in showing the remaining duration of the W, which made it easy to time the W to the latest possible second (important since it’s based on missing hp). *
- Steps to reproduce: Get in any game mode as Briar with loss of control bar enabled in interface, press W near a minion
- Expected result: The loss of control bar should show up under your summoner name (same as if you were stunned)
- Observed result: No loss of control bar under your summoner name
- Reproduction rate: 100%
* The orange bar under HP is very imprecise; I feel the tick rate, so to speak, is lower than the loss of control bar, which makes it way harder to properly time the last possible moment to W
Server: OCE
Type of Bug: ranked game suddenly closes, just like alt-tabing however afterwards it can be reopened. Happens during action.
Description: The game suddenly alt-tabs/minimizes without pressing alt tab commands during action in-game. I’m running Mobalytics and porofessor.gg . Even after I closed these 2 apps and overwolf the bug repeated. This has never occurred before and I have top of the line pc.
Video / Screenshot: Unable to produce due to nature of bug/game error.
Steps to reproduce: Unable to produce in custom-game as it mainly occurs during matchmade games.
Expected result: I’m expecting it to repeat.
Observed result: During the last game the game closed from main screen 3 times, costing us the game.
Reproduction rate: Unable to directly reproduce.
System specs: 4090 i7. Not system issue.
Is there a way to disable the persistent champion selection sound during a League of Legends match?
Server: EUW
Type of Bug: Quickplay unavailable
Description: I can’t chose my pick, the message : “Each player must select a valid champion” appears. I tried different combination of champion and lane, nothing work. This problem appeared on two different accounts after reaching level 10. Accounts : Teemo Jungle 001 and Teemo Jungle 002.
Video / Screenshot: https://gyazo.com/151405b58bc4ed3aa5fe896f0e4170dc
Steps to reproduce: Open the league client, try to start quickplay.
Expected result: The game should queue.
Observed result: Can’t queue.
Reproduction rate: 10/10
System specs: Windows 10,AMD Ryzen 5 5600 6-Core Processor, 3501 MHz, 6 cœur(s), 12 processeur(s) logique(s), Radeon RX Vega.Is it a bug that in Soloq or any ranked lobby right now it’s not shown which side firstpicks?