CycKath, on 08 December 2018 - 08:10 PM, said:
What you're talking about, though, was when everything was still owned under one roof. It's not like that anymore.
To add clarity to why this is unsettling for the IP and off-putting for Battletech fans:
In a best case scenario, they're attempting to do some legalese double-speak and say it's not canon (with a big nudge-nudge-wink-wink), while at the same time telling the fanbase that it is canon and to treat it as such. In a worst case scenario this is outright lying to the fans, on stage, at the "big" convention for the Battletech IP; and then releasing a "correction" at a later date, in a subdued fashion, and hoping that the fan base blindly buys the "related" products. Sadly, regardless of the case, in the end it will mean that CGL products will contain nothing directly connected to the video games; and that'll leave the fanbase angry and unhappy about the CGL products.
In addition, before anyone says, "Well, the HBS stuff is just ideas." Remember that they went to a part of the Inner Sphere with no lore, no governments, no factions, and no specific characters written for it. That means that everything created was created BY HBS and FOR HBS . . . all for the video game side of the IP. According to CGL's "corrective" statement, that means that they can't actually touch it. That would mean that the Aurigan Reach "lore book" isn't going to be connected to the game in any way, for people who were hoping for that; and even the naming might be only loosely related. Therefore, IF CGL secured some kind of license to make the connection a reality, then that'd mean they'd already have a means of establishing license connections to unify lore, mechs, etc. between Microsoft and Topps (the two respective owners of the electronic and physical sides of the game, who the sub-licensees would need to go through) and they're just employing selective unification for the sake of alienating a section of Battletech fans. That doesn't make the situation or image of CGL any better in that case, either.