RCVolus / lol-pick-ban-ui

Web-Based UI to display the league of legends champ select in esports tournaments.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Error when starting backend

M-BAXI opened this issue · comments

I'm very sorry that it was #138 closed due to my wrong operation.
After I use the instructions you #138 provided, the content displayed on the backend is as shown in the figure
微信图片_20220506072948

Or is there a manual way to modify the port and password in leagueclient connected? It seems that in the version update in November 2021, the lockfile is no longer used to store tokens and ports, but the running parameters of "leagueclientux. Exe" need to be taken out. Run "wmic process where caption ='leagueclientux. Exe 'get commandline" in CMD.It is not the same as token in the figure.
屏幕截图 2022-05-06 121848_WPS图片

No worries :)
Unfortunately there is no easy way to set this manually. We will look into adding an option with this workaround for the LCU connection, but I can't give you a timeline on how long this will take.

No worries :) Unfortunately there is no easy way to set this manually. We will look into adding an option with this workaround for the LCU connection, but I can't give you a timeline on how long this will take.

Never mind, I can wait for you. If you need help due to regional problems during the repair process, I can help you as much as possible. If you can, please inform me after the repair is completed

Would you be able to download the newest version and try it again, please?

Would you be able to download the newest version and try it again, please?

Unfortunately, I tried to run the new version at the first time after receiving the message, and the same error still occurred when I ensured that both PowerShell and the game client were running as administrators
屏幕截图 2022-05-06 222854

Would you be able to download the newest version and try it again, please?

I'm glad I'll tell you a good news! I found a new lockfile file that follows the launch of the game client, and copied the contents to the abandoned lockfile. Fortunately, the back end is running normally, which may be that you need to modify the path to obtain the lockfile file. I can see in the web link that the program is working very hard to obtain the information of the client. However, there is a new problem. As in #113 and #114, "waiting for league client to connect" appears in the back-end content. I tried the solving instructions in #113 and #114, but they didn't seem to work. I used "NPM start - debug - experimentalconnector - leaguepath" C: \ riot \ riot games \ League of Legends "to prompt" not connected to LCU, but distributed to get data ", and" NPM start - debug - experimentalconnector "to prompt" ready connected, Not checking ". Is there another solution? I will continue to try to change the path in the first instruction and try to repair it.
屏幕截图 2022-05-06 232413

As far as I can tell, the backend successfully connected with the alternative lockfile. Do you get events and the UI popping up when entering a champ select?

We will look into adding an option to connect with this alternative method once we find time – for now manually changing the lockfile contents might be a workaround.

A possible fix for this should be implemented in the fix-#141 branch. Could you try downloading the tool from the branch and try if this version can connect to your client?

A possible fix for this should be implemented in the fix-#141 branch. Could you try downloading the tool from the branch and try if this version can connect to your client?

I tried to use the tool in #141 branch to link with the alliance client, and it reported a new error, unable to verify the first certificate
屏幕截图 2022-05-11 215716

Sorry, I didn't mention that this should be without the experimental connector (that one still uses the old method).
Could you try with just npm start?

Sorry, I didn't mention that this should be without the experimental connector (that one still uses the old method). Could you try with just npm start?

I'm sorry I didn't understand clearly before After trying NPM start again, it seems to be the correct link? but it's puzzling that the UI still doesn't display correctly on the web page
屏幕截图 2022-05-11 223857

The connection looks good :) The champ select not showing up is probably due to weird PowerShell behavior. Could you try again and make sure nothing is highlighted in PowerShell and you see the small line blinking?
image
Pressing enter a few times in the PowerShell window also clears that hangup of the console.

The connection looks good :) The champ select not showing up is probably due to weird PowerShell behavior. Could you try again and make sure nothing is highlighted in PowerShell and you see the small line blinking?

I tried the link again. It seemed that it was correctly linked, and I saw the small bar flashing. However, after starting the front end and the web page, the same problem was still displayed on the console platform of the web page, and I didn't see any UI displayed
(1HNS N6WDLGG0SPC 3 N
LD{YE1JW)ZAR8H)0W0W5F

ok to test out if the lcu API works for you as it does for us, could you please start the backend to get the password and port. after you started that please start a champ select then. Then go to https://127.0.0.1:PORT/lol-champ-select/v1/session and replace PORT with the port from the console. If you get asked for login details type in 'riot' as username and the password you got from the console.
Please send us the content that is displayed to you on the website.

ok to test out if the lcu API works for you as it does for us, could you please start the backend to get the password and port. after you started that please start a champ select then. Then go to https://127.0.0.1:PORT/lol-champ-select/v1/session and replace PORT with the port from the console. If you get asked for login details type in 'riot' as username and the password you got from the console. Please send us the content that is displayed to you on the website.

Do you need this screenshot? It looks as if it's working properly
屏幕截图 2022-05-12 235624

Could you please provide the context as text instead of a screenshot?

Could you please provide the context as text instead of a screenshot?

Sorry, the text is as follows:

{"actions":[[{"actorCellId":1,"championId":33,"completed":true,"id":1,"isAllyAction":true,"isInProgress":false,"pickTurn":1,"type":"pick"},{"actorCellId":2,"championId":30,"completed":true,"id":2,"isAllyAction":true,"isInProgress":false,"pickTurn":1,"type":"pick"},{"actorCellId":3,"championId":81,"completed":true,"id":3,"isAllyAction":true,"isInProgress":false,"pickTurn":1,"type":"pick"},{"actorCellId":4,"championId":98,"completed":true,"id":4,"isAllyAction":true,"isInProgress":false,"pickTurn":1,"type":"pick"},{"actorCellId":5,"championId":102,"completed":true,"id":5,"isAllyAction":false,"isInProgress":false,"pickTurn":1,"type":"pick"},{"actorCellId":6,"championId":81,"completed":true,"id":6,"isAllyAction":false,"isInProgress":false,"pickTurn":1,"type":"pick"},{"actorCellId":7,"championId":143,"completed":true,"id":7,"isAllyAction":false,"isInProgress":false,"pickTurn":1,"type":"pick"},{"actorCellId":8,"championId":99,"completed":true,"id":8,"isAllyAction":false,"isInProgress":false,"pickTurn":1,"type":"pick"},{"actorCellId":9,"championId":62,"completed":true,"id":9,"isAllyAction":false,"isInProgress":false,"pickTurn":1,"type":"pick"},{"actorCellId":0,"championId":67,"completed":true,"id":10,"isAllyAction":true,"isInProgress":false,"pickTurn":1,"type":"ban"}],[{"actorCellId":0,"championId":34,"completed":true,"id":11,"isAllyAction":true,"isInProgress":false,"pickTurn":3,"type":"ban"}],[{"actorCellId":0,"championId":35,"completed":true,"id":12,"isAllyAction":true,"isInProgress":false,"pickTurn":5,"type":"ban"}],[{"actorCellId":0,"championId":22,"completed":false,"id":13,"isAllyAction":true,"isInProgress":true,"pickTurn":1,"type":"pick"}]],"allowBattleBoost":false,"allowDuplicatePicks":false,"allowLockedEvents":false,"allowRerolling":false,"allowSkinSelection":true,"bans":{"myTeamBans":[67,34,35],"numBans":6,"theirTeamBans":[]},"benchChampionIds":[],"benchEnabled":false,"boostableSkinCount":1,"chatDetails":{"chatRoomName":"c1~a2cd984548b04b342113ee1590895f84a2aeed80@sec.pvp.net","chatRoomPassword":"rMu2n5BzHDNLEkiL"},"counter":-1,"entitledFeatureState":{"additionalRerolls":0,"unlockedSkinIds":[]},"gameId":0,"hasSimultaneousBans":false,"hasSimultaneousPicks":false,"isCustomGame":true,"isSpectating":false,"localPlayerCellId":0,"lockedEventIndex":-1,"myTeam":[{"assignedPosition":"","cellId":0,"championId":22,"championPickIntent":0,"entitledFeatureType":"","selectedSkinId":22000,"spell1Id":3,"spell2Id":6,"summonerId":2856311816612416,"team":1,"wardSkinId":0},{"assignedPosition":"","cellId":1,"championId":33,"championPickIntent":0,"entitledFeatureType":"","selectedSkinId":33000,"spell1Id":18446744073709551615,"spell2Id":18446744073709551615,"summonerId":0,"team":1,"wardSkinId":-1},{"assignedPosition":"","cellId":2,"championId":30,"championPickIntent":0,"entitledFeatureType":"","selectedSkinId":30000,"spell1Id":18446744073709551615,"spell2Id":18446744073709551615,"summonerId":0,"team":1,"wardSkinId":-1},{"assignedPosition":"","cellId":3,"championId":81,"championPickIntent":0,"entitledFeatureType":"","selectedSkinId":81000,"spell1Id":18446744073709551615,"spell2Id":18446744073709551615,"summonerId":0,"team":1,"wardSkinId":-1},{"assignedPosition":"","cellId":4,"championId":98,"championPickIntent":0,"entitledFeatureType":"","selectedSkinId":98000,"spell1Id":18446744073709551615,"spell2Id":18446744073709551615,"summonerId":0,"team":1,"wardSkinId":-1}],"recoveryCounter":0,"rerollsRemaining":0,"skipChampionSelect":false,"theirTeam":[{"assignedPosition":"","cellId":5,"championId":102,"championPickIntent":0,"entitledFeatureType":"","selectedSkinId":102000,"spell1Id":0,"spell2Id":0,"summonerId":0,"team":2,"wardSkinId":-1},{"assignedPosition":"","cellId":6,"championId":81,"championPickIntent":0,"entitledFeatureType":"","selectedSkinId":81000,"spell1Id":0,"spell2Id":0,"summonerId":0,"team":2,"wardSkinId":-1},{"assignedPosition":"","cellId":7,"championId":143,"championPickIntent":0,"entitledFeatureType":"","selectedSkinId":143000,"spell1Id":0,"spell2Id":0,"summonerId":0,"team":2,"wardSkinId":-1},{"assignedPosition":"","cellId":8,"championId":99,"championPickIntent":0,"entitledFeatureType":"","selectedSkinId":99000,"spell1Id":0,"spell2Id":0,"summonerId":0,"team":2,"wardSkinId":-1},{"assignedPosition":"","cellId":9,"championId":62,"championPickIntent":0,"entitledFeatureType":"","selectedSkinId":62000,"spell1Id":0,"spell2Id":0,"summonerId":0,"team":2,"wardSkinId":-1}],"timer":{"adjustedTimeLeftInPhase":36203,"internalNowInEpochMs":1652371185593,"isInfinite":false,"phase":"BAN_PICK","totalTimeInPhase":37437},"trades":[{"cellId":1,"id":101,"state":"INVALID"},{"cellId":2,"id":102,"state":"INVALID"},{"cellId":3,"id":103,"state":"INVALID"},{"cellId":4,"id":104,"state":"INVALID"}]}

Ok, this looks completely fine, all the info is present as expected. Could you try starting the backend with this command to test if the frontend works as expected? npm start -- --data ../recordings/tournament-draft

And if that's no use either, could you please tell us which node version you are using? just use node -v.
Aswell please please go into the layouts/layout-volu-europe folder and do an npm ci and then npm startagain.

Ok, this looks completely fine, all the info is present as expected. Could you try starting the backend with this command to test if the frontend works as expected? npm start -- --data ../recordings/tournament-draft

After using this command, I can see the test UI running normally on the web page! This is the first time I have seen its true face on my computer (/(°∞°))
屏幕截图 2022-05-13 003722

And if that's no use either, could you please tell us which node version you are using? just use node -v. Aswell please please go into the layouts/layout-volu-europe folder and do an npm ci and then npm startagain.

I tried NPM Ci and NPM start again, but it still doesn't work properly. My node version is V16.7.0, maybe my node version is wrong?

No, this is the node version we test/develop on.
In theory, everything looks alright :(
Could you try running the new connector with the debug flag? (npm start -- --debug) This might give us some more insight into whatever is still going wrong

No, this is the node version we test/develop on. In theory, everything looks alright :( Could you try running the new connector with the debug flag? (npm start -- --debug) This might give us some more insight into whatever is still going wrong

The back-end operation looks very good, but it is very strange that the status of variables not queried is always displayed on the page :( In the previous test instructions, I noticed that the value of the variable champselectactive is true. However, during the formal run, the value of the variable becomes false. Is this the problem?

屏幕截图 2022-05-18 020100

屏幕截图 2022-05-18 020924

Just to make sure we're not chasing any ghosts:
In which order are you starting things to test? I'd recommend starting League Client -> Backend -> Frontend -> Champ select

In theory, champSelectActive should flip to true as soon as the session endpoint returns any data (which we have confirmed it does), which is why we are confused :(
Do you see any debug/info entries in the console when starting different champ selects (e.g. practice tool, custom game, as spectator)?

Just to make sure we're not chasing any ghosts: In which order are you starting things to test? I'd recommend starting League Client -> Backend -> Frontend -> Champ select

In theory, champSelectActive should flip to true as soon as the session endpoint returns any data (which we have confirmed it does), which is why we are confused :( Do you see any debug/info entries in the console when starting different champ selects (e.g. practice tool, custom game, as spectator)?

I can't see anything. I tried it again according to the process you suggested, and it didn't work. If it is convenient for you to provide your email to me, I can record a video of the starting process to you. As for reading the returned data of the session endpoint, will it be caused by the same reading error as the previous lockfile? For example, the client does return some values, but the back-end read path deviates.

Just to make sure we're not chasing any ghosts: In which order are you starting things to test? I'd recommend starting League Client -> Backend -> Frontend -> Champ select

In theory, champSelectActive should flip to true as soon as the session endpoint returns any data (which we have confirmed it does), which is why we are confused :( Do you see any debug/info entries in the console when starting different champ selects (e.g. practice tool, custom game, as spectator)?

Good news! I tried to download and install the riot client to run the league of legends. Based on the riot client, the UI successfully ran on the web! Obviously, the front-end and back-end are normal, and the problem appears on Tencent client. However, I can't find out the difference between the two clients. Maybe you can help adapt the back end to Tencent client when you are free. After all, the riot client does not support servers in China. I have to run the UI with more than 300 Ping, which is very difficult. So that I can't hold a very formal competition among my friends. Thank you very much for your technical support

We gonna put it on the list of stuff to improve and fix, but pls be aware that this may take a bit for us to figure out.