# How do you pick a lock successfully?

In Fallout 4 what's the best tips for lock-picking so I don't break hairpins?

Simple Tips

Immediately stop putting any pressure on the bobby pin as soon as it starts to stick. This will allow it to stick in multiple spots before it breaks.

Remembering where your last pick was when it broke is easier if you pay attention to where it is in relation to the little chips and marks around the outside edge of the lock before you start turning it.

Full Algorithm

As far as figuring out where to turn the knob, use a modified binary search algorithm. A binary search is the same algorithm children are taught in school when they learn how to use a dictionary. This one is a bit different, as we have to test a couple points and compare before going left or right.

In these instructions, "test the point" means to turn the lockpick there and see how far it goes.

1. Start with a point in the middle. This is the "center point". The left endpoint is the point rotated all the way to the left, the right endpoint is the point rotated all the way to the right. Test the center point and make sure you haven't lucked out and found the solution already.

2. Select left and right test points. The left test point should be midway between the center point and the left endpoint. Similarly, the right test point should be midway between the center point and the right endpoint.

3. Test each of the test points. One will turn further than the other. The target point is on this side of the center point.

4. Repeat steps 2 and 3, but with the more successful of the last two test points as your new center point. The old center point will become one of the new endpoints, as well as the previous endpoint on the same side of the old center point as the new center point.

The width of the section that will turn at all gets narrower as the locks become more difficult. As you attempt more locks you'll get a better feel for how wide each type of lock's sweet spot is.

This can inform your choice of test points, as you might not always want to choose points midway between the center point and the endpoints. This is especially true if the initial center point turns a little. In that situation, pick test points closer to the center. If the center point doesn't turn at all, pick points closer to the endpoints.

If one of your test points turns far enough, you might not even want to bother testing the other point, as you can be confident you're on the correct side already.

Occassionally, neither the center point nor either test point will turn at all. This complicates things. You'll simply have to try more test points until one of them turns at least a little. Once this happens, you can use this as your center point and the nearest spots you tried on either side of it as your endpoints.

Technical Notes on the Binary Search Modification

A normal binary search is done on a set of ordered elements, usually numbers. This search is also done on an ordered set of points, but when we're running the search we're unable to directly read the value to determine if it is greater than or less than the target value. Instead, we can only determine the distance (absolute value of the difference) between the test point value and the target point value. To be clear, I'm referring to how far the pick turns. When it turns a little, you're far away, when it turns a lot, you're close.

Since distance is undirected, we don't actually know whether to go left or right after the test. This means we check both left and right, then compare to determine on which subset of the set we recur. Because our center test point is not the target point (if it were we'd be done already), we know that when comparing two equidistant points on either side, one of them must be closer to the target than the other. This necessarily implies that the target point is to that side of the center point, although it doesn't tell us which side of the test point we need to check.

So we recur and repeat.

• That's not really a binary search... – Rawling Nov 13 '15 at 7:58
• I think it would be safe to call it a "modified" binary search. But yeah, not a true binary search. – Broots Waymb Nov 13 '15 at 14:45
• I would suggest trying it with a controller that can rumble. You will break far fewer bobby pins, because you will be able to feel the pressure on the bobby pin long before you see the lock stop rotating. – Unknown Zombie Nov 13 '15 at 17:45
• @DangerZone That's fair. I was thinking last night how I should add a note about modifying it due to not being sure about the ordering. – DCShannon Nov 14 '15 at 1:02

You want to just lightly tap the controls for rotating it and move the bobby pin from spot to spot till you find the spot that allows for the lock to turn from there once it turns a little move the bobby pin a bit more and keep trying to turn the lock lightly of course until you get to the spot that unlocks it. The best explanation would be a video such as this one.

• Is this video actually from FO4? Lock doesn't look like mine at all (XB1). – Iszi Dec 10 '15 at 22:56

If you look carefully at the lock, there are lots of "landmarks."

So start in the middle and if it doesn't turn, then half-way clockwise/halfway counter-clockwise until the lock starts to turn. Once you see the lock turn a little you are "close."

From then on, make a note of where the edge of the bobby pin is in relation to any markings on the lock. If you still haven't got it, reposition the bobby pin a little in either direction from the marking and try again.

For Novice locks, you can move the bobby pin more freely between tries, but for the harder locks, the marking positions are more important

DCShannon has a good and thorough procedure, but it seems to understate some of the opportunities for optimization.

Firstly, once you've found a point that moves at all (well, more than just a teeny-tiny jiggle) you need to stop swinging all over the lock's face. You've found a good starting point. No matter how little it moves, you shouldn't go too far away from it for your next check.

Secondly, every point that you check afterwards is telling you something. You don't need to test two more points every time (not even nearly most of the time) to figure out where to go. If a spot moves further than the spot before it did, you're probably headed in the right direction - go just a few degrees further in the same direction and try again. Rinse and repeat until you either unlock the thing or you find a spot that moves less than the one before it.

If you find a spot that moves less than the spot before it, then one of two things happened:

• You went in the wrong direction.
• You went too far in the right direction.

It's hard to give guidance for this that will be both efficient and universally applicable. But keep in mind what I said earlier - every point you check is telling you something. Consider how the lock has responded thus far, and you should be able to logically conclude what the appropriate course is for now. In any case, you definitely need to reverse direction. The question you'll need to work out for yourself is just how far. Work in small increments at this stage, and the lock will tell you soon enough.

As for where to start the whole process, I find the following points (in this order) tend to be the most productive:

1. Part-way left, more or less in line with the "X".
2. Part-way right, about the same distance from center as point 1.
3. Dead-center. (You'd think this should logically be first, but I find the other two points more commonly yield results.)
4. Full-left, or very close to it.
5. Full-right, or very close to it.

Nine times out of ten, one of those points will respond favorably to some degree - usually, it's one of the first three. On the off chance they don't, just start poking around in between them until something does.

• I considered elaborating further upon "This can inform your choice of test points...if the initial center point turns a little...If the center point doesn't turn at all...turns turns far enough, you might not even want to bother testing the other point", but figured the answer was long enough. I think these optimizations should become apparent over time. Still, +1. – DCShannon Dec 10 '15 at 23:25