Another reason: synchronize our efforts so that creating BattleScribe files also allows immediate publication of AB files. This would probably win over AB data authors to do BS files, thus leaving AB as second-thought system.
Net result: we have more data authors, BS gains even more dominant position.
It would be a considerable task to build one for 40k, because the data is much less structured than KT. We have all built our KT catalogues pretty much the same way. The 40k cats have many quirks depending on who implemented them and when.
@amis92 The reason that AB was “horrible” back in the day was that the only solution for creating army lists was to do it on a computer. Their app on iOS/Android was entirely a viewer app. And their support on non-windows platforms was awful.
@amis92 yes, I have actually done some dev work for AB back in 7th but strictly for creating my own custom scenario units, and it is a painful and messy process that is as opaque as a brick wall (the same could be said for most of LWD's products, with the exception of realm works)
Considering the file structure is radically different, porting would be pretty much impossible, so better to just work on a XMLreader/Output viewer for BS that is better
That was pretty much the only reason I used AB back in 7th when there was file parity, pretty much strictly because the print output was easier to customize and work with