Which lock/terminal exposed the bug? The "locklevel" of the lock/terminals (getlocklevel console command)
A quick solution to most broken locks is the console command "Resetquest Lsstandalonequest".
============================================== CHANGELOG: =============================================== 2.0: Made a few changes that *should* prevent any locks/terminals from being excluded. For some reason vanilla novice locks could be set at either level 0, 1 or 25 for "novice"... thanks for that Bethesda. Anyway! Should all be taken care of now. Please re-download your chosen versions(s).
I jammed a lock on a safe using this mod. Will I Never be able to open this safe again? Just for the record, I have never had this with the vanilla minigame. Always wins.
And could you upload the mod which simply gives you guaranteed success if you have the perk, without the minigame?
I've been using this mod really much and after quite some time it bugged out. Resetting the quest did help at first, but now all locks which I unlocked are inaccessible after the cell reloaded (you know, raiders are back, contents of containers are back).
Reinstalling and resetting the quest did not help in this case. Now I have to use the console command unlock to open all those inaccessible containers.
Going to keep an eye on this and try to find out why the quests buggs out in the first place.
For two playthroughs in a row the journey to Nuka-World (or rather back from it) rendered the lockpicking part of the mod useless. Each time I have the same problem as mentioned beforehand. I do not like that DLC at all, so I'm gonna ignore it in future playthroughs.
If anybody has or has not the same problem occuring, please post it here.
The hacking mod is working. The lock picking mod has stopped working even after a couple reinstalls. I don't know, maybe some bethesda update broke it.
I am encountering the occasional locked safe or door that after a single attempt without a broken pick, it becomes inaccessible. Even if I reload before the lock it still fails.
It has happened on novice and advanced locks so far. Next one I encounter I will post the level for you. I just saw your sticky that was dated before my post.Sorry, I totally missed that.
I've a problem: The lockpick mod stopped working. I don't know, what happened exactly, 'cause I didn't pick a lock for hours (building settlement, walking arround...). I picked the perks "Animal Friend" and "Wasteland Whisperer" - and your lockpick menu doesn't show up. "Get queststage" shows 1 on lsstandalone and 0 on tsstandalone.
But as said: I don't know, which changes could cause this issue, because I was just wandering arround/building for hours. ============================== OK, I reinstalled the mod - worked fine until I failed to pick a lock. The lock was marked as "broken" - and from this moment your lockpick menu stopped working and I got the vanilla menu. Looks like the fail of a lockpick is breaking the script.
Can fix this manually by resetting the "lsstandalone" quest. I'll have a poke at the file and see if I can spot the problem
==========
"Resetquest Lsstandalone" should take care of it in console.
I've tried creating a new game and picking the cryolator lock, no problem. The lock "jammed" after three failed attempts but then reset after 10 seconds as normal. That being said, there has been 2 or 3 locks throughout other playthroughs this week which seem to be immune to the mod (weird). Which lock didn't work for you?
I would love to see an option where if you have the required perk, you just automatically do it and do away with everything else. So if I have the perk to unlock Master locks, I simply do, no skill check required. Even running a skill check seems silly. If I have the skill of making a hamburger and I go to make a hamburger, I'm going to be successful at my hamburger creating activities. I've never understood why companies like Bethesda require you to invest in a skill and still have an annoying and repetitive mini-game instead of mini-games that could have been cool like cards, or bowling. Either way, you are doing the work of the gods.
I actually did create a version of the mod which functions in this way, but I haven't got round to testing it. If I put the file up, would you be willing to give it a shot?
After some excessive testing with some hardcore looting sessions I can say: The gameplay is so much smoother with this mod - no interruption with these annoying minigames. Good work!!!
42 comments
==========
Please include:
Which lock/terminal exposed the bug?
The "locklevel" of the lock/terminals (getlocklevel console command)
A quick solution to most broken locks is the console command "Resetquest Lsstandalonequest".
==============================================
CHANGELOG:
===============================================
2.0: Made a few changes that *should* prevent any locks/terminals from being excluded. For some reason vanilla novice locks could be set at either level 0, 1 or 25 for "novice"... thanks for that Bethesda. Anyway! Should all be taken care of now. Please re-download your chosen versions(s).
Just for the record, I have never had this with the vanilla minigame. Always wins.
And could you upload the mod which simply gives you guaranteed success if you have the perk, without the minigame?
Reinstalling and resetting the quest did not help in this case. Now I have to use the console command unlock to open all those inaccessible containers.
Going to keep an eye on this and try to find out why the quests buggs out in the first place.
If anybody has or has not the same problem occuring, please post it here.
I also went into console and resetquest, still did not work.Not a huge deal, if you are unable to solve the issue.
Which lock did this happen on?
If you could, open up the console and use the "getlocklevel" command to see what 'level' the lock is please.
"Get queststage" shows 1 on lsstandalone and 0 on tsstandalone.
But as said: I don't know, which changes could cause this issue, because I was just wandering arround/building for hours.
==============================
OK, I reinstalled the mod - worked fine until I failed to pick a lock. The lock was marked as "broken" - and from this moment your lockpick menu stopped working and I got the vanilla menu.
Looks like the fail of a lockpick is breaking the script.
==========
"Resetquest Lsstandalone" should take care of it in console.
I've tried creating a new game and picking the cryolator lock, no problem. The lock "jammed" after three failed attempts but then reset after 10 seconds as normal. That being said, there has been 2 or 3 locks throughout other playthroughs this week which seem to be immune to the mod (weird). Which lock didn't work for you?
Good work!!!