 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
The machine sound is always precached regardless of any entities you add, so that it's first on the list for some protocol message hacking. Not sure why drip1.wav isn't being precached if you've set it in the noise field, I've just made a test map in which this sound works.
I also included a door with 'sounds 0' and I get no warning messages. "doors/ir_strt.wav" is the noise for 'sounds 5', but if that was the cause then it would be precached. You're gonna have to send me the map file with these problems, as I can't replicate them myself. Oh, I didn't know there's a 'sounds 5' option (as well as 'sounds 6' which uses er_strt/stop), especially since none of the sounds are included in the Quoth 1/2 paks.
I'll send you the map file later on. Sounds to me like you're trying to do some hacky stuff with the noise fields to support custom sounds on your door. This isn't necessary in quoth, leave the sounds field at 0, and set noise1, noise2 to the desired effects. They will be precached by the progs if you do this, so you don't have to worry about including them with another entity.
Yeah, I'm using sound hacks. Setting the sound fields to 0 did the trick.
As for the ambient_generalpurpose sounds, I don't know what I did apart from moving some entities up the list but for some reason it works now. Odd. Place the button in line with the starting position of the door(the "closed" position). Not very intuitive, but the buttons don't take account of the spawnflags of the door. In theory this could be changed, but if I did that now, then you'd be put in the position of making a map that works with the current progs, or one that will work with a new one.
New issue: It appears from the documentation that trigger_relay can't use the broadcast flag. Yet, when I rename it to trigger_once (so I can set the notouch flag), the entity mvoes to the origin and becmes unselectable by clicking on it (GTKR 1.5.0). I must be missing something here...
The documentation might be a bit misleading then, because the broadcast flag does work on a trigger_relay, it should work on any of the regular entities used for activating targets. Myself and Kell would like to add that we cannot be held responsible for editor bugs that result from attempting to make a Quoth map : - ).
No, that was only added to trigger_hurt, and I didn't know it was there until now. Adding it to trigger_multiple/all triggers is certainly something to think about for Quoth part 3 though.
Finally being able to toggle triggers is something to think about for Quoth part 3!
it being a neat little feature, but a bit limited for trigger_hurts; only really good for making health generators.
The multiple targeting features mean the mapper can just killtarget whatever they like, but an internal thing (to the trigger) would make it simpler and avoid potential logic fuck-ups. I was wrong about "that just leaves". I've also noticed that info_groupspawn and info_multispawn aren't described in here yet. Because it's not obvious to me: which one is the old func_hordespawn, and what does the other one do?
The documentation specifies the following:
coop_only = 4096 not_in_coop = 8192 However, my own experiences, combined with examining the source to e1m2quoth tells me that the opposite has been implemented, namely: not_in_coop = 4096 coop_only = 8192 This could be a serious shock to any mapper that doesn't do lots of testing, and a source of confusion to any mapper that does. Was a definite wtf moment for me... Both of these entities are for spawning multiple monsters(or items are supported now) from a single entity. Combined with corpse removal or judicious killtarget use, this lets you juggle entities in a large map. They differ in the position and way they put the monsters into the map once triggered - the multispawn teleports the monsters in one at a time from the origin of the object; the groupspawn teleports a whole squad in at once.
info_multispawn Quoting from the old documents on func_hordespawn: This entity spawns them in one at a time from the same point (it's origin). The entity will only spawn a monster if there is room, and will wait if there isn't. Once it is activated, it will spawn until it has created the amount of monsters specified. The value for "spawnclassname" and "spawnfunction" should be the classname for the type of monster to be spawned e.g. monster_demon1. Both of these values must be added and both must be the same. Only one type of monster can be spawned form each func_hordespawn. Specify the number of monsters to spawn with "count". Default is 3. Key change here, the default value of "count" for an info_multispawn is 1 instead of 3. Note that if you use the old name of func_hordespawn then the default remains 3. This is the only difference between these two entity classes, and the latter only exists for legacy support. So don't include it in entity definition files "just for completeness". The "wait" key as usual is used to specify the pause between each spawning. If you want to have different types of monster spawning into a horde, you can use multiple func_hordespawns but you cannot place them on top of each other without risking different monsters getting stuck. It should be added that only the following keys get transfered from the info_multispawn to the monsters spawned from it: angles spawnflags target corpse_time startonground aflag For anything more sophisticated(if you're trying some entity hack for example), you need to add the entity in the regular manner. info_groupspawn All the info about setting spawnclassname, spawnfunction, count and which keys are transfered is common to both these entities. The wait key is not used. Instead, the monsters are spawned in a grid starting from the origin of the entity. The entities are spaced "lip" units apart, and the rows are "t_width" units wide in total. So to get a 3x2 block of monsters 64 units apart, set "lip" to "64" and t_width to "192" You may have to experiment a little to get the placement and values correct. (thanks to Kinn for this idea) Yeah, the documentation has them transposed, from the source:
float NOT_IN_COOP = 4096; float COOP_ONLY = 8192; Ok, we've had you waiting a lot time, but there was one glitch that took this long to iron out. I now present to you the Quoth 2.1 patch:
http://kell.quaddicted.com/quoth/quoth2_1.zip Drop the pak2 in with pak0 and pak1. There's a full list of fixes included, but the main ones are fixing the info_bomb crash and including the default earthquake sounds. Another big change is that info_rubble/func_breakable entity now support a "dmg" key which sets how much damage they do on contact, and setting this to 0 makes rubble do no damage. Now, I know in this thread I argued forcefully for damage to be non optional, but Kell persuaded me with a more compelling argument: the entity as it stands is so flexible in terms of types of debris it makes, that it should be able to accommodate both things that inflict damage and things that do not. So that change is in, and I don't think too many people will bemoan it. Many thanks to Than and Ricky for doing the playtesting on this, hopefully there are no huge bugs left. Enjoy. Quick question: How can I get all the information I need to map for Quoth 2 in GtK? I apparently only have enough for Quoth 1.
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |