4 replies to this topic

[Nothing Whatsoever]

After rereading the Command Chair section about how Clan BattleMechs could be Built/Customized, I was thinking that having separate individual Clan Omnimech's for each Configuration is going to unnecessarily overfill the Mechlab since the base configuration, the core of the Omni will not be changing between them (which I happen to like as it stays to the rules as mentioned in the post).

Currently the largest packages will include 24 Mechbays for example to handle that. Then from what I've looked at so far Omni's can have plenty of Alternate Configurations.

• Warhawk (Masakari) - Prime plus seven Alt. Configs
  
• Timber Wolf (Mad Cat) - Prime plus ten Alt. Configs
  
• Stormcrow (Ryoken) - Prime plus ten Alt. Configs
  
• Adder (Puma) - Prime plus seven Alt. Configs
  
• Dire Wolf (Daishi) - Prime plus nine Alt. Configs
  
• Summoner (Thor) - Prime plus thirteen Alt. Configs
  
• Nova (Black Hawk) - Prime plus nine Alt. Configs
  
• Kit Fox (Uller) - Prime plus eleven Alt. Configs

So, I was thinking, instead of having so many redundant core Omnimechs (three of each in the package) taking up all of those Mechbays, what if the packages would instead be 1 Mechbay for 1 core Omnimech, that then provides the appropriate number of modular pods (with weapons, ammo and equipment) for each included configuration (the Prime and two Alt Configurations)?

Having the Pods with various hardpoint layouts is certainly a good idea to have and there would simply be a need to have a new category Tab in the Mechlab to swap Pods on the core Omni; similar to how we have the Weapons Tab, Ammo Tab and so on to customize the Omni's.

So the number of included Pods for each unique Omnimech in the Clan package could be:

• Head - three, one for each configuration in the Package
  
• Left Arm - three, one for each configuration in the Package
  
• RIght Arm - three, one for each configuration in the Package
  
• Left Torso - three, one for each configuration in the Package
  
• Right Torso - three, one for each configuration in the Package

Therefore, the package would have, for example, with the Kit Fox (Uller) package, one mechbay for one omni and 15 modular pods to use to build the Prime Configuration and two Alternate Configurations along with the appropriate equipment on each configuration.

Hope that makes sense, what do you think?

[Hythos]

I could see having one Omnimech, and all configs available to all chassis.
Tripple exp required per skill-box, and call it a day.

Clan Mechwarriors are supposed to be the most skilled, and responsible pilots ever - make their requirements to advance reflect the duty, diligence, and skill by in-game requirements in accordance to Clan Rules of Engagement.

[Almond Brown]

The MechBay idea does have a benefit though. You currently store a config (similiar or otherwise) and it is a "Click and Go" change process. With this single Prime config bay vs a build an Alt setup after every drop, without a required preset Bay per say, I can imagine the "in between" Mech re-configs becoming a nightmare given the rage we see when folks having to wait 45 seconds just to load in.

Edited by Almond Brown, 22 December 2013 - 08:09 AM.

[Gladewolf]

This looks like a good suggestion, but we'll need to see what they do to the clan mechs in question first...who knows...they might make the cores totally different from one another....

Edited by Gladewolf, 22 December 2013 - 08:15 AM.

[Nothing Whatsoever]

Gladewolf, on 22 December 2013 - 08:14 AM, said:

we'll need to see what they do to the clan mechs in question first...who knows...they might make the cores totally different from one another....

Indeed, the Primes in the Clan packages should be getting a different look to go along with their C-Bill boost from what I understand, but making the cores different seems to go against how Omnis are supposed to be built.

We definitely need more info.