v0.6 - Fixed Command Destroid missing from Phalanx & Spartan
v0.5 - All Zentraedi Force Cards implemented. However Support Options (besides Regult Squad), Built-In Upgrades, & Special Characters are not implemented yet.
Regult Artillery Squadron
Regult Attack Squadron
Regult Attrition Squadron
Regult Recon Squadron
v0.3 - After the learning curve of figuring out the initial build out of the Army Builder system adding the Destroids was pretty quick.
Area Denial Destroid Squadron
Armored Destroid Squadron
Artillery Destroid Squadron
Brawler Destroid Squadron
Close Quarters Destroid Squadron
Fire Support Destroid Squadron
v0.1 - This reflects about a week of research and figuring out the Army Builder ABCreator tool. It's rather complex, almost overly complex. I however was able to figure out how to build the rules needed to reflect the unique status of Veritech vehicles between their 3 modes. I've also implemented the entire Veritech Squadron Core Card along with the Built-In Upgrades, Special Force Cards, Support Force Cards, and Character Cards that are for the Veritech Squadron. Known Issues include the fact that I have not built in all of the rulesets yet so you can do things like violate force organization by having more than two Support Force Cards and Built-In Upgrades. Also the Built-In upgrades enforcement does not pass down to the child units yet forcing them to include the upgrades. Same with allowing a Character Card to only be used once per force.
Awesomness. Thanks for undertaking this. I've played around with Army Builder, modifying 40K files for custom units, but never started a datafile from scratch, let alone a game system from scratch. I'd love to offer to help you, but you're already in deeper water than I can swim in.
I'm hoping soon I'll have all the core rules in place so it'll just become data entry at that point. Where you can help out is I'll release some sample copies along the way to test and I'll need feedback from people who have played a lot more than I have to make sure the rules I build are correct.
I figured out a huge core logic mechanism over the weekend so now I can start implementing restrictions like you can only ever have 1 special character in an army and minimum Force Cards and things like that. Once I feel I have everything in place for the Valkyrie Squadron I'll put up a file you can load and run through to give feedback on how it's working and the validity of the rules.
If you play any other games that there are AB files for, pick one you're familiar with and try opening up the datafiles for that game. That'll let you examine how others handled different features and restrictions. It should be a little easier than trying to learn purely from scratch.
I play WH40K, WarMachine, and Dust Tactics using AB. I've been using the WH40K rules as learning source but the issue with that is their stuff is hyper complex on top of AB already being a massive learning curve. Also the AB documentation is outdated which makes learning slower when I have to post to their forums and hope someone responds and that person has an answer.
I've got a sample data file to test. You may have to download and import the file as I could not get the secondary source method to work anymore in the latest AB 3.5 version. I'm not sure if it's an issue on my side or theirs but I've reported it. The data file lets you create a Valkyrie Squad from the force card along with all of the upgrades associated with it. I've tried to implement as much of the game rules as possible that relate to this as well so it limits you to only 1 Special Character, 2 VF-1S, etc etc.
Take a look and provide feedback please. Just remember some things are setup because of restrictions in AB.
One suggestion off the bat - in the Support Force Cards options, there are two entries that just say VF-1R Upgrade. One is for upgrading 2 VF-1As, and the other for upgrading the VF-1J for the squadron leader, but I had to figure that out by trial and error. Maybe add a (VF-1Ax2) and (VF-1J) to the descriptions?
"I will BURN YOUR HOUSE DOWN! With the LEMONS!" - Cave Johnson
Because of the way AB works I can't manipulate individual sub-children, you can only apply something to all children or the first child of a type. So in order to allow someone to upgrade any of the 1A or the 1J I had to allow the person to pick and choose the items they wanted so I couldn't force it via code but instead enforce it via a rule. So you can at any point check the VF-1R upgrade option on a child item even if you didn't pay for it and the top level one is the payment for it, I agree it's a bit confusing.
I wanted to make them a * like add-on like the Valkyrie Wing but I can't because of the type of item they are. How about I add some info to the Description like "After selecting you can upgrade either 2 x VF-1A or a VF-1J & VF-1A to be VF-1R versions in the units below."
I'll play around with it some more to see if I can make it more user friendly. I think I can even hide the VF-1R option on the children if the upgrade option hasn't been checked. Maybe I can find a way to make them * addons like the Valkyrie Wing I hadn't before.
I don't feel like renewing my AB license to enable automatic downloads - can I still download the updated roster file from the earlier link?
They actually moved away from the yearly renewal so if you have a license that was bought after a certain time you automatically get updates.
However even if you don't fall into that and use the older version you'll still always get "data file" updates for free you just don't get AB updates. As far as I know I haven't done anything specific to AB 3.5 so my data files should work with AB 3.2 and forward.