# Triggerdelay in new engine?

**URL:** <https://forums.sourceruns.org/t/triggerdelay-in-new-engine/2455>\
**Category:** Half-Life 2\
**Created:** [September 14, 2014, 1:42pm UTC](https://forums.sourceruns.org/t/triggerdelay-in-new-engine/2455 "2014-09-14T13:42:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rama](https://b-cdn.sourceruns.org/letter_avatar_proxy/v4/letter/r/ccd318/32.png) [@Rama](https://forums.sourceruns.org/u/Rama)\
**Post date:** [September 14, 2014, 1:42pm UTC](https://forums.sourceruns.org/t/triggerdelay-in-new-engine/2455/1 "2014-09-14T13:42:21Z")

</div>

Is there a way to do triggerdelay in new engine?

---

<div class="post-metadata">

**Author:** ![WindedCone859](https://b-cdn.sourceruns.org/letter_avatar_proxy/v4/letter/w/f6c823/32.png) [@WindedCone859](https://forums.sourceruns.org/u/WindedCone859)\
**Post date:** [September 14, 2014, 2:09pm UTC](https://forums.sourceruns.org/t/triggerdelay-in-new-engine/2455/2 "2014-09-14T14:09:39Z")

</div>

Nope

---

<div class="post-metadata">

**Author:** ![YaLTeR](https://b-cdn.sourceruns.org/user_avatar/forums.sourceruns.org/yalter/32/553_2.png) [@YaLTeR](https://forums.sourceruns.org/u/YaLTeR)\
**Post date:** [September 14, 2014, 2:37pm UTC](https://forums.sourceruns.org/t/triggerdelay-in-new-engine/2455/3 "2014-09-14T14:37:00Z")

</div>

OrangeBox+ has changed waits and waits are the only things that broke the command processing cycle to my knowledge. So unless there’s something else in OrangeBox, no.

---

<div class="post-metadata">

**Author:** ![mike](https://b-cdn.sourceruns.org/letter_avatar_proxy/v4/letter/m/58f4c7/32.png) [@mike](https://forums.sourceruns.org/u/mike)\
**Post date:** [September 15, 2014, 6:42pm UTC](https://forums.sourceruns.org/t/triggerdelay-in-new-engine/2455/4 "2014-09-15T18:42:44Z")

</div>

Although what YaLTeR said is 99.999% likely to be correct, it would be interesting to look around just in case there is some weird way to do it 😛 Having said that I don’t even like trigger delay much. If console commands are required to do something, it’s not really a “proper” glitch. Things like duck spam are OK because they are theoretically possible with normal input but I don’t like spamming console commands which aren’t even gameplay related in order to skip gameplay. I suppose it’s kind of cool how you can skip large sections of map though. Hmm…