mughzee wrote:I'm dumb. I dont' get it. Can you break it down real quick?
Edit: Wait, before I confirm me being dumb. Is it that simple that you just put down your starting number in the first and each turn just take away? Or, are you checking the the number of deaths each turn?
When you play necrons, you have to keep track of how many dudes you have left. If you get down to <=25%, you phase out and loose the game. In the past I've
kept track using 2d10. I've recently found that I'll make mistakes when I do it that way though. So I figured I'd make checkboxes to mark every time I fail a
WBB
roll.
ArbitorIan wrote:I don't know what any of this means.
Since I won't necessarily be playing the same list every time, the number of checkboxes I'll need will change from list to list. Rather than edit my check box
file every time I want a new number of boxes, I wrote a program to make the file for me. The first program was in perl, which is a handy language which ships
by default with most Linux distros, and is on OS X, but is a separate download for Windows. Further, the first program is command-line only. This isn't too
big of a problem for me, but not everyone is comfortable with the command-line. So I decided that given the majority of people here probably don't have
perl on their system, but likely have java, that I would rewrite it using that language. And as long as I was rewriting it, I figured go ahead and build a GUI
for it so that you don't have to be a console jockey to use it.
So both programs produce the same output (almost, the java version has a place for you to put some text that will be written out under the checkboxes), but
the java version is more likely to be useable in more places, and has a more user friendly interface. On most systems you should be able to just double click
on the jar file and it'll run the program. Jar files are like an exe for java, they contain the executable code and some other information that the system needs.
The cool thing is that they're just zip files though, so you can change the extension and decompress them if you want to know what's in one. I almost always
include the source code for my programs in the jar files I make, so if you wanted to read how the program worked (and knew java) you could unzip the jar
and read the Generator.java file. I didn't make the comment about the perl source because perl is different in that the source and the executable are the
same.