devtrackers.gg
Only Epic? No play then.
We’re also on Steam, don’t worry <3 https://store.steampowered.com/app/1276790/Ruined_King_A_League_of_Legends_Story/
Only Epic? No play then.
We’re also on Steam, don’t worry <3 https://store.steampowered.com/app/1276790/Ruined_King_A_League_of_Legends_Story/
Why do they all look so much better than we are used to O.O
would beefup Illaoi bit more, but holy f**k that's amazing
This is Joe Mad’s take on the League universe :)
It's outsourced by Riot to be made by another game studio, though, isn't it? They are mentioned at the bottom of the site:
Not outsourced. Airship are our partner for the game, it’s their game. They pitched the idea and have led creative. We’ve been there to help guide them in making sure the game is faithful to the lore. Joe Mad and the team have been amazing to work with.
There was a tonne of pressure and expectation to perform in this series and a lot of nerves. I hope Vedius and I delivered for you.
I'm exceptionally proud of the entire broadcast team, I felt today's show was a banger from top to bottom and I am so happy SN gave us some great games. The best team at worlds won the title. Congrats DWG
Final Boss is still the best team name ever (next to clg of course)
TBF what made it so cool was that it was true... at their peak, they were the undisputed team to beat, and that they leaned into that was so cool.
Dang... I might go play some MCC after Worlds is over. This comment got me all nostalgic.
I couldn't imagine Ender pulling that segement off so well at the beginning of the year. Dudes grown so much and you know he's only going to get better
I'll try my best! thanks!
Ender your earrings at worlds have been fire, f**k haters.
thank you :)
[deleted]
There will be more opportunities that we’ll announce.
/u/CodeofBear is there a chance that there will be tech blog post explaining what and how did you create behavioral systems and the results? I really love the tech blog posts that you guys make.
I'd love to have the team give insight into the tech decisions and architecture. Some of these problems have unique and challenging solutions under the hood.
Read moreI don't think this is directly related to the client - maybe the in-game client, but last night I started closing my out of game client during the match & it helped at first but not always:
I get either a memory leak or some kind of network problem while I'm playing League with a web browser open (ie I've got spotify going in the background or something). Even with the one window open, and I've tried Firefox/Chrome/Edgium to no avail, eventually it just bogs my game down until I close the browser. I tried just powering through it & it actually DC'd me from the game until I closed the browser.
It may well be a PC problem to troubleshoot, but I only noticed it start happening maybe a month or two ago, and I don't see it happening with other games.
Is the client cleanup involving the in-game client, or is it only the out of game client?
Edit for posterity: I'm fairly strongly convinced it's a browser ad. It happens frequently on u...
That's really strange. This shouldn't be related to League Client (unless its been open for a long time). I've seen this with Chrome before and had to exit out of that but I'm not really sure, sorry!
Piggybacking to add:
- The rune page, as it is now, works horrendously when you're on the secondary tree and want to change one of the runes while staying in the same rune path. For example, you have Presence of Mind and Cut Down, and want to swap one of those for Legend: Tenacity, but the client randomly picks which one you want to replace, instead of replacing the one you tried to edit.
This should hopefully get a lot better next patch. Sit tight!
Feedback:
- Why doesn't the rune page auto save after every click. Clicking a save button seems like extremely old tech.
- Why does the rune page need it's own popup that requires you to move in and out of during champ select? Why is it not integrated in the champ select window so you do not need to open and close windows while performing other tasks?
- The ability to scroll wheel through skins, rather than spam clicking.
For players: If you have issues with memory leaks and other ember issues related to that, set your client to close while in game. This will forcefully reboot your client regularly so it never builds up. It's not that bad of a wait after a game with the improved boot up time.
Appreciate the feedback. You have some really interesting ideas that I want to present to the team. There's likely a number of technical issues and limitations that prevent us from implementing these types of changes, but I think they at least worth looking into.
In regards to the 'set client to close in game' - it's not a bad idea but I think the experience can be a bit janky since there are more stutters and less feedback given than if the client remained open. I'm not sure if this option actually 'reboots' the client but if people are really struggling with their end game experience, it could be worth a shot.
Read moreSince you're here, just wanna say I miss your work so much :(
I miss all the rotating game modes that you guys managed to put out like Ascension and all, it was SO MUCH fun...
It feels so bad that Riot has moved away from these due to what I assume to be low play rates :/
I swear those rotating game modes like Black Market Brawlers/Invasion/Nexus Siege is literally all I want back ._.
I know you're at Riot Forge nowadays but if you have a way to communicate this piece of feedback internally please do, having custom made modes for events was the shit and made every events feel sooo much more special.
I might just be one small voice in an ocean of many but god do I wish those modes were still being made, honestly I think I've started playing League way way less around the time riot discontinued them, Odyssey was a ton of fun as well but after that, haven't gotten much afaik. Spirit Blossom was amazing but still, I would give anything for a PvE ...
I had a blast making them too, was almost 5 years of game modes and hard to pick a favourite. I'm not on LoL anymore, so not exactly sure where they're at with them nowadays.
I had to eventually move on though honestly. 5yrs was a loo-ong time to make game modes :P but the kinds of games I wanted to make I was never going to be able to do inside of 'League of Legends the PC MOBA'. Riot Forge though is exactly the kind of stuff I wanted to make more of. Indie games, single-player, more story driven, different genres.
+1 for co-op PvE modes inside LoL PC though. :)
Regarding the leaver/afks. Some people just click here and there every few mins to avoide leaver buster but still stay in base afk. I mean when a champ hasnt left the fountain for 5min is save to say they are not playing the game. It shouldnt be that easy to "out play" a leaver buster.
We have in-flight work to directly improve our detection of these exact behaviors. They're not quite ready for launch yet, but they are showing improvements in test.
Do these changes apply to norms? I don’t play ranked because of the shit punishment system. But guess what? The same problems exist in normals.
I don’t wanna hear “it’s just norms”. Do we tolerate extreme toxicity / game ruining behaviour when we play pick-up ball?
Yes, these changes apply to normal queues. The exception is the LP consolation changes.
Does that 1.6 MB leak fix apply to every time someone opens the ward skin/summoner spell/whatever was causing it?
If so it's a pretty big fix long-term for people who (I have no idea why they think this is a good idea but they do it anyway) leave the client open overnight, or for multiple hours. Definitely appreciate the fixes being applied here. I don't know how many times I see someone complain about their client running poorly and when I ask how long they've had it open they say "I constantly leave it open for 3 days at a time" or something.
if you set both wards and spells, yes, every time. And we have ran our tool to capture a lot of these leaks. for example, every time you visit match history, there is a leak. So with the fixes we are putting in in the next couple patches, we expect those leaks to stop, which would reduce the memory footprint game after game
I feel like every time one of these posts come up, they're so hand wavy. Even the sparse data that they show isn't helping their case that progress is being made. Like, wow, saving 1.6 mb of memory leakage from wards in champ select is not worth even mentioning when they say in the same paragraph that there's over 100 mb of memory leakage just for using champ select.
With the first set of memory fixes, yes they were small, but we had to make sure everything else remained stable. We have a good number of additional memory improvements we are launching very soon, which should improve the reliability of Champ Select and the client, and it is larger than 1.6 MB overall :)
Threads like this bring a tear to my eye. <3
Any talk on addressing the massive .tmp files in players have been reporting in patch 10.21? Seems like a pretty significant issue
But I have definitely noticed their efforts in improving champ select. There was a few months where, idk if it was my internet or what, but I could randomly freeze on 0 seconds at any point in champ select for entire minutes, and if my pick was during that time it would force a dodge. I have t had that issue for at least a few patches now, so great work on their end fixing that.
Yes, that is an issue outside of the client.
I am getting updates from the team looking into that issue and it seems as though the game engine is crashing before getting back into the client successfully. I can assure you we have a team looking into it.
Thanks,
Jesus the amount of bandage fixes are astonishing.
Imagine removing experiences to make a CORE feature of the game (champ select) work better. What a complete waste of time and resources these updates are.
And what’s even more shocking is that without community persistence, the client would’ve only gotten worse. But guess what, it already is even with the legendary client team on the job; just shambles man.
Drop the ego, build from scratch 🤦🏽♂️
Your fault it got this point anyways, pure neglect and “if it ain’t THAT broke then why fix?” attitude.
Appreciate the feedback, we are not putting band-aid fixes
We posted the first couple of client cleanup posts to reflect the architecture work we are doing (reducing ember apps, plugins) in order to optimize code and deliver improvements. After listening to players, they do not necessarily care about us cleaning up the architecture (even though internally it's our goal), but would rather see how it would improve their experience using the client
So we put these comms posts in a position to clearly articulate what benefits players will see while cleaning up the architecture (e.g. reducing ember apps in champ select) to provide a more reliable experience.
We also wanted to be transparent, we promised players we are going to do a complete review of the UX/UI of Champ Select to see where we make performance and reliability gains. If we find a lot of players are using the features we listed, we will keep them, and also fix/optimize them