lobby | multiplayer game lobby and JS library | Game Engine library

somewhat sorted by least to most advanced

it doesn't show any errors.

state = action.payload is never a valid operation in an Immer-powered reducer. Immer works by tracking mutations to existing state, or letting you return a new value. state = just changes the local state variable to point to something different, which is neither a mutation nor a return. You need return action.payload.

See the RTK "Writing Reducers with Immer" docs page for further details on this.

For the login action use the below xpaths. This way your code will look neat.

Based on the djs doc's updateOverwrite doesn't have any syntax with an array. Probably you just misunderstood the parameters.

updateOverwrite have the following parameters: (userOrRole,options,reason).

In your case

The second approach is not faster and is harder to implement, as each container is loaded separately and starts to reload after the first load is done. It looks like a nightmare to automate.

I tried Selenium's explicit waits and time.sleep() neither of the approached worked. The code below clicks the button, switches to a new iframe and tries to get containers content. But the content is almost always empty for the reasons described above.

With Selenium I'd use css selector:

driver.find_elements_by_css_selector(".svg--1nrnH")

Update for Selenium: wait for iframe. This is the reason why element could not be found.

Disclaimer: novice here so take this with a pinch of salt. I've provided a solution below that certainly isn't the most elegant but will help you on your way without altering too much of your code.

• We can take the section of class 'fog' out entirely for the time being to simplify things a little.
• We then take the div of class 'absolute-bg' and place this immediately below the body, making sure that all of your remaining elements are within this div and therefore (visually) 'on top' of your background.
• We then set the 'absolute-bg' class to have a lower z-index than everything else (e.g. -1).
• Next, we can take the div of 'fog-container' and give it two simple CSS properties: position: fixed; top: 0;
• This removes the element from the Document flow and places it in a fixed position relative to the browser window, in this case, top: 0.
• Finally, you want to be able to click-through your div 'fog-container' which now sits 'on-top' of everything else when rendered, therefore, we can add these two properties to .fog-container: pointer-events: none; touch-action: none;

Hope this helps. Elegant, no? A push in the right direction? Hopefully!

It seems to be an error when accessing the variable, but without the entire code, it is not viable.