Memory Beta, the wiki for licensed Star Trek content.

   

   

   

COMIC
Strategy
Cover by Jeremy Geddes
Attribution

From GuildWiki

Definition

Team strategy is a plan of how a team intends to win a battle. Team Strategies are more pertinent in PvP play when the enemy's behavior is not scripted. Because human players can surprise you with how they play (and can also panic and lose concentration if properly surprised), designing a solid team strategy is crucial for success in PvP, especially in the more competitive settings like Tournament and GvG battles. There is still a need for team strategy in the PvE game and many of the elements discussed below apply to PvE as well.

There are many elements to building solid team strategy in Guild Wars, these are some of the basic ones:

Team Work

This is the most fundamental concept in team strategy. The team must work together. A player who does not listen to strategies is as big a threat to his/her teammates as the enemy. A common reason players do this is that they either do not care (too young to understand or simply too self-absorbed), or they believe in other plans. If a player believes in other strategies, he/she should discuss that with the team, instead of planning on breaking with the team plan.

Here are some basic team work principles:

Calling Targets

In most cases it is useful when the team agrees on a target calling strategy. A calling strategy defines who will attack what (and when, e.g. the team will first take out monks, then mesmers, then necromancers... etc). This makes it easier for the team to act coherently even if calls are not made in a timely fashion.

The simplest way to achieve this is selecting a primary caller. All party members should follow his/her calls except those exempt from this (like a battery necromancer busy with generating energy, or off target attackers).

The team should also decide... If the primary caller falls, does he/she keep calling or will there be a secondary caller.

Healing Plan

On simple team builds that have a pair of monks as healers, they should make every effort to coordinate their healing. If both cast the same healing/protection spell on the same target, then that is a wasted spell.

Some coordination techniques include:

• One monk takes the top four in the Party List and the other takes the bottom four.
• They split professions among them (one warrior and elementalist handled by each monk).
• They constantly call their healing.
• Designate one monk to function in the role of bonder.

Facing Warriors

Inexperienced spell-casters sometimes flee when attacked by enemy warriors. Running spell-casters take more damage from warrior attacks and are useless to their teammates because they cannot cast spells while running for their lives!

A team should plan for protecting their back-end members. Will they use Protection Prayers, wards or some other tactic? Do their warriors up front ever come back to help out or do they just go for called targets and ignore all? It should be made clear, whether the monks feel confident enough to allow casters to tank attacks, or if they should try to kite them.

Resurrection Plan

Plan on resurrecting teammates. An understanding of the type of challenge facing the team and the dynamics of the game is necessary. Here are some useful tips:

• Resurrect healers first.
• Call your resurrects: This will save the aggravation of having multiple people attempting to resurrect the same fallen comrade.
• Always carry a Resurrection Signet in PvP. There are few exceptions, largely including Monks who instead carry a different resurrection skill effective in PvP, or often don't carry one at all.
• Rebirth is terrible for PvP battles, as both resurrected teammate and healer are useless for some time after.
• Rebirth is extremely valuable for PvE sections, particularly during missions and other areas where the task must be started from scratch if the party wipes.
• You will usually need to resurrect during combat in PvP, since humans won't allow you to run away and regroup.
• In PvE, characters should not be resurrected in combat if they will be killed almost right away, if the resurrecting character's skills are important for the team, or if the team can handle the enemies without the dead person. Characters should be resurrected if they are important for the party, such as monks or tanks, if the rest of the party can survive without the resurrecter for a time, or if the party is not able to win without the dead character's skills.
• Monks in general should not resurrect in PvE unless other characters can heal or defend themselves while the monk is resurrecting.
• In PvP, non-healers should resurrect first. If healers stop healing to raise the dead, this will often result in someone else dying.

The Team Build

There are as many team builds as there are hairs on a Yak's back, but there is no such thing as a perfect team build. Every build, no matter how dominant, will be taken down. Once people figure out how the build works they will be able to attack its weaknesses, and all builds have a weakness. (If a build really is invincible, then ArenaNet will modify the game to make it no longer so.)

Some famous team builds, that have since been nerfed include:

• IWAY
• EoE Bomb
• Minion Factory

The Individual Builds

Even though much of a single member's build will be based on the team's build and what they expect from that member in his/her role, there is still room for creativity within a single character's build. For example, a hammer warrior thinking about equipping a knockdown skill has much to think about. Assuming their elite skill is not used by the team build... Do they equip Devastating Hammer or Backbreaker or Earth Shaker? Each has much to offer.

Do Your Homework

Understand the game and the skills used in the game. A charging team that does not notice a spirit of Frozen Soil will be shocked to find out they cannot resurrect their fallen! A warrior who does not notice Empathy on himself will kill himself! And a group of casters with Spiteful Spirit on a couple of them could self-destruct. So, learn about these tricks and how they affect the game.

From Halopedia, the Halo Wiki

5.00

(2 votes)

There is more information available on this subject at Real-time Strategy on the English-language Wikipedia.

Real-time Strategy, or RTS for short, is a genre of computer games characterized by being wargames which take place in real-time, where resource gathering, base building, technology development and direct control over individual units are key components.

Real-time strategy titles do not involve "turns" like turn-based strategy video or board games. Rather, game time progresses in "real time;" it is continuous rather than turn-by-turn, and all players may give orders to their troops at any time. While the word "strategy" originally referred to high-level war planning (armies, campaigns, and entire wars), in real-time strategy games individual units or persons are given orders. Also integral to the gameplay of real-time strategy games are economic and production aspects (resource gathering, construction, positioning of buildings, expansion, and production of units), and though military confrontation is a significant part of real-time strategy gameplay, it is most often heavily stylized with relatively little emphasis placed on simulating real warfare, in contrast to games of the genre known as real-time tactics.

It is common for games to be miscategorized as belonging to the real-time strategy genre. This is partly because real-time strategy is a vague denomination, giving rise to the assumption that all games involving strategy played in real-time are "real-time strategy" games. It is also partly due to the fact that the genre is so commonly recognized and well-established that there is a tendency to classify many different types of games within it. For instance, SimCity, which is a city-building game, Railroad Tycoon, an economic simulation game, and games of the real-time tactics genre of military simulations are often classified as "real-time strategy."

Halo Wars, designed by Ensemble Studios, was planned to be an RTS game, releasing to be so. Halo: Combat Evolved was also originally planned to be an RTS game, but it was converted into a First Person Shooter game. Halo 2 and Halo 3 have followed in those footsteps.

From City of Heroes Wiki

Introduction

When City of Villains was preparing for release, the community was asked for input to help identify information in the game manual that needed to be updated. Since this would be the first update to the game manual since City of Heroes release, there was a lot of material that needed to be covered, and the community tackled it with great enthusiasm. As a result, the City of Villains manual was pretty much up to date at initial release.

At present, however, the game manuals are once again very out of date. And while the various articles here on the wiki are able to give players a pretty broad idea of how the game works, there is still a lot of useful information that was contained in the game manuals that hasn't previously been covered here.

This project--given the name "The Players' Guide to the Cities"--essentially creates what we hope will become a living, breathing game manual to be maintained by the community at large. As such, it should provide a good starting point for anyone new to either the wiki or the "City of" franchise who is looking to learn more about the game but maybe a little unsure what they are even searching for. It should also serve as a quick-reference document for more advanced players who are just looking for general information on broad subjects they might want to brush up on.

So, welcome to the Players' Guide to the Cities. We hope you find this guide both useful and informative. And since this is a community project, if you find any out-of-date or incorrect information, edit away.

--Eabrace 16:24, 16 August 2007 (EDT)

Contents

• System Requirements
• Getting Started
• Creating a Character
• Character Slot Management
• User Interface
• Your First Game Session
• Movement
• Interacting with the Environment
• Fighting and Other Actions
• Leveling
• Powers
• Rewards
• Missions
• Teams
• Super Groups
• Coalitions
• Trading
• Slash Commands, Macros, Keybindings, and Emotes
• Options
• Zones
• Enemy Groups
• Player vs. Player
• Glossary
• Credits