This is unfortunately not new. It is also not good.
It is also not going to be high TPS just because it's algorithmic. The algs needed are not very good.
I mean this is kinda just another intermediate version of Tripod.
I worked on something similar a long while back where you simply build a LL 2x1 bar into the last F2L slot, do an alg to solve the last pair and form the LL 2x2 using that pair, then the Tripod LL case.
And let’s keep...
Nobody really understood what they meant lol.
They are doing CPDB to get left with L5E/Parity L5E (which are terrible alg wise).
6 CPDB cases. 4 EPLL, 5 pEPLL, 12 L5E, 12 pL5E.
39 algs total.
That doesn’t really matter. FTO is fine at this point. Nobody was complaining that clock was called clock, and nobody calls the NxNs their actual names either like Rubik’s Revenge or the Professor Cube.
It’s okay-ish. I was working on CO solved LL for a while. I learned antipll and the diag cases. Overall 10000% worse than just doing ZB (I know about half of ZBLL and some ZBLS). Drastically blows up alg count for LS and the 1LLL cases seem to be worse than ZBLLs alg wise ( but they are also not...
That massively overcomplicates things. You really only need a list of speed optimal ZBLS algs, then document the 6/27 CO cases that lead to H/Pi and have an alternate ZBLS alg.
It's not really worth further complicating your LS just to avoid HP imo, particularly when ZBLS is still developing...
So as someone who learned the Tripod method and then improved it with TLS, this caught my eye, so I messed with it for a few minutes.
After looking at what you're doing and the end state reaching, I have some unfortunate news to break:
After you get to the point of having solved the 2x3 block...