doesn't work like that. sorta. it'd be better to just overlap triggers with keys; when a trigger is spawned with a target it's loaded as that. if there's more then one target weird things happen; client thinks its going someplace server says its going to a different place, client gets confused and the whole map gets borked client-side. sorta.
its rare, but it can happen. its weird i know.
if someone just overlapped a few triggers with different destinations it'd work better. picking the start is much easier on the client then picking the destination once the client starts to teleport or thinks it already did teleport.
try it sometime, make a q3 map with one trigger teleport and make many targets for the destinations; you'll see a flash as you go from one to the next. with allot of entities flashing in and out, the client's pvs getting slammed with data that can lead to fugliness client-side.
