ovinnik

They mark such mods as "DELETED" during the archiving/removal process -- by renaming them, it looks like. I suppose we ought to make of that what we will.

Well, it looks like partial deletions are a thing now. Doesnt really fix anything, but if anyone's keen of retaining access to the mod author forums, here it is.

It's worth considering that they will likely continue to look into ways to 1) enhance Premium benefits and/or 2) worsen the non-Premium experience. Think of the extra hoops non-Premium users now have to jump through in order to download stuff. Who knows what else may follow at this point.

If only one could have mods without those pesky authors getting in the way, ruining everyone's fun.

This won't work in every case and situation I find it exceedingly hard to believe that they won't invent some new rule against "nonsensical" updates if enough authors start doing this.

I would say that I do not think it can get any worse, but I have been proven wrong on that before... Considering that Premium users won't even need to be aware of individual mods featured in a collection, yes, I'd say it can get infinitely worse.

It's a hobby for us. For them it's business. That's where the discrepancy stems from. An opt-out would solve exactly nothing, because we still wouldn't be able to properly retire our own content.

No. Once a list is published it will stay as it is. The creator can create an updated version of the list and users will have the choice of using the original or the updated one. That is reliability. The choice will be up to the user. Let me get this straight. Collections are being implemented for the sake of accessibility. (Ostensibly. Yes, there's also the $$$ aspect.) They're targeted at people who are maybe not tech-savvy, likely short on time, whatever. These same people, who are probably not overly interested in the inner workings of the mods they install, are then encouraged to use outdated but conveniently static content, all in the spirit of engaging even less with the particularities of the stuff they put into their games. That's not reliability; it's errant complacency.

It's my understanding, that the list maker, will also be able to include things like a 'bashed patch', etc. In order for things to play nice. Of course, just like mods, there are going to be lists that have issues, and lists that are really good. And everything in between. It will be up to users to police which are which. As always, read the comments/bug reports before downloading. :D The point being, Collections will require regular upkeep and evaluation of user feedback to be (and stay) in any way reliable. Nexus Mods' approach (and subsequent treatment of authors) does not constitute some inherent utopia for end users, much as some would apparently like to believe that. ...This is in reference to someone's post about "reliability" above; I should've quoted that one.

What reason is there to assume that some cobbled together list of mods is in any way reliable, be it on Steam or here? Will these so-called "curators" provide their own compatibility patches? If not, then simply pointing to outdated and quite possibly bugged versions of mods they've had no hand in making seems like a laughably poor approach to "reliability".

Yes, one or two containing some entertaining speculating.

Was it really? It looks like this has been cooking for nigh on two years, and they're obviously not interested in compromise (or discourse, for that matter). At this point, I'm not sure this could have ended any other way. On topic, authors who leave now, especially non-Bethesda modders, are more or less bound to scatter to the winds. Their profiles are definitely the best place to check up on them, but many (myself included) will probably just stop sharing content altogether. At least for a while.

Ah, yes. Obviously, this is just a particularly riveting chapter in the life of us narcissistic hobbyists slash raging nerds who just so happen to produce the free creative content this site and its user base so very much detest to rely on. It not like we've been given an honest-to-goodness ultimatum with a deadline. That would be quite absurd.

On the off chance that anyone's still reading this: I've been cudgelling both my brains and Frosty Editor in hopes of figuring out how to trigger War Table operations. The only ops with easily accessible plot flags are those further down some quest chains. They can be triggered using a flag found in the AfterActionReportActions of their preceding op. Even so, not all consequtive ops seem to be triggered this way; sometimes their preceding ops don't provide any. Unsurprisingly, initial War Table ops (the first ones in a chain of quests) and standalone ops (those not part of any chain) are even more of a mystery. I've tried various approaches, ranging from questionable edits to WarTableAssets to scouting for potential plot flags in JournalSystem.ebx/.xml. So far, no dice. I've also thought about replacing an existing op with the one I'd like to trigger. That would obviously come with multiple caveats, so I'm not too keen on this. The (likely) bug that sent me down this path is Ser Barris' missing War Table quest chain and subsequent promotion when the player disbands the templars. The related dialogue assets look fine: There are flags for whether one has allied with or disbanded the templars, and for whether or not Barris lives and becomes an agent. These all seem to be set correctly and should work. Maybe I'm missing something obvious. In fact, that would be awesome.

@Tannin42 I'm not asking for Vortex to be made compatible with every conceivable form of mod. I'm fully aware that this would be an impossible (and rather unnecessary) task. What I'm worried about is essentially communication. Vortex is said to support games it doesn't -- or apparently doesn't fully -- support. See, for example, the .override file format for DA:O. Your answer is to tell mod authors to repackage their mods to fit your tool. My concern is with reviewing the way it's being advertised as fully compatible. That's it. So no, this isn't about blaming you, or anyone. I have no stake in this other than hoping for fewer frustrated posts by people dealing with incompatibilities and user error. Though I guess that there will always be that. @Zanderat As an aside, No friendly Fire involves recompiling various combat-related base game scripts. It's completely incompatible not fully compatible with Dain's Fixes. And you definitely don't need ZDF alongside Qwinn's Fixpack.