AngelLoader v1.11.0 - now works better on Wine! (updated 2025/07/24) - by FenPhoenix
MrMunkeepants on 27/5/2021 at 03:50
thank you for all your hard work, Fen.
I installed the new version in a new folder, but it (predictably) didn't import my notes, Finished On settings, etc. How do I bring that over, or was I supposed to drop the new data in the old install folder?
FenPhoenix on 27/5/2021 at 04:37
You're supposed to install new versions to the same folder, but to bring over your settings you should copy your old version's Data folder over, then copy the latest (
https://fenphoenix.com/apps/AngelLoader/languages/English.ini) English.ini file to the Data\Languages folder in your new install.
Corsair on 30/5/2021 at 02:25
Can you add global options for disabling some or all mods?
FenPhoenix on 30/5/2021 at 02:42
Hmm, if you want to
globally disable mods, you should probably just go into cam_mod.ini and do it there. It's basically the same process as doing it in AngelLoader, you have to edit a + sign separated list of mod dirs, so like if your mod_path was:
Code:
mod_path usermods+NecroAge+EP2+T2FMDML
and you wanted to disable NecroAge, then you would go like
Code:
mod_path usermods+EP2+T2FMDML
Plans are to make a more user-friendly mod management system for AngelLoader, but the dark-mode UI stuff took up so much time that I pushed it back.
sneakus on 24/6/2021 at 18:19
Woohoo! Nice work Fen, dark mode + archive delete :thumb: :)
Marzec on 20/8/2021 at 07:07
(Feature request) Hi Brian. Please check this post and 5 next posts:
(
https://www.ttlg.com/forums/showthread.php?t=151422&page=2&p=2476238&viewfull=1#post2476238)
There is a potential for FM loader to clean up config after previous missions better. Do you think you could add it? I think you might implement it with some default intial config files or just reset settings that are problematic (one is mentioned in posts linked above).
Cheers
Konrad
FenPhoenix on 20/8/2021 at 14:29
EDIT: baeuchlein got there before me. Yes, you're right. Having a loader auto-remove this line is a potentially intrusive thing to do and we need to make sure we're not making anything worse or stepping on anyone's toes etc.
Original:
I'm aware of the issue of course, and AngelLoader does do cleanup of a couple of other things like that. But, the lines it removes are lines that are supposed to be specified in other config files but end up being written by the game to cam.cfg, and so I can be reasonably sure that removing them from there is safe because they're almost certainly specified in their proper places elsewhere. In other words I'm really just removing duplicates that will cause problems later.
I hesitated to implement auto-removal of the "character_detail" line because I don't think it's documented anywhere that it should be specified in any other config file (or documented anywhere at all, period) and I didn't want to go removing the only instance of a config line that some people might be using for some legitimate purpose in their setup. I mean I don't know if there is one, but I just didn't want to go messing with peoples' config files to that degree.
But, it seems to be causing people a lot of grief, so I'm leaning towards just auto-removing it. Maybe add an advanced option to suppress the removal in case there's some niche case where someone wants it there, but yeah.
baeuchlein on 20/8/2021 at 16:01
Maybe that auto-removal procedure could be enhanced a bit. What about the following:
AngelLoader first installs the mission (regardless whether by pressing some "Install FM only" button or "(Install and) Play FM" button). Just before starting the mission (by "Play FM" button), AngelLoader checks the game's (not the FM's!) configuration files for "character_detail 0" lines. If there is one, no auto-removal is done. If, however, the game's config files do not contain "character_detail 0" (in which case they should contain "character_detail 1"... should they...?), AngelLoader also checks the FM's config files, and if "character_detail 0" is present in any one of them, AngelLoader makes a "mental note" of that. After playing the mission, AL checks whether "character_detail 0" is now present in the game's config files. In that case, it would be a candidate for removal afterwards.
Of course, there are some caveats. What if the player installs the mission, plays it, stops playing - but does not uninstall the mission, and plays it again (or continues playing it). In that case, AngelLoader would now detect "character_detail 0" among the game's config files, but should not make a (new) note about it - after playing, "character_detail 0" should still be removed again from the config files, just like the first "mental note" says. Maybe removing "character_detail 0" any time the player ends playing the mission would help.
If that does not give you enough headaches, think of a situation where a player plays the mission, doesn't uninstall it, but decides to put "character_detail 0" in the game's config files now for whatever reason. This time, AngelLoader should not remove that "character_detail 0" line automatically.
Still no headache? Think about a player having "character_detail 0" in a game's config file before playing and then adding it on his/her own to another one of the game's config files...:tsktsk:
As an alternative, AngelLoader could simply inform the player if "character_detail 0" crops up in the game's and/or a FM's config files at any time. On the other hand, if AngelLoader then gives the player a window upon every start, stating the problem, and then forcing the player to press "OK" or something else, this could also lead to the player being seriously annoyed.
Enough headaches. Let's see whether they stay with you for the weekend only, or even longer.:ebil:
EDIT: This "character_detail 0" thing stems from the original version of "Thief" (and "Thief Gold"). These games had an option in the options menu where the player could switch between simple, but rather ugly, AI models, and advanced ones. "character_detail 0" would be written into cam.cfg for the simpler models, while "character_detail 1" selects the more advanced models. In fact, with rather slow machines from the Pentium I era, I noticed sometimes increased game performance with the simpler AI models. With modern computers, however, it's not important anymore.
With the somewhat modified Thief 2 game engine, this option in the menus vanished. Apparently, the engine still contained program code that reacted on "character_detail" lines, but usually, "character_detail 1" would be found in cam.cfg. As long as everyone keeps his/her dirty hands out of the game's holy config files, nothing bad would happen. People crossed fingers, kept their hands from files not made for everyone, and the (game) world became a better place.:cheeky:
The NewDark engine is the upgraded Thief 2 engine, and it is also used to play Thief 1 NewDark nowadays. Apparently, this engine also still has code in it that reacts on that "character_detail" stuff. But with the possibility of putting such configuration options in a FM's config file, the game engine also has to react on such stuff. And apparently, it does this in a buggy way - some changes are permanently stored in the game's config files, not just temporarily. And that's where the feces make contact with the fan.:eww:
Another problem does appear when someone has an older T1 install (pre-newdark), and upgrades it to NewDark. An already present "character_detail 0" line may be kept in cam.cfg, even if the player did not do the upgrade all by himself, but let TFix do the dirty work instead.
One last headachy thing: I just let a program search for "character_detail" strings in T1 gold, T2 (both pre-NewDark), T1 NewDark and T2 NewDark installations. Surprisingly, it detected it not just in cam.cfg and thief.exe/thief2.exe, but also in dromed.exe. Who knows what the editor does while you use it? Another problem to watch out for...:sweat:
Well then, young novice. Put this lesson on character details to good use, and may the Builder guide your hands on the keyboard. And may you never use your hammer on the computer, for that tool is made for sturdy stone surfaces, not delicate equipment... and maybe for the soft material that the Pagan heretics and vile thieves are made from.:ebil: --Excerpt from the Tome of Correct Hammer Usage, suitable for Hammerite novices for "Hammering 101" courses.
EDIT 2: And of course, while I wrote my post of gigantic size, others continued the discussion and probably went ahead of me.;)
Marzec on 20/8/2021 at 16:05
If a FM sets it, it should be there.
After FM is uninstalled, it should roll back to default settings (whatever that means, depending on your implementation). It's as simple as that.