[Gtkradiant] [Bug 521] New: q3 trigger_hurt problem?

gtkradiant@zerowing.idsoftware.com gtkradiant@zerowing.idsoftware.com
Tue, 14 May 2002 07:44:04 -0500


http://zerowing.idsoftware.com/bugzilla/show_bug.cgi?id=521

           Summary: q3 trigger_hurt problem?
           Product: GtkRadiant
           Version: 1.2
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: editor
        AssignedTo: ttimo@idsoftware.com
        ReportedBy: ttimo@idsoftware.com


From: Brenda Make <brendieellen@yahoo.com>
To: Timothee Besset <timo@qeradiant.com>
Subject: Re: Qeradiant bug form
Date: Tue, 2 Apr 2002 02:33:57 -0800 (PST)

Select a brush, make it into a trigger_hurt. Read the
last sentence. You can't make it toggle unless the
spawnflag is set for it, but it doesn't exsist in the
entity definition.

There are only available:
silent (4)
no_protection (8)
slow (16)

I had found a workaround somewhere for this online and
never bothered to submit a bug. For some reason
manualy setting the spawnflags to 11 will make it
work, though it would seem that more than one flag is
being set at once by choosing 11. I have been away
from this for a while, and I can't remember where/how
I found the fix only that I didn't discover it. I have
a feeling that it is either the 1, 2 or 3 bits : )

----------------------------------------------------------

I looked at trigger_hurt, and the help says:
-------- SPAWNFLAGS --------
SILENT : supresses the sizzling sound while player is being hurt.
NO_PROTECTION : player will be hurt regardless of protection (see Notes).
SLOW : changes the damage rate to once per second.
-------- NOTES --------
The invulnerability power-up (item_enviro) does not protect the player from
damage caused by this entity regardless of whether the NO_PROTECTION spawnflag
is set or not. Triggering a trigger_hurt will have no effect if the TOGGLE
spawnflag is not set. A trigger_hurt always starts on in the game.

It actually looks like the TOGGLE spawnflag is missing
anyone know which bit it is?



------- You are receiving this mail because: -------
Whoops!  I have no idea!