Well things have been down long enough to start annoying me so I started looking into the recent changes in the data stream processing code.

After a couple of hours I was able to find the relavant locationas and follow the disassembly enough to see where they added the opcode encryption and work through the bit twisting in the first combined packet pass. I am up to determining how and where the lookup table beyond that point gets filled, which seems like it should be the last step in reacquiring a valid opcode.

If I was able to get this far in a couple of hours after not looking into the code for half a year, then I have to imagine that a fix is around the corner. Otherwise I will keep poking at it as time permits.

And in case it is not obvious, anyone who says this was not an attack on SEQ, just a fix for inefficient netcode is so wrong it isn't funny.