Commander/ko

사령관은 폐기된 직접 행동하지 않는 팀 포트리스 2의 클래스입니다.

사령관은 맵을 내려다 보며, 공중 지원을 하고, 구조물을 짓고 전략을 이야기하도록 예정되었습니다. 팀 포트리스 2의 긴 개발 동안 폐기되었지만, 사령관의 개념은 코칭 시스템으로 재탄생했습니다.

정보

기원

팀 포트리스 2, 원래는 밸브 팀 포트리스로 이름붙여지고, 나중에 팀 포트리스 2: 브라더후드 오브 암즈라고 불리는 개발 기간 동안 개발자들은 게임을 디자인하며 더 현실적인 접근을 하도록 했습니다. Valve worked to create a modern war game with the then state-of-the-art technologies and techniques, which included parametric animation; seamlessly blended animations for smoother, more life-like movement; and Intelligence's multi-resolution mesh technology dynamically reducing the detail of on-screen elements as they become more distant to improve performance (a technique made obsolete by decreasing memory costs, since today's games use a technique known as level of detail, which uses more memory but less processing power).

Included in this modern direction was the design of a military command hierarchy, introducing a Commander role; the player would have a bird's-eye view of the battlefield, reminiscent of Real-Time Strategy games, allowing for new influence in battle. With numerous innovations such as networked voice communication, the Commander would have been able to help coordinate attacks, alert to enemies, placing structures, call for parachute drops over enemy territory, and possibly more. However, unlike the remainder of the classes, due to the RTS design the Commander was a non-physical role and was only able to passively influence battle.

Complications and Removal

In a Gravel Pit developer commentary with Robin Walker, he discusses why the development of Team Fortress 2 took a significant amount of time. Among the reasons were the balancing issues with the Commander role in gameplay.

“

In developing TF2 we tried out many many features, a few of which made it into the final product, but most of which were cut. For example, our initial versions of TF2 were focused on trying to build a game around the concept of a commander: a single player who had a real time strategy view of the battlefield. He would be responsible for building structures and providing a unifying strategy for the team. But there was significant design challenges involved. For instance, how do we design the game such that the commander can have fun and at the same time ensure that the players down on the ground can have fun? How do we ensure that the players and the commander value the output of each other? How do we ensure that the game is still fun if you have a terrible commander, or conversely, if you're a great commander with a terrible team? We spent many months working on these and other issues and never really reached a point where we were satisfied. In addition, our game has become overly complex, due to our attempts to add a strategy layer deep enough to warrant the addition of the commander in the first place. In the end, we made the hard decision to remove him from the game and moved on. — Robin Walker

”

The Commander, along with other features creating a more realistic approach, were scrapped during Team Fortress 2's development and steps toward the cartoonish final design then began.