The Orcuber's Hunt For The Best 3x3 Method

Do you think this is a good idea? Or are the methods out there good enough?

  • Yes

    Votes: 14 73.7%
  • Current methods are fine

    Votes: 5 26.3%

  • Total voters
    19
  • Poll closed .
APB is basically where you solve a 2x2x3 block in the back left, then you solve the back right pair, then solve EO, finishing off the 1st and 2nd layers, then doing ZBLL
bro I don’t think you know what APB is either😔💀

APB is this:
step 1: solve 223 on the LEFT (usually done by solve a 1x2x3 then solving DFDB)
step 2: solve BR pair (an alg set allows you to do this while solving EO but there are a lot of algs)
step 3: EO (only 11 algs)
step 4: LXS (also has an alg set but can be done intuitively)
step 5: ZBLL (can also use OLL and PLL)
 
bro I don’t think you know what APB is either😔💀

APB is this:
step 1: solve 223 on the LEFT (usually done by solve a 1x2x3 then solving DFDB)
step 2: solve BR pair (an alg set allows you to do this while solving EO but there are a lot of algs)
step 3: EO (only 11 algs)
step 4: LXS (also has an alg set but can be done intuitively)
step 5: ZBLL (can also use OLL and PLL)
I’m stupid idk why i said “back left” i was completely aware it was supposed to be on the left side but i just ndhdienwosn
 
ok but is my method good or not, if so, we can continue with the next step
There’s a general guideline when it come to solving quickly:
Always start from the back left, the the back right, then the front left, then lastly the front right.
Your method starts the opposite way. So I say we solve the xcross in the back left (leaving the DF edge unsolved), then solve the back right pair, then the front left pair WHILE doing EO, then solve the DF edge, and then WV and PLL.
 
There’s a general guideline when it come to solving quickly:
Always start from the back left, the the back right, then the front left, then lastly the front right.
Your method starts the opposite way. So I say we solve the xcross in the back left (leaving the DF edge unsolved), then solve the back right pair, then the front left pair WHILE doing EO, then solve the DF edge, and then WV and PLL.
Adding to Caleb, (I don’t think anyone has noticed this yet) but WV only works when you have that case that can be solved with U R U' R'. So you would need to setup the pair first before doing WV
 
There’s a general guideline when it come to solving quickly:
Always start from the back left, the the back right, then the front left, then lastly the front right.
Your method starts the opposite way. So I say we solve the xcross in the back left (leaving the DF edge unsolved), then solve the back right pair, then the front left pair WHILE doing EO, then solve the DF edge, and then WV and PLL.
ok we can rotate that
 
yeah, it can be entered with that alg
image.jpg

No but what if you get like this case for the last pair? Winter variation is only the F2L 1 case, this isn’t a winter variation case as the pair isn’t paired and it’s not facing the front (paired pair facing the front is F2L 1 case). If you look in winter variation algsheets like https://speedcubedb.com/a/3x3/WV you won’t be able to find this case

And even if we make a specialised algset that solves any F2L case while orienting corners, that would be 1107 algs which is too many
 
View attachment 48145
No but what if you get like this case for the last pair? Winter variation is only the F2L 1 case, this isn’t a winter variation case as the pair isn’t paired and it’s not facing the front (paired pair facing the front is F2L 1 case). If you look in winter variation algsheets like https://speedcubedb.com/a/3x3/WV you won’t be able to find this case

And even if we make a specialised algset that solves any F2L case while orienting corners, that would be 1107 algs which is too many
good question, it is actually supposed to be fixed into a pair (in this case, R U' R'), & it is just intuitive F2L whichcan be done with R & U moves
 
View attachment 48145
No but what if you get like this case for the last pair? Winter variation is only the F2L 1 case, this isn’t a winter variation case as the pair isn’t paired and it’s not facing the front (paired pair facing the front is F2L 1 case). If you look in winter variation algsheets like https://speedcubedb.com/a/3x3/WV you won’t be able to find this case

And even if we make a specialised algset that solves any F2L case while orienting corners, that would be 1107 algs which is too many
then just do R U’ R’ lol
if you’ve been doing your slow solves, then you should have noticed that most F2L algs will almost always convert into an easy insert (usually R U R’ or R U’ R’).
 
good question, it is actually supposed to be fixed into a pair (in this case, R U' R'), & it is just intuitive F2L whichcan be done with R & U moves
then just do R U’ R’ lol
if you’ve been doing your slow solves, then you should have noticed that most F2L algs will almost always convert into an easy insert (usually R U R’ or R U’ R’).
Yes, I have noticed this, but it’s still a bit inefficient imo

Also, if you want to make this method more efficient you’re gonna have to also include summer variation (R U R')
 
Yes, I have noticed this, but it’s still a bit inefficient imo, and that example case I showed was one of the more forgiving ones.

Also, if you want to make this method more efficient you’re gonna have to also include summer variation (R U R')
why would summer variation come, we are solving the back pair first!
moreover, it is intuitive and not efficient and yk that
 
why would summer variation come, we are solving the back pair first!
moreover, it is intuitive and not efficient and yk that
As Caleb said
most F2L algs will almost always convert into an easy insert (usually R U R' or R U' R').
(Pay attention to the bolding in the quote) this is the F2L case that summer variation is

Edit: accidentally bolded R U' R' in the og message
 
Last edited:
Back
Top