#Vortex mod manager archive invalidation mod
#Vortex mod manager archive invalidation Patch
#Vortex mod manager archive invalidation windows 10

They're not the same product at all and development on 10 is not somehow being backported to 8.

#Vortex mod manager archive invalidation windows 10

I see where you're coming from now since you appear to consider Windows 10 to be an iteration of Windows 8.

#Vortex mod manager archive invalidation mod

Both are Mod Organizer, which is why, in the ModOrganizerDevs Discord channel, everyone distinguishes between 'MO1' and 'MO2' rather than just saying 'MO' when the distinction is necessary.ДЄnd when you say 'Fallout 4,' you could mean any version of FO4, which is why it is important (for developers, testers, and sometimes modders) to ask, 'Which version?' Same deal with Windows. You'll note all of MO2's documentation refers to MO2 as Mod Organizer, MO2'sВ splash screen still says 'Mod Organizer,' and MO2's titlebar and About window product name remains 'Mod Organizer' albeit suffixed with the version number 'v2.1.1.' The assembly name is also still ModOrganizer.exe. So, when you say 'MO is abandoned,' it is most certainly not because MO2 is an active project.В MO2 superseded MO1, but 'Mod Organizer' (MO) now refers primarily to MO2. A kingdom evolves with a change in leadership just as an open source project evolves with a change in leadership.Д«ut, on reflection, perhaps we're talking about different things. That does not mean MO is abandoned (i.e., empty, no one home, dilapidated, no longer maintained.) Saying MO is abandoned because MO1 was forked to MO2 is like saying a kingdom is abandoned when the prince takes over from the deposed king. Open source projects have occupants called contributors, and as long as they call that project home, that house will never be abandoned. Just because I don't agree with you doesn't mean I'm impossible either. MO2 isn't simply a minor revision to MO, it's an entirely different project at this point. It is therefore abandoned by every known definition of the term that exists for software.ДЇallout 4 1.5 and 1.7 are not the same thing at all. Better to make it clear there's a change, IMHO.ДЄ program is not a house though, which was my main point. Personally, I think it's better to hard fork abandoned projects unless there's an explicit agreement to stick to the same direction as the previous developer(s), otherwise it becomes like that 'if you replace the brush and the handle, is it still the same broom?' thing, which can negatively impact users due to their (reasonable) expectations of continuity. The software is abandoned (by me) even if it's not abandoned (by others). With open source stuff the distinction is often less important, but if I abandon one of my mods or bits of software, it doesn't really matter if someone else later picks it up and gives it a new lease of life, I've still abandoned it.

#Vortex mod manager archive invalidation Patch

While script extender devs and their ilk may be able to use wizardry to patch the code to some degree, it's hardly the same thing. The people who can have moved on from it, therefore it's abandoned. I certainly wouldn't call the original Skyrim supported or maintained just because people are still modding it, it's not like they can claim any ownership, control, responsibility, liability, etc. We also wouldn't say TESV has been abandoned because there's a huge community of modders still working on it. TESV and SSE are different versions of the same game, andВ TESV is no longer being updated,В but we don't say Skyrim has been abandoned.