02:47:23 <zzo38> Perhaps the format of the USERSTATE data for the .LVL lumps should be changed, to support other features in future. Currently, it consists of the move list, followed by three 16-bit numbers, being the mark position, level version number (minus one if you have not solved it), and the length of the move list.
02:49:17 <zzo38> One thing I want to include support for (in this and other files; there are many places where it would likely need adjusted) is multi-byte moves, which may be needed to support coordinate input (I cannot think of any other reason why multibyte moves may be needed, though).
02:50:14 <zzo38> So, the proposal is that each record has a one byte record type, two bytes giving the data length of the record, and then the data.
02:52:30 <zzo38> Also, the USERSTATE data for the LEVEL.IDX lump could store a bitmap of solved levels for quick access when displaying a list of solved/unsolved levels and when otherwise using that information in a SQL query.