Move teleport velocity modes from trigger to destination entity

BLT

I'm talking about the teleport mode entry here

My rationale is that I can see no situation where you'd want different triggers to send you to the same teleport destination while having different behavior (please enlighten me if you do!). On the other hand, having these settings on the info_teleport_destination would not only give the special entity a purpose, it would also make changing your tp modes after the fact much easier and consistent, because there's no way you've missed a teleport trigger (think of a (KZ-)Bhop segment where each block could have a singlehop trigger that teleports you).

Now landmark mode might be different since it's relative to the tele trigger but the other settings depend on where you're going and not which trigger you're coming from.

This is of course a bit of theory crafting but I thought I should suggest it and put it up to discussion now, because in the future it would probably be too late and too difficult to change if hundreds of maps are released. (Also half of the maps are broken because of the teleport trigger change now anyways and would need some kind of patchup at some point).

hex

I don't think there's any harm in having it linked to teleports as it is now (besides occasionally having to manually set a couple teleports to the same behavior for the same destination but that shouldn't be a big deal if you're grouping entities and so on smartly). All that linking the behavior to destinations does is limit what you can do without having to duplicate destinations. For example, think of the door into a new stage on bhop_eazy. Say I'm using the same destination for both the door on the previous stage and the fail tele on that stage. If I want to allow telehops into the course but prevent them from failing (to avoid annoying the user) then I would now have to use 2 separate teleport destinations where previously 1 would have worked.
What if I want to teleport to something other than a tele destination in my complex logic chain but also want to filter telehops? I wouldn't be able to do it as easily anymore with this (though im sure it'd still be possible in some way).

Either way both ideas are fine by me, I just think the current system is a bit more intuitive and avoids having to do some unpleasant workarounds like duplicating extra entities.

BLT

hex You're right, I forgot that there's lots of cases where the fail dest is also the stage entrance and obviously there shouldn't be any loss of functionality. I had a scenario in mind where you would run into an issue with the current system concerning progress teleports, but maybe it's too contrived. I should set it up in hammer at some point.

zer0k_z

I don't know much about hammer, but if it's possible it would be nice to let mappers choose the behavior itself, that way we can have all the advantages without any of the downsides.