Rapidly swapping loadouts apparently could crash lobbies, sending everyone back to orbit.

The & is the html escape code for an ampersand (&) symbol, which is used to separate query params in a url – it appears like this has been re-encoded so the single & in the URL becomes & by something breaking the link. If you change all of the &s to $ it works. it’s not really an “amp” link in the “Google Amp” meaning.

Also after posting this comment, it appears to be Lenny’s url encoding, I think I’ve fixed it but if not, remove the amp; from the 3 sections of the url you see it and it’ll work

Sure, they obviously are dropping the ball here, just trying to explain what they might mean by “thoroughly tested” and why it’s not succeeding

This is all assumption from me, but I think a lot of testing would likely be diagnostic machines and specialized testing – not actually playing games. I would assume it’s something like plugging in, confirming the parts all meet spec after whatever the refurb is. That spec is probably more around frequencies, power use, temperatures.

Obviously that’s not good enough if they’re sending out these clearly broken refurbs.

All just my opinion/feelings on this shit.

The problems have been building since last year. Plunder and Seraph were less stable and more buggy. Plunder was kinda panned as a bad season by some, but between a Showcase promising us features we’d been wanting for years (in-game Loadouts, in-game LFG, a renewed focus on the ritual playlists, probably more I’m forgetting) and Seraph’s awesome story and (imo) fun missions, some hype came back for a lot of us.

Lightfall itself was a mixed bag, but they eventually made progress on the stability issues (credit where it’s due, shit is a lot more stable for me). It had story issues, but they weren’t WORSE than previous story issues imo, just a regression. It wasn’t a GREAT place, but if they fixed stability it would be ok.

Then the SotG comes out, which says (loosely translated) “Stop asking us to make more PVP/Gambit maps, we’re never gonna do it like you want because it wouldn’t make us enough money. Also no more free armor, because y’all didn’t appreciate our basic ass armor sets as much as the ones that make you into a fucking t-rex, just pay up piggies”

If they had not said anything, it would’ve been better than posting a “We, a company purchased for billions of dollars, can’t do the #1 thing our fanbase is asking for because it wouldn’t make us enough money”.

There is some good news in there, I guess. Favoriting shaders is the kinda basic QoL stuff we should’ve seen years ago when they redid shaders, but better late than never.

The obvious:

1. Stop airing a single women’s match every show. IMO the TV titles show be getting defended every other week each, and it shouldn’t count as the women’s match when the TBS champ has a match.
2. Give them more build than one woman giving an interview and another showing up to randomly challenge her. The slowest improvement on the planet here.
3. Don’t stall 1 of the 2 belts for a year waiting for a single person to come back from injury, no matter how good she is.

The more controversial:

1. Firm up some larger factions and brew up a big ol faction war. It’s a great way to restart/kickstart the division imo, since so much is completely uninvolved. TFM TK keeps toying with something like this and then chickening out
2. Push this into giving the women one of the marquee matches, Blood n Guts or Anarchy in the Arena or Casino Battle Royale or something that gets the big name on the posters and all the photo slots. Actually let them headline some shit
3. Don’t bother with any more belts atm, there’s already 2 we rarely see.

If I’ve learned one thing from the Yakuza games, it’s that land in Japan is precious and you gotta build on it now, no matter what.

As long as tools to unclip the shell aren’t consider specialized, I think almost all existing handhelds are gonna meet the actual requirements here - they just have to be user replaceable, not use swappable, without the use of specialized tools or thermal energy. If you can unscrew it, disconnect the old battery and connect the new one, it complies. It’s really only an issue in waterproof devices, where they have to glue everything to seal it.

Obviously, being from England the Blackpool aspect of it is a natural fit

I think he’s a good fit, but this is kinda like saying “Obviously being from America makes Mox a good fit to join the Hollywood Hunks” lol

Looks like the mount definitions require the :ro (or maybe :rq?) at the end unlike regular docker volumes, that was the issue.

What’s required to map a folder into one of the containers (i.e. retroarch)? I’ve attempted to edit config.toml to include it, but the main wolf container immediately crashes on boot due to interrupt code 11. There’s no other error messages, just a binary stack trace.

The folder exists. I’ve tried directly mounting the host path as well as mounting it into Wolf-Wolf-1 and using the local path, but nothing works. Even perfectly mirrored paths don’t work. Wolf appears to be running as root so I don’t think it’s a permissions error? I can certainly access the folders. They are a locally mounted NFS, but I’ve used this with dozens of containers without issue.