6741a492eef6e

6741a492f0643
1 Guest is here.
 

Topic: Need help with newbie guide load order Read 521 times  

6741a492f0b36Dweller

6741a492f0b9d
I've reinstalled System Shock 2 and have been setting up things with the newbie guide, but Four Hundred and Quest Note Notifier are not included in the guide's screenshot despite being in the modlist. So I don't know where in the load order they should be, and I could use some help. (Though I think Four Hundred goes where AccFam is in the guide's screenshot?)

My load order, for reference:

1. SS2 Flora Overhaul
2. Tacticool Complete
3. Four Hundred
4. SS2 Rebirth
5. SS2 Vaxquis Vintage Song Remake
6. SS2 Black Egg
7. Vurt Goo (Impact Blood)
8. Vurt Goo (Dripping)
9. Vurt Goo (Grub Pod Vanilla)
10. Vurt's SS2 WormPod
11. SHTUP beta 2
12. Obj_fixes
13. SCP_beta6
? Quest Note Notifier

6741a492f0cc3voodoo47

6741a492f0d15
quest note notifier can be 1 and it will be fine. basically it's SCP all the way down, then obj fixes, SHTUP and then it doesn't rally matter.
6741a492f0e9d
Since there are so few mods for System Shock 2 (as opposed to the hundreds of thousands of mods for some games, such as Doom, Skyrim, the GTA games, etc), then wouldn't it be possible to maintain a simple file that contains the correct order for the mods, and would be used by ss2bmm.exe to automatically place in order the mods that are present? And when a new mod is made available, then this file could be updated by one of the moderators or SS2 experts on this forum.

6741a492f0f57voodoo47

6741a492f0fb0
this has been considered, but would probably be just a lot of pain for next to no benefit in the end.

just remember what I said in my previous post and you'll be fine 99% of times.

6741a492f10fbZylonBane

6741a492f1147
Has it been considered? This is the first I'm hearing about it, and it sounds like a ridiculous, impractical idea. Someone would have to update such a thing every time a new mod was released, and they'd have to test it with every mod to satisfy its compatibility guarantee.

Hell no. It's fine just to remember that huge mods go at the bottom and smaller, more specific mods are usually fine bubbling around on top.

6741a492f1204voodoo47

6741a492f124f
yes, very sure I was thinking about the manager snapping the big three into their proper places in the manager dev thread in at least one post. decided to not pursue - I am capable of sane decisions every once in a while.

6741a492f171bsarge945

6741a492f1773
The way Wrye Bash works is that it maintains a list of tags for each mod (which the authors themselves provide), and these tags contain information about compatibility and load order, like Gameplay mods will go after Graphics mods, etc. Mods can additionally include a list of known incompatible mods (both in terms of strict incompatibility, and which mods have to be loaded before/after the relevant mod), which Wrye Bash will warn you about. It's a clever system, and allows it to maintain and organise lists of hundreds, if not thousands of mods by essentially making mod authors responsible for maintaining their own compatibility information.

But I agree with ZB here (ZB and I agree on something? GASP!!!), this is not worth the effort. Due to the nature of DML, "load order" is, most of the time, not really relevant unless multiple mods are editing the same properties on the same objects, and if they are, you're likely to run into issues regardless of load order, because one of the mods is going to have issues. This becomes even worse with Strings files because one mod is going to break another mods strings, there's nothing that can be done about it. The only other relevant compatibility note is that, if you're using Alarming Cameras and RSD together, you need to use the Alarming Cameras fix that was shipped with RSD, which contains the strings from both mods combined into one file.

I would support some work being done in the mod manager to allow it to detect conflicts between mods by analysing DML, but it's also probably not worth the effort unless someone decided to take it on as a personal project or whatever. That said, if someone is going to be working on mod compatibility in the mod manager, it would be much better if they could add better string file compatibility, because that's an issue right now and will only get worse over time as more mods include modified strings.

In general, gamesys mods go at the bottom. SCP, and Secmod are the only really relevant gamesys mods right now, as most other ones are deprecated. Then Obj Fixes and SHTUP (and Portrait Fix if you're using Secmod, unless it was included in a recent version I don't know about). Then map mods, the only relevant example is Rickenbacker Automaps, which was made obsolete by SCP 5 but is still useful for SCP 4. Then everything else.

If you're looking for a mod-list that mostly works well together and has a lot of compatibility, I made a guide which you can read here. I'm not sure if it's all in order for SCP b6, although I did update it for SCP b5 so it should still mostly all work.
« Last Edit: 23. September 2024, 02:55:13 by sarge945 »

6741a492f19e7Dweller

6741a492f1a61
quest note notifier can be 1 and it will be fine. basically it's SCP all the way down, then obj fixes, SHTUP and then it doesn't rally matter.

Sorry for the late reply, but thank you!

And regarding what's been said, as a relative newbie to installing SS2 mods, I don't find it difficult enough to require a built-in load order. Just maybe some small changes to the mod guide will help, in my opinion.

Though I believe MO2 has support for loading text files with load order info (I think the Viva New Vegas modlist uses it), a feature like that would be helpful and maybe less difficult to implement.

Your name:
This box must be left blank:

Look at you, hacker: a pathetic creature of ____ and bone!  (Fill in the missing word):
1 Guest is here.
In addition to stats, you can upgrade your robotic body parts, which grant bonuses to stats, protect you, help you run faster or hide better or refill energy, and so forth.
Contact SMF 2.0.19 | SMF © 2016, Simple Machines | Terms and Policies
FEEP
6741a49300808