dot-spawn

dot-spawn decides where a player, an NPC or a prop enters the world. It answers a question and emits a signal; the game does the spawning.

Requires dot-core. It does not raycast — can_see_fn is supplied, because this addon has no opinion about which collision layers count and dot-physics already does.

Usage

var spawns := DotSpawnDirector.new()
spawns.rules = DotSpawnRules.team_deathmatch()
spawns.tick_rate = 64
spawns.enemies_fn = func(team): return positions_of_enemies_of(team)
spawns.can_see_fn = func(a, b): return physics.query().line_of_sight_3d(world, a, b)
add_child(spawns)
spawns.refresh()                       # collect the markers in the level

var res := spawns.choose(DotSpawnRequest.make("ada", &"blue", &"rifleman", tick))
if res.ok:
    player.global_transform = (res.value as DotSpawnChoice).transform

# Once a tick: expires protection and drains respawn timers.
for key in spawns.advance(tick):
    respawn(key)

Points and areas, in 2D and 3D — a point spawn fails in the exact case a round begins, with sixteen capsules at one coordinate.

Selection modes

Conditions veto; weights argue

DotSpawnCondition.allows() is a veto and bonus() is an opinion. A condition that expresses a veto as a large penalty still picks the forbidden site when it is the only one left — which is how a game spawns the attacking team inside the defenders’ base in the one round where it matters.

Four ship — MinimumEnemyDistance, OutOfSight, NotOccupied, MetaEquals — and DotSpawnCondition is the subclass point for a fifth.

Randomness is per request, not per director

One generator seeded from (seed, tick, key) per call, never a shared member. A single stream makes a spawn depend on how many other spawns happened first, so a server that processed two deaths this tick and a client that saw one pick different points, and the player materialises in two places.

Respawn timers and waves

queue_respawn, take_due, advance. Queuing somebody twice keeps the earlier time — a kill credited twice must not push a respawn further away — and due keys come out sorted, because a dictionary’s key order is not a promise and two machines disagreeing about it is a desync with no obvious cause.

wave_respawn holds everybody until the next boundary, which is the round-based modes’ answer to a trickle of players arriving one at a time into a fight that is already lost.