Using Deacon's excellent how-to on entity creation
http://www.clanwos.org/forums/viewtopic.php?p=31041&highlight=viewpos#31041, you can add your favorite goodies, including support for off-world transport.
I have tweeked the primary map on Phlem's Meet 'n Greet to use entity files now instead of hardcoding, and came up with a mildly useful approach to making this work in a generic manner.
For each of 7 different off-world maps, I add a "key" or "misc" item unique to that server, also in the entity file. This object appears above the teleporter until you go through it.
The reason for doing this is that generating a trigger box around the teleport (as is done in the hacked bitchweiser map that I had running on the Phlem server before) is not possible using entity files, at least not that I have been enable to determine.
The scheme I came up with (subject to evolution based on user feedback) is as follows:
Server 1 - key_blue_key (loxophilia in my example)
Server 2 - key_red_key (Lox Unlimited in e.g.)
Server 3 - key_data_cd (mr bo's in e.g.)
Server 4 - key_data_spinner (deacons primary server in e.g.)
Server 5 - key_pass (wixen's in e.g.)
Server 6 - item_ancient_head (mr cctv's in e.g.)
Server 7 - key_pyramid (deacon's secondary serer in e.g.)
Note that these servers were picked because they seemed to be running when I did this experiment ...

If your server (or your favorite server) is not in this list, there was nothing meant by the disclusion.
The Phlem Server is loaded with these now, applied to the Wos_Temple map. It's a big map, though, so you have to hunt a bit to find where the offworld teleporters are located.
If you want to try this for your server and favorite map / maps, you can create the standard ent file per Deacon's how-to, then simply paste the attached ENT fragment to the bottom of your ent file, and edit the coordinates to match where you want things to be in your map.
Code:
{
"origin" "560 -2200 -474"
"targetname" "ledge"
"target" "q2@207.210.230.240"
"classname" "misc_teleporter"
}
{
"origin" "560 -2200 -443"
"classname" "key_blue_key"
}
{
"origin" "1158 705 -186"
"targetname" "ledge"
"target" "q2@65.99.206.74"
"classname" "misc_teleporter"
}
{
"origin" "1158 705 -155"
"classname" "key_red_key"
}
{
"origin" "-141 1417 -335"
"targetname" "ledge"
"target" "q2@mrbo.dyndns.org"
"classname" "misc_teleporter"
}
{
"origin" "-141 1417 -304"
"classname" "key_data_cd"
}
{
"origin" "-446 -434 -186"
"targetname" "ledge"
"target" "q2@deaconstomb.org"
"classname" "misc_teleporter"
}
{
"origin" "-446 -434 -155"
"classname" "key_data_spinner"
}
{
"origin" "46 2011 -344"
"targetname" "ledge"
"target" "q2@212.242.234.154"
"classname" "misc_teleporter"
}
{
"origin" "46 2011 -313"
"classname" "key_pass"
}
{
"origin" "1714 -1062 -188"
"targetname" "ledge"
"target" "q2@mrcctv.ath.cx"
"classname" "misc_teleporter"
}
{
"origin" "1714 -1062 -157"
"classname" "item_ancient_head"
}
{
"origin" "-9 -984 854"
"targetname" "ledge"
"target" "q2@deaconstomb.org:27911"
"classname" "misc_teleporter"
}
{
"origin" "-9 -984 885"
"classname" "key_pyramid"
}
Here is a hint: when you do the
viewpos, subtract 31 from the Z axis coordinate, but only for the TELEPORTER coordinate, not for the item.
Using the LOXophilia entry as an example:
Here is the LOXophilia ENT example singled out:
Quote:
{
"origin" "560 -2200 -474"
"targetname" "ledge"
"target" "q2@207.210.230.240"
"classname" "misc_teleporter"
}
{
"origin" "560 -2200 -443"
"classname" "key_blue_key"
}
The BOLD text is the Z coordinate for the teleporter pad.
Let's assume that you went into your favorate map to scout out some locations for offworld teleporters, found a good spot, ran viewpos, and came up with these numbers:
-224, 1044, -125
(these are X, Y, and Z numbers)
You would substitute in these new coordinates into the above example, subtracting 31 from the Z coordinate for the teleporter only.
Your new ENT file entry would look like this:
Quote:
{
"origin" "-224 1044 -156
"targetname" "ledge"
"target" "q2@207.210.230.240"
"classname" "misc_teleporter"
}
{
"origin" "-224 1044 -125"
"classname" "key_blue_key"
}
Again, note the Z coordinate for the teleporter.
On the Phlem server, I have a special bit of code that plays a unique sound for each of the 7 teleporters (you may notice an items/teleportX.wav file download when you connect). Of course, if you go through the teleporter, you will not hear the sound, as you have just jumped to another server.

After this code is shaken down a bit, I will look at adding it to the core LOX code.
You might have noticed the
"targetname" "ledge" entries in the examples. In this case, I picked a real teleporter targetname from the larger entity file. All this really does is cut down on the erroneous error messages that are generated on the server when the map and entity files are loaded. If you have a bogus value in there, it won't really hurt anything.
The only downside I have seen on this so far is that the keys do not seem to come back very fast, sometimes not at all until the map is reloaded. That means if someone has gone through the teleporter, you can no longer see it looking any different than a regular teleporter. I am still working on this ...
Feel free to play around with this and add it to your server entity files if you want. Of course, you can choose whichever target destination hosts you want, and even replicate them.
- Phlem
PS - I have a Linux build of ENTDUMP available if anybody needs one. I can also send you a copy of the Windows ENTDUMP.EXE if you can't download it for some reason.