rossbach451 Posted September 23, 2011 Posted September 23, 2011 Can't kill TorGal because of some necklace. It is said to go into ShadowKeeper, delete the necklace and you are good. Trouble is, you can't save the changes under the file names you see, you have to make one up. Also, there are many TorGal files, which is correct? How do I know that the ones I monkeyed with actually get used?
lynx Posted September 23, 2011 Posted September 23, 2011 why don't you just use the cheat key to kill him?
Avenger Posted September 23, 2011 Posted September 23, 2011 why don't you just use the cheat key to kill him? Most likely the necklace makes him invulnerable. To know which torgal to edit, use ctrl-m on the actor in game. The amulet is monhp1 You can simply edit the amulet (remove the equipping effect for the time you kill torgal), then restore the original.
rossbach451 Posted September 23, 2011 Author Posted September 23, 2011 why don't you just use the cheat key to kill him? Most likely the necklace makes him invulnerable. To know which torgal to edit, use ctrl-m on the actor in game. The amulet is monhp1 You can simply edit the amulet (remove the equipping effect for the time you kill torgal), then restore the original. Thanks! Did that, hope it works. I now have some sort of disease entering Windspear dungeon, can't get rid of it. Is this a BP thing, does anyone know?
lynx Posted September 23, 2011 Posted September 23, 2011 BP? It definitely shouldn't be a gemrb problem, since I played through that about a month ago.
Miloch Posted September 23, 2011 Posted September 23, 2011 Ctrl+r usually gets rid of disease opcodes, unless it's some sort of script-based thing.
rossbach451 Posted September 24, 2011 Author Posted September 24, 2011 Ctrl+r usually gets rid of disease opcodes, unless it's some sort of script-based thing. I went into my ShadowKeeper file and noticed 3 separate annotations for disease under my character. I deleted them, still no luck. I will try ctrl-r.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.