> For the complete documentation index, see [llms.txt](https://docs.morpheusemulator.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.morpheusemulator.com.br/events/morpheus-events/pvp-1x1.md).

# PvP 1x1

A GM-refereed duel: the GM picks two players, they fight where they stand, and the first to reach the target score wins.

## What it is

1. The GM types `/pvp`. Only the GM sees "\[PvP] Started!", because this event is set up by hand.
2. The GM **sends a trade request** to the first fighter, then to the second (no trade window opens). The order sets who is fighter 1 and who is fighter 2.
3. As soon as both are picked, the server announces "\[PvP] *A* x *B* started!", both characters charge at each other, and each sees the other with a red (outlaw) name.
4. Each kill gives the killer 1 point, with the score announced to the whole server. The dead fighter respawns **on the spot**, with no PK penalty for either side.
5. The first to reach `EventPvPMaxScore` points wins: fireworks, announcement, coin reward.
6. If one fighter disconnects, the other wins at once. If the time runs out, the duel ends with no winner.

There is no teleport: the duel happens wherever the two players are.

## Enable it

All keys are in `GameServer/Data/GameServerInfo - Event.dat`:

| Key                   | Default | Meaning                                                                                      |
| --------------------- | ------- | -------------------------------------------------------------------------------------------- |
| `EventPvPSwitch`      | `1`     | `1` enables the event                                                                        |
| `EventPvPMaxScore`    | `3`     | Kills needed to win. Server default if missing: `3`                                          |
| `EventPvPMaxTime`     | `3`     | Total time from `/pvp`, including the time the GM takes to pick the fighters, in **minutes** |
| `EventPvPAutoReward1` | `0`     | **WCoinC** for the winner                                                                    |
| `EventPvPAutoReward2` | `0`     | **WCoinP** for the winner                                                                    |
| `EventPvPAutoReward3` | `0`     | **GoblinPoint** for the winner                                                               |

## Files & syntax

No event file. The keys above and the `/pvp` command (no arguments) are all there is.

## Example

```
EventPvPSwitch = 1
EventPvPMaxScore = 5        ; first to 5 kills
EventPvPMaxTime = 10        ; 10 minutes from /pvp
EventPvPAutoReward1 = 25    ; 25 WCoinC to the winner
EventPvPAutoReward2 = 0
EventPvPAutoReward3 = 0
```

In game: `/pvp`, then send a trade request to player A, then to player B.

## Rewards

The winner gets the three `AutoReward` values as WCoinC / WCoinP / GoblinPoint, credited to the account. Shipped values are all `0`. A win because the opponent disconnected also pays. No item bag is used.

## Commands related

| Command | Who                     | What                                                                                                     |
| ------- | ----------------------- | -------------------------------------------------------------------------------------------------------- |
| `/pvp`  | Admin (`#GameMaster` 2) | Starts the event (the GM then picks fighters by trade request). Typed again while it runs, it cancels it |

## Pitfalls

* The 3-minute default includes the time the GM needs to pick both fighters. Raise `EventPvPMaxTime` if your fights take longer.
* There is no arena or teleport. Bring both fighters to a quiet, non-safe-zone spot before you pick them.
* `/offpvp` doesn't protect a player who has been picked as a fighter.
* A fighter who disconnects gives the win to the other one, so a player can lose by closing the game.

## Reload module

`/reload event` re-reads the keys. A running duel isn't cancelled, and the new `EventPvPMaxScore` and rewards apply from the next kill.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.morpheusemulator.com.br/events/morpheus-events/pvp-1x1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.