Jump to content


  • Posts

  • Joined

  • Last visited

Contact Methods

  • Website URL

Recent Profile Visitors

1581 profile views

fireundubh's Achievements


Initiate (4/10)



  1. I haven't tested other games, but it looks like the issue was limited to a single version number. The steps to reproduce that issue got that version number into a bad state, which broke file uploading and versioning for that version number. I'd bet that issue can be reproduced with any game. So, yeah, don't make the mistake of entering the version of an old file when uploading a new file.
  2. No idea. It might have something to do with the .manifest file.
  3. When I upload a file with a certain structure, that structure is changed in the file that you download. When I preview the file contents on the Nexus: So, the new Nexus site backend appears to be messing with the contents of files. Also, don't make the mistake of entering the version of an old file when uploading a new file.
  4. @Utumno Did you see my earlier posts? I already looked.
  5. For me, Fallout 4 appears on a second screen, so I'm not sure what's up with your screenshot. As an aside, it's kind of silly that Wrye Bash needs to be installed into each game directory. Some work should be done so that's not a requirement. xEdit has a similar problem in that you have to rename the binary for each game.
  6. I just built the 150-fo3-fnv-support branch (307.201803041642). I don't see any issues with the installer. There are no issues in the NSIS installer either. Going back to playing Kingdom Come.
  7. In the Kingdom Come Nexus, it seems my mods are frequent targets of people wanting permission to merge, derive, or clone them—and upload them as wholly separate mods. I feel that merged, derived, and cloned mods detract from the source mods, so I don't support this at all and do not grant permission. Am I wrong?
  8. That's some wall of text, alt3rn1ty. I honestly had forgotten all about this conversation until the forum pinged me. I'm not sure why you want to take credit for the tangent, but okay, you can have it. Whatever. Also, I think the "knight protector" dig was a gross exaggeration. I wasn't waging war. I was clarifying that MO, which also means MO2, is an active project. /shrug
  9. Windows 10 is technically a fork of Windows 8 and was originally planned as a Windows 8 update codenamed Threshhold. In any case, my chart was about what things are called, not their development histories. Mod Organizer (MO) is the name of both MO1 and MO2. We use "MO" generally, and "MO1" and "MO2" when we need more granularity. Only reason why I brought up MO not being abandoned was because I know you have a strong bias against MO (perhaps only MO1 now that I think about it), so I just wanted to make clear to anyone lurking that MO, via MO2, is still alive and kicking. There are something like 400+ people on average in the ModOrganizerDevs Discord server. There's also a beta virtual file system in the #builds channel that prevents MO from moving edited plugins to the overwrite folder, which makes xEdit modding much less tedious. Hmm, now that Tannin has moved on, I wonder if I can get in a fix for the totally useless conflicts system he implemented.
  10. Open source projects have occupants called contributors, and as long as they call that project home, that house will never be abandoned. Tannin retired from MO1. 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. A kingdom evolves with a change in leadership just as an open source project evolves with a change in leadership. But, on reflection, perhaps we're talking about different things. This is how I see things: 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. 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. MO1 is Mod Organizer. MO2 is Mod Organizer. 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. And 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. As an aside, we are so off-topic.
  11. A house can be abandoned only when there are no occupants. Whether the builder of that house remains is not relevant to the state of the house. That the house was furnished and upgraded does not make the house a different house. It is a house with additions. Fallout 4 v1.5 and Fallout 4 v1.7 are not two different games; they are both Fallout 4. Ugh, you're impossible. I don't know why I bother.
  12. Is a house abandoned when the builders move on to the next development, or is a house abandoned when there are no occupants? Tannin built a house and moved on, but the house remains occupied by residents who have since added on to it.
  13. 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. We also wouldn't say TESV has been abandoned because there's a huge community of modders still working on it.
  14. I thought you meant MO itself was abandoned, as in not being worked on by anybody and not receiving updates. Tannin may have started the project, but open source projects can have many different lead maintainers over their lifetimes. MO2 is a fork of MO, but that's a conceit of how GitHub works. MO2 is MO albeit in the hands of a different lead maintainer with a more open approach to community contributions. My two cents.
  • Create New...