Jump to content

WrinklyNinja

Members
  • Content Count

    261
  • Joined

  • Last visited

About WrinklyNinja

  • Rank
    Initiate

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. LOOT v0.14.5 released! Thanks to everyone who contributed towards this release.
  2. Maybe, I've seen people do all sorts of things with spreadsheets. Why would you, though? Pick the right tool for the job. You can provide conditions for most metadata, e.g. load B after A if C is present.
  3. A) As I see it, JSON vs. YAML is a matter of who's going to be working with your data more - JSON is much simpler to serialise to / deserialise from, so great for passing data between programs, but it's also much less human readable due to the noise of quoting keys and wrapping all objects and arrays in {} and []. YAML's also got a few neat features like anchors/aliases that are very helpful for reducing boilerplate and avoiding typos. B) GitHub's the most user-friendly approach to version control I've come across, and version control is a hard requirement for any software project I'd want to go anywhere near. Anyone not familiar with Git can still contribute to the masterlists through the website without really knowing how to use Git, and GitHub's help and tutorials are pretty extensive for the basics. C) LOOT will error if it encounters a cycle, because they can't be represented in a load order, which must be linear. You can provide conditions for most metadata, e.g. load after A if B is present. D) A separate list is more maintainable. The vast majority of plugins are one-game-only, so you'd end up with a huge masterlist with content that is mostly irrelevant for whatever game you're currently sorting or maintaining, which just makes it harder to spot what's relevant. You'd also increase the risk of accidentally applying a change to more games than you need to. It would be nice if mods supplied the load order info so the masterlist didn't need to, but modders are less likely to know all possible interactions with other mods up front, and mods tend not to be updated indefinitely. Plugin descriptions can also only be so big - probably not enough to hold the necessary information.
  4. Yes, that's right. Sorry for the late reply about this... There's no authentication requirement to download from Bintray, all I can think of is that there's something on your end that's giving you the error message, e.g. a proxy or VPN that's blocking Bintray downloads?
  5. Load after rules shouldn't allow anything to contradict them, if anything does it'll get ignored or cause a sorting error. Can you share your debug log after sorting?
  6. Unless it's something that's been added since I stopped working on it, BOSS doesn't detect plugins that can be merged into the Bashed Patch either.
  7. LOOT doesn't detect levelled lists or plugins that can be merged. I can't replicate this, if I set more than one plugin to have the same timestamp with Wrye Bash then sort and apply a load order in LOOT, it ensures that there are no duplicate timestamps for me.
  8. What benefit would providing Morrowind support actually give though? mlox provides a certain quality of sorting, and for LOOT's support of Morrowind to be worthwhile, it would have to surpass that, which would involve either converting whatever rulesets mlox uses (if possible) and building on them, or a lot of effort to independently get LOOT to the same place. I'm not against it (I don't think it would take much in the way of code changes), but I don't want to introduce confusion over which tool is "better". If people want to help maintain LOOT's Oblivion masterlist, I'll accept pull requests and they can file issues in the GitHub repository, but I don't think I have the time or interest to make changes myself. There's a patch for Provincial Courier Service on the Landscape Fixes For Grass Mods Nexus page, and one for Cutting Room Floor on JK's Skyrim's Nexus page.
  9. Regarding Morrowind, the last time I looked people seemed generally happy with mlox, and I didn't want to "split the ecosystem". The hard part about maintaining the Oblivion masterlist would be making all of BOSS's implicit load order rules explicit (e.g. does B load after A in the BOSS masterlist because it needs to, or just because that's where it was put?). Though now that LOOT has groups, I suppose you could try bunging everything in a load of groups to match the BOSS masterlist and go from there. That's a very heavy-handed approach though.
  10. Well, nobody's really been maintaining the LOOT masterlist for Oblivion either, I think that BOSS will probably still give better results, at least for complex setups like FCOM. It would be great if LOOT were brought up to the same level, but that hasn't happened yet...
  11. LOOT v0.14.3 released! Thanks to everyone who reported and helped me track down the bugs that this release fixes! That's due to a bug that's fixed in the new version of LOOT.
  12. If you supply the filenames of the plugins involved, probably.
  13. The "weighting number" was priority. Priorities were replaced by groups, which provide roughly the same feature. The Apply button only shows up (in the top right corner of the window) if you've sorted your load order (the button for that is also in the top right).
  14. @Gr3yStar Are you able to file an issue for your aliases feature request on GitHub? If it's there it's much less likely to be forgotten about, and is easier to keep track of.

Support us on Patreon!

Patreon
×
×
  • Create New...