devtrackers.gg
update: it now shows for me the journey tab again! thank you
Great! We did a few fixes we think might have resulted in this so I'm glad it fixed the issue!
Thank you again for posting so we could get eyes on it asap as it was not a very common bug 🫡
update: it now shows for me the journey tab again! thank you
Great! We did a few fixes we think might have resulted in this so I'm glad it fixed the issue!
Thank you again for posting so we could get eyes on it asap as it was not a very common bug 🫡
Read moreI'm going to try and engage in good faith and do the math for you for BOTH sides rather than just what we're getting now.
Old Battle Passes (Free track)
300 tokens per completed free pass.
1 Champion Shard costs 50 tokens. 300/50=6 Champion shards 960 minimum BE. 960x5=4,800. 6 passes a year, 4,800x6=28,800 BE lost.First Win Of The Day
For this calculation we'll be doing that you play a single coop vs AI game per day for it and ONLY it. We're ignoring the potential exp you would have gained from said game.
400 Exp and 50 BE per 24 hours.
50BEx365days=18250 BE 400expx365days=146,000exp Average level is 3171exp. 146000/3171=46.0422 levels. We'll keep it at 46 to be simple. 1 level = 1 capsule 46 capsulesFor simplicity sake we'll say 4 of those capsules are Glorious ones due to getting 1 every 10 levels and say you start at 1 every time we calculate this.
New Free ...
Appreciate you doing the math!
Some considerations: - many players do not play every day, which means that max values are different from median or average values - the expected value of FWOTD is less, since it required a win, so you generally need to halve it (if you mix in a guaranteed Co-Op win game you can multiply this vs the rate at which people play those versus standard matchmade), contrast this with the daily mission that only asks to play a game at all (you can get the expected value of that by looking at average BE value of a pass level and then multiplying it by 150/500 for the win bonus. If you rate a champ capsule as being worth 3000 BE, which is the average cost of a champion you get a pretty large number) — will do below - the first 50 levels still grant capsules iirc, so you need to add more of that into the calc
It’s lower max BE for a hyper engager but much more BE on average based on standard play patterns
BE Capsule avg value = 3000 x 4...
Read moreHello! Thank you for your work! I wanted to ask on your thoughts on removing(/reducing) the 1 minute 30 second window of dead time at the start of the game with this mode, feels kinda weird when you go right into loading screen and its supposed to be faster
Not something we are actively considering at the moment but definitely not out of the question.
Do we have a timeframe for when? It doesn’t say in the patch notes.
There is no plan at the moment to enable Swiftplay in the future for OCE. That is of course subject to change.
In my head it's just the clash sudden death where the outermost structures slowly burn when the soft time limit starts guaranteeing a Nexus hits 0 by a hard time limit. (which would need to account for respawning Nexus turrets now too.)
most likely that would be what it looks like, at least in the short term.
why would they not mention anything about swiftplay matchmaking?
no ways its intended to be this terrible
There were some pretty severe bugs on launch, as of a few hours ago those should be fixed. Doesn't mean everything's perfect for sure, but should be meaningfully better.
Hey Galaxysmash, do you know when it’s arriving in OCE? There’s been zero communication and we still have quickplay?
Swiftplay currently will not be enabled on OCE per the patch notes.
Do you know when/if swiftplay is coming to OCE, alot of my ARAM only friends are excited to use it as a way to ease back into summoners rift
Definitely something we want to do, but it has to make sense given OCE's player population and the distribution of ranked play versus casual. When you say ease into SR do you think you'd want to play only Swiftplay or would you use it as a bridge back into Ranked/Draft pick
Some spells might need adjustments in their CD's, i understand that the game is meant to go faster but there's been times where in order to keep a solid pace and scale, I don't really have a chance to retreat and purchase items and refill mana. Makes it incredibly punishing if you have to use resources to even contest your enemies when they are resourceless. Since all they need to stay relevant early games is d shield + second wind, makes it almost impossible to not lose gold/xp to stay relevant.
Will be submitting some balance adjustments for Swiftplay soon, including in future patches https://x.com/RiotPhroxzon/status/1877822985421402230
Hi Galaxy!!! how are you i hope that you are fine!
Swiftplay is good addition, i had fun playing some games and the fast pace.
Would it be possible for you to experiment with a new "slot" for games that go beyond 30 minutes or something like that? like a new slot for another item that only unlocks after certain amount of time or objectives? It could be filled with a new item, or a powerfull elixir, or maybe a dropable item when you are killed?
maybe this would help with those games that go beyond 30 minutes.
Having 7 item slots (6 normal, 1 for trinket) is a bit of a core foundation for our game. Changing it is probably quite complex and would only be reserved for a massive update to our game. That being said, I wouldn't rule out any additional changes to gameplay that are specific to swiftplay.
Have you considered having the nexuses (nexi?) coming alive and moving towards the centre of the map to attack each other. Pretty cool idea imo.
Haha not out of the picture but any sudden death would likely be slightly more serious than the one from nexus blitz.
Yea I played 4 swift matches this morning and every game was between 28 and 36 minutes long. I feel like we need more damage to structures of even 3 less towers per team. Maybe even start us at level 3 or 6. I love the concept of a faster game and more even gold generation. I just want it to actually be a shorter game lol.
28 minutes is far above the average so that is quite surprising, but either way we will definitely look into cutting down game time on the high end. Average game time is still hovering around 20-25
Would making objectives and waves come up in less time help with this? I was thinking something similar to Wild Rift which has really quick games. The accelerated gold is neat but I also feel like getting full build quicker doesn’t necessarily make the game faster, especially if a full build is tanky.
You run into an issue where all you are doing is fighting objectives if we reduce their spawn times. Making objectives give more powerful rewards is a more likely direction.
Lobby UI is atrocious. It's like trying to do champ select on ⅓ of the normal size. Champions Sort by: Mastery would be great.
For swiftplay itself, some elements of summoners still feel so sluggish. Why do we still have to afk for nearly 2 min before minions spawn?
Death timers also feel really rough. Having to afk for 65+ seconds at 20 minutes is awful
Definitely noted feedback, appreciate it
How soon is ASAP? This one is pretty frustating
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
At the risk of diving into a minefield here, I do want to separate the difference between idea and execution.
Chemtech Soul we definitely took as a point of comparison of things we want to avoid. The question is, do we think the concept of a "revive" to be a concept that is completely off-limits in League.
I think the answer to that is no. And given that one of Atakhan's [the LoR card] main thing is about reviving people we wanted to pay that off. But I do think the execution matters a lot. Chemsoul being permanent, having pretty minimal counterplay (you can't really do anything differently) made it notably different from Voracious buff in our mind.
For Voracious, we expect a lot more gameplay around waiting the buff out as it's one time, perhaps prioritizing trading objectives more than straight up fighting the opponents, etc. At the end of the day though, taking Atakhan is meant to give an advantage for the team that takes it and it's a new set of gamep...
Read moreeternals still don't level up in swiftplay, but mastery and challenges do. is this intended?
It's not, sorry. We were able to resolve Mastery and Challenges like you noticed, Eternals are still in progress but we didn't forget! Hoping to have that fixed today for the weekend.
I’ve heard that with the removal of capsules on level up, all the old new player related content has also been removed. Do you know if that’s the case?
Nope, I do not know anything about that. It doesn't _sound_ correct to me.
I figured, since the quickplay system cuts down on the interstitial time between games so much, but thought it worthwhile to ask!
One more question, if it's cool with you! What kind of balance support are we going to be seeing with swiftplay in the weeks and months ahead? Is the plan to implement mode-specific nerfs a-la ARAM or Arena, or to essentially let it ride as a mirror of summoner's rift?
We are gonna use ARAM and Arena style balance, using direct champion modifiers to abilities as well as general % buffs. So if for example we though Kassadin was too good we could nerf his R cooldown directly and also apply a -5% damage dealt buff to him.
I really want to like it, but I was under the impression it was going to be tuned to be much faster than a regular rift game.
I'm happy people are liking it, but I've been surprised with my 25-30 minute games so far. Doesn't really feel like it's significantly different to a draft game, aside from the time saved queuing up.
Game pacing is something we are keeping an eye on. I think 20-25 minutes is both ideal and realistic, our main concern is the occasional outlier game going 35+ minutes. Honestly I don't think we would make the game be that much faster than it currently is (the core Summoner's Rift experience starts to get unrecognizable at that point) but we do want to come closer to guaranteeing that when you pick Swiftplay, you aren't running into the possibility of being in a game for 35-40 minutes or more in some cases. So less about "really fast games" (they should still be faster) and more about "we assure you that this experience in total will not be more than 30 minutes (rough estimate) from start to finish"
We have a few options of how we go about that, including sudden death, but we are still waiting to see what exactly game time looks like first.