Single Comment

For the Dragon Horse and Dragon King, where you have a checkride, you don't also need a checkleap. But this is just redundancy, not anything that would break these functions. The *L functions don't have this redundancy and seem alright.

When you say the code does not recognize these pieces, please be specific about what you're doing, what you expect to happen, and what happens. The pieces are not objects that are either fully recognized or fully not recognized. I could move these pieces, but I could not see legal moves displayed for them. Also, other pieces on the same side could capture them.

I think both problems are due to the piece labels not being purely alphabetical. With piece labels that have non-alpha characters in them, you cannot rely on islower and isupper to tell the sides apart, and you cannot rely on onlylower and onlyupper to provide a list of all pieces belonging to one side. You will have to rewrite any code relying on the assumption that piece labels are purely alphabetical. Alternately, you can use a smaller set that does use purely alphabetical labels for pieces. I never use the Alfaerie: Many set and do not encourage its use.