Original Post — Direct link

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 12.7 Patch should be reported below.

Prerequisites to be noted before reporting a bug


  1. A bug will ideally be accompanied with a screenshot or a video. This provides credibility to your report.
  2. Steps to recreate the bugs should be submitted if possible. This helps Rioters recreate the bug and helps them find the cause behind it.
  3. 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.

External link →
over 2 years ago - /u/GalaxySmash - Direct link

Originally posted by Sp00ky_Senpai

Elise - any skin and any game mode. This has been in the game for months.

Self-casting rappel while an enemy target's (any target, including plants) character model overlaps with Elise causes her to descend from rappel instantly.

Server: NA

Type of bug: In game

Description: self-casted rappel will descend instantly.

Steps to reproduce: place a target dummy directly underneath Elise and self-cast rappel with alt+E.

Expected result: Elise will rappel for up to 2 seconds, with the option to descend early.

Observed result: Elise descends instantly.

Reproduction rate: 10/10. Can be done on every attempt.

Alright we have this made as a bug ticket and will be looking to fix this soon. Elise mains rejoice.

over 2 years ago - /u/GalaxySmash - Direct link

Originally posted by Sp00ky_Senpai

Thank you so much!

In case it helps, Elise had a bunch of rappel bugs in 12.5 that showed up in bug fixes on that patch, and this bug is separate from those - it existed before, it temporarily went away as a consequence of the other rappel bugs, and it exists again now. I don't have an exact date, but my best guess is that this bug was introduced sometime around the beginning of the year.

Sound about right. If you want you can go through all the other bugs here and that might help get eyes (8 to be exact) on them

over 2 years ago - /u/GalaxySmash - Direct link

Originally posted by Meriipu

How can I tell whether a bug has a ticket?

I have reported a bug with Lulu Q indicator breaking on death (100% reproducible, just die and try to cast with indicator) multiple times but I am not sure if it has been registered yet (just at a low priority).

Well I'll look into it and assuming its real you now know it has a ticket :)

over 2 years ago - /u/GalaxySmash - Direct link

Originally posted by Haiku0205

- **Server:** NA
- **Type of Bug:** In-Game Bug
- **Description:** After hitting blast cone into dragon pit, dragon is not in vision for a brief period of time
- **Video / Screenshot:** https://streamable.com/glhlfr
- **Steps to reproduce:**
- **Expected result:** Should see dragon immediately after blast coning in
- **Observed result:** Dragon not in vision for about a second
- **Reproduction rate:** didn't try, but I've never seen this before and I've played a lot

We are actually investigating this issue, it occurs with all jungle camps and generally happens when you dash into vision. No promise on a ship date but we want to look into this in the coming patches.

over 2 years ago - /u/GalaxySmash - Direct link

Originally posted by Tails365

  • Server: EUW
  • Type of Bug: In game bug
  • Description: Janna's Q base damage (the initial damage, without ramp up) does not factor in AP scalings. This could be a target dummy only bug.
  • Video / Screenshot: none
  • Expected result: Janna's Q deals damage equal to the predicted damage
  • Observed result: Janna's Q deals damage equal to the base amount of the ability
  • Reproduction rate: 100%
  • System specs: Irrelevant

Alright we are going down the rabbit hole on this one. Thanks for the report, we are looking into it.