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.14 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 NerevarTheKing

Server: NA

THIS BUG HAS PERSISTED FOR A MONTH NOW!

• Type of Bug: In Game Bug

• Description: Stuttering and FPS drops beginning ~6 mins or when Herald spawns until Baron Nashor spawns. Leaving and reconnecting fixes the issue for many, but not everyone.

• Video / Screenshot: This is well documented already.

• Steps to reproduce: Wait for Rift Herald to spawn.

• Expected result: Game plays normally and FPS remains how it otherwise should be. No anomalous lag or in-game stuttering.

• Observed result: FPS drops, stuttering, volatile performance and laggy visuals

• Reproduction rate: 10/10

• System specs: AMD 500 series GPUs and Ryzen 2600 are among the most well-known at this time.

We are working on a fix but open question to anyone that has this occur: Are your drivers up to date? That is something that is potentially causing issues

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

Originally posted by MrrWarlock

- Server: EUNE

- Type of bug: In-game bug

- Description: When you smite (has to be un-upgraded) under 15 secs to get the 2nd smite stack instead of resetting to the default 15 secs it flashes to 15 secs and then resets to 1:30 (you have to actually wait out the 1:30 mins to get the 2nd smite stack)

- video (clip of mine from twitch): https://clips.twitch.tv/GlutenFreeSmellyMarrowBCWarrior-b5vX1IhdN4qC6Drn

- steps to reproduce: Smite when you're close to getting the 2nd smite stack (less than 15 secs)

- expected result: Smite being at 15 sec cd

- observed result: Smite having 90 sec cd

- reproduction rate: 100%

- system specs: Don't matter

This has been micropatched. Thank you for the report!

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

Originally posted by TehAnon

  • Server: NA
  • Type of Bug: in-game
  • Description: Taliyah Q has incorrect mana costs at ranks 2 and 4, as shown in tooltip (55 / 50 / 65 / 60 / 75) and verified in gameplay
  • Video / Screenshot:
  • Steps to reproduce:
  • Expected result: 55 / 60 / 65 / 70 / 75 mana cost
  • Observed result: Ranks 2 and 4 mana cost are too cheap, by 10 mana due to improper scaling
  • Reproduction rate: 100% (n=5 games, live and practice)
  • System specs: N/A

Thanks for the report! We are looking into this :D