TinyEric

Because 1. the old animations were run in-engine (as in, being processed and calculated in real time) as opposed to just playing a video. The running game scene for both the level up and the gameplay state itself is too much memory for low end devices. We seriously considered retrofitting the old ones too but that would have been millions of dollars and hundreds of hours of dev time.

1. Animating in-engine requires an art team that can do its work in Unity itself and takes up engineering and tech art resources that are custom to each champion. And you don’t know ahead of time whether the idea you have is going to blow memory budgets, so there’s a lot of iteration cycles to deliver a single level up.

2. Conversely, outsourcing a video to a vendor means we can do things in parallel and free up the gameplay engineers and artists to do other things. The video vendor makes the video and we plop it in when it’s ready. Vastly simpler on the production side AN...

Hello LoR players!

We have a fun opportunity for y'all. We've been discussing our champs for next year, and we got it narrowed down to a smaller list, at which point we thought, "why don't we let the community tell us which ones they're most excited to see?"

So here we are with some polls to help determine some of the champs we'll be working on and releasing in 2025!

Poll 1 - New Constellation champs:
https://www.youtube.com/post/UgkxeYiMESxUY394PcDruTl3zpHsXnE2qp3X

• Galio (formidable yet cuddly!)
• Nautilus (deep yet doesn'...

Hi all - update for you. First, thanks for your patience, we know this bug sucks for you and it sucks for us on our end because it's been an absolute pain to solve for properly.

But by today, you should be able to see the quest reappear after re-logging in once so that the services can update your account.

Next week we will run a script to help those players affected by the bug so they're not set back by the loss of progression opportunity.

Lastly, we'll be having internal discussions with our support teams based on the feedback from the thread as well. Again, thanks for your patience.

Hi there - we're definitely looking into this. We're very sorry that you had this bad experience and we're trying to get a resolution on this as soon as possible so that your battle pass progress is not set back.

Hi there! We looked into this and fortunately it should be fixed when the full patch goes live tomorrow. So for now don’t tap the quest log, and apologies for the inconvenience :-/

We are working on it! No specific patch yet, but it’s gonna happen.

Hi there, if you could DM me your Riot ID (both parts before and after the hash tag), I'd like to be able to look at your account state. Even better if you could submit a bug report and send me the bug number.

Thanks for the update, we will dig in further. If you haven’t done so already, please submit a bug report to help us track these things - Reddit is not a reliable method of reporting issues to us.

We believe we've fixed this (we saw an issue with just Malaysia), please let us know if you keep seeing this issue.

I will say we are investigating methods where you can play against friends or in other "free play" modes with all cards, including path cards. We'll update you if these explorations prove successful.

This is all great feedback - we were just talking yesterday about the possibility of gold reliquaries on the pass. Old rewards are a good idea too - we will need to find a suitable way to cover the situation when someone already owns those rewards, we don't want someone to avoid buying a pass because they already own some of the rewards, and there may be people who would rather have the wild fragments instead of the PvP reward.

There are a lot of reasons but the biggest one is balance.

PvP design used to take 18 months for 5 champs, with an entire initiative behind it. We got that down to 12 months for 3 champs. Now, we are designing a new champ in less than 3 months with a smaller team.

A huge amount of that time and bandwidth was for balance in Standard. We see the worst outcomes for PvP in imbalanced formats. So we don’t want to release a new champ that’s not been balanced for PvP. And it takes a long time, because you’re not just balancing one card. You’re balancing the entire format (remember Azirelia?). And we don’t have the bandwidth to balance an entire format while also making our champs as fun as possible for our focus, which is Path of champions.

A roadmap is a good idea, but while we have a strong sense of roughly which champs we want during certain periods, a lot of things change rapidly and we often have to juggle things - so any roadmap we released would quickly get outdated. Anything more than a quarter out gets subject to the realities of live ops.

The cap extensions are coming up real fast - in fact, they were intended for this release, but life happened and they were pushed back.

Nope, we mean 4 brand new to LOR entirely, not just Path.

Edit for clarity since I'm seeing other convos where people are mis-reading this: These will all be Path-exclusive champions.

I agree with this.

They are silver star vessels.

The titles will start accruing with this new season, not the past season (which was still the Dreamlit Paths season under the old system). You'll see your titles in your loadout screen for each deck.

Hi all, so we are pretty sure that this is a result of you being in an active Path of Champions match when our patch rolled out this morning. Even though you quit the game, we keep that TPOC match live for awhile, in case you were disconnected or things like that. So your old game, still active on our server, is using the old data game version, and your client is updated with the new game version. That's where this mismatch is coming from.

So unfortunately you'll have to wait till that old match times out (usually 90 minutes to ~4 hours) before you can play.

If you write into Riot player support with your player ID, we can try and speed that up for you.

We know this has been a pain point for a long time, and the unfortunate reality is that we believe this iPad mini bug is due to code from a third party, not Riot code. And so we're unable to address this until that third party releases a fix that we can update to that we feel confident will fix this bug.