Aa!

What debacle? The biggest mods out there worked right out of the gate with the next gen update (Sim Settlements 2, for example). Most mods on Nexus have not been updated in years and still work fine

The script extender was updated within hours of the last update, and anyone depending on the script extender was aware that updates would mean they would have to update their se plugins.

All this says for me is that fallout London is likely a mess. And after the way the Frontier turned out, I was not going to get my hopes up until I saw the finished product

Right, that’s really more of a Steam issue than a Bethesda issue. I get why Valve and Bethesda don’t want to provide customer support for old versions, but they don’t have to. People have been figuring out their own problems when using obsolete systems or software for a long time.

I have no issue with Steam pushing the updates and encouraging you to take them, but giving no way to decline is a pretty poor user experience. Especially when we already know they keep old versions on their servers, as people have made guides on how to downgrade with Steam

The mods that weren’t backwards compatible were primarily the ones that depended on the script extender. This was an unsupported executable that expanded on the commands available to the scripts in the mods.

Not to say unsupported is bad, but everyone was well aware that if they depended on the script extender, they would break if the game updated at all. The biggest mods avoided that dependency for exactly this reason, and really didn’t have any trouble. (Sim Settlements still worked the entire time, for example)

And like usual, the community stepped up and updated their unsupported extension quickly, ready for this outcome.

If you made a mod that depends on the script extender and then quit playing the game or supporting your mod, that was a choice you made as a modder. Meanwhile there’s mods that haven’t seen an update in 8 years that continue to work without issue.

The mods that updated for the first update were already updated within 24 hours of the next one.

The only mods that are still broken now are mods that were made and maintained by people who have stopped playing the game some time ago.

And even most of those still work, if they didn’t rely on the script extender

I’m not sure what it is “for” exactly, but in practice it tends to show a lot of brand new posts with zero comments or votes

Eh? I thought we had the date of this update a couple of weeks in advance. I don’t think any more notice would have helped get the mods updated faster when many of the modders just don’t play anymore

It’s a fantastic show. My biggest complaint is a problem we’ve been seeing with a lot of shows lately: not enough episodes in a season. Almost feels like it’s just a half season really.

But when the biggest complaint is that I wanted more, that’s a good sign.

From my limited perspective, it seems like the community wants mod support, but they were mad about some combination of these things:

• Updates and hot fixes don’t come quickly enough
• Updates sometimes break a large number of existing mods
• Not enough new features or explicit support for certain mod features being promised
• Things they promised not working as well as people hoped

This isn’t everything, but it’s what I observed for myself. As you can see, there’s some contradiction here, and some of that comes from different people in the community, and some of it comes from people who just want to be mad at everything

For whatever it’s worth, most people seem to be just enjoying the game and are excited for anything new coming for it.

They already had the Joker as the twist reveal in two games, one of which he was already dead for.

At this point I don’t think they know how to make a game without putting the Joker in it, and I’m not even surprised anymore. If they can retcon Deadshot, they can do whatever the hell they want I guess

A couple of main points:

• You are reading tutorials to help you get it up and running. Most of the time these are designed to walk you through setting things up on a fresh node, and most often just VMs on an isolated (trusted) network. When you are providing a guide to just get someone up and running, the first thing to do is establish a known baseline configuration to start from.
• Kubernetes is a complex distributed application, and as such, the audience is generally expected to be relatively experienced. Meaning if you don’t know how to configure your firewall, people assume you aren’t going through this tutorial.

Still, I feel your pain. When trying to get into these technologies, most people who have done the work are engineers, and we stink at writing documentation. I’m sure you’re familiar with it, we automate the solutions for issues we encounter, and then those tools or automatic configurations fail to make it to the end user.

And I’m probably biased, but don’t use a video guide for this sort of thing. It’s just the wrong medium for a technical tutorial.