RiotGraydiance

Thanks for the report, helped me track this one down. Originally I thought it was part of the Swiftplay bug, but it was separate and specific to the Hextech Rift Hexgates.

This sadly won't get fixed before 15.2, but I can confirm that the ARAM Hexgates DO work for the mission in 15.1, if you've still been stuck on it.

Thanks for the context! I'm glad it worked in the ARAM game. Do you know specifically which keystone rune within Inspiration you used for both the Swiftplay and ARAM game? Was it the same or different?

Hi there - since I'm not sure if your comments were before or after the Swiftplay patch, were you able to make progress on the Inspiration keystone mission in the last three days?

Can I ask for more details? Which specific missions weren't working for you yesterday?

Checked the ticket for this - it should be fixed as of yesterday.

Now! A micropatch went out for it about 20 minutes ago; ran a swiftplay on live and saw progress.

Totally agree on it being frustrating. I wanted to do my OWN missions in swiftplay too

We're tracking down a issue with certain missions not working on Swiftplay queues (which includes bots) - these missions are on that list. Hopefully will have a fix in ASAP. Thanks for the info!

EDIT 1/10/2025 5:10PM PST A micropatch was deployed in the last hour that fixes the bug with Swiftplay queues not granting progress towards certain missions. All missions possible in Swiftplay queues should now be functional.

There is a separate issue with a single specific mission - Takedown 30 enemies in a single game of ARAM - that a fix is still ongoing for. Thank you everyone for your reports, they helped me track down the core issue very well.

Hi there - was this in a Swiftplay match? There is a known issue where certain missions aren't tracking in Swiftplay queues (bots is included in that), those two missions are on the list.

Looking into this - thank you for the report!

Investigating this - we've narrowed down the issue to be a Swiftplay-specific one. Certain missions aren't properly progressing in Swiftplay. Thanks for the report!

Not sure if I have my redname properly. sorry if i don't mods <3

There's a tough balance to find between "let everyone play naturally" vs. "help people find fun they may not have been aware of." It's my goal to be accepting of where players are, for all modes, all playstyles, all champion mains, and even odd people like myself who actually prefer fill and who play like 87 champions (not well, mind you).

It's difficult to create a mission system that is wholly inclusive unless it's, well, a bit boring. As u/BarackProbama said elsewhere in this post, we've been thinking about this for a while and have some longer term plans around it. I'm one of the folks trying to find the right direction to go here :)

As the person who wrote the "Better Hat Wins" mission for Winterblessed Arena, that mission is borderline on "gameplay warping," even if the optim...

hi hi i'm not them but we're on it :)

u/dhiwbrvej ty for the post - as folks guessed this was just an oversight, our tutorial mission tests passed because blind pick was still available. Fix will be in ASAP, and we'll be changing the mission text to say that you should play Quickplay!

Most of these are on my watch-list :) Not sure if/when they might get updates, but I know that some challenges need both a balance pass and their descriptions updated to reflect what we're actually asking you to do. Farm Champs is one of those examples - it's presently set to need you to do that many kills in one game, rather than adding up progress over separate games. We don't want to make challenges' requirements harder, so if that one gets changed, we'll likely lower the values and make it clear that it has to be done in one game.

Adding on /u/BarackProbama's comment on this to say "we're looking into this, expect them to change!" We want challenges to take several years, but with a challenge that's triple-stacked against you (requires you to win games AND you can't progress it consistently on your own schedule), it's a bit unfair to ask for this much perfection.

/u/Levinant- we totally agree with you that these are too difficult. The intention was to capture the effort people had already put into Clash, and make sure that they didn't get an unfair advantage, but what we changed the values to didn't exactly match up to that intent. My intention is to ...

I'd be challenger in all of these

Great job on the icons!!

Intentional! As we were playtesting different versions both with modified rubble and without rubble, all of our tests where the lane was more open were well-liked.

So when it came to the choice to revert the rubble, we wanted to keep the bridge fixed to see if a zero-choke-point ARAM leads to more fun fights in the mid-game with more room to maneuver, and larger brushes to dodge in and out of.

Thank you! We're really glad it's being well-received :)

A few of our tests went REALLY long, so we're monitoring to make sure game times don't get excessive, but we're seeing good trends in the data so far.

Oh I totally spaced out on this - I have a riot flair on the WR sub, but not here. I can reach out myself to them too! Thanks for the help haha

This change is just for URF, correct. The URF timers were particularly long, and warranted a quick fix since URF won't stay online forever.

We did reduce death timers in ARAM by 1 second in 13.1, and as the note says we agree that the ARAM timers are still too long! With all the issues of the last two weeks, we just haven't been able to fully validate that lowering ARAM timers further will have no negative effects on the mode :(

Hey there! I'm Graydiance, a game designer who swapped over to Modes from Wild Rift with the new year! I'm one of the designers now working on ARAM, and I can confirm we're actively looking into timers and other frustration points, like the turret rubble. Coming from Wild Rift, I'm learning a lot about how the games are both very similar and very different. One thing holds true in both - League's a game where often the best way to make sure the game ends is to remove people from the map. But, this isn't exactly fun, and we recognize that and emphatically agree with how the community feels.

We are trying a variety of solutions to make sure that if we change something frustrating, we aren't creating a different pain immediately. I didn't want to overshoot a death timer change in 13.1 because we didn't have a lot of time to test whether games would stall out with the Hexgates. We're doing that diligence now and will have something to share soon. We may not g...