Article 5AHPY Pokémon Go raises its level cap for the first time in over four years

Pokémon Go raises its level cap for the first time in over four years

by
Kyle Orland
from Ars Technica - All content on (#5AHPY)
  • poke50-4-980x513.jpg

    Players who reach Level 40 before the end of the year will be the only ones able to access a limited edition in-game Gyardos hat. [credit: Niantic ]

If you're still playing Pokemon Go over four years after it first set mobile gaming records (and near-record revenue numbers in July suggest there are plenty of you out there), you've probably been stuck at the game's experience cap of level 40 for a while now. If so, you'll be happy to hear that level cap will be increased for the first time ever, to level 50, as part of an upcoming update branded Pokemon Go Beyond.

"Leveling up is one of the most important and meaningful aspects in the game," Niantic Product Manager Philip La said during a press presentation. "Reaching the current cap of 40 is a 'badge of honor' that other trainers will recognize. Some have reached it multiple times over. Now is the right time [to increase that cap]. Many dedicated players have achieved so many milestones and [are] looking for new challenges."

While Niantic isn't discussing specific timing for the level cap update (beyond "soon"), the company did say that trainers who hit the current level 40 cap by midnight on December 31 will receive a "Legacy 40 Trainer" badge and additional "exclusive rewards." That seems to suggest leveling past 40 will be available in early 2021, if not as soon as the year transfers over. A few lucky level 40 players in Australia will get to test the new level cap in the coming weeks.

Read 7 remaining paragraphs | Comments

index?i=m0ndptKSavY:RGkFuCzsdbs:V_sGLiPB index?i=m0ndptKSavY:RGkFuCzsdbs:F7zBnMyn index?d=qj6IDK7rITs index?d=yIl2AUoC8zA
External Content
Source RSS or Atom Feed
Feed Location http://feeds.arstechnica.com/arstechnica/index
Feed Title Ars Technica - All content
Feed Link https://arstechnica.com/
Reply 0 comments