Bugfix: don't try to reactivate a destroyed spawnpoing in SERVER+CLIENT - Reimplemented the spawn point status based on new internal state - this retains original behavior Editor-only bug caused by my previous change of pooling behavior (destroy object instead of trying to pool it on scene unload). Tests: on Craggy spawned and disconnected - no errors. Checked BaseSpawnPoint inheritance hierarchy to ensure there's no other places trying to activate gameobjects