3 replies to this topic

[Surn]

Technically, the public matches could have an impact in CW. This is about how it could be implemented.

In wars there are often small skirmishes and patrol/recon encounters. They do not have large individual impacts. However, they are important operations and at times can be summarized as gorilla warfare.

The three public match game modes impacts upon CW or "the what".

Public match game mode impact on CW planets.

• Assault - Increases attacker drop deck tonnage by 5 tons. Represents increase in combat momentum/morale, salvage parts, confiscated fuel, ammo, etc. Maximum value for sector 10 tons.
  
• Conquest - Changes sector Defense mission into Counter Attack (Hold Territory). Representing a defeat of forces in that sector, but does not change ownership.
  
• Skirmish - Reduces Defender drop deck tonnage by 5 tons. Representing a small loss of resources by defenders. Maximum value for sector 10 tons.

This new meta matchmaker mode would be known as "Patrol." The basic idea is that attacker victories can gain tactical advantages. Defender victories maintain the status quo.





The advantages are placed randomly around the contested sectors to eliminate the possibility that a powerful faction would flood the public queue to gain additional advantages where needed. A small faction like FRR may be able to use this as a gorilla warfare tactic.

Programming Logic Flow or "the how".

Step 1, Gather Attackers.

• The specific game mode is chosen as it currently does.
  
• Only players with "patrol" game mode checked are included in this next search.
  
• If 12 players from the same faction are in the public queue for the current game mode, the matchmaker separates them for a "patrol."
  
• Intentionally did not define when the "patrol" check is run. This is meant to be optimized based on the current logical flow of which I am unaware. The matchmaker might gather 12 players and then choose game mode.
  
• The "patrol" matchmaker allows both 2 to 12 man teams and random players to initiate this branch of logic. It is meant to work within the current matchmaking logic with no changes.
  
• The "searching..." notice changes to "patrolling...".

Step 2, Choose the planet sector.

• Randomly, a planet that can be attacked by the "gathered attackers" is chosen.
  
• If no planets are available, a planet the "gathered attackers'" faction is defending that is less than 100% owned is randomly chosen.
  
• A random sector is then selected that is not under control of the attackers.
  
• if no sector is available, the 12 players are switched from attackers to defenders.

This process should only take a few seconds.





Step 3, Gather Defenders.

If the "patrol" group is in attacker mode.

• The matchmaker gathers 12 valid defenders, they must not be the same faction as the "patrol" attacker group but can be any combination of IS or Clan. This is to prevent making public matches into mini CW matches.
  
• The "patrol" matchmaker has 1.5 minutes to find opponents.
  
• If no opponent is found, the "patrol" group switches to defender mode.

If the "patrol" group is in defender mode.

• The "patrol" matchmaker looks to see if a valid defense is needed for any other "patrol" matchmaking queue. They must not be of the same faction.
  
• The "patrol" matchmaker has 30 seconds to find a mission
  
• If no defense if found the "patrolling..." message changes to "searching..."
  
• The 12 players are released into the normal public queue.

I am making one assumption, that the game mode is assigned at the beginning of the match making process. I make this assumption to take into account which game modes are checked by all the players involved. However, changing the timing of the game mode selection is likely trivial in this logic flow.





Data requirements

Each public match would need an foreign key to a patrol table. Default would be null. If you do not use a strict relational database model, add fields to the game/match table.

You will need to know:

On the games/match (whichever table holds game history) or patrol table,

• if a match was a patrol: binary/boolean
  
• the sector affected: integer.
  
• the game mode: I assume this already exists in the table or is relational to the table.
  
• Did the attackers win: binary/boolean

On the sector table, (whichever table identifies sector ownership)

• Attacker Tonnage Modifier: integer
  
• Defender Tonnage Modifier: integer
  
• Defenders in counter attack (hold territory) mode. There are a lot of ways you might be determining this, so I won't venture a guess at it.
  
• Reset all modifiers upon ceasefire

Possible Flaw

One thing to be minimized is forcing public queue players to face 12 man teams. However, this is already possible as teams can launch into the public queue. It may be necessary to exclude full 12 man teams. That said, I would NOT exclude them. It is extra logic.


Comments, suggestions, questions...
I may have overlooked something, but this seems solid for a quick idea to get more people interested in CW. This is not a sales pitch for a new game mode, it is a idea of how to implement a new game mode.

Edited by MechregSurn, 06 April 2015 - 11:14 PM.

[Metafox]

I like the general idea, though the presentation here is a bit overcomplicated. I'm guessing that PGI can't implement these ideas verbatim so it's probably best to present a basic idea and let them work out the details. I'd like to see public matches have an impact CW, though I'm thinking that public matches might also be able to tie into the CW logistics system that PGI has been trying to work out.

[HelBound]

I also like this idea. I like the idea that smaller factions may use the 'patrol' function to effect CW where perhaps they cannot hold planets against a larger faction like the wolves. Needs some work but the general idea is solid I think.

[Surn]

My hope is that by considering the implementation it could be more seriously reviewed.



what do you think about the advantages earned? Too much or too little ?