Update on Content Management Permissions (Patreon)
Content
As you may know, if you follow Skyrim modding drama at all, Arthmoor and I have been in a bit of a debate over the past few months over what actions Wabbajack should be allowed to perform during installation. Before I continue, I do want to make it clear that the debate is not about what *can* be done by someone on their own machine, but what actions should be enabled or *encouraged* by a tool. Wabbajack has the potential to broker some of the first interactions a gamer has with the modding community, and we shouldn't take that lightly.
So yesterday I sat down with Arthmoor, and Sigurd Stormhand (a member of the USSLEP team) and we agreed to a moderated discussion about how to move forward on these issues. Sigurd did the moderation, and I'm happy to say that we reached an agreement!
The transcript of the chat is available on AFK Mods.
The TL;DR version is that I agreed to implement a permissions system that would allow modders to control how their content is modified (or not) in a modlist created and installed by Wabbajack. I also agreed to switch our 3rd party downloading to a whitelist system where we refuse to download any non-nexus mod that's not in our official whitelist. This information is queried both during creation and installation of the modlist meaning any permission changes are handled retroactively.
This system was quite easy to implement, and is already in the master branch. After we start signing executables it should be fairly failsafe. If the Nexus ever implements a modlist installer with a custom permissions system we can easily update our code to leverage those new APIs.
In other news, I ordered the code signing cert a few days ago, and it turns out that the validation process takes the longest time. So I'm off to find a notary this week so I can prove I actually live where I say I live.
So that's the latest news, and honestly, it feels great to be making some good progress in this area.