Code:


I know that the offending bit of code is "If (E-L1(L2(3))=~4 or E-L1(L2(3))=4) and L1(E)=0:Then" because it hits the Pause before it, but refuses to do anything after that. It makes no sense because the values are correct.

I can't figure out for the life of me why the checkers won't move now.

And yes, all the values match up properly. There doesn't appear to be a reason why it's not working. :< I will, of course, keep testing.

So, update.

I've managed to make this move each player's checker once. To the right if you are player 1, or to the left if you are player 2. I'm not sure why you can only move once, but at least I'm finally moving this off in the right direction, after days of no progress.



I'm thinking it's some form of list issue, but I'm not sure. I'll do some more extensive testing tomorrow sometime.

code for the engine thus far:


Code:


Far from clean code, just been moving things around and hacking things together to try to make things work. Cleaner code at some point in the future.


Edit:

Note to self, I need to shorten the clearing of checker pieces, so not to clear out the board black lines.

Code:


Now we move around properly, but you can only move a checker once. After that, you can't move it again, and I've no idea why.


http://tifreakware.net/tifreak8x/checkers/AB.zip

That should be the program and the pic var needed to make it work. For now, to speed up testing, I've just stored the board and checkers as a pic var so I can quickly test changes made to the code.

Last edit, I hope. You use 2nd to select a checker. I haven't added the code yet to deselect your checker.


Edit 2:

Need to add in code to block I from changing if the cursor is on the border and doesn't really move.

Edit 3:

Need to change how determining distance of movement is done via cursor variables instead of subtracting last known list element to new list element. Since on the first shot, it was +/-4, the second time you go to move the checker, it was actually -3/+5. Can't use that method reliably, so verifying that L2(1/4) +/-19 and L2(2/5) +/-20 will give me the results I want!

So! Checkers now go all the way across the board, they don't overwrite other checkers, and you can only select the checkers that is for your turn.

Things to do now:

-Make it so only does the I switching when the cursor actually moves
-Make it so you can jump opposing checkers
-Make it so you can be crowned
-Need to be able to remove the selection on a checker, with Alpha
-Maybe make it store as a Picvar when the board is generated as a quick way of restoring the board for a rematch?

Anything else I'm missing?

Edit:



http://tifreakware.net/tifreak8x/checkers/AB.zip

2nd to select, Alpha to cancel selection, MODE to exit the program.

Thoughts?

Yes! Looks perfect!

You've really embraced the 84C tifreak, superb work as always .

Thank you tr1p1ea! There is still a bit to do with this, but I think it's finally coming along nicely

I need to add a box off to the right that shows the color of the checker for whose turn it is. Maybe something that shows how many pieces lost? Not sure that's relevant, but might assist in giving me a form of win detection.. Hmm..

I finally have made it so you can take eachother's checkers!

Thoughts?

Congratz, looks great

This is really coming along tifreak, and looking wonderful!

Thanks guys!

I promise it's more responsive than what the screenshot shows, doing animated screenies makes key presses hard to detect or something.

I'm not sure I'll be able to support multi-jumping. I've not thought of a way yet that won't bloat the code horridly.

I still need to have it display who's turn it is, and make it so accidentally hitting the border of the board and pressing again in that direction doesn't break things.

It looks pretty responsive to me from the screenshot, tifreak8x. How do you currently support single-jumping that would work poorly extended to multi-jumping? I was thinking you could have the user specify a sequence of steps, as long as each step involved jumping over an opposing piece. The first step to not involve jumping an opposing piece would prevent the user from adding any more moves to the chain.

Basically, anytime you select a checker, it stores those values to 2 elements in a list. Player 1 gets 3 elements, player 2 gets the same. It also stores the last list element accessed for the board list.


Code:



Edit:

I've updated the main Checkers file with all the revisions I've made via the test programs. It all seems to work happily together, so now I just need to figure out how to make it not break with the cursor issue.

Alright, I've fixed my issues with the cursor, so now it doesn't seem to break. Hooray!

Also, I've done this:



What do you think? Good placement? The color of the number is going to change based on the color of the checker for the player.

Looks perfect, tifreak8x! Good compromise of player number and using the player color. I'd change the text to something like "Turn: Player X", just to make it abundantly clear what the player number is referring to. That's just me, though.

Alright, I'll make the modification afterwhile and post another screenshot

The only things left are crowning and making it reset for a rematch. Should I worry about #2?

Crowning shouldn't be horrifically hard, I would think. Only problem is, this game is sitting at 5356 bytes in size. No idea how large crowning will cause this to go. I really need to see if I can downsize the overall game by combining some things..

Made some progress on this. Shaved off 156 bytes from the game by combining a few lines.

Also worked on the ability to king pieces. Realized I can't use Pt-On( to do what I need, will have to come up with some Line( commands to indicate kings.

I still need to see about getting it to move when a piece is kinged, as it was used the old setup, and that setup fails at life.

Hopefully I'll get this figured out tomorrow.

Sorry for letting you combo-post like that without any interruption. The screenshot looks much better; thanks for taking my suggestion. I wouldn't worry terribly much about #2; why not just make the program close when it ends?

Well, I don't have any form of detection in place to determine if there is only the 1 checker left. And I don't think I'm going to bother adding that. But if 2 students want a rematch, it'd be a little easier if I had a temp pic var for such things to load from when they hit.. Say 'clear', and it just reset the variables and lists and such and redisplay the temp pic. After they close the game, the pic would be deleted.

Progress! I now have it set up so that when the red checkers hit the end of the board, it will mark it as kinged. Now I just need to make it so it will go back the other direction, and make that code work for player 2 as well.