Correct TP dest entity.

Discussion for Level editing, modeling, programming, or any of the other technical aspects of Quake
Post Reply
User avatar
Hipshot
Posts: 1547
Joined: Sun Jan 20, 2002 8:00 am

Correct TP dest entity.

Post by Hipshot »

How would you create a teleport?

trigger_teleport -> misc_teleport_dest (as seen in q3dm17)
trigger_teleport -> target_position (as seen in q3dm7)
trigger_teleport -> target_teleporter

All these three seems to work, I always assumed the first one was the correct, but seems there are different solutions here? Does it matter which one you use, seeing how id used two different?
Q3Map2 2516 -> http://www.zfight.com/misc/files/q3/q3map_2.5.16_win32_x86.zip
Q3Map2 FS_20g -> http://www.zfight.com/misc/files/q3/q3map2_fs_20g.rar
GtkRadiant 140 -> http://www.zfight.com/misc/files/q3/GtkRadiantSetup-1.4.0-Q3RTCWET.exe
dONKEY
Posts: 566
Joined: Mon Oct 15, 2001 7:00 am

Re: Correct TP dest entity.

Post by dONKEY »

I always understood it was misc_teleport_dest

target_position is the correct target for jump pads.

target_teleporter should target at a misc_teleport_dest iirc.
obsidian
Posts: 10970
Joined: Mon Feb 04, 2002 8:00 am

Re: Correct TP dest entity.

Post by obsidian »

Generally, you should use trigger_teleport --> misc_teleport_dest
Touching this will teleport players to the location of the targeted misc_teleporter_dest entity. This entity allows client prediction of events.
target_teleporter is used if you want to have something trigger it, though I'm not entirely sure how that works.
Activating this will teleport players to the location of the targeted misc_teleporter_dest entity. Unlike trigger_teleport, this entity must be activated by a trigger and does NOT allow client prediction of events.
Technically, I think whatever you target at the end doesn't matter too much since all it does is assign an origin for the player to spawn at. misc_teleport_dest has a better visual object in the editor so you don't spawn a player's shoulder in a wall.
[size=85][url=http://gtkradiant.com]GtkRadiant[/url] | [url=http://q3map2.robotrenegade.com]Q3Map2[/url] | [url=http://q3map2.robotrenegade.com/docs/shader_manual/]Shader Manual[/url][/size]
phantazm11
Posts: 362
Joined: Tue Jan 31, 2006 12:03 am

Re: Correct TP dest entity.

Post by phantazm11 »

target_teleporter is used if you want to have something trigger it, though I'm not entirely sure how that works.
People use this to have the player teleported if they shoot the teleporter, though id didn't use this in the final game as far as I know.
$NulL
Posts: 100
Joined: Wed Mar 27, 2002 8:00 am

Re: Correct TP dest entity.

Post by $NulL »

I think you can also use target_teleport to have team specific destinations via a target_relay.

ie:

Code: Select all

trigger_multiple -> target_relay ( red only) -> target_teleport -> misc_tele_dest
                 |
                 -> target_relay (blue only) -> target_teleport -> misc_tele_dest
Silicone_Milk
Posts: 2237
Joined: Sat Mar 12, 2005 10:49 pm

Re: Correct TP dest entity.

Post by Silicone_Milk »

$NulL wrote:I think you can also use target_teleport to have team specific destinations via a target_relay.

ie:

Code: Select all

trigger_multiple -> target_relay ( red only) -> target_teleport -> misc_tele_dest
                 |
                 -> target_relay (blue only) -> target_teleport -> misc_tele_dest
that actually sounds like it could be a useful little setup.
Post Reply