Rioter Comments
: At least one person has mentioned disabling their Antivirus solved their issue. May be worth a try while we investigate.
: kk can you give me your game logs? Ty! In eg. C:\Riot Games\PBE\Logs\GameLogs There are folders for each run of the game (with a timestamp) Find your latest run (or the one where it crashed) In that folder grab the ***_r3dlog.txt
I've been trying to connect all night. Nothing (from today) in my GameCrashes, GameLogs, or Performance Logs. I do however have some stuff in the LeagueClient Logs. 000000.000| ALWAYS| Logging started at 2019-04-30T19:21:15.012 000000.000| ALWAYS| Application Version: - CL:2726802 - Build Date: Apr 29 2019 - Build Time:19:21:42 000000.000| ALWAYS| Log file C:/Riot Games/PBE/Logs/LeagueClient Logs/2019-04-30T19-21-15_23264_LeagueClientUxHelper-renderer.log 000000.001| ALWAYS| Running LeagueClientUxHelper version 000000.001| OKAY| Initial working directory: "C:\Riot Games\PBE\RADS\projects\league_client\releases\\deploy" 000000.001| OKAY| Current process: "C:\Riot Games\PBE\RADS\projects\league_client\releases\\deploy\LeagueClientUxRender.exe" 000000.001| OKAY| Command line arguments: --type=renderer --no-sandbox --disable-databases --lang=en-US --lang=en-US --log-file=C:\Riot Games\PBE\RADS\projects\league_client\releases\\deploy\debug.log --disable-spell-checking --enable-pinch --device-scale-factor=1 --num-raster-threads=2 --content-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --video-image-texture-target=3553 --channel=6044.1.996188813\171131885 /prefetch:1 --app-name=LeagueClient --ux-name=LeagueClientUx --ux-helper-name=LeagueClientUxHelper --log-dir=LeagueClient Logs --bugsplat-name=league_client_riotgames_com --app-port=64438 --bugsplat-platform-id=PBE1 --app-log-file-path=C:/Riot Games/PBE/Logs/LeagueClient Logs/2019-04-30T19-20-59_26896_LeagueClient.log --primary-ux-log-file-path=C:/Riot Games/PBE/Logs/LeagueClient Logs/2019-04-30T19-21-01_6044_LeagueClientUx.log 000000.001| OKAY| Memory Monitor enabled: 000000.001| OKAY| - update interval 5s 000000.001| OKAY| - memory delta threshold 10MiB 000000.001| OKAY| - page fault delta threshold 100K 000000.001| OKAY| - region count delta threshold 10 000000.019| OKAY| Working Set Size: 8MiB Peak: 8MiB Pagefile Usage: 99MiB Peak: 99MiB Private Usage: 99MiB 000000.019| OKAY| Paged Pool Usage: 0MiB Peak: 0MiB Non-Paged Pool Usage: 0MiB Peak: 0MiB 000000.019| OKAY| Committed Total: 177MiB Committed Image: 112MiB Committed Mapped: 13MiB Committed Private: 51MiB Reserved Total: 30MiB Reserved Image: 0MiB Reserved Mapped: 22MiB Reserved Private: 8MiB Free Total: 3887MiB Limit: 4095MiB Largest Free: 2033MiB Region Count: 492 000000.019| OKAY| Page Fault Count: 2K 000000.303| OKAY| Browser 1 created. 000002.500| OKAY| Registering V8 context for browser 1, frame 2, url https://riot:Qj1mW7iR5x37gZkRLFvs9w@ 000005.019| OKAY| Working Set Size: 78MiB (+70) Peak: 114MiB (+106) Pagefile Usage: 164MiB (+65) Peak: 208MiB (+109) Private Usage: 164MiB (+65) 000010.021| OKAY| Working Set Size: 131MiB (+53) Peak: 185MiB (+71) Pagefile Usage: 204MiB (+40) Peak: 270MiB (+62) Private Usage: 204MiB (+40) 000010.021| OKAY| Page Fault Count: 129K (+127) 000010.892| OKAY| Registering V8 context for browser 1, frame 3, url 000011.620| OKAY| Registering V8 context for browser 1, frame 4, url 000014.041| OKAY| Registering V8 context for browser 1, frame 5, url 000015.022| OKAY| Working Set Size: 202MiB (+71) Peak: 207MiB (+22) Pagefile Usage: 272MiB (+68) Peak: 275MiB (+5) Private Usage: 272MiB (+68) 000020.025| OKAY| Working Set Size: 241MiB (+39) Peak: 262MiB (+55) Pagefile Usage: 309MiB (+37) Peak: 332MiB (+57) Private Usage: 309MiB (+37) 000025.026| OKAY| Working Set Size: 275MiB (+34) Peak: 276MiB (+14) Pagefile Usage: 349MiB (+40) Peak: 350MiB (+18) Private Usage: 349MiB (+40) 000025.026| OKAY| Page Fault Count: 254K (+125) 000030.026| OKAY| Working Set Size: 282MiB (+7) Peak: 286MiB (+10) Pagefile Usage: 360MiB (+11) Peak: 364MiB (+14) Private Usage: 360MiB (+11) 000040.050| OKAY| Working Set Size: 265MiB (-17) Peak: 286MiB (+0) Pagefile Usage: 343MiB (-17) Peak: 364MiB (+0) Private Usage: 343MiB (-17) 000048.900| OKAY| Unregistering V8 context for browser 1, frame 5. 000049.303| OKAY| Registering V8 context for browser 1, frame 6, url about:blank. 000049.427| OKAY| Unregistering V8 context for browser 1, frame 6. 000049.522| OKAY| Registering V8 context for browser 1, frame 6, url 000050.089| OKAY| Working Set Size: 287MiB (+22) Peak: 287MiB (+1) Pagefile Usage: 364MiB (+21) Peak: 364MiB (+0) Private Usage: 364MiB (+21) 000055.090| OKAY| Working Set Size: 342MiB (+55) Peak: 342MiB (+55) Pagefile Usage: 418MiB (+54) Peak: 418MiB (+54) Private Usage: 418MiB (+54) 000059.754| OKAY| Unregistering V8 context for browser 1, frame 6. 000059.857| OKAY| Registering V8 context for browser 1, frame 7, url about:blank. 000060.110| OKAY| Working Set Size: 523MiB (+181) Peak: 524MiB (+182) Pagefile Usage: 629MiB (+211) Peak: 630MiB (+212) Private Usage: 629MiB (+211) 000060.715| OKAY| Registering V8 context for browser 1, frame 8, url about:blank. 000061.253| OKAY| Unregistering V8 context for browser 1, frame 7. 000061.325| OKAY| Registering V8 context for browser 1, frame 7, url,filter_ranked_enabled,filter_location_usa,filter_location_usa_ma,filter_location_usa_ma_lowell,filter_revival_false,filter_lane_nolane,filter_rank_tt_not_ranked,filter_rank_flex_not_ranked,filter_rank_solo_bronze,filter_rank_unranked,filter_interest_145,filter_interest_83,filter_interest_28,filter_interest_236,filter_interest_36,filter_testgroup_6#protocol=https:&port=64438. 000062.280| OKAY| Unregistering V8 context for browser 1, frame 4. 000062.281| OKAY| Unregistering V8 context for browser 1, frame 3. 000065.110| OKAY| Working Set Size: 534MiB (+11) Peak: 539MiB (+15) Pagefile Usage: 642MiB (+13) Peak: 642MiB (+12) Private Usage: 642MiB (+13) 000065.110| OKAY| Page Fault Count: 373K (+119) 000070.111| OKAY| Working Set Size: 549MiB (+15) Peak: 572MiB (+33) Pagefile Usage: 653MiB (+11) Peak: 655MiB (+13) Private Usage: 653MiB (+11) 000072.174| OKAY| Registering V8 context for browser 1, frame 9, url about:blank. 000075.112| OKAY| Working Set Size: 572MiB (+23) Peak: 595MiB (+23) Pagefile Usage: 662MiB (+9) Peak: 671MiB (+16) 000078.269| OKAY| Unregistering V8 context for browser 1, frame 9. 000078.615| OKAY| Registering V8 context for browser 1, frame 10, url about:blank. 000080.114| OKAY| Working Set Size: 627MiB (+55) Peak: 627MiB (+32) Pagefile Usage: 751MiB (+89) Peak: 751MiB (+80) Private Usage: 751MiB (+98) 000083.254| OKAY| Unregistering V8 context for browser 1, frame 7. 000084.008| OKAY| Unregistering V8 context for browser 1, frame 10. 000084.234| OKAY| Registering V8 context for browser 1, frame 11, url about:blank. 000085.115| OKAY| Working Set Size: 541MiB (-86) Peak: 670MiB (+43) Pagefile Usage: 859MiB (+108) Peak: 863MiB (+112) Private Usage: 859MiB (+108) 000085.115| OKAY| Page Fault Count: 475K (+102) 000090.119| OKAY| Working Set Size: 700MiB (+159) Peak: 700MiB (+30) Pagefile Usage: 955MiB (+96) Peak: 961MiB (+98) Private Usage: 955MiB (+96) 000095.120| OKAY| Working Set Size: 724MiB (+24) Peak: 746MiB (+46) Pagefile Usage: 978MiB (+23) Peak: 979MiB (+18) Private Usage: 978MiB (+23) 000105.122| OKAY| Working Set Size: 710MiB (-14) Peak: 746MiB (+0) Pagefile Usage: 964MiB (-14) Peak: 979MiB (+0) Private Usage: 964MiB (-14) 000107.561| OKAY| Unregistering V8 context for browser 1, frame 11. 000110.122| OKAY| Working Set Size: 580MiB (-130) Peak: 746MiB (+0) Pagefile Usage: 813MiB (-151) Peak: 979MiB (+0) Private Usage: 813MiB (-151) 000145.130| OKAY| Working Set Size: 593MiB (+13) Peak: 746MiB (+0) 000150.132| OKAY| Working Set Size: 605MiB (+12) Peak: 746MiB (+0) Pagefile Usage: 830MiB (+17) Peak: 979MiB (+0) Private Usage: 830MiB (+17) 000155.132| OKAY| Working Set Size: 508MiB (-97) Peak: 746MiB (+0) Pagefile Usage: 719MiB (-111) Peak: 979MiB (+0) Private Usage: 719MiB (-111) 000185.135| OKAY| Working Set Size: 471MiB (-37) Peak: 746MiB (+0) 000300.165| OKAY| Working Set Size: 414MiB (-57) Peak: 746MiB (+0) 000300.165| OKAY| Page Fault Count: 577K (+102) 000416.951| OKAY| Registering V8 context for browser 1, frame 12, url about:blank. 000418.067| OKAY| Unregistering V8 context for browser 1, frame 12. 000418.134| OKAY| Registering V8 context for browser 1, frame 12, url,filter_ranked_enabled,filter_location_usa,filter_location_usa_ma,filter_location_usa_ma_lowell,filter_revival_false,filter_lane_nolane,filter_rank_tt_not_ranked,filter_rank_flex_not_ranked,filter_rank_solo_bronze,filter_rank_unranked,filter_interest_145,filter_interest_83,filter_interest_28,filter_interest_236,filter_interest_36,filter_testgroup_6#protocol=https:&port=64438. 000420.190| OKAY| Working Set Size: 435MiB (+21) Peak: 746MiB (+0) 000440.192| OKAY| Working Set Size: 406MiB (-29) Peak: 746MiB (+0) Pagefile Usage: 698MiB (-21) Peak: 979MiB (+0) Private Usage: 698MiB (-21) 000465.195| OKAY| Working Set Size: 343MiB (-63) Peak: 746MiB (+0) 000770.340| OKAY| Working Set Size: 247MiB (-96) Peak: 746MiB (+0) 000885.459| OKAY| Working Set Size: 201MiB (-46) Peak: 746MiB (+0) 000925.484| OKAY| Working Set Size: 139MiB (-62) Peak: 746MiB (+0) 000930.485| OKAY| Working Set Size: 123MiB (-16) Peak: 746MiB (+0) 000935.486| OKAY| Working Set Size: 103MiB (-20) Peak: 746MiB (+0) 000980.541| OKAY| Wor
: Draft Pick is enabled {{sticker:zombie-brand-mindblown}}
If only we could start a game. {{sticker:zombie-brand-clap}}
: PBE Bugs & Feedback Thread: Pool Party and Headhunter Akali Chromas!
Is there any chance that the Headhunter Master Yi chromas will be revisited to look as nice as the newer ones for Rengar and Akali?
: I mean to be fair if you take a look at R/Akalimains there have been a number of complaints ranging up players who had 3 million masterypoints on the old akali vs ones that just recently picked her up and in between. This feels like you wanted to nerf live akali in every way possible to make her as healthy as possibly for the rest of the playerbase that doesn't care for her. Not to mention it's obvious that the team behind akali forced us to basically focus on the shroud as her core identity piece when that wasn't what made akali, akali to us. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The sustain is shit compared to live akali, where you previously if you got low could back down do a quick jungle camp and get back to decent health whereas now you barely notice any sustain in general unless extremely ahead and even then its -insert missing enemy ping- in terms of vagueness. how the ult is handled is shit as well, still don't understand the forced cooldown in between the charges as it should be optional how quick you wish to use the execute rather than be forced to wait 3 seconds. screams leblanc before she got reverted in terms of wanting to artificially delay burst. this does **not** work. There's a reason lb got reverted back learn from these mistakes. anyways to list a number of complaints from community members so this hopefully would get some visibility. Though if you actually wish for feedback and critique it's all compiled within r/akalimains either way so.. - "I'm honestly surprised that almost everyone is just hyping up the rework when it's honestly not so great. I mean there are many things that I love about the new akali but the lacking sustain, removal of the resets and the 120s ult cd are honestly a big nerf and completely kill her playstyle. If I just want to go in and assasinate someone I could also play other assassins like Zed or Fizz. But I played akali because she was different.. short cooldowns, resets etc. you get what I want to tell." - " Akali caught my attention in the game precisely because she was a champion with quick decision making, although she was never really a tanker, she gets into the fights and does what needs to be done quickly, now appears to be a champion without mobility and extremely slow. Diana with her current kit is more of a assassin than Akali. It's not just about dealing damage, killing, or needing to buff the skills, but it seems like she lost the assassin essence with those skills." - "The ultimate cooldown itself, I feel like, is way too long. As an Akali, I want to constantly go in and out with my ult, that's the play style I loved. I am ok with the ult not doing so much damage, but I would like for it to be on lower cooldowns at least. This Akali feels nothing like the previous one, the play style is too different. There is ridiculous amounts of wait involved to the point where i think it's actually more similar to a mage with a burst ultimate or Zed even." - "Ultimate cooldown is very time consuming, between the first and second dashes." - "the CD makes me literally sick. She used to be rewarded an extra charge if she got a kill or assist. Now you get fucked. There's no more 1v5 potential. You run out of energy far too fast, your ultimate CD is a lifetime long, your Q eats too much energy with the only way of restoration being your W because your passive energy return requires you to spend x3 the amount of energy for 1/3 the return. The range on it is terrible too. Your E damage is absolutely horrible. Your W, if you W after being CC'd, the donut hole forms around you and you exit shroud for the duration of the CC and until you can move back into the shroud." - "Her Sustain is GONE - like GONE GONE , its extremely extremely bad compared to old Akali. This is one of the most disjointed things I am suffering with her , the fact that late game you can no longer go get all your HP back from a jungle camp is cancer. I suggest changing the heal on Q from % premigation damage done to healing % missing HP scaling by level." - "How is the new akali any better than the live akali. I mean the old passive, q, r are just the better versions of the new one. E is different than the live akali and the only difference for the w is that you can't be targeted by the turrets. Other than that live akali is just way stronger than the reworked one: " - "Old Akali could get two passive heals in 8 seconds on average - that's 0.9 AP. New Akali gets one Q heal every 8 seconds on average - that's 0.2 AP (though ad scaling is higher, but who cares about that). " - "I hate the long ulti cooldown.. I just..hate it , compared to the 30 second stack system we used to have. I understand that the extra power in the new ult has to be balanced by cool down but they could at least make it so if you dont used the execute portion of the ultimate the cool down gets reduced by 50%" -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Don't get me even started on the visuals.. Professor Akali's video rework spotlight included content he shot when he playtested at riot HQ back in April, and guess what... nothing and literally nothing of those visuals have been improved within the skins. everything has been left untouched and thank god there is some sort of proof to hold back as a referendum with what we have now and compare.. Akali has 5, freaking 5 skins that have a value of 975 RP or higher, and only 2 of them got fitting vfx... Silverfang akali got nothing, all star akali got nothing, nurse akali got nothing this is honestly unfair when reworks are done to fit the visual norm of today within the visual aspect yet here we have 3 975 rp skins that received no vfx whatsoever. and we all know that riot wouldn't dare to release a new skin for 975 rp with absolutely no changes or recolors in vfx as of right now in 2018. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Before i close off, don't take this comment as someone being a hater or trolling because that isn't the case, it's because i'm extremely passionate about Akali and to see the overall rework feel so "meh" in every aspect be it gameplay or visually (skins) is disheartening. it feels like we're just getting ignored just like how r/aatroxmains got treated even though they were **warned** before that aatrox would be completely different. while that wasn't the case here and her rework was promoted as a modernization of akali when iconic parts of her kit have been ditched..
I thought killing Akali's old playstyle was the point of the 2 reworks? Someone effortlessly pressing R on an enemy and killing them while healing to full health was really obnoxious. The shroud was the only part of her kit that had something resembling counterplay - you knew approximately where Akali was and didn't stand in the shroud. The healing was ridiculous but she had such a bad kit that healing half of her health in 30 seconds was the only way she survived lane. Then after level 6 and gunblade, she would kill her lane opponent every time the poor bastard dared to walk into her lane. The new kit is designed so that she can fight enemies before level 6 and kill them when she has her ult. The cooldowns and skillshots give enemies breathing room so that they can possibly fight back. You could maybe debate that the new akali is weaker than the old one, but if that's true, it's easy to fix with buffs to her numbers and small functional changes. It also comes off as pretty arrogant to judge the champion so harshly when literally none of you have come close to mastering her yet; she only just appeared on the PBE a day ago. "She has no 1v5 potential anymore" Oh give it a rest. The fact that she had that potential at all only proves that she had severe counterplay problems.
: Draft Pick Champ Select Timing Improvements on PBE
I logged in just to say this is an awful idea. I can't count how many times I've tried to ban a champion, but the button (to lock the ban) didn't light up until the last second. Everybody has problems in champion select like this, fix them before you try to make the experience more "engaging."
: Hi everyone, Have you tried adding movespeed to Lux W? It just feels like the champion keeps receiving buffs and buffs until its seen on LCS and that is just not going to happen unless she is straight up broken. Maybe a rework to her passive? I dunno, it just feels like adding power to the champion in weird places.
Lux has a fine passive and I don't think the solution to every underpowered champion is to give them more movement speed.
: PBE Chat with the Playtest Team - 8.8
This is an interesting change of pace... I guess it makes sense the never-before-seen changes are the ones that you get asked about a lot on the Playtest Q&As. 1) What version(s) of Ahri are you gravitating to? Which changes are showing the most promise? 2) Do you think the Vi changes could make her viable in top or possibly mid lane? Or do you think her kit has more fundamental weaknesses that force her into the jungle? 3) Will Varus get more nerfs to compensate for the addition of a new active ability? 4) What larger problems with Nautilus need to be addressed? Meddler mentioned something about that in [this]( post.
: Ideas to buff Yi (constructive)
I think the concept of Master Yi meditating *before* fighting to build strength is okay, it's just that the implementation here is weak for reasons I explained in this post:
Rioter Comments
: PBE Bugs & Feedback Thread: Snow Fawn Poppy!
All three of the skins are 1350RP? I mean obviously they're epic skins, but why is every skin release lately 1350RP?
: [CLOSED] PBE Bugs & Feedback Thread: Victorious Graves!
I hate the purple but I guess it doesn't matter when all 3 of the chromas look better.
Rioter Comments
: We have something in mind. I think that's too much but agreed it's pretty good :)
: > [{quoted}](name=literalweebtrash,realm=PBE,application-id=cMKtzQHY,discussion-id=sELJIHkn,comment-id=0002,timestamp=2017-09-12T20:57:05.761+0000) > > I like the skin overall has a great flow, but the animation for doublestrike seems VERY forced and VERY unatural. Everything else, sound FX, particle effects are easy to read and great to look at. I think there needs to be some tweek to the animation of double strike. As it sits right now its like an overhead swing witha back hand afterwards and again its just very jarring to look at. Thanks for the feedback! I'll bring this back to the animator and get his thoughts on the double-strike.
I just wanna say, I actually like the Double Strike a lot. It's a small thing that makes the skin feel unique and interesting.
: > [{quoted}](name=CarnicorePBE,realm=PBE,application-id=cMKtzQHY,discussion-id=sELJIHkn,comment-id=0004,timestamp=2017-09-12T23:01:27.508+0000) > > Character Inking doesn&#x27;t work for this skin :( Sorry, it's been purposefully removed for this skin because it didn't look that great with the transparent cloth tassles. :<
: [CLOSED] PBE Bugs & Feedback Thread: Eternal Sword Yi!
Character Inking doesn't work for this skin :(
: PBE Bugs & Feedback Thread: Cosmic Blade Master Yi!
The E activation is too quiet, in the middle of the fight I have no idea whether I activated it.
: PBE is currently overloaded. As people filter out of the client, this will resolve :) For now, the new champions are free to play as a work around.
: Galio Feedback Thread
: Galio Feedback Thread
Do you want to make hundreds of thousands of players happy with less than 2 hours of work? Make a Traditional Galio Chroma. Please?
: Great Patch Riot 10/10 And thanks for paying SOO much atention to the boards. 11/10 why do you even have boards at this point?, just release the patch and hope it works, why pay atention to the feedback?.
The PBE server shut down for maintenance, they're probably working on the problem.
: Adding Simple Recalls- Now on PBE!
I appreciate the "Ruuuuruuus." You guys need to set ground rules for feedback more often, it helps keep players focused on suggesting realistic changes.
: Hunt of the Blood Moon game mode available shortly on PBE
That allowed champion list is ridiculous. Ahri and Kennen barely belong on that list, but yet Fiora, Irelia, Kled, Master Yi, Nocturne, Nidalee, Riven, Quinn, Wukong, Jarvan, Jax, and Xin Zhao are all absent. Idk why Ahri is allowed if Jayce isn't, Jayce at least plays aggressively.
: Warwick Update Feedback Thread
The new W passive is terribly confusing to play against. Regardless of where I am, dropping below 50% health (which is a completely normal part of laning) causes that blood hunt indicator to hover over my head and ominous music to start playing. I feel like I'm being hunted even when Warwick is literally across the map from me. Which seems very wrong to me.
: Power farming junglers are something that we're suppressing as we've never really been happy with the gameplay of continuously power-farming your jungle until you come out fully farmed at 20 minutes. This isn't a line we intend to support. In general, the full clear will give more gold and xp than before - but not enough to match the continuous power-farming era.
First you remove the attack speed from Ghostblade, and now this. {{item:3070}} {{champion:11}} {{item:3070}}
: [PBE - Jungle Notes] Notes on updated Jungle for 6.22
>Camp respawn times increased to 150 from 100 Did I miss something? Do camps give more gold now? If not, this is going to kill farming junglers...
: Target's Level. Live Value (20) PBE Value. | Level | Live | PBE | |:------------:|:----:|:-----:| | 1 | 20 | 8.67 | | 2 | 20 | 9.33 | | 3 | 20 | 10.00 | | 4 | 20 | 10.67 | | 5 | 20 | 11.33 | | 6 | 20 | 12.00 | | 7 | 20 | 12.67 | | 8 | 20 | 13.33 | | 9 | 20 | 14.00 | | 10 | 20 | 14.67 | | 11 | 20 | 15.33 | | 12 | 20 | 16.00 | | 13 | 20 | 16.67 | | 14 | 20 | 17.33 | | 15 | 20 | 18.00 | | 16 | 20 | 18.67 | | 17 | 20 | 19.33 | | 18 | 20 | 20.00 | tl;dr: At face value it's a nerf until level 18, but remember that there are new sources of Lethality and new mechanics taking advantage of it (i.e.: Reworked Duskblade). Did we do the math right? Because according to Feral Pony, Lethality should be breaking even much sooner than level 18.
: [Assassins] - Mini Updates Discussion
What's up with this list? It has almost no information. Shaco's ult drops 3 boxes when it dies, which is a *huge* detail, but it's not mentioned here. There's other crucial stuff like Ekko losing the slow on his passive, Shaco getting % missing health damage on E, no details here about Akali's passive, etc.
: Target's Level. Live Value (20) PBE Value. | Level | Live | PBE | |:------------:|:----:|:-----:| | 1 | 20 | 8.67 | | 2 | 20 | 9.33 | | 3 | 20 | 10.00 | | 4 | 20 | 10.67 | | 5 | 20 | 11.33 | | 6 | 20 | 12.00 | | 7 | 20 | 12.67 | | 8 | 20 | 13.33 | | 9 | 20 | 14.00 | | 10 | 20 | 14.67 | | 11 | 20 | 15.33 | | 12 | 20 | 16.00 | | 13 | 20 | 16.67 | | 14 | 20 | 17.33 | | 15 | 20 | 18.00 | | 16 | 20 | 18.67 | | 17 | 20 | 19.33 | | 18 | 20 | 20.00 | tl;dr: At face value it's a nerf until level 18, but remember that there are new sources of Lethality and new mechanics taking advantage of it (i.e.: Reworked Duskblade).
That's... awful. You're right that we have one or two new sources of Lethality, but the item pool actually feels smaller than before with the loss of Maw. If you did your math right, this is a huge nerf. Like, every item I tried on the PBE feels like they do much less damage than on live servers. Ghostblade lost its attack speed with almost no compensation. EDIT: okay maybe you're right about Duskblade. But wow, now everyone will have to build it.
: Personally want her to have enough AD scaling that she can comfortably pick up a gunblade if she wants
That item hasn't been viable on her for years, all her abilities are AoE so she heals virtually nothing. I don't see that changing with this rework, unless she shifts to more of a skirmisher playstyle with really extended fights.
: [6.22 Alistar changes] Context and feedback thread
This just came completely out of nowhere lol. Any other reworks we don't know about?
: Remove Zed's %AD boost and don't add that other AD boost. Why would you give such a safe champion with incredibly high kill power another way to scale based on how much AD your carry builds then dies because QSS doesn't remove Death Mark?
You can't just nerf a balanced champion without giving something in return.
: [Assassins] - Mini Updates Discussion
Not mentioned: Shaco's ult drops boxes when it dies. 3, with an Illuminati visual effect... I'm not kidding
: Assassins Bug Reporting Thread
Boy are you going to look dumb if there turn out to be any Kha'Zix bugs.
: Please ban this guy
[This guy]( too.
Rioter Comments
: If this is seriously intentional, then whole point of Alpha Strike existence just dissapeared.
I don't see how that's a bug with Alpha Strike. That would've happened with any champion becoming untargetable.
: everyone who's played a few games of yi knows that's the behavior on live, he's wondering if it's intentional or not. It is very annoying to get knocked back ~400 units every time you hit q and puts him at a disadvantage that no other champion that I know of has to deal with.
>puts him at a disadvantage that no other champion that I know of has to deal with. But despite this, he's probably one of the best champions for soloing dragon.
: I played on the PBE a min ago and so far so good. There was a moment when Hecarim ulti me when i was i Alpha Strike and it killed me, not sure tho i was low around 50-100 HP, DOT may have killed me. Unfortunately my LoLReplay was outdated and did not record the game. ~~Can we except Master Yi buffs or changes, especially when Assassins rework hit live. As i heard pink ward no longer reveal stealth which mean Master Yi will suffer from this, since champions like Akali will go stealth for the whole Highlander duration and nothing can be done. Even right now he feel someone weak who rely on RNG, either your team has to do well or you lose. According to EUW, his win rate in 46.31% with over 350 000 games played this month. ~~ Once again thank you for working on the Alpha Strike bugs.
Do bugfixes count as buffs? I'm curious to see how these changes affect him, and I'm sure the balance team is as well.
: FEEDBACK WANTED - Alpha Strike
Awesome. Any chance we'll see a post talking about this on Riot's engineering blog? These bugs kept you busy for months.
: I've never seen the middle gray bar flicker in position before. That is probably a symptom of the issue.
What *is* that grey bar?
: If only you took the feedback about Zombie Ryze this seriously....
They couldn't give him exposed brains/bones and other decay because of China. So they compensated by giving him new spell effects. It's a fair compromise IMO.
: Why Q? What if I want a point in the E?
It doesn't really make any difference, they would just rescale the numbers. All that matters is that there's a total of 18 skill points.
: Ryze Champion Update Feedback and Discussion
Could you sharpen the red of Dark Crystal Ryze? There's very little contrast between his skin and clothing, or muscle definition.
: [6.14] Cooldown Pings on PBE
Wouldn't the default "ping" button (G) make more sense than Alt?
: [League client update] Testing loot, clubs and (soon) ranked! (Updated 9/7/2016)
Is there any general feedback thread for the new client? For QoL issues?
: Mid Season Mages Bug thread!
Viktor's E is bugged. The second part [doesn't deal damage to champions.](
: MYMU Annie, Fiddle, Veigar Discussion
To be clear, Annie's W no longer "cheats", but Tibbers still does, correct?
Show more


Level 37 (PBE)
Lifetime Upvotes
Create a Discussion