Creating CCP maps

From Valve Developer Community
Revision as of 14:23, 18 June 2016 by Fayti1703 (talk | contribs) ("ah advantage" -> "an advantage")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Creating a CCP type map is a little more difficult than your average TF2 map, due to the unstable nature of its gameplay (requiring more forethought and planning for balance) and also due to the "workaround" nature of the map mechanics (TF2 wasn't designed to support this type of maps, so the I/O connections get very hairy).

Team control points

Your team control points need to be setup in an overall "circular" arrangement. Pay attention to how the map layout affects game balance — it is usually a good idea to have a very symmetrical map to make sure neither team has an advantage.

So far, only a 4-point configuration has been attempted. And while more testing is required, the CCP author (Hovis) feels a good map can consist of as many as 6 nodes, or maybe more.

Respawn rooms

There are two basic ways to handle respawning with CCP. One is through team-neutral spawn rooms (that change owners with the node re-association) for each node, and the other is with 2 respawn rooms per node that are team-specific. This is a matter of taste for the map author, both can be made to work, but I find the "neutral" respawns to be easier to handle.

If you're going to use "neutral" respawn rooms, you must deal with a new issue - spawn camping. A very simple solution to this is to simply do away with func regenerates and make the respawn rooms exit only via map design, or clever triggers combined with func respawnroomvisualizers. You are free to make more than one spawn room per node, however be prepared for the extra-work that needs to be done in order to accomplish that task.

In either case, you will need some intermediate I/O control to make sure that players are spawning in the right rooms and at the right time. Generally, you will want players to spawn into the room associated with the most "forward" control point that their team owns.

The following events must be triggered (per team) when a node is captured (in neutral node setup):

  1. Enable this func respawnroom
  2. Set this func respawnroom to this team
  3. Disable the last func respawnroom
  4. Enable these info player teamspawns
  5. Set these info player teamspawns to this team
  6. Disable the last info player teamspawns

Early win detection

It is possible for one team to capture the opposing team's starting node before they manage to take it themselves. This causes a problem because the automatic win detection doesn't activate if not all of the nodes are captured, and the enemy team cannot continue because you need a node to capture a node. Hovis has developed a workaround system to detect these cases, it's not easy to understand, but it works. Please inspect the logic_compare entities in the reference VMF for the working I/O settings.

Note:If I still understood how it works, I'd describe it; but I don't remember, and somebody else can probably build a better one anyway. (Hovis)

Reference material

Feel free to use the original I/O design as a reference for your own CCP-type map, or even use the map in its entirety as a foundation for your own. If you do use ccp_mechanics as a jumping point, make sure to also credit its author (Hovis).

See also