Introducing...Joe's All-Purpose 40K Measuring Device Includes 1", 2", 6", 9" and 12" measurements Technically 3" as well LOL "Why?" you ask. Because I wanted one tool that would measure all those distances And mainly, because I could.
make it in two parts with a small space between, and you could slip the knight gauge into it to make a compact carry case to stop the knight thing getting bent or dinged, and the same for one of the combat gauges they make
just use the space where the riser is to make a pocket, and then some kind of sleeve for it out of like a felt
instant multi-tool/carry case that does 12 and below and solves the main issue that the knight gauge always presented to me which was "how to stop thing getting bent by accident"
which is really the only reason I haven't bought one yet
can't wait till I can upgrade to resin printer from my i3, some of the stuff you can get like shoulder pads and stuff for minis, just astounding.. and as for Fusion360, well I gave it a go as a beginner but it was just too powerful, I'm sticking to straight lines and Sketchup for now... it's like the MSPaint of CAD
I've spoke with alpha and we agreed that once a fresh, usable set of datafiles for HH is produced, I'll make the cleanup (involving a change of lead dev...) and we can once and for good forget that disaster current dataset actually is.
I really don't think the file size is that important. It's the memory footprint the file takes when loaded into app memory - and it doesn't correlate with file size that much. Many of those 200k lines are probably empty arrays (like <constraints/>). Those empty lines will be no more when 2.02 hits, and they sure as hell make no difference for the app right now.
However, a good point is that maybe until 2.02 hits you guys could work out the guidelines/framework.
Also, since it's a huge amount of work, I think you can already start building the files with 2.02 BETA.
It'll get published sooner than you finish HH I bet.