Skip to content

Friendly Fire and Ally Protection

Quick Answer

In ArcheAge Chronicles PvP channels, party members and guild members are excluded from the players who can attack you. In standard channels, players cannot attack one another at all.

In ArcheAge Chronicles PvP channels, party members and guild members are excluded from the players who can attack you. In standard channels, players cannot attack one another at all. The important distinction is therefore your channel type and your actual party or guild relationship, rather than whether another player is someone you recognize.

A friend standing beside you without being in your party or guild is not included in the stated PvP exception merely because you intend to cooperate. For exploration without player attacks, use a standard channel. For a group entering PvP, confirm party membership and the shared channel before approaching other players.

Read protection as a relationship rule

The PvP rule is broad: everyone else can attack you except your party and guild members. That makes membership the useful test. A stranger can become a protected party member by joining the party; a familiar person outside the stated relationships is not automatically protected by familiarity.

This is different from a rule based on class, outfit, nearby position, or a shared monster target. Two players using the same weapon or attacking the same boss have not thereby joined a party. Likewise, standing inside the same area does not establish a guild relationship.

The rule also does not require you to describe a custom damage-reduction percentage. The announced exception concerns who can attack whom. There is no need to invent a configurable percentage, a temporary shield duration, or a particular setting name to explain it.

Use the relationship information visible in your actual group setup. If someone has been invited but has not joined, do not assume the invitation alone establishes the completed party relationship. Confirm the group before using the PvP exception as the basis of your plan.

SituationStandard channelPvP channel
Another player is in your partyPlayers cannot attack one anotherParty member is excluded from player attacks
Another player is in your guildPlayers cannot attack one anotherGuild member is excluded from player attacks
A friend is outside both relationshipsPlayers cannot attack one anotherNot included in the stated ally exception
An unrelated player is nearbyPlayers cannot attack one anotherCan be a player-combat threat

Standard channels provide the broader safety choice

If the goal is simply exploring together without other players attacking you, a standard channel is the straightforward choice. It removes player attacks as a category rather than relying on each nearby player's relationship to your group.

That does not remove monsters or encounter hazards. The rule concerns player-versus-player attacks. A protected teammate can still need help against enemies, and entering a standard channel should not be described as making every source of damage disappear.

For a mixed group with different interest in PvP, agree on the channel type before starting an activity. A player who wants an uninterrupted story session and a player who wants open-world fights have different goals, even if both are willing to travel through the same region.

This decision is especially useful for newcomers joining a more experienced group. Explain the channel choice directly rather than promising that party protection makes the entire environment safe. Party protection excludes friendly party attacks; it does not exclude hostile players outside that relationship in a PvP channel.

PvP channels preserve hostile players outside your group

A PvP channel is otherwise the same zone, with the same monsters and quests, but different player-combat rules. Party and guild protection lets you cooperate without treating those members as ordinary player targets. It does not make a party a private version of the open world.

If your party encounters another group, the stated exception does not automatically extend between the groups. Sharing a destination, agreeing informally to a truce, or helping with the same monster is not one of the announced protected relationships. Make decisions around the actual relationship rather than the intention alone.

Guild membership creates a different protected relationship from party membership. That means an individual guild member need not be in the same four-player dungeon party to fall within the stated guild exception in PvP channels. It does not establish that every friend of that guild member receives the same status.

For practical play, identify your own group first and regard other player relationships according to the channel rules. This helps avoid interpreting every nearby character as either an ally or a guaranteed enemy based only on how the scene looks.

Two melee characters in a close-range PvP exchange with the combat interface visible

PvP channels allow attacks against players outside the stated party and guild exceptions.

Handle two cooperating parties as two relationships

Consider friends exploring as two separate parties. Within each party, the party exception applies. Between the parties, cooperation by itself is not a listed protection rule. If everyone also belongs to the same guild, the guild exception is relevant; if they do not, do not assume that a social agreement changes the channel's targeting rules.

This is a useful reason to choose a standard channel for a larger informal gathering whose goal is peaceful exploration. It avoids requiring every participant to infer every other participant's relationships. If the group deliberately chooses PvP instead, make the relationship distinction explicit before approaching another party. A friendly intention and a game-defined ally relationship are different inputs to the rule.

Channel switching is a separate action from joining a party

You move between standard and PvP channels at a Nui Statue. Switching has a cooldown, so it is not described as an instant escape you can repeat whenever a fight goes badly. No exact cooldown duration is established here.

Joining a party and selecting a channel solve different problems. Membership establishes the party relationship; sharing a channel lets players meet in the same copy of the area. If friends cannot see one another, confirm both instead of assuming a damage-protection problem.

The pre-launch improvements say that parties now stay together across Peace and Conflict Channels, that invitations work across both, and that players can move directly to the party leader's channel. Those are practical improvements for maintaining the group, not a replacement for choosing the desired combat rules.

Before a group activity, use a simple order: agree on standard or PvP, confirm everyone is actually in the party, and confirm everyone has reached the shared channel. That order avoids discovering a separation only after an encounter begins.

Nui Statue interaction menu showing Move to PvP Channel

The channel option appears in the statue interaction menu.

Server separation cannot be fixed with channel protection

Channels belong within the larger server structure. If you and a friend created characters on different servers, joining the same named region or looking for a party channel is not enough to make the characters meet.

Early Access rules state that characters cannot transfer to another server and players on different servers cannot play together. Coordinate the actual server before character creation if playing together is essential. Friendly-fire protection does not bridge that server separation.

This distinction matters because the word same can refer to several different things. The same game, region, server, party, and channel are not interchangeable descriptions. You need the relevant shared server and channel to occupy the same space, and the party or guild relationship to apply the stated ally exception.

For an existing group that cannot meet, first identify whether the mismatch is server-level or channel-level. A channel mismatch has a described party-leader channel route. A server mismatch is constrained by the no-transfer rule and should not be presented as something a PvP toggle can repair.

Use the rule when positioning around other players

The protection rule is useful before you use an attack near a cooperating player. Ask whether that player is actually a party or guild member and whether you are in a PvP channel. That is a more reliable question than judging safety from the size of a spell effect or the distance between characters.

The available explanation does not separately document every projectile, ground effect, reflected attack, or unusual interaction. Do not invent exceptions for those cases. If you need to evaluate a specific interaction, keep it separate from the general party-and-guild rule and describe what actually happened.

A report about apparent ally damage should therefore identify the exact relationship at the time, the channel type, and the attack involved. This makes it possible to distinguish an unexpected interaction from a case where the other player was never inside the stated protected group.

The same care applies to visual effects. A dramatic effect appearing near a teammate is not, by itself, proof that your attack damaged that teammate. Look at the actual outcome before changing your interpretation of the rule.

Party protection does not replace encounter coordination

Being unable to attack your party members does not establish that their positioning is irrelevant. They still need to see enemies, respond to attacks, and stay together through the content. Protection solves a specific player-targeting issue, rather than making every form of group coordination unnecessary.

It also does not establish a finished traditional tanking system. The developers have identified party aggro as an area needing further work. A durable player standing in front cannot promise that all monsters will remain focused on them while everyone else ignores danger.

Keep those concerns separate when discussing a failed encounter. A monster changing targets, another party member taking an environmental hit, and a suspected friendly-fire interaction are different events. Identifying which happened prevents the group from trying to solve a combat problem by changing unrelated PvP settings.

For a group learning an area, a standard channel removes outside player attacks while leaving the actual encounter mechanics to learn. A PvP channel adds player threats beyond the protected members of your own party or guild. Choose the environment that matches the activity you intend to do.