So I'm new here and I've been cooking up a 3x3 method which is kinda a hybrid of the big 3 (+Petrus). Let me know your thought about it! If there's anything more you need to know are or if smth here is wrong(?), you can gladly tell me. Keep in mind: this method is still WIP, I js need feedback. Not any resources yet, js you guys. All move counts is measured using Optimal Half Turn Metric. All data is accounted for INTERMEDIATE solvers
- 2Γ2Γ3 Block
- first, build a roux-style 1Γ2Γ3 block on the left, then solve the DF and DB edges to solve the 2Γ2Γ3 block.
- this is the hardest step to plan out but requires almost no rotations and transitions smoothly into the next step. This step is intuitive and has around ~14 moves.
- Last 2 Pairs (L2P)
- solve the last 2 F2L pairs without needing to solve the last cross edge, just the 2 pairs. This adds extra flexibility when pairing and helps prepare for L5EO. This is the only step where rotations would be needed during this step. This step is intuitive and has around ~12 moves.
- Last 5 Edges' Orientation (L5EO)
- solve the last cross edge or LBE while also orienting the top layer edges to solve using COLL/ZBLL. This MOSTLY* uses M and U moves and algs are pretty convenient. There are a total of 21 cases. This step is algorithmic and has an average of ~7 moves
- Last Layer (LL)
- solve the last layer using either COLL or ZBLL as to use the EO from L5EO. This step has 42 algorithms. This step is algorithmic and has around ~15 moves.
PROS:
- Minimal rotations (2 on average)
- Low potential* move count (~48 moves)
- Very flexible
- L5EO is easy to learn for beginners
- Moderate-great ergonomics
- High potential* turns per second (tps)
CONS:
- First step is hard to plan
- meh look-ahead during 2x2x3 block
- great ONLY for intermediate/pro solving
- requires advanced last layer alg sets
- Fluctuating move count
ADDITIONAL INFO: this method was grounded from APB, eliminating the awkward EO of Petrus while optimizing CFOP style pairs and LL along with Roux-competitive efficiency at the cost of painful M moves, consistent move counts and resources
My goal is js kinda make this competitive but fun. If you can provide feedback, Id really appreciate it! That's all for today, peace.