No replies to this topic

[Lilferret]

There are a lot of feelings about launch modules and how PGI is implementing them. I am a fan of the Launch Module idea but have a few suggestions that may make them more useful and more appreciated by the community.

Public
Keep this like it is. this is great fore "free to play" accounts and gives them a better way to play the game with strong controls.

Premium
There are some good things here and as a whole I think the community approves.
Changes I suggest would be to allow Cbills and Achievements to be attained. There is little reason to disallow this and the risk to the game balance or community is minimal. Sure if someone wanted to exploit this to grind Cbills or XP they could but they would need a lot of cooperation or computing power to achieve this with an end result that doesn't really affect game play or the community. Also, make this free with premium time or MC per drop without premium.

I also suggest a League variant
Either MC per drop, or MC per length of league
This would assist leagues.
The following options would be available.
Registered clans and pilots
granular drop requirements
Pilot Ready
Defined drop decks
Automatic Group Assignment
Drop Command


More information on these.

Granular drop requirements
On top of overall league requirements each drop may be defined. For example in drop 1 the clan must bring at least 6 light mechs and have at least 4 ECM, may not bring artillery, air strike or LRMs, and no chassis over medium are allowed. Once these conditions are in compliance the drop ship may be made ready for league drop. Defined victory conditions or tie breaker rules.


Registered clans/pilots
Some leagues require clans to send in pilot rosters. After the creation of a league the owner of the league can use the registered clans to set up ladders and only registered pilots can join drops. The clan will not be able to ready their drop ship until all requirements for the league, specific drop requirements, and pilot roster are in compliance.

Pilot Ready
Pilots on the roster may join the league module in a "Ready" state to prepare for a drop without actually being part of the drop.

Defined Drop Decks
The Drop Commander for each side may pre-generate drop decks, as well as edit them on the fly. They may specify who is in each drop and which chassis they are to bring, or which weight class (equal to or less than specific tonnage)
Example>
Lilferret / Drop 1/ JR7-D
Lilferret / Drop 2/ Light =< 30 tons
Lilferret / Drop 3 / Light
Lilferret / Drop 4 / Jenner
Lilferret / Drop 5 / Any

Automatic Group assignment
If a pilot is in the drop ship in the "Pilot Ready" state mentioned earlier, and the drop ship enters a drop in which that pilot is assigned in a Defined Drop Deck, they will be automatically added to the group for that drop. The pilot will appear in a call out color if they are not in the mech that they were assigned to drop in if applicable. If a pilot ends a drop and is not in the subsequent drop they will be removed from the drop group and be placed in the "Pilot Ready" state until they leave the League Drop Module.

If a clan is registered in a multi-week event the designated Drop Commander may generate or modify these lists at any time in accordance with the league regulations. The league may reserve the right to not allow Drop Commanders to modify roster and instead submit roster changes.

Drop Command
Someone in the League Drop Module may be designated as Drop Command. This could be any pilot in the module that is not in a current drop group. This person may launch games without having to be in that specific drop. It would be great if that person may elect to be in overwatch of the match allowing them to capture footage of the match in a free floating camera or in a mini-map type display with all mechs from both sides visible for post game review.