.... I didn't forget to commit for a while... You can't tell
This commit is contained in:
+3
-3
@@ -58,10 +58,10 @@ Use a normal trigger volume around the scoring area.
|
||||
Attach:
|
||||
|
||||
- Condition: `PlayerInMinigame`
|
||||
- Effect: `ModifyPlayerScore`
|
||||
- Effect: `ModifyScore`
|
||||
- Fields: `Operation = ADD`, `Amount = <points>`
|
||||
|
||||
If the score is team-based, use `ModifyTeamScore` instead.
|
||||
If the score is team-based, use `ModifyScore` with `TargetType=TEAM`.
|
||||
|
||||
### Phase Gate
|
||||
|
||||
@@ -90,7 +90,7 @@ Tag each team spawn volume with:
|
||||
|
||||
This means checkpoint-based games can still override spawns per player, while team arena games can rely on tagged team spawn volumes.
|
||||
|
||||
Player deaths during a minigame automatically use the same destination order. `DestinationId` and `SetSpawnPoint` values are coordinate strings, such as `100,64,200` or `world_name,100,64,200`; team-spawn fallback is resolved from tagged spawn volumes.
|
||||
Player deaths during a minigame automatically use the same destination order. `RespawnPlayer.DestinationId` accepts coordinate strings, such as `100,64,200` or `world_name,100,64,200`; `SetSpawnPoint` uses separate `X`, `Y`, and `Z` fields. Team-spawn fallback is resolved from tagged spawn volumes.
|
||||
|
||||
### Counters
|
||||
|
||||
|
||||
Reference in New Issue
Block a user