Relative importance of multislotting? (and thoughts about improvement?)

Smiles

Veteran
Joined
Apr 22, 2012
Messages
573
YouTube
Visit Channel
So just a bit of background, my usual average sessions were sub-13 last year and then I quit.
And then I came back.

So I've been really trying to improve my solving in whichever way I could, and I have already identified weaknesses.

Just yesterday I got a 13.4x average of 200, and today a 13.3x average of 150.

My main question is: just how important are multislotting techniques?
I don't mean a whole list of 1000 doubleslotting algs, i mean the influencing of other pairs with different inserts (R U2 R', R U' R', sledge)

I've been working on lookahead a lot but it just seems a bit overwhelming right now to try and always know which insert to do when. Like if I notice 2 pairs already paired, yes I will instinctively choose the insert that preserves the other pair.

Do people choose different inserts regularly? Like to prevent the awkward F2L cases from showing up?
Or if not, how often does it happen?

I just don't wanna waste my time with too much thinking if it's not worth it.

Otherwise, the only improvement I've made to my F2L (besides lookahead) is learning a couple of easy algs for cases that normally require cube rotations or other dumb stuff. Collin Burns made a great video demonstrating a few of these :)

I also have some more thoughts: how do I go about improving from here?
Yes my times are getting better from practice practice practice, but I'm wondering what thoughts you guys have for getting past this little area under sub-15.

Should I upload a video of me doing some solves?
 
There's some discussion about multislotting here: http://www.speedsolving.com/forum/showthread.php?t=45301

I have done a systematic analysis of many multislotting cases to identify those that are most worth learning, in terms of move count saving. I define those as cases where doing an insert other than the obvious default will set up another pair, whereas doing the obvious would put that second pair into a "bad" case that could take ~11-12 moves. The potential saving is thus ~6-9 moves in each such case. I have written about 20 of these cases into a guide laid out in table form. I'll post the guide once finished.

I'm not fast, but have been trying to work some of these cases into my lookahead training, and found it good fun. It gives me more to think about and makes F2L practice a bit less boring. It also seems to have the side effect of making regular lookahead seem easier :)
 
Back
Top