: Made an entire game where you clicked somewhere and moved there 40 seconds later. Luckily, I was playing Twitch. Big brain positioning plays ensued.
> [{quoted}](name=BeardedSausage,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=wElkPHBh,comment-id=0005,timestamp=2019-10-21T22:39:43.650+0000) > > Made an entire game where you clicked somewhere and moved there 40 seconds later. Luckily, I was playing Twitch. Big brain positioning plays ensued. "Turn on auto-attack, and just sit there for others to come by"?
: Insane ping
My game slowly got back to normal, and we won a 2v3 in the end I got some pretty nifty snipes with Jinx ult.
: Why?
This is a TESTING environment. There are bound to be issues because of how close to bleeding edge the changes are. While, yes, they want it stable, they would rather have this env be unstable than live.
: Queue not starting (players not ready)
Practice tool worked...but that is all that does
: Unexpected error with the login session?
Update: It happened again, when league client was downloaded again. This time I fixed it in a new way. 1. Opened up the live client (this brought up the new Riot client) 2. On the Riot client, changed **NA** to **PBE** 3. Logged in with my PBE credentials 4. PBE client opened up. Not sure if this will be a permanent fix, but the problem is definitely related to the Riot client
: https://imgur.com/AQluTPb No, it's Urf
> [{quoted}](name=Pingiwin,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=Ohk0gfBn,comment-id=00010000,timestamp=2019-10-16T04:29:52.124+0000) > > https://imgur.com/AQluTPb > > No, it's Urf It says urf, but it is still arurf.
: Unexpected error with the login session?
1. it is still ARURF 2. delete the riot client folder 3. open PBE client 4. let it repair itself 5. you should be able to log in
: ARURF - Item Nerf
Get sweeper - laugh while shaco dies because he thinks he is being tricky.
: Why the Heck would you make Maintenances at this time ?
Because it is in the middle of the US workday, specifically it is around lunch time in the Pacific time zone, where Riot's developers live & work.
: Blitz Qs disappearing?
Looks like it was fixed with the Friday patch
: Exiting Game Bug - After game has concluded
You can also click reconnect, but it will sit for about 5 minutes trying to connect, then fail, so you click "exit" and then see the end game screen.
: Blitz Qs disappearing?
I found this last night: If you try to hook when your cursor is out of range, it fails to fire. If your cursor is in the hook range, it works fine.
: blitz Q bug
So, in my last game I think I figured it out: If you try to cast Q when it is out of range, it fizzles and doesn't fire. If you keep it in cast range, it is fine. I had to change it to smart cast to remove my habit of casting things out of range, to get more precise rotational control.
: predator + ghost malphite. he's a champ that can 1v7. no other champ can do that. or a yi. full crit makes him alpha, then he automatically autos, causing a one shot. then theres perma stun champs or juggarnauts that do dmg. then you have useless champs like kennen, nidalee, j4, etc or champs that are too squishy. careful when you say "any champ can beat any other champ." also, careful about the word "teamwork." this is PBE we're talking about, where it's more toxic than the actual servers.
> [{quoted}](name=KOSYasuo,realm=PBE,application-id=AYQh7p7O,discussion-id=oPvhyE4T,comment-id=00020000,timestamp=2019-10-02T00:07:04.259+0000) > > predator + ghost malphite. he's a champ that can 1v7. no other champ can do that. or a yi. full crit makes him alpha, then he automatically autos, causing a one shot. then theres perma stun champs or juggarnauts that do dmg. then you have useless champs like kennen, nidalee, j4, etc or champs that are too squishy. careful when you say "any champ can beat any other champ." also, careful about the word "teamwork." this is PBE we're talking about, where it's more toxic than the actual servers. When is J4 useless? Also, the massive aoe stun from kennen (which, due to urf, is stupidly low CD) which basically makes team fights an iffy proposition vs a kennen team. With Nid, you can super poke out letting your lane partner soak up the cs and get way ahead putting the enemies behind. Speaking of J4...I would take a good j4 over a good yi any day.
: ARURF SUCKS
I have seen pretty much any champ beat any other champ. It is less about the champs than it is about the teamwork.
Rioter Comments
: Register for pbe
For clarity: the PBE signup link is this: https://pbesignup.na.leagueoflegends.com/en_US/pbe To use it, your friend needs to be logged into their live account, since PBE & Live accounts are linked together (meaning a punishment in one, could cause a punishment in the other as well). Remember, the Live account must be in any region, except Korea, and must be Honor Level 3.
: Could dodge timers be disabled until this bug is fixed?
> [{quoted}](name=DaCookiez,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=trzvKlAc,comment-id=0016000d,timestamp=2019-10-01T02:17:48.816+0000) > > Could dodge timers be disabled until this bug is fixed? A reasonable request. Perhaps even just clearing leaver buster penalties and resetting the leave status for all PBE accounts that have played in the past two weeks.
: any update? It's still going on for me. Had to play on NA {{sticker:sg-zephyr}}
> [{quoted}](name=IceJustice,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=trzvKlAc,comment-id=001600030005,timestamp=2019-10-01T01:56:58.168+0000) > > any update? It's still going on for me. Had to play on NA {{sticker:sg-zephyr}} Ewww, that's gross
: Looking back into it! Appears this didn't work for all. {{sticker:zombie-nunu-bummed}}
> [{quoted}](name=Riot Porosite,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=trzvKlAc,comment-id=00160003,timestamp=2019-09-30T22:56:34.744+0000) > > Looking back into it! Appears this didn't work for all. > {{sticker:zombie-nunu-bummed}} You probably already know, but I saw this in my client logs: > 001981.938| ERROR| rcp-be-lol-lobby-team-builder| TB ready check error: methodName=callFailedV1, status=Error: GROUP_NOT_FOUND then, this: > 001981.939| ERROR| Remoting| HTTP Response 500 to POST '/lol-matchmaking/v1/ready-check/accept' Then it boots me saying I dodged. Because of the sporadic nature of success/failure, it seems to be that a few services instances are down/failing, and the load balancer in front of them is not aware (hence forwarding the requests to a broken instance), Just an outsider's thoughts.
: > [{quoted}](name=ModiPBE,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=41P9ybvk,comment-id=0001,timestamp=2019-09-30T21:47:58.635+0000) > > No, I am saying that your attitude of entitlement saying "PBE is broken, I am being cheated out of this" is out of place. > How about you don't forge and misquote people to make yourself look better in the 1st place? How about instead of copy pasting the same bad excuses post to everyone having similar issues and falsifying quotes, you stay on topic? It's about the issue - in it's current state completely broken, so no one can test it atm. Its not about your ego being hurt or anything else.
> [{quoted}](name=lazydot,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=41P9ybvk,comment-id=00010000,timestamp=2019-09-30T23:01:55.013+0000) > > How about you don't forge and misquote people to make yourself look better in the 1st place? > How about instead of copy pasting the same bad excuses post to everyone having similar issues and falsifying quotes, you stay on topic? > > It's about the issue - in it's current state completely broken, so no one can test it atm. Its not about your ego being hurt or anything else. Forge and misquote? I present you (the pot) calling me (the kettle) black: > [{quoted}](name=lazydot,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=41P9ybvk,comment-id=00000000,timestamp=2019-09-30T21:35:09.503+0000) > > ... > "someone else making big mistakes is our excuse to justify breaking everything and not even bother to test basic stuff before deploying it". > ... Follow your own advice, perhaps. But, you are right, it **is** about the issue, and that issue is not: > the absolute core like starting the client and the game should not be entirely broken like that The issue is that they delivered something broken to a **testing** environment. Oh me, oh my, they tested something. This is not production. This is not where money depends on it. This is where they give you the opportunity to participate in the feedback cycle. Acting as if they broke some cardinal rule by putting something broken into the PBE is how I drew the conclusion of your (perceived) entitlement. Funny, it's almost like you drew a similar conclusion about my comment in your first reply --- # tl;dr: PBE is going to be broken from time to time, sometimes to the level that it is unplayable. Riot does not owe you anything for this downtime. Riot does not have to answer to you for this downtime. You are encouraged to report issues. You are also encouraged to search the PBE bugs board _before_ posting, rather than rinse/repeat the same issue as had been reported several times before.
: Timeout after failing to accept match many times because of "accept"-dialog bug
No, I am saying that your attitude of entitlement saying "PBE is broken, I am being cheated out of this" is out of place. Before you say "I never said that", I quote (again): > I understand its beta, but beta is not an early alpha. They don't have to allow anyone access to their test environment. They are doing so to catch issues, exactly like this one, before they get into live.
: Can't accept match
Already a thread: https://boards.pbe.leagueoflegends.com/en/c/bugs/trzvKlAc-game-gets-stuck-on-accept-screen-again . > how is anyone expected to test something when its all "small indie company" all over the PBE I direct you to search for "gmail outage" or "aws outage". If companies worth $800+ billion can have massive outages in **production** I think it's fair to have a much smaller company have a massive problem in a dedicated test server.
: Now can t Accept the match
Already a thread: https://boards.pbe.leagueoflegends.com/en/c/bugs/trzvKlAc-game-gets-stuck-on-accept-screen-again . > WTF is this bugs... cant accept the match urf. now i get 15min ban and going moreee.. fix. hate riot wtf. I direct you to search for "gmail outage" or "aws outage". If companies worth $800+ billion can have massive outages in **production** I think it's fair to have a much smaller company have a massive problem in a dedicated test server.
: More chromas bundles would be nice.
I agree! While I'm happy you can purchase them while in champ select, it would be really nice if they had per-skin bundles & possibly whole-champ bundles. No need to reduce the price even, just make it easier than buying each chroma one---at----a----time.
: Yup... You guessed it right! Match accepting problems
Already a thread: https://boards.pbe.leagueoflegends.com/en/c/bugs/trzvKlAc-game-gets-stuck-on-accept-screen-again . > fix your game RIOT and stop being a freaking Indie Company otherwise like some other users have already said, how the hell are we supposed to test your game for you if you don't let us join the damn game?! I direct you to search for "gmail outage" or "aws outage". If companies worth $800+ billion can have massive outages in **production** I think it's fair to have a much smaller company have a massive problem in a dedicated test server.
: Timeout after failing to accept match many times because of "accept"-dialog bug
Already a thread: https://boards.pbe.leagueoflegends.com/en/c/bugs/trzvKlAc-game-gets-stuck-on-accept-screen-again . > I understand its beta, but beta is not an early alpha, the absolute core like starting the client and the game should not be entirely broken like that. I direct you to search for "gmail outage" or "aws outage". If companies worth $800+ billion can have massive outages in **production** I think it's fair to have a much smaller company have a massive problem in a dedicated test server.
: Agreed. I'm just posting so they know it is happening. Is why I made my own post with a video. But for now, there's nothing more I can do to help them, so I'm off to play some BL3. Good Luck
> [{quoted}](name=Justmenow,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=trzvKlAc,comment-id=000100010000,timestamp=2019-09-30T19:56:55.011+0000) > > Agreed. I'm just posting so they know it is happening. Is why I made my own post with a video. But for now, there's nothing more I can do to help them, so I'm off to play some BL3. Good Luck Yep, your post was exactly the kind of post developers need. As a developer (not affiliated with Riot), I want to say thank you for posting the information, and being understanding. {{sticker:slayer-pantheon-thumbs}}
: Yeah, okay, so what youre telling me is. They don't ship updates to their private test server, they just ship it to the PBE and hope something breaks? Cause this seems to be a pretty basic feature, and how they manged to break it is beyond me.
> [{quoted}](name=oma wa mou,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=trzvKlAc,comment-id=000100010001,timestamp=2019-09-30T19:57:05.323+0000) > > Yeah, okay, so what youre telling me is. They don't ship updates to their private test server, they just ship it to the PBE and hope something breaks? Cause this seems to be a pretty basic feature, and how they manged to break it is beyond me. What I'm saying is that there should be no expectation of stability. Hell, shit breaks in production all the time in every organization that uses software. Don't believe me? Do a search for "gmail outage". If it can happen to the largest organizations in their **production** environment, why is it so egregious when it happens to a much smaller company in their designated **testing** environment?
: However it would still be nice to know when they are doing stuff like this that way we can plan around it OR at least know that it's ACTUALLY them and not just the code breaking again and that they are going to fix it. Additionally, if they are going to intentionally see how something like that would react, it would be nice to at least temporarily disable the leaver buster that way people can continue to "test" the match accept feature instead of either completely ignoring PBE or getting larger and larger punishments. Just thoughts for food.
> [{quoted}](name=0x2A,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=trzvKlAc,comment-id=000100010002,timestamp=2019-09-30T20:44:45.964+0000) > > However it would still be nice to know when they are doing stuff like this that way we can plan around it OR at least know that it's ACTUALLY them and not just the code breaking again and that they are going to fix it. > > Additionally, if they are going to intentionally see how something like that would react, it would be nice to at least temporarily disable the leaver buster that way people can continue to "test" the match accept feature instead of either completely ignoring PBE or getting larger and larger punishments. > > Just thoughts for food. Sometimes you don't know that what they are changing will break something else, until you see it in the wild. I have had plenty of code work perfectly in my unit tests, and on my local environment, then have some configuration difference between the local & the integration server cause a massive problem, which I didn't foresee.
: How the actual fuck, do they manage to FUCK up this badly? Seriously!?
> [{quoted}](name=oma wa mou,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=trzvKlAc,comment-id=0001,timestamp=2019-09-30T19:40:51.848+0000) > > How the actual fuck, do they manage to FUCK up this badly? Seriously!? Ok, people, you need to understand, you are in a BETA environment. The point of doing this is to TEST things. As a software development professional myself, I fully understand that anything and everything can (and probably will) break at some point or another. It is part of the process. There are plenty of times where I have had to break something, making a piece of software worse, just to test fixes for a different issue. The fact that you decided to play here, on a testing environment, means you should expect things to be broken frequently. You are not here to play the new game mode, or collect all the skins. The fact that they grant you RP/BE to buy skins is a _privilege_ of playing on PBE.
: [GAME BREAKING][URF] Champion cannon bug
This has actually been a problem since the inception of the cannot. It is not new, but it is rarely used/effective.
: IT HAS BEEN 3 DAYS AND STILL CAN NOT PLAY ANY GAMEMODE ON PBE !!!!!!!!!!!
If you are seeing the same problem as [this thread](https://boards.pbe.leagueoflegends.com/en/c/bugs/kbji8l1M-my-client-does-not-start-the-match), please upvote that one, as it already has several of us who have the same issue.
: I have been reconnecting and cannot enter the loading game! ?
Add comments/upvotes to [this thread](https://boards.pbe.leagueoflegends.com/en/c/bugs/kbji8l1M-my-client-does-not-start-the-match). It has a larger collection of people with the same issue.
: Update all. This maintenance _should_ fix the bugsplat on login for the new client. If you were encountering this issue yesterday and didn't bypass by deleting the Riot Client folder, please check again after maintenance and reply to this comment if it worked or not, but especially if you're still bugsplatting! If you did do the workaround for the bugsplat no worries! Keep on testing.
> [{quoted}](name=Riot Porosite,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=A9ynynbG,comment-id=002e,timestamp=2019-09-25T18:39:20.823+0000) > > Update all. This maintenance _should_ fix the bugsplat on login for the new client. If you were encountering this issue yesterday and didn't bypass by deleting the Riot Client folder, please check again after maintenance and reply to this comment if it worked or not, but especially if you're still bugsplatting! > > If you did do the workaround for the bugsplat no worries! Keep on testing. Have you seen [this thread](https://boards.pbe.leagueoflegends.com/en/c/bugs/kbji8l1M-my-client-does-not-start-the-match)? It is a different issue, affecting several of us. It is not a bugsplat, but it is preventing us from getting into a game at all. For me, it started around the same time as the bugsplat issue, so my guess is the same PBE update caused that issue as well.
: Win10 system updates appear infinite reconnection
Here's a larger thread about this topic, upvote this one: https://boards.pbe.leagueoflegends.com/en/c/bugs/kbji8l1M-my-client-does-not-start-the-match
: Not enter on all modes match
A larger thread can be found here: https://boards.pbe.leagueoflegends.com/en/c/bugs/kbji8l1M-my-client-does-not-start-the-match
: My client does not start the match
More details for any Rioter, this is the output from **[timestamp]_LeagurClient.log** for one click of the 'Reconnect' button for a practice tool game that did not launch for me: > 000280.354| ALWAYS| rcp-be-lol-gameflow| Attempting to reconnect to existing game > 000280.354| ALWAYS| rcp-be-lol-gameflow| Entering game flow > 000280.354| ALWAYS| rcp-be-lol-gameflow| Game flow is already active. > 000280.354| ALWAYS| rcp-be-lol-gameflow| Launching game client > 000280.354| ALWAYS| rcp-be-lol-gameflow| GAMEFLOW_EVENT.GAME_STARTED > 000280.354| ALWAYS| rcp-be-lol-gameflow| Gameflow: exiting state 'ReconnectAvailable' > 000280.354| ALWAYS| rcp-be-lol-gameflow| Gameflow: entering state 'GameStart' > 000280.358| ALWAYS| rcp-be-lol-lobby| lol-lobby: Preparing service proxy request: parties.service.proxy > 000280.365| ALWAYS| rcp-be-lol-user-experience| Deleting affinity. > 000280.366| ALWAYS| rcp-be-lol-chat| chat received game phase: inGame > 000280.366| ALWAYS| rcp-be-lol-chat| chat updating presence, availability: dnd, gameStatus: inGame > 000280.441| ALWAYS| rcp-be-lol-lobby| lol-lobby: Started service proxy request: parties.service.proxy (53d75624-8e3d-834c-a0da-9116b314b634) > 000280.481| ALWAYS| rcp-be-lol-lobby| lol-lobby: Fulfilled service proxy request: 53d75624-8e3d-834c-a0da-9116b314b634 > 000280.502| ALWAYS| rcp-be-lol-gameflow| Game Message Ack'ed. > 000280.503| OKAY| rcp-be-lol-gameflow| Game launch working directory: C:/Riot Games/PBE/Game > 000280.503| OKAY| rcp-be-lol-gameflow| Game client launch exe path: C:/Riot Games/PBE/Game/League of Legends.exe > 000280.503| ALWAYS| rcp-be-lol-gameflow| Game args: 52.37.152.123 5351 ovhIft0X6AGtQ5Cd37rkkQ== 2173877433 -PlayerID=2173877433 -GameID=4322793455 -GameBaseDir=C:/Riot Games/PBE -Region=PBE -Locale=en_US -SkipRads -SkipBuild -EnableCrashpad=2 -EnableLNP -UseNewX3D=1 -UseNewX3DFramebuffers=1 -RiotClientPort=57093 -RiotClientAuthToken=JYUOZaHuuwD3_1FNiYw-2w > 000280.524| ALWAYS| The following message is prepared to be sent to dradis: > Event Name: riot__rclient__event > common.account_id: 2200937358 > common.application_name: LeagueClient > common.client_id: lol > gameflow_phase: 6 > common.application_version: 9.20.290.7446 > common.installation_id: UKhb1A== > common.login_session_id: 7a0fc0c3-4f14-9e41-82c7-c8cf066cad18 > common.locale: en_US > common.os_version_major: 10 > common.machine_id: C6GWZJKYUU+pht3fLAx0RQ== > common.os_edition: , x64 > common.os_platform: Windows > common.os_version_minor: > common.platform_id: PBE1 > common.puuid: 98ed640c-c1f8-5a82-ad64-011c9990d85c > common.region: PBE > common.session_id: af69942a-cf97-6349-af3b-6eaf047935ab > event_name: game_launched > reason: 4 > watch_phase: 0 > 000280.524| ALWAYS| Queued Dradis event to be sent. > 000280.524| ALWAYS| rcp-be-lol-gameflow| Game Client Launched. > 000280.524| ALWAYS| rcp-be-lol-gameflow| GAMEFLOW_EVENT.GAME_LAUNCHED > 000280.524| ALWAYS| rcp-be-lol-gameflow| Gameflow: exiting state 'GameStart' > 000280.524| ALWAYS| rcp-be-lol-gameflow| Gameflow: entering state 'InProgress' > 000280.529| ALWAYS| rcp-be-lol-end-of-game| Game client is now running > 000280.532| ALWAYS| rcp-be-lol-matchmaking| MATCHMAKING_EVENT.GAME_STARTED > 000280.538| ALWAYS| rcp-be-lol-user-experience| Setting affinity to postgame. > 000280.539| ALWAYS| rcp-be-lol-chat| chat received game phase: inGame > 000280.539| ALWAYS| rcp-be-lol-chat| chat updating presence, availability: dnd, gameStatus: inGame > 000280.553| ALWAYS| rcp-be-lol-chat| chat received game phase: inGame > 000280.553| ALWAYS| rcp-be-lol-chat| chat updating presence, availability: dnd, gameStatus: inGame > 000280.554| OKAY| rcp-be-lol-gameflow| mGameflowSession.gameClient updated: running, not visible > 000280.554| ALWAYS| rcp-be-lol-gameflow| Setting gameflow patcher lock to 1569460962066. > 000280.572| ALWAYS| Ux state set to MinimizeAll. > 000280.667| ALWAYS| rcp-be-lol-chat| chat received spectating: false > 000280.667| ALWAYS| rcp-be-lol-chat| chat updating presence, availability: dnd, gameStatus: inGame > 000280.707| ALWAYS| rcp-be-lol-gameflow| Client is no longer running. > 000280.732| ALWAYS| The following message is prepared to be sent to dradis: > Event Name: riot__rclient__rcp-be-lol-gameflow.cpu-use-in-game > common.account_id: 2200937358 > common.application_name: LeagueClient > common.client_id: lol > common.application_version: 9.20.290.7446 > common.installation_id: UKhb1A== > common.login_session_id: 7a0fc0c3-4f14-9e41-82c7-c8cf066cad18 > common.locale: en_US > common.os_version_major: 10 > common.machine_id: C6GWZJKYUU+pht3fLAx0RQ== > common.os_edition: , x64 > common.os_platform: Windows > common.os_version_minor: > common.platform_id: PBE1 > common.puuid: 98ed640c-c1f8-5a82-ad64-011c9990d85c > common.region: PBE > common.session_id: af69942a-cf97-6349-af3b-6eaf047935ab > foundation: 30.000000 > system: 60.000000 > timeRatio: 1.070374 > uxChildren: 120.000000 > ux: 20.000000 > 000280.732| ALWAYS| Queued Dradis event to be sent. > 000280.733| ALWAYS| rcp-be-lol-gameflow| GAMEFLOW_EVENT.RECONNECT_AVAILABLE > 000280.733| ALWAYS| rcp-be-lol-gameflow| Gameflow: exiting state 'InProgress' > 000280.733| ALWAYS| rcp-be-lol-gameflow| Gameflow: entering state 'ReconnectAvailable' > 000280.736| ALWAYS| rcp-be-lol-end-of-game| Game client is now not running > 000280.745| ALWAYS| rcp-be-lol-user-experience| Deleting affinity. > 000280.746| ALWAYS| Ux state set to ShowMain. > 000280.746| ALWAYS| rcp-be-lol-chat| chat received game phase: inGame > 000280.746| ALWAYS| rcp-be-lol-chat| chat updating presence, availability: dnd, gameStatus: inGame > 000280.878| ALWAYS| The following message is prepared to be sent to dradis: > Event Name: riot__rclient__player_preferences__game_settings > common.account_id: 2200937358 > common.application_name: LeagueClient > common.client_id: lol > common.application_version: 9.20.290.7446 > common.installation_id: UKhb1A== > common.login_session_id: 7a0fc0c3-4f14-9e41-82c7-c8cf066cad18 > common.locale: en_US > common.os_version_major: 10 > common.machine_id: C6GWZJKYUU+pht3fLAx0RQ== > common.os_edition: , x64 > common.os_platform: Windows > common.os_version_minor: > common.platform_id: PBE1 > details: 200 > common.puuid: 98ed640c-c1f8-5a82-ad64-011c9990d85c > common.region: PBE > common.session_id: af69942a-cf97-6349-af3b-6eaf047935ab > retries: 1 > type: SAVE_SUCCESS > latency: 114 > tokenLen: 703 > status: SUCCESS > 000280.878| ALWAYS| Queued Dradis event to be sent. > 000280.895| ALWAYS| rcp-be-lol-chat| chat received game phase: inGame > 000280.895| ALWAYS| rcp-be-lol-chat| chat updating presence, availability: dnd, gameStatus: inGame > 000280.895| OKAY| rcp-be-lol-gameflow| mGameflowSession.gameClient updated: not running, not visible
: My client does not start the match
Also, I just tried to start a practice tool game in PBE, that also failed, so it's not game-mode specific.
: Yeah, let us just hope everything gets fixed!
> [{quoted}](name=MeepiePBE,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=A9ynynbG,comment-id=000f0008000000000000,timestamp=2019-09-25T18:39:17.799+0000) > > Yeah, let us just hope everything gets fixed! Unfortunately, it did not, and I'm not the only one: https://boards.pbe.leagueoflegends.com/en/c/bugs/kbji8l1M-my-client-does-not-start-the-match Hopefully they see this other thread. {{sticker:cass-cry}}
: Reconnect stuck loop
A bigger thread opened hours ago: https://boards.pbe.leagueoflegends.com/en/c/bugs/kbji8l1M-my-client-does-not-start-the-match
: My client does not start the match
I will say, I'm glad I'm not the only one. This started happening for me at the same time that the Login Bugsplat started happening.
: Who knows, I mean I did exactly what someone else said, I posted it in steps to help others. I havent had any issues since following those steps. I been playing a couple games now with no problems.
> [{quoted}](name=MeepiePBE,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=A9ynynbG,comment-id=000f00080000,timestamp=2019-09-25T17:24:52.536+0000) > > Who knows, I mean I did exactly what someone else said, I posted it in steps to help others. I havent had any issues since following those steps. I been playing a couple games now with no problems. Yeah, I'm gonna wait out the next update (which looks like it is in progress right now) rather than subject my teammates to a 4v5 situation.
: I choose this one as the designated thread for the new bugsplats people are encountering with 9.20 hitting PBE! First apologies the transition to 9.20 wasn't as stable as anyone would like! We'll dig into these bugsplats first thing in the morning. If you're encountering bugsplats, sit tight and we'll have a fix for you as soon as we can. {{sticker:slayer-pantheon-thumbs}}
> [{quoted}](name=Riot Porosite,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=A9ynynbG,comment-id=000f,timestamp=2019-09-25T06:40:58.388+0000) > > I choose this one as the designated thread for the new bugsplats people are encountering with 9.20 hitting PBE! > > First apologies the transition to 9.20 wasn't as stable as anyone would like! We'll dig into these bugsplats first thing in the morning. If you're encountering bugsplats, sit tight and we'll have a fix for you as soon as we can. > > {{sticker:slayer-pantheon-thumbs}} While following the comments in this thread can help fix the "Bugsplat on LoL client load", it does not fix the issue I am seeing. My issue has been preventing me from joining a game at all. When I try to start a game, it just shows the client with "Game in Progress" with the "Reconnect" button. When clicked, it tries to load the game, fails, and brings me back to the same screen. After trying to reconnect several times, I opted to restart the client entirely, causing the bugsplat mentioned in this thread. The problem persists for around 30 minutes, which is the typical length of an URF game, so my best guess is that it is not solely the Riot Client and/or League Client, but also has some connection to the game itself.
: Had you checked your match history recently? I remember I used to get names from peoples match history I'd checked (including mine), a while back, sometimes pop up on post game lobby, even the stats for kda/items etc too sometimes, been a while since I'd seen that though.
> [{quoted}](name=Kaisa My Jam,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=RVEwrPPy,comment-id=0001,timestamp=2019-09-25T08:07:43.176+0000) > > Had you checked your match history recently? > I remember I used to get names from peoples match history I'd checked (including mine), a while back, sometimes pop up on post game lobby, even the stats for kda/items etc too sometimes, been a while since I'd seen that though. I had not played a game with someone named "You" that I can remember, but no, I did not check match history recently.
Rioter Comments
: buff the nasus large minion and monster stacks a bit i barely get 400 stacks on a great 20 minute game, you only stack well with a glass cannon build please look into this if possible i'd greatly appreciate it.
> [{quoted}](name=D Bolts E,realm=PBE,application-id=AYQh7p7O,discussion-id=mA4Lz9ER,comment-id=0026,timestamp=2019-09-18T21:42:45.023+0000) > > buff the nasus large minion and monster stacks a bit i barely get 400 stacks on a great 20 minute game, you only stack well with a glass cannon build please look into this if possible i'd greatly appreciate it. I have had several Nasus (what is the plural of "Nasus" anyway?) in my games that went tank + stacking, and they were monsters. The key is to get a lane partner who is willing to let you stack while they zone out the others. I did this once as Veigar, where all I did was poke & zone, and let him stack. Late game, he was tank Nasus with ~ 700 stacks and I was tank Veigar with ~ 400 stacks. We were unstoppable! While you aren't incredibly likely to get that kind of treatment, having your lane partner work with you is the most important way to get stacks.
: ARURF Available for Testing!
Suggestion for a change to how re-rolls work (and this could be applied to any random champ mode, like ARAM): Instead of making rolled champion available for others, give it a 3 second timeout, for the original roller to get it back. This may make it more likely that people will use their re-rolls for the benefit of the team, rather than hoarding them for themselves.
: Can't even join queue now when attempting to retry, so it seems to be getting worse for me at least.
> [{quoted}](name=Miásmà,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=KbJTpP3c,comment-id=0009,timestamp=2019-09-12T02:04:33.159+0000) > > Can't even join queue now when attempting to retry, so it seems to be getting worse for me at least. Relog, if you are seeing this. It seems to fix that issue.
: Lol chill out nerd, the IFS was just an example I wrote in order to enhance the following: They don't want to invest money into fixing it. The heads are too busy ordering and giving money in order to create skins which for once they made something good and not something pedoskins. If they wanted to they would have. Live server client is much much more complicated than PBE's client and with way more players. I only see two people here defending them and not actually try to argue with me. Good job, if you don't have to add something to argue with and just spread thin air, don't reply at all. No I won't waste my time opening any thread here just for it to remain un-replied by the apathetic staff of PBE, thanks but no sorry.
> [{quoted}](name=Cowseption,realm=PBE,application-id=A4D2003433C8FCD715185A7264A9CC6FDFAD7FEF,discussion-id=xJRd4hRu,comment-id=00050000000000000000,timestamp=2019-09-11T13:18:18.877+0000) > > Lol chill out nerd, the IFS was just an example I wrote in order to enhance the following: They don't want to invest money into fixing it. The heads are too busy ordering and giving money in order to create skins which for once they made something good and not something pedoskins. > If they wanted to they would have. > Live server client is much much more complicated than PBE's client and with way more players. > I only see two people here defending them and not actually try to argue with me. Good job, if you don't have to add something to argue with and just spread thin air, don't reply at all. > No I won't waste my time opening any thread here just for it to remain un-replied by the apathetic staff of PBE, thanks but no sorry. Sick burn, it was a good one. {{sticker:slayer-jinx-unamused}} Maybe you should take that chill pill yourself. The PBE client is (more than likely, almost certainly) the exact same *code* as what goes into live in the next patch. Otherwise, what would be the point of even having the PBE client? The live client is not "much more complicated", as you say. You say no one has argued with you? You made a baseless claim. I refuted it with a logical argument. Your move.
Show more

ModiPBE

Level 180 (PBE)
Lifetime Upvotes
Create a Discussion