target key on the trigger, targetname key on the destination, and set the value the same on both of them. Each separate teleport->destination pair should have a different value. 

http://quakewiki.org/wiki/info_teleport_destination

That should help. Basically you need a key value of "targetname" for both and they both need to be the same. 

I made both the info_teleport_destination and the trigger_teleport have targetname "name"

and it does not work. 

Here is the map. I don't know what is wrong...https://dl.dropboxusercontent.com/u/10224384/teleportmaptest.zip 

and necros is correct. the key on the trigger_teleport should be "target", not "targetname" 

no no...

trigger_teleport: "target" "blah"
info_teleport_destination: "targetname" "blah" 

 

Please tell me if the wiki is broken and not allowing editing. 

when i load the map on devmap it loads then stops and go back to the main menu, there is a aas file and when i try to add bots in map it says aas not found/active 

I went through the wii and no mention of func_plat anywhere. I added target and targetname stuff retrospectively, and I cant figure out how to make the floor move or even how to define the height. 

/*QUAKED func_plat (0 .5 .8) ? plat_low_trigger
Plats are always drawn in the extended position, so they will light correctly.

If the plat is the target of another trigger or button, it will start out disabled in the extended position until it is triggered, when it will lower and become a normal plat.

Flags:
"plat_low_trigger"
???

Keys:
"height"
determines the amount the plat moves, instead of being implicitly determined by the model's height.
"sounds"
1 = base fast
2 = chain slow
"speed"
moving speed (default: 150)
"targetname"
entity name
*/ 

meant to hit preview.
anyway, as you can see, the amount of movement is normally determined by the actual lift model. but you can override it with height. 

http://www.quakewiki.net/archives/worldcraft/entity/standard/standard.shtm

Much more complete entity list than the wiki :D 

In the second byte of spawnflags there's flags to not spawn ents in Easy, Normal and Hard mode, but not Nightmare?

Is there a way to make an ent not spawn in Nightmare but spawn in the other skill levels? 

Nightmare is hard skill with different monster AI. A NM-only spawn would require modified progs. 

You could have a NM-only killtarget for your ent to not exist in NM, but it's a setup that requires a start map and a rune. 

I was thinking like, make certain ammo or weapons not appear in NM to raise the challenge, but it sounds complicated. :P 

You could have a NM-only killtarget for your ent to not exist in NM, but it's a setup that requires a start map and a rune.

You put the rune in the nightmare entrance? 

Also made it so the player couldn't avoid accessing NM after collecting the rune, unless they opened the console. 

Then use func_episodegate logic gates in the actual map. 

You have 24 hours to come up with the CORRECT maphack before I put you all to shame. Nightmare only trigger - go! 

hmmmm all I can think of it somehow using SUB_AttackFinished which will allow 2 or more consecutive attacks on nightmare skill..? 

Yeah, I specifically searched the source for "skill == 3" before posting that. I was thinking something like what necros said but I couldn't figure out how I'd exploit it on an entity. 

As if Preach's on-demand mentality for revealing hacks wasn't bad enough, now he's even teasing us with it! 

Lunaran, you were so close! Here's the trick:
http://tomeofpreach.wordpress.com/2014/10/07/nightmare-skill-detection/