Skip to content

This is general knowledge or an external-engine reference, not an Apollo architecture or implementation claim. See Apollo's architecture status for target terminology and verified implementation boundaries.

Q54: How to handle multiple players fighting over the same monster / resource? ​

Core Conclusion ​

The core of multiple players fighting over a monster or resource is not "who is faster," but how the system defines ownership, the contention window, and the reward allocation rules.

What really needs to be determined first is:

  • By what rule ownership is produced
  • When ownership is locked and when it expires
  • How parties, guilds, and temporary alliances share ownership
  • How loot and gathering results avoid duplicate settlement

If the rules are not unified, both the player experience and anti-cheat will suffer.

1. First distinguish two kinds of contention ​

1. Monster ownership contention ​

Concerned with:

  • Who holds the kill rights on the monster
  • Who can get the loot
  • How team and damage output are calculated

2. Resource node contention ​

For example mining nodes, herbs, treasure chests.

Concerned with:

  • Who occupies it first
  • Whether the occupation can be interrupted
  • Resource respawn and cooldown

Although both are called "fighting over," their rule designs differ considerably.

2. Ownership rules must be defined first ​

Common ideas include:

  • First-hit ownership
  • First-valid-party ownership
  • Cumulative contribution ownership
  • Final kill plus participation threshold

No single rule suits every mode.

For example:

  • Normal wild monsters suit simple rules
  • World bosses suit contribution or team ownership better

3. Ownership does not only decide "who can hit it," it decides "who can get it" ​

Many disputes are not actually about the monster-fighting process, but about unclear loot ownership.

So you usually need to define at the same time:

  • Combat ownership
  • Loot ownership
  • Experience ownership
  • Quest counter ownership

Otherwise you get situations where the monster was killed by party A but the reward is picked up by player B.

4. Party sharing rules must be clear ​

As long as there is party play, you must make clear:

  • Whether party members share ownership
  • Whether losing sharing eligibility happens when too far away
  • Whether someone who joins the party mid-fight still gets loot
  • Whether sharing still works across maps or across lines

These details directly affect monster farming and power-leveling behavior.

5. Resource gathering usually needs an occupation state ​

Resource nodes differ from monsters. They commonly introduce:

  • Gathering in progress
  • Locked
  • Interrupted
  • Gathering complete

In other words, resource contention is more like a "short transaction." You need to be explicit about who holds the gathering right.

6. World bosses and large shared goals need extra care ​

In these kinds of scenes, using only a simple first-hit or last-hit rule often makes the experience very poor.

A more reasonable line of thinking is usually:

  • Participation threshold
  • Contribution ranking
  • Party or faction sharing
  • Independent reward settlement

This reduces last-hit stealing and malicious interference.

7. Engineering must prevent duplicate settlement ​

In multiplayer contention scenes, one of the most dangerous problems is:

  • The monster death event fires more than once
  • Loot spawns are duplicated
  • Multiple players collect the same resource at the same time

So the key points usually include:

  • Death and resource completion have exactly one authoritative submission
  • Loot and reward issuance are idempotent
  • A client "winning" the grab does not mean the server has already issued it

8. A more reliable engineering design ​

A common approach is:

  • The target object maintains an ownership context
  • Ownership changes are updated by explicit rules
  • Death or gathering completion goes through final settlement exactly once
  • Loot is then distributed or escrowed according to rules

That keeps the boundary between monster fighting and the loot system clear.

9. Common misconceptions ​

1. Whoever clicks first should own it ​

Not necessarily for resource nodes, and even less so for monsters. The rules must be designed around the actual mode.

2. Ownership only affects loot ​

In many cases it also affects experience, quest counters, and event contribution.

3. The client showing a successful grab means it succeeded ​

No. The final result must be decided authoritatively by the server.

References ​

  • Various MMO world boss, resource gathering, and ownership allocation practice materials

Released under the MIT License