I have mixed impression about this mod. Princess Daystar made excellent and wonderful work with mech modelling. Her models are really amazing. But when you look at mechs’ loadouts you get many questions. They ALL are non-canonical. For example Koschei-5I with ten integrated in engine SINGLE heatsinks (with it’s heavy energy weapons, yeah) instead of 13 double as it must have. Koschei-5MC with 275-rated engine instead of 325-rated and strange mix of engine’s double heatsinks kit and installed double and single heatsinks instead 14 double. Maelstrom with 400-rated engine instead of 375-rated and so with less armor and equipment. Hoplite-4B with LRM-20 instead of LRM-15 and so with three tons less armor. Hoplite-4X with ammos in opposite torsos of their weapons. Coyotl and Pouncer mechs with not only different armor value for different configurations but also with engine’s single heatsink kits in a few configurations (Clan OmniMechs, yes). Poumcer has also either 4 or 5 jump jets, though it must have 5 permanent installed. Every variant which is made by Empress Daystar has non-canonical full head armoring (30 instead 18 or 24 instead 16 for Crossbow), but weak legs’ armor (and often weakened armor on other parts), ignores engine’s heatsink slots, often has strange heatsinks types mixing and other such problems. I can understand this when you create any custom or apocryphal mech (as Ares, Wildcat, Hellcat, Sambuca), but if the mech has canonical description and record sheets of it’s variants, you must use them.
A suggestion: instead of writing something like this report them as bugs so that i can actually see the bugs and fix them. I have dyslexia and misread things on the sheets quite a bit. Thankfully the mod devs i work alongside are nice enough to poke me when they notice something wrong.
the Maelstroms are being fixed in the next update regardless as again - it was brought to my attention through a bug report instead of a section i seldom if ever check.
Opinion about the mod (2 comments)
the Maelstroms are being fixed in the next update regardless as again - it was brought to my attention through a bug report instead of a section i seldom if ever check.