jimmyzimms wrote:
Our sister site specialist-arms is the center of things BFG related. The lists are buried in the various PDFs themselves. You can linked out to the OG lists, the 2010 version, BFG-R, BFG France, ASC, etc here
http://www.forum.specialist-arms.com/in ... pic=5203.0You should talk with the chap Horizon over there about things as he's one of the main BFG dudes.
He didn't respond, I sent him a PM, so if you know the guy and can reach to him that would be helpful.
Ok, my plan for the next pull request is:
1) Next version of Solar Auxilla for HH,
2) Necron fleet list for BFG as a PoC,
3) Implement latest changes to Legion Astartes HH,
4) Also I am thinking of adding a Badab War "generic chapter" army list.
What do you guys think of 2 and 4?
Also I took a peek into war/js/*.js files and there are three topics:
1) The "formation limit per # of points" seems to have an issue, i.e. the first formation of given type is not taken into account. I will investigate that later and fix if needed.
2) Allies. I wonder if there a better of doing allies. At the moment the list creator is forced to hard wire
allied list into the basic list, which tedious. Have you thought about this? Anyone considered "list inclusion mechanism"? I guess it must be difficult due to "reuse" of ids.
3) Formation stats in print. At first it seems daunting because that would put a lot of work on reweriting a lot of text and also would have complicated a lot existing json files. And the I thought that it might be possible to create a base of unit stats in separate json files. e.g.
Code:
{"id":505, "name":"Landing Craft", "pts":350},
would be enriched with optional attribute "stats"
Code:
{"id":505, "name":"Landing Craft", "pts":350, "stats":"landing_craft"}
,
and "landing_craft" stats would be kept in another generic stats.js. Possibly one per "supplement".
What do you think?
_________________
I am
Army Forge contributor, so if you need to add something or you have spotted a bug do not hesitate to contact me.