Smithnikov Posted August 23, 2015 Posted August 23, 2015 Simply put, something I've done has now rendered me unable to die, even at 0 health. Any possible theories on why my redguard suddenly joined Clan MacLeod? My list of mods, for what it's worth. -Blackthorn buildable town -FNIS Behaviors+spells -XP32 Maximum Skeleton -Immersive Armors -Killer KEOS Skimpy Armors -Realistic Ragdolls and Force -Alternate Start -Run for Your Life -When Vampires Attack -Multiple Adoptions -Immersive Patrols -Frostfall -Realistic Needs -Guard Dialogue Overhaul -Apocalypse: Magic of Skyrim -HDT High Heels -Caliente's Beautiful Bodies -Better Males -Falskaar -Climates of Tamriel -Skyrim and all DLC Unofficial Patches -DD: Explansion, Integration, Device Cutting -ZaZ Animations, Patch and Textures -DD: Cursed Loot -Captured Dreams -Immerslave .9 -Sexlab Framework+Sexlab Aroused, SL Dialogues -Sexlab Defeat -Hydra Slavegirls -SexSlaves for Vanillabandits -Racemenu 3-2-2 -Fuz Ro Doh -Immersive Weapons
myuhinny Posted August 23, 2015 Posted August 23, 2015 Might be from Sexlab Defeat rest of them I don't think use any type of health levels to activate when you hit those levels. Have you also tried going into console and typing in TGM (turns god mode on and off) then let something try to kill you to see if that worked?
Sailing Rebel Posted August 23, 2015 Posted August 23, 2015 Probably Defeat. It's happened to me in the past. Open the console click on the player (ID should be 0x00000014) and enter setessential 0 That should fix it.
Content Consumer Posted August 23, 2015 Posted August 23, 2015 DD Cursed Loot has a known bug in the current version (will be fixed in the next release) that makes you unable to die if you have enabled certain options in the MCM. Check the support thread.
Smithnikov Posted August 23, 2015 Author Posted August 23, 2015 Probably Defeat. It's happened to me in the past. Open the console click on the player (ID should be 0x00000014) and enter setessential 0 That should fix it. I put it in, but got a Item 0 Not Found for parameter Actor base.
Content Consumer Posted August 23, 2015 Posted August 23, 2015 Probably Defeat. It's happened to me in the past. Open the console click on the player (ID should be 0x00000014) and enter setessential 0 That should fix it. I put it in, but got a Item 0 Not Found for parameter Actor base. Go into third person mode (so you can see your character). Then open the console (default key is "~"). Type "setessential 0" and press [ENTER]. That should do it. For more information on the console, including the large number of commands available and what they can do, see the USEP page on the subject. EDIT: Huh... I thought your post said something about needing more clarification. Must be blind.
Smithnikov Posted August 23, 2015 Author Posted August 23, 2015 Still saying it's an Invalid Actor Base, even after putting in the ID given. I reedited the post afterwards, apologies for that. Update: I checked myself out with IsEssential and indeed, found myself to have a 1 beside it, so that's where the core of the problem be. Now if only the console would let me be unessential again...
Content Consumer Posted August 23, 2015 Posted August 23, 2015 Still saying it's an Invalid Actor Base, even after putting in the ID given. I reedited the post afterwards, apologies for that. Update: I checked myself out with IsEssential and indeed, found myself to have a 1 beside it, so that's where the core of the problem be. Now if only the console would let me be unessential again... Whoops... I omitted a step. My bad. Go into third person mode (so you can see your character). Then open the console (default key is "~"). Click on your player. Type "setessential 0" and press [ENTER]. That should do it. That should work. Hopefully! EDIT: player.setessential 0 maybe? prid player followed by setessential 0? There's nothing quite like being told a dozen conflicting instructions, is there?
Smithnikov Posted August 23, 2015 Author Posted August 23, 2015 Still saying it's an Invalid Actor Base, even after putting in the ID given. I reedited the post afterwards, apologies for that. Update: I checked myself out with IsEssential and indeed, found myself to have a 1 beside it, so that's where the core of the problem be. Now if only the console would let me be unessential again... Whoops... I omitted a step. My bad. Go into third person mode (so you can see your character). Then open the console (default key is "~"). Click on your player. Type "setessential 0" and press [ENTER]. That should do it. That should work. Hopefully! EDIT: player.setessential 0 maybe? prid player followed by setessential 0? There's nothing quite like being told a dozen conflicting instructions, is there? No joy. Same message.
WraithSlayer Posted August 23, 2015 Posted August 23, 2015 You guys are missing a parameter, the syntax for for that command is: setessential <base ID> <1/0>. So try: setessential 7 0 And no, you don't need to click-select the player with the console, because this command isn't applied to RefIDs, but rather BaseIDs. (7 corresponds to the player's BaseID, whereas 14 is the RefID)
Smithnikov Posted August 23, 2015 Author Posted August 23, 2015 You guys are missing a parameter, the syntax for for that command is: setessential <base ID> <1/0>. So try: setessential 7 0 And no, you don't need to click-select the player with the console, because this command isn't applied to RefIDs, but rather BaseIDs. (7 corresponds to the player's BaseID, whereas 14 is the RefID) Gave me no error messages when I tried, but I'm still immortal and IsEssential lists me as a 1.
WraithSlayer Posted August 23, 2015 Posted August 23, 2015 You guys are missing a parameter, the syntax for for that command is: setessential <base ID> <1/0>. So try: setessential 7 0 And no, you don't need to click-select the player with the console, because this command isn't applied to RefIDs, but rather BaseIDs. (7 corresponds to the player's BaseID, whereas 14 is the RefID) Gave me no error messages when I tried, but I'm still immortal and IsEssential lists me as a 1. After you've typed the setessential command, give your game some breathing room: close the console and let the game run for a couple seconds. Then open the console again and check the output of isEssential.
Smithnikov Posted August 23, 2015 Author Posted August 23, 2015 You guys are missing a parameter, the syntax for for that command is: setessential <base ID> <1/0>. So try: setessential 7 0 And no, you don't need to click-select the player with the console, because this command isn't applied to RefIDs, but rather BaseIDs. (7 corresponds to the player's BaseID, whereas 14 is the RefID) Gave me no error messages when I tried, but I'm still immortal and IsEssential lists me as a 1. After you've typed the setessential command, give your game some breathing room: close the console and let the game run for a couple seconds. Then open the console again and check the output of isEssential. Still no joy. Hiked all the way from Ysgramor's tomb to Winterhold after the command, IsEssential still puts me at a 1. May have to wait for that DD Cursed Loot patch to fix it up.
WraithSlayer Posted August 23, 2015 Posted August 23, 2015 Still no joy. Hiked all the way from Ysgramor's tomb to Winterhold after the command, IsEssential still puts me at a 1. May have to wait for that DD Cursed Loot patch to fix it up. I guess the method DD Cursed Loot is using to set the player to essential immediately undoes the console command.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.