Trigger load bug

Printable View

Show 40 post(s) from this thread on one page

15th November 2020, 07:33
IzNoGoD

Make your own trigger_use_touch by using a trigger_multiple with a hud element ("Press F to activate") and a custom script.
15th November 2020, 13:17
pollo

Quote:

Originally Posted by IzNoGoD

Make your own trigger_use_touch by using a trigger_multiple with a hud element ("Press F to activate") and a custom script.

Thx, will do this :)

Btw, is there any way to simulate a trig_damage as well by script? By libcod maybe? I thought to use setAlive but maybe there are other options. Will test this afternoon :)
15th November 2020, 18:24
IzNoGoD

Quote:

Originally Posted by pollo

Thx, will do this :)

Btw, is there any way to simulate a trig_damage as well by script? By libcod maybe? I thought to use setAlive but maybe there are other options. Will test this afternoon :)

Setalive() turns stuff (script_brushmodel for example) into a trigger_damage with a damage notify.
15th November 2020, 19:10
pollo

Quote:

Originally Posted by IzNoGoD

Setalive() turns stuff (script_brushmodel for example) into a trigger_damage with a damage notify.

That's perfect then :D I'll report back after testing it
16th November 2020, 00:57
pollo

Update on this:

I remade all of the buggy triggers from scratch, but now making sure they don't collide with any other brushes around (for doors that need the trigger to be at both sides, I did Mitch's technique; making 2 brushes, 1 per each side, and then making them a single entity). By doing this, the trigs from the jail were fixed, but there was another that still was bad (one of the doors). However, setting a different width/height for that trigger also fixed it. The only buggy one now is this trig_damage, that I'm gonna try to do through libcod.

So all in all, apparently this is fixed by trial and error :confused:

Last edit:

Trig dmg also fixed, I just moved and rotated it to a near position. All works now :D

Show 40 post(s) from this thread on one page