Faction Play was always meant to be the playground of dedicated units of experienced MechWarriors who play in organized and communication heavy groups. Internal structure of who does what within a unit is completely in the hands of the players and unit leaders/officers. This isn't the problem area in Faction Play, the problem stems from the various roleplaying aspects when it comes to lore and the BattleTech Universe. Any number of methodologies and systems can be designed to create battles that integrate into Faction Play but there will always be various blockers that will be discovered when it comes to the mixture of technical implementation and needs/wants of players. The reason I'm bringing this up is, in order to move forward there will have to be give and take on both sides of the equation here. Similar to the discussions that took place previously. There is still a mountain of features that were requested by the community that is still on radar but the need to get the first step of a Faction Play update was to get the key components of a new system in place in order to facilitate the new era of Faction Play.
So let's dive right into this. The writing method used in this post will be a generic design spec and numbered in a manner in which feedback can be directed at key components of the design.
1) Choosing a Faction for Loyalty.
1.1) If a player chooses to be a Loyalist to a Faction, this selection should be persistent to the player's profile.
- This ensures that no matter which subsequent role a player chooses, it will not affect the overall profile Loyalist selection.
- Essentially this allows a player to always fight under the banner of their selected faction without ever needing to switch or display a 'temporary' faction alignment.
1.2) The selection of Faction will be done on the Faction Details (will need to rename this tab) pages which display information about all the factions available.
- A button will appear on each faction's detailed information page which will allow the player to pledge loyalty to said faction.
- The player must be warned that the selection is permanent.
2) Earning Loyalty Points (LP) After Pledging Loyalty
2.1) Faction players will earn LP in the same manner as previously with additional bonuses.
- When a player plays a match with their Faction in a Conflict, they will earn maximum LP for their in-game actions.
- Participation in war obligations while the Faction is in Conflict.
3) Expanding LP Gains Outside of the Player's Faction's Conflicts
- Players should be able to gain LP even when their Faction isn't directly related to the current Conflict.
- The broad term "Alliance" will govern these gains using specialized tables of rewards depending on which Factions are part of a given Conflict.
3.1) The Alliances
- The Inner Sphere Factions will be split into two Alliances.
- While alliances are not strictly lore, for game purposes and keeping queue buckets to a minimum, they serve a major role in allowing players to remain loyal to their faction and still gain LP
- There needs to be 2 Alliances in both the IS Factions and the Clan Factions
3.1.1) IS Alliance 1
- There is a somewhat natural alliance between Steiner and Davion. Adding to this, is a more neutral association with FRR.
- This Alliance (Steiner/Davion/FRR) will always provide LP to their respective partners.
3.1.2) IS Alliance 2
- While not as strong of a bond between Steiner and Davion, there is a loose affiliation between the Factions of Kurita, Liao and Marik.
- This Alliance (Kurita/Liao/Marik) will always provide LP to their respective partners.
3.1.3) Clan Alliance 1
- While Clan Factions were never really 'friendly' toward each other, there was a slight resemblance of tolerance between some of the key Factions involved.
- Clan Jade Falcon/Clan Ghost Bear/Clan Smoke Jaguar had the strongest sense of tolerance among the main invasion force.
3.1.4) Clan Alliance 2
- Wolf was always the lone wolf (no pun intended) when it came to Clan pride over being a good neighbor and this was shared by the secondary Clans that entered the battle later.
- Clan Wolf/Clan Nova Cat/Clan Steel Viper/Clan Diamond Shark would work best as the second Clan Alliance.
NOTE: Yes, there were the Wardens and Crusaders but the volatility in those alliances was so fragile that using that division would mean Jade Falcon would NEVER fight with Wolf. See section 3.2
3.2) How LP is rewarded when a Conflict is in play that does not include the player's pledged Faction.
- The Alliances outlined above will never be in a Conflict within themselves. (e.g. Steiner will never be in a Conflict with FRR)
- This allows all Factions to have an alliance member involved with all Conflicts.
- In the following tables, all indicated LP gains are for the Faction Player's pledged Faction only. (If you are a Ghost Bear Loyalist, all tables are indicating LP gains from Ghost Bear.)
3.2.1) Case 1 - Steiner vs Marik
- In this scenario, all loyalist players in alliance with Steiner (either Davion or FRR Loyalists) will be able to fight on behalf of Steiner while still earning LP for their pledged Faction.
- The amount of LP would be reduced but still significant enough to participate.
Table 1
In Table 1, you can see how this plays out in terms of which Factions will still generate LP when backed by Allied Faction Loyalists. The green squares represent a Loyalist Player playing for their pledged Faction. That player will earn 100% LP while playing during that time. The yellow squares represent LP gains when fighting during a conflict that an ally is involved in at a 60% rate. The orange squares represent Factions the player would not fight for as they are part of the opposing alliance. (Remember, allied Factions will never war with each other. This means there's never a case in this scenario of not being able to accumulate LP)
Table 2
Table 2 extrapolates this further to show the Clan side of things.3.2.2) Case 2 - Kurita vs Clan Ghost Bear
- When it comes to a Clan vs IS Conflict, things need to change. The IS knows that an invasion of any type from the Clans is a bad thing. The leaders of all Factions know that a fight on that front is a fight for the greater good.
- Clan vs IS conflicts will treat all Factions on opposing sides as allies. This means Kurita Loyalists will earn 100% LP gains from Kurita. A Davion Loyalist who comes to the aid of Kurita during this Conflict will earn 60% Davion LP.
Table 3
Table 3 shows how the IS side of things change when the Conflict is a Clan vs IS Conflict. And again, the same is reflected on the Clan side as in Table 4 below:Table 4
4) The Big Problem Areas- The following are the biggest glaring holes in this system and while there are some heavy handed solutions to them, it's not what's intended to happen here.
- You the community will have the biggest voices here so please share your thoughts.
4.1) The Faction Selection for Loyalist is currently permanent in this proposed system.
- Should a Loyalist be able to switch Factions? (Remember, the major feedback so far in this area is that a Loyalist would never switch.)
- When would a Loyalist be allowed to switch?
- Would there be penalties of some sort involved in doing so?
4.2) When it comes to Section 3 above, there's a big blocker in place.
- If the Conflict is an IS vs IS Conflict, there is NO way that Clan Loyalists can earn LP.
- If the Conflict is Clan vs Clan, the same thing happens on the other side, meaning IS Loyalists cannot earn LP.
- One suggestion made internally was to just provide a base LP payout when these situations arise. For example, if the Conflict is IS vs IS and a Clan Loyalist plays in the Conflict, they will still earn a 25% LP gain from their Faction for doing so even though it contradicts the idea of a hard core Loyalist.
5) Let's Do This
The main takeaways from this post are as follows:
- We want to make sure that Loyalists do not have to switch Factions to participate in FP
- We want to make LP gains consistent for all Factions.
- This design spec has NOT been through a tech review so there's no guarantees that everything is technically possible.
- This is a big change and will require quite a bit of development time to implement.
- This is not a straight up "this is happening and it's the only way", but it's the strongest candidate that some of you have already touched on in previous comments/suggestions as well. Strongest doesn't mean best/only plan.. it means it fits the majority of criteria with a give/take approach.
This is the FIRST post of a discussion that will be followed just like the other discussions we've had previously. I want to take the same tone as last time and keep it a discussion and not a corporate refined response system.
Looking forward to your thoughts on this spec and trying to finalize something soon so development can start on it ASAP.
-Paul