Albert on 3/10/2012 at 16:21
Yes, although a bit annoying. We should throw all these scripts together into one .zip file, and/or distribute them with FMSel.
Myagi on 3/10/2012 at 17:35
Quote Posted by Sensut
Just in case, copy all of the latest custom scripts into Thief2 directory and leave them there forever
That's good to know. I'll probably still poke around a bit and see if it can be solved the other way too, to satisfy my pedantic side, but if it doesn't lead anywhere it's not a problem anymore with your solution.
Telliamed on 3/10/2012 at 19:39
Quote:
When an FM is active, an OSM that wants to access a file must first look for the file in the FM's dir, and then
the current working dir.
This should not affect most scripts. It
does confuse version.osm. The following missions are affected:
All Torc (tnhScript, Public Scripts)
The Cell Next Door (Public Scripts)
Wedding at the Bar (tnhScript)
Assault at the Gas Station (Public Scripts, tnhScript)
The Librarian (tnhScript, Public Scripts, NVScript)
Bathory parts 1&2 (Public Scripts, tnhScript)
CoSaS Mission X (many)
Most of these can be handled by installing the scripts manually in the Thief directory. (Unfortunately, I think the game will still load the mission's scripts even if they're older than the top-level version.) MissionX is trickier because it uses many unique scripts. I'll have to investigate further to see how to deal with that.
Telliamed on 4/10/2012 at 23:56
Quote Posted by Telliamed
CoSaS Mission X (many)
I checked and although it loads the OSM, it does not actually use VersionCheck, so it should be fine.
I also think there may be issues with missions that use helper libraries. Be sure that you have DH2.OSL and DarkHooks.dlx in the game folder.
Sensut on 5/10/2012 at 06:18
Thank you! I checked too and the scripts are not affected, only "version" is confused, but olny with the new FM Selector. There are no problems in DarkLoader and GarrettLoader.
Telliamed on 5/10/2012 at 07:15
Quote Posted by Sensut
Thank you! I checked too and the scripts are not affected, only "version" is confused, but olny with the new FM Selector. There are no problems in DarkLoader and GarrettLoader.
But the version check still succeeds if you have the latest copies of the three well-known script packages in the main Thief directory, correct?
(BTW, is anyone else with Chrome not able to edit their posts?)
Sensut on 5/10/2012 at 10:37
Yes, if the modules are copied manually to T2 dir, FM Selector works fine as well.
Edit: looks like the problem with the general use of the latest script versions occurs at those FMs in which the author added the version number as well for the version checker.
Sensut on 7/10/2012 at 06:59
Thanks! Looks like is working from the FM pack. Installed the FM with the new fm selector and overwrited "version.osm" with this new one in the unpacked mission directory under FMs. For my 2 campaigns I had to rename it to "vrdracul.osm" because in this name is loaded.
Pheonix on 30/10/2012 at 13:21
With the Carpathian cycle, the new scripst (or renamed scripts, whatever) have to be in the Thief 2 directory. However, this requirement is inconsistant. With "A Weakend Getaway" you have to use an older version of thnscript (1.5.4 is what comes in the zip file, 2.1 is the latest.) The game crashes with v2.1, I originally had to remove v2.1 and install 1.5.4 into my Thief 2 directory. However, FMSel doesn't seem to have this problem, the FM works just fine with 2.1 in my Thief 2 directory and 1.5.4 in the zip file. I have no idea what FMSel does to make the game run right with FMs but it seems that in the case of some scripst it uses the one in the FM directory and in others they have to be in the Thief 2 directory.
