For those that don't know what abba caving is, you should refer to this topic here.

Anyways, after each game of abba caving, we always bounce around and waste time trying to verify how many points each person has gotten.

I've decided to write up a program that will help speed up this issue, currently on the CE. Which of course means immediate backwards compatibility with the CSE.



I have ideas on how I want the input interface to be for telling the calc how many of each item is present. It will also store the list into Archive and recall it each time the program is run, so you don't always have to reconfigure the values. That's essentially the setup for first time run.

I plan to port this to all the z80 TI calculators, for fun. And because, why not?

Code currently sits at 800 bytes, and now clears the screen out below the title to make room for the main menu.

Little bit of an update, I've nearly gotten the ore counting bit done, and it figures in the scores as it loops through the ore types. I also have it set up to run against the dungeon artifacts, but so far it isn't 100% completed. I still also need to add in the totals screen. Plus I still need to add in the surprise function that hasn't been mentioned yet.

Project is sitting around 1800 bytes. I have places that need cleaning up, mostly identifiers for the Ends. Might do that in Tokens once the program is 'completed'.

Latest progress:

This now counts all ores based on scores, ignores any ores that has a score value of 0, and tallies up the values after you input all the amounts of each item. At most, you can say you have 36 stacks of any ore, or 36 dungeon items. For ores, you input stacks and how many loose, which is 0-63.



If you watch, first screenshot shows first time running the program. Second one shows running it again. Second shot shows off changing the points for some of the items, and you'll notice that when I go to enter the scores, it ignores the ones with a value of 0.

Also, because I want to keep an online backup of my code as it is now:


Code:


This is, in no way, my final version. Please don't offer suggestions to things, as I still have more to add and a lot of clean up to do. Thanks.

Very cool! I bet this makes things waaaaay easier when counting, though I wouldn't know, as I can never get on when you guys are playing a round.

You should definitely find a way to get in on an event.

I'm running into problems writing up a count down timer, and it's bothering me. I can easily deal with the minutes aspect (got the code for that to work no problem) but I can't seem to get the 60 seconds aspect to work properly.

I'm still fighting with it, hopefully I'll have something soon. I want to set it up so it's all set up in one loop to determine how many minutes to run the event, and start/cancel the timer while the clock is in progress.

Any thoughts on the screenshots?


Code:


The Text( line there gives the minutes. I've tried going with a few variations for the seconds, but have not been successful on making it work. Thought I'd post the code in case someone else might want to offer up ideas on it.

I like that you give people the option to enter how many stacks and how many remaining blocks of each ore they have, rather than needing to compute 3*64 and hit an arrow key 192 times. The screenshots look great to me, and other than not knowing what the timer will look like, I see nothing I'd suggest changing in the screenshots. I know that I'll want to use this tool the next time we Abba Cave on the Cemetech Minecraft server, for sure.

Need some help, guys. The following code isn't updating properly, and I'm not sure why.


Code:


I know the last part of the Text( probably isn't completely correct. I've been struggling to get the seconds to display properly while messing with this. I've tried this in a For( loop and a Repeat loop, with the same results. Need the While loop because of the way I plan to set this up.

Things do finally update to 13 : 120 at some point, took a while to get there.

Any help resolving this aspect would be greatly appreciated.

Try this:

Code:

or if you have a color calc:

Code:

That works much better, and now it actually updates. I run into a problem at some point that seconds has 3 digits, I have no idea exactly when that happens, though. Going to do some more playing around with it when I have some time. (This is more a note to self than anything, so I remember what I need to adjust.)

Thanks for the help.

That is easy: you don't erase the numbers, so when going down from 10 to 9, the 1 will be overwritten, but not the 0, so it looks like 90 or so. You can display some extra spaces to erase them.

*bump* How's this going, tifreak? Did you repair the problem with three digits appearing, or does it still exist?

Apparently, it's not generating a 3 digit spot. It's the fact I'm using a single Text(, it shifts over to the left. Going to mess with the Text commands, make it so things shift around properly.

Honestly, this was the hard part of the timer, thanks to PT_ for helping me fix my issue with showing seconds.



The first bit counting from 10 minutes, where it goes to Time!, that's because I hit the cancel button. Just want that to be clear before someone makes mention of it :p Next part is to get this beastie to adjust how much time you want for a match (thinking setting default to 30 minutes, adjusting by 5 minutes (maybe?) down to 15 minutes and up to 1 hour.

Thoughts on the times?

Those sound like very reasonable bounds. Why have limits at all, though? Would it be harder to make it increments of 5 minutes, but down to 5 minutes and up to (whatever)? I suppose the most difficult part there would be erasing hours, but you'd have to do that for 1 hour anyway.

Well, for 1 hour, it will show 60 minutes, before counting to 59 : 59, so hour is irrelevant.

Anything less than 15 minutes for a match is just silly, there wouldn't be time to do anything. Anything over an hour, well.. I dunno, is there any reason to have a match longer than an hour?

Well, since no one has offered up a counter argument on this, 60 minutes will be the max time, and will be integrated into the overall program! This will entail mostly adding in the clearing function, and placing text so it looks nice to describe what you are doing at any given time.

So, overall, the program works and is functional. I've done some cleaning up of the code, could probably do a little more but I'm not truly sure it's worth the effort. Going to share with the one person that I know will be able to at least understand how to use it, see if it works for him, and release

A couple of comments on this:
1) I couldn't figure out how to quit from the score configuration screen. [CLEAR] or [MODE] to immediately quit from that would be helpful (and obviously if it's the first run, it's fine it that does or does not reappear the next time I run the program). I eventually pressed [2nd], but I'm not sure if that's supposed to be Quit or Apply. I'd say it's confusing for Quit.
2) On the Set Timer screen, add units (minutes) after the number.
3) Cancel after starting the timer makes the timer end, but doesn't quit from the timer mode. Is that intentional?

Other than that, great job! I look forward to seeing this gain wider usage.

2nd is mostly a confirm button, the readme is going to be far more comprehensive for the final. I wasn't sure where to put that on screen, since there isn't overly larges amounts of room with all I put up there.

Not really sure what you mean in regarding adding the units after the number?

The way I have it set up, pressing cancel or running out of time goes to the same routine, to save space.

As per recommendations, I've added in the : 00 behind the minute selector, and I've added some helpful instructions when starting the program.