Angel Posted December 6, 2023 Share Posted December 6, 2023 Found it! In stratagems/sfo2e/lib_ssl.tph at line 92, the REPLACE_TEXTUALLY is exactly backwards from what it should be, it should be the same as line 95. This is in a block that only gets executed on non-Windows systems. diff --git a/stratagems/sfo2e/lib_ssl.tph b/stratagems/sfo2e/lib_ssl.tph index a8bc243..95ea45a 100644 --- a/stratagems/sfo2e/lib_ssl.tph +++ b/stratagems/sfo2e/lib_ssl.tph @@ -89,7 +89,7 @@ BEGIN END END ELSE BEGIN // something else, assumed to have perl natively present OUTER_PATCH_SAVE ssl_loc "%ssl_loc%" BEGIN - REPLACE_TEXTUALLY EXACT_MATCH "/" "\" + REPLACE_TEXTUALLY EXACT_MATCH "\" "/" END OUTER_INNER_PATCH_SAVE scsargs "%path%/%script%" BEGIN REPLACE_TEXTUALLY EXACT_MATCH "\" "/" Fixed file attached, drop this in stratagems/sfo2e/. lib_ssl.tph Quote Link to comment
jmerry Posted December 7, 2023 Share Posted December 7, 2023 Is it fixed? Because that isn't something that changed in v35. It's undoubtedly a mistake to fix, but how could it be the one that breaks things when it was there before? Quote Link to comment
Angel Posted December 7, 2023 Share Posted December 7, 2023 2 hours ago, jmerry said: Is it fixed? Because that isn't something that changed in v35. It's undoubtedly a mistake to fix, but how could it be the one that breaks things when it was there before? Yes, fixed it for me and I already have had several others confirming it fixed it for them as well. There are two versions of the ssl_to_bcs function, one is in stratagems/sfo/general/lib_general.tpa, the other is in stratagems/sfo2e/lib_ssl.tpa. Most likely v34 was still using the old one which doesn't have this bug. Quote Link to comment
jmerry Posted December 7, 2023 Share Posted December 7, 2023 So the change is which version of the sfo libraries was being used. OK, that makes sense. Quote Link to comment
Guest Reeca Posted December 7, 2023 Share Posted December 7, 2023 Yes! Thank you @Angel! The updated file was put into the folder and all components installed perfectly. @DavidWthank you so much also for continuing to pump these mods out. You're doing the lords work. Quote Link to comment
DavidW Posted December 11, 2023 Share Posted December 11, 2023 Thanks for your detective work! Fixed locally, will be in 35.2. Quote Link to comment
Recommended Posts
Join the conversation
You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.