Masteries Bug

Av14nOSUpLyr12·8/6/2016, 3:26:38 AM·1 votes·448 views

IMAGE: http://i1152.photobucket.com/albums/p486/Av1212/error%20league_zpspnesz7ga.png

BUG: I got an error message when I created a new mastery and then after that when switching masteries. The game used the newly created mastery I used in the previous game.

EXACTLY WHAT I DID:

  1. I logged in
  2. I verified my e-mail and got the IP boost
  3. I queued for a game
  4. Called my lane first. Someone wanted it. I gave it to them. I picked Caitlyn. Created a new mastery page because I'm new to Caitlyn. Did not name it. Closed it.
  5. Opened it. Named it 'adc' (exactly)
  6. When I closed it I got an error message, but it used the right mastery page. The newly created one, when I was in game.
  7. Game finished. We lost. Queued for a new game. In champion select, I got an error message every time I switched masteries using the tab. I tried doing it a couple times. Kept getting an error message, but it still let me choose a mastery (as seen in the picture). Even though I chose my tank support mastery page, it used the previous one in game, because I had the fevor keystone.
  8. We still won game (wew summoner 3 ) I relog, and the mastery page isn't named 'adc' anymore. It went back to Mastery Page 11.

POSSIBILITIES FOR BUG CAUSE: Combination or singular

  1. Verifying the e-mail and getting the IP boost, but not relogging.
  2. Naming the mastery page 'adc' when there's a mastery called 'ADC' (this one is in caps).

1 Comments

lmsyl8/7/2016, 12:01:44 AM1 votes

I just had this happen to me as well and I'm almost positive it's due to naming, like you said.

I queued up to play a game and quickly made a new master page and called it "Varus". It gave me that error but I didn't think anything happened. Someone dodged, next queue I switch mastery pages and it gives me the error and when I get into game I do not have a keystone.

Keeps happening in my next queue and I realize I already have a page called "varus" so I delete the new page I made and the error stopped.