Right o! shoulda done that in the first place... you name by the  way im guessing is a reference to Aidan Pryde of the Falcon Guard?

Kodiak: Mechwarrior 2 Mercs (Loadout pages), Battle Tech Technical read out 3055 (reference book for Btech game), "Operation Audacity" by Blain Lee Pardoe... The Kodiak was a rare beast that was not mentioned much in novels or table top games so its info is hard to come across.

Atlas: Do i really need to site all of them? Im just going to sight a few. "Warrior Riposte" By Michael A Stackpole, 'Battletech Record Sheets 3025&3026", "Prince of Havoc - Twilight of the calns VII" by Michael A. Stackpole, "Storms of Fate" by Loren L. Coleman

Its a gray line. Authors ABSOLUTLY have sway in everything that happens in the way of new lore and old lore. TROs and "Official documents are broad swath ... generalizations? about the universe designed to make it playable and more streamline. Authors have the right to "create" new facts but they do so rarely with consulting the others among them and potentially the fan base.

an example is Snord's Irregualrs. A crack A rated Merc unit. Original named Cranston Snord's Irregulars it was modified to match up with the storyline and a TOE was created. This allowed other authors to use them, but they would ov course talk to the origional designer (Ross Babcock III). It originally started off as a pack for BTech, but evolved over the novels becoming better.

It also comes down to how controlling the licensing company is.  Take Games Workshop for instance.  They are very involved in the creation of books using their universe.


Platform shoes? 

I know the mechcommander version is incorrect. I'm just saying you shouldn't take the info from the games, they're all different.

Wonderful post, I have a small bit of advice not added yet.  Since you said you know a bit of Maya, and you are going to stick around and watch the project evolve, why not do a bit of training with Maya or Max and grow your skills.  Who knows how big this project will get, so why not train your skills up and maybe in the future there could be a role.  Just a thought.

well i'd be willing to give it a shot, im not skilled but i do learn fast. Right now im more of a write than I am an artist

hey guys gimi some feedback on what you want you maps to look like... i have an overhead photo of the map im working on right now. despite appearances its not flat... lots of hills.. is this something similar to what u guys need (once i have it finished), or am i totally off base.

OK... your going to have to excuse the realy crappy markings i made....

RED: Clan Start
Blue: IS start
Gray Box: Cities (skyscraper in mid, rural in the smaller)
Green Dots: Fortified locations (dono what exactly that means but oh well)
Yellow X's: Expected hotspots.
Black lines: major roads

Flow is very simple, fast and furious out in the open, and nasty short ranges in the cities. Most forces are expected to go for the city (objective or something), but some (light mechs/fast hovers) can rush north from IS base and try to go across the shallow sand bar to attack the clan base directly. Most of the terrain is relatively open, rolling hills and such, but the clan base has got a serious high ground position, but no direct routes to cities or the sand bar.

Areospace assets will mostly be used to harass units in the open, and secure the sand bar (both teams). Inf are going to hafta hitch a ride because of the vast open areas with little tree cover (trees are scattered across map). Mechs and tanks are going to need to be on air watch out side of cities, and on defensive inside of cities due to harassing inf.

that is at least my intention of how i want things to go... maps never survive contact with players however.