Using 3s to do 1LLL

[abunickabhi]

Rather than learning 1LLL algset which is a humongous number of algs, I feel it is easier to do a quick trace and do 3 style exec to complete the last layer.

It definitely saves a look compared to OLL PLL, and most of the ZBLL cases are just parity cases in blindsolving.

What do you guys think?

 

[Caleb Valenzuela]

doesn’t 3s exec require slice moves?

 

[Fred]

I think the final form of any two-step last layer method is one-look, two-alg last layer. 3style last layer makes the one-looking much easier, but at the expense of worse algs in some cases. For example, if your corner case is three twisted corners and your edges are not already solved, it would be faster to do a sune and learn how the edges move around to predict what edge case you'll get. Even if the edges were already solved, some people solve that case with sune+Uperm.

 

[Thomas.Caleb]

Cool ig

 

[abunickabhi]

doesn’t 3s exec require slice moves?

Yes for edge comms.

Slice moves are super fast yo

 

[NukesAway]

It's neat if there's no parity and one corner is solved
But parity cases are prety ugly for 3s ll. How about fish n chips or cll+1?
If theres no parity but theres a L4C case its even worse, feels like i lost to a cfop boi because i wanted to show off

 

[LBr]

Rather than learning 1LLL algset which is a humongous number of algs, I feel it is easier to do a quick trace and do 3 style exec to complete the last layer.

It definitely saves a look compared to OLL PLL, and most of the ZBLL cases are just parity cases in blindsolving.

What do you guys think?

Don’t buy this at all, unless a corner is already oriented 2 algs will be needed and for the edges it’s the same case but only fully solved pieces can be avoided.

Since I don’t use 3style I don’t know whether you’d recognize edges while solving corners. But CLL/ELL has a lower stm than OLL/PLL so we should probably be comparing it to that especially given that you solve edges and corners separately