Wonder if the legacy version of those mods is still available anywhere?

not sure what mods are SCP 4 compatible.

resource replacement mods (textures, objects etc) should be fine, functional mods (RalSG, Repairman etc) much less so, those are always upgraded to the latest SCP standard and backwards compatibility is not taken into consideration. you will have to trial and error those (off the top of my head, Repairman probably ok, RealSG probably not for example).

I was wanting to play this again (getting back into SS2 with the new anniversary edition), but as we are now 5 years later on SCP 6, I'm not sure what mods are SCP 4 compatible. Any recommendations for a good mod list to play this with today?

Planning to run RSD + Enemy AI + Randomizer, and whatever graphic updates will run on SCP 4. Open for other gameplay mods that work well with RSD.

yea, you can have many SS2 installs on the same drive, I have more than 20.

most mods will work with b4 still, but some might have issues, you will probably have to use older version of RealSG for example (1.05 I think).

Why not? Has RoSoDude abandoned it, or he/she's stopped visiting this forum, or what?

@RoSoDude has been super busy working on real life stuff.

It's "abandoned with intent to get back into it at some point".

This guide was written for SCP b4 originally, and most/all of the mods on the list should still work with it.

Unfortunately, this mod is never going to get updated.

Why not? Has RoSoDude abandoned it, or he/she's stopped visiting this forum, or what?

I've always intended to one day try this mod, but never gotten around to it. If I do try it, do I have to make a new install of SS2, use SS2Tool, then install SCP beta 4? Should I then install the recommended mods ( https://www.systemshock.org/index.php?topic=4447.0 ) ?

Partially compatible with Beta 5. The RSD player script still derives from SCP Beta 4, so truthfully, this mod is only fully compatible with Beta 4.

oh this was meant more for @RoSoDude to check.

share a save.

I can't use fragmentation grenades in 2.04 Beta.  I can cycle through all other grenade types, but not frag.  Dragging and dropping onto the grenade launcher won't load them, nor does attempting to reload with only frags in my inventory.
Not sure if it's a mod conflict, but here's my load order:
SS2-RSD_2.04_BETA
SCP_beta6
obj_fixes_v14
SS2_Vaxquis_VintageSongRemake
Quest Note Notifier
Flashlight Aug
English Subtitles

I've tried disabling everything but RSD and SCP, but it still happens.  Disabling RSD makes frags (but not the other types) disappear completely from my inventory and overworld.

I tried SCP6 with SS2-RSD_2.03 and noticed that player flooring on level start wasn't working anymore, so it's definitely clobbering some functionality of SCP's player script.

Is this currently compatible with SCP Beta 6? I remember playing around with it with Beta 5 and noticing a glitch with the UI where the Security System countdown would bleed through the UI in-game. I was also wondering when the scary monsters AI upgrade would be updated to be compatible with Beta 6 as well.

Yo RoSo, in your custom panel code, I'm curious how you integrated them into the native overlay system with regards to deconflicting with the other panels, automatically closing when use mode toggled, etc. I've been playing around with modding a panel replacement, and so far it seems like the only way to do this is brute force, i.e., on open deactivate every overlay that could overlap, then in the draw handler check for any of those overlays being opened. So I'm hoping you'd discovered a more elegant approach.

Edit: Well I've managed to resolve most of these issues, but still stuck on how to detect when the player has opened another MFD while my MFD is open. Looping through 23 overlays to check their visibility every single draw call seems less than ideal.

Edit2: Duh, CanEnableElement() was exactly what I was looking for.

Heads up that in SCP Beta 6, the hack text for the SHODAN shield interlock computers will be updated to reflect their altered effect. So you'll need to set HackText on CPU1/2/3 back to Shield_Interlock.

It was probably a question of how/when I was checking for conflicts with the native alarm overlay, but my problem was that I would get alarms (or maybe security hacks, I don't recall which) endlessly looping. That was when I checked per overlay update, which would obviously not be my preference as far as performant code goes. I'm sure I must have tried doing the check on custom overlay open/close which must have had some other problem...?

Anyway, maybe I'll take another stab at it.

I guess that's a safe method of achieving the same effect. I was just trying to get the minimal SCP compatibility stuff out of the way, and I just flagged the hard security minimod incompatibility for later. Beta release and all.

I can get it cleaned up in the next version.

generally speaking, if a mod that tweaks game mechanics makes changes in a certain area, it's very much not recommended to load more mods that touch the same area.

Just a heads up that in Beta 6, SCP will be fixing the Soma Drain psi power so it can't heal the player for more HP than the target actually has. It will also fix the drain FX object only appearing on Creature type targets (the vanilla script never teleports it to the target location).

Since healing the player will be handled by the SomaDrain script, the DrainStim receptron that heals the player will be disabled by setting its effect multiplier to 0.

class SomaDrain extends RootPsi {
function ActivatePsi() {
base.ActivatePsi();
doDrain();
DeactivatePsi();
}

function doDrain() {
local mod, drain, heal;
local obj = ShockGame.GetDistantSelectedObj();
if (obj && Link.AnyExist("StimSensor", obj, "DrainStim")) {
drain = GetData("Data1");
mod = GetData("PsiStat") - GetData("Data3");
if (mod > 0) {
drain += mod * GetData("Data2");
}
heal = scp.Clamp(drain, 0, Property.Get(obj, "HitPoints"));
ActReact.Stimulate(obj, "DrainStim", drain, "Player");
ShockGame.HealObj("Player", heal);
createFX(obj);
}
}

function createFX(obj) {
local fx = scp.CreateAt("Soma Drain FX", obj);
if (Property.Possessed(obj, "Creature")) {
local lnk = Link.Create("ParticleAttachement", fx, obj);
LinkTools.LinkSetData(lnk, "Type", 2);
LinkTools.LinkSetData(lnk, "Joint", 3);
}
}
}

Agreed. Destroyed only by high value resources or invulnerable are the two sensible options. Destroyed by anything is the realistic, yet silly method.

Realism brain worms is a blight. Abstraction as it pertains to game design is a lost art of the glorious 1990s.

Let me highlight why with the following example: realism's end goal here is they are a not a hazard at all because they'd just squish immediately when stepped on by this 180lbs (or whatever) man. It is clearly explained the worms are in their infancy, and you can see when you look at the piles they're too small to do any damage puncturing future space marine footwear, nor withstand such weight when stepped on. So, realism's end goal is therefore they are nothing of consequence unless you take your boots off and run around the ship barefooted, or your footwear are otherwise compromised perhaps.
Realism for realism's sake is often antithetical to game design, even when the intentions are good e.g immersion, sense of freedom as is the case here. Irrational had it right by making them hazards that cannot easily be removed, simply do chip damage when stepped on instead of attaching to your foot and needing surgical removal, and yet were just straddling the line of believability for the player to not stop and question it. The only questionable part of their design here is encouraging players to get on their hands and knees with beakers collecting them all to use a gun that isn't particularly satisfying and requires significant investment. But I get their thinking. The idea is novel and cool, and could have been good. Just did not have the best execution.

That's a point too, keeping them indestructable preserves worm ammo counts for new players whom have no idea about any proliferator worm gun thing until much later. Are you sure you thought this through Zylon?

So tacking on specific requirements to kill worm piles doesn't make lore sense and misses the point of them, which is that they're only a threat when not noticed.

This reminds me: I need to randomise worm positions in the randomiser. If I wanted to get fancy, I could even re-randomise them when returning to the map if it has been a long time.

Maybe in a future version. I barely want to touch it for now.

Also, making worm piles not destroyable makes sense gameplay wise because they are supposed to be floor hazards. There are certain areas (like one of the interview rooms in Ops) where the challenge is jumping properly to avoid them, not "noticing them", and this change maintains that gameplay. I agree they are mostly a non-threat in the typical case, but you do have to keep at least some mental awareness to avoid them, especially on return visits to areas where you're less likely to be paying attention.

I completely understand the lore objections, though. It doesn't really make too much sense that you can kill one worm but not a swarm.

Okay, I've uploaded 2.04 BETA to the first post. I have not 100% verified that everything is working in the levels, but I did play up through Hydroponics.

#### 2.04 BETA ####
-Updated for SCP Beta 5 compatibility and reverts
   -SCP Beta 4 is no longer compatible
   -Grenade Launcher base damage not increased by 85%
   -Worm piles cannot be destroyed by most damage types (only incendiary and anti-annelid)
-Removed debug logspam for frobbing psi pull items
-New headshot system for Pistol and Assault Rifle bullets
   -Weapon base damages decreased by 25% (Pistol 4->3, Assault Rifle 8->6)
   -Headshots deal an additional 66% damage (25% more than before)
   -Damage type weaknessess/resistances apply to bonus headshot damage
   -Hybrids, Monkeys, Midwives, Assassins, Rumblers are susceptible to headshots
-Decreased bullet projectile size by 80%

Hello!

In the OT I read: "Installation and Mod Compatibility
Requires SS2 v2.48 patch or above. SS2-RSD is built for SCP Beta 4 (and hopefully beyond), which is required."

Can someone confirm that the latest version is fully compatible with the SCP Beta 5 changes?

Thanks!

Huh, I skimmed the change notes and didn't see that mentioned.

Would be interesting if instead of just blowing up, psi mines had a fixed amount of damage they could deal, and would sit there zapping enemies until it was all used up. That would be a somewhat radical change though.

Would it be possible to make the damage from Remote Psionic Detonation scale with PSI level? Assuming it doesn't already do that. The vanilla description doesn't say it does, so... eh.

Just a heads up regarding the AddText function in this. As I've recently discovered when expanding it to support more than one substitution per string, the Squirrel built-in function format() is basically C's sprintf(), so it can replace the entire SpliceDataIntoString function. The version of AddText in SCP has now been reduced to this:
function AddText(strID, strFile, strDefault = "", subVal1 = "", subVal2 = "") {
local strText = Data.GetString(strFile, strID, strDefault);
if (strText != "") {
strText = format(strText, subVal1, subVal2);
ShockGame.AddText(strText, "Player");
}
else {
print("ERROR: String \"" + strID + "\" not found in \"" + strFile + "\"");
}
}