Storing to picvar should be made optional. Although I encourage using pics for fast loading or data storage to get around the RAM limitations, there are certain players who are extremely uptight about program file sizes, as I saw on certain forums in the past, so maybe they won't like if a Checkers game requires an extra 21 KB of archive just for 1 pic.

Yeah true. In many cases it's close to impossible to have enough features in small space anyway (especially RPGs, when you don't want to end up with 1 hour of gameplay)

Alright, I believe I've gotten all the glitches and bugs worked out. I've even gotten rid of a pesky bug where if you went to the edge of the board, and then tried to go that way again, it messed up part of the checker selection.

Now, I've implemented the remainder for the title area:



The number under Player: will change to the color of the current player's checker, along with changing from 1 to 2.

What do you think?

And all updates to the game have been integrated into the main game program itself. The game is now sitting at 5,202 bytes in size, without the above screenshot stuff included. And it sadly only offers single jumps. I'm not sure how to implement multi jumps, yet.

Is it me or the tokens position inside squares are 1 or a few pixels off to the right?

Ah ok. Weird then

Making things small can be a bit hard in BASIC since sprites are drawn with lines/pxl-on/etc, although I don't mind if it's very large, personally.

By the way, to gain extra speed, have you considered releasing another version of this game in hybrid-BASIC using LCDTOOL asm lib? The game would take the entire screen width, but be 160x165 (stretched to 320x165) instead of 265x165. Of course, it wouldn't be pure-BASIC anymore and the display might be affected (mostly by larger text), but maybe it would take less time to load stuff if drawn vertically. It could look like this (quick mockup):



The lib in question is available in the zip file of this sadistic disaster and was made by calc84maniac. Syntax is as follow:

Resolution+ScreenStartPos:Asm(prgmLCDTOOL

Resolution can be i (320x240) or 2i (160x240), the i being the imaginary i. ScreenStartPos can be any number from 0 to 319 (in your case, you would use 2i+27:Asm(prgmLCDTOOL).

I can't really say I'm impressed with that, as it makes the checkers and text not look so nice :<

I agree that the text is quite ugly this way, but the pieces are not looking so bad.
And the speed gain would be worth it in my opinion