I can think of so many scenarios in which that would be awesome. 

You forgot the func_destructable (or whatever it was called). It's in Quoth1 but doesn't work.

Yes, no requests; but to have that working and destroyable by enemies and the player would be the muts nuts. 

On my current project, I used Quoth, and I have a weird effect when (quick)saving, and reloading the map. The monster count (at the end of the level) doesn't correspond to any of the skillset.. Any idea about this issue ?? 

A flag on all flame lights / braziers for 'burning damage' - the player takes 1 damage per 0.5 seconds that they're within 8 units of the light's origin. With the 'BBBB played with fire' deathmessage, of course. Wouldn't work for the tall braziers but the others would be ok. It'd just save a bit of legwork and entity count.

Ok, no more requests.

Except maybe drowning, burning and corroding monsters. And weight physics. With tipping. 

The way I see it is that I've taken over coding for Quoth, but I've haven't taken over designing. I'm a caretaker. So I'm trying to work with a soft touch, not really adding things that aren't already established in Quoth, just implementing promised features and bug fixing stuff. Even adding the key dropping feature was probably overstepping those bounds. If there was something that is absolutely needed for a one of the maps in this pack, then I'd probably relent.

Also, if you can persuade Kell or Necros it's a good idea, I'll add it. 

Something like the built in flame damage would be a nice thing to have, but its not a map breaker and I reckon you've got enough on your plate with all the 'promised' stuff.

I'm putting something together now in Quoth which will be finished after Quoth2 is out; so I'll most likely backtrack and integrate the new features / enemies it contains.

Just thinking that anything that makes Quoth a more universal Quake mod can't be a bad thing; ie. 'why use Quake standard progs anymore?' 

... because the weapons and other player resources are actually balanced against the monsters? 

Just thinking that anything that makes Quoth a more universal Quake mod can't be a bad thing; ie. 'why use Quake standard progs anymore?'

That's what I was thinking. The trigger related stuff isn't going to imbalance the gameplay because it's more for map scripting etc. But yeah, I guess it's important to get the opinion of Kell and Necros before messing with things too much. 

is the single most irritating thing I've ever encountered in a Quake map. 

The Quake Guy is too bad ass to be damaged by mere torches. 

yeah, I don't like it either because it feels like the mapper has gone to some effort to add something totally pointless that punishes the player for no reason.

It was pretty pointless in Q3 too and the sound effect was shit.

Besides, now you can add trigger_hurt without using a precache slot, you can set them up manually for each torch and do the same shit if you really want to irritate the player. 

as Ijed said, would be required for maps currently in progress (as Ijed put it, "something") but aimed at "after Quoth2 is out" :/

In short, I still think that "backtracking" is suboptimal. We'd have to redo monster placement and playtesting. I got the progs updates, but the pak updates would be nice too. Kell, did you choose to not reply or did you just not get my email? Or is there "another reason"? :) 

it more irritates when flames don't hurt! 

Sorry, not at my computer, so I put them here.

1. After dying in f. ex. slime, the screen is still tinted upon respawn. Happens regularly. Example is the Quoth startmap, die in the lava and respawn with red tinted screen. Tint goes away when picking up armor etc.

2. togglewall (forcefield) is buggy. The particles often aren't spawned for no apparent reason, but the wall is obviously working/blocking. To do with proximity of other ents? angle? texture? other forcefields? Noise/noise1 key isn't working on togglewall at least when used as forcefield. I have to use a trigger_multiple for playing a blocking sound.

3. Breakable is buggy. It looks for rock.mdl but can't find it. It also can't find some impact sounds. pak issue? :(

Feature request (hey, I reported bugs): Could the forcefield only spawn particles when touched? That shouldn't be too difficult to implement. Star Trek style.

gb 

^ 

Lots is going on behind the scenes here, don't worry.

The 1st bug in the post above was kinda interesting though, as it turns out it's a very long standing engine bug. If you're in lava and you execute "v_cshift 0 0 0 0" command, then restart the level, the lava tint remains and v_cshift doesn't affect it. This only occurs in software rendering engines though. I have just this minute discovered a workaround for this though, "v_cshift 0 0 1 0" looks the same, because the intensity of the colour shift is zero, but the bug doesn't occur for this value.

Fun time trick: run winquake, and type "v_cshift 0 0 0 -2500" in. Better than the TF spy's grenade, that's for sure. 

...please send source for PH8DM2 to my gmail acc. Ta! 

still working on mine second maps 70% made ore one month t might be ready! 

...if it drags on a bit more I might be able to add this to the mix:

http://img263.imageshack.us/img263/6071/dissp08zl1.jpg 

I still have plenty of work to do on my map and I wont get to it until the Indian Summer map is finished. No official due date has been given, I suspect it will depend on the next pak release, and come through a consensus, and typicaly such things are scheduled weeks after a consensus is reached.

Trinca has the URL for the beta pak tucked away somewhere, so I would suggest shooting him an email if you need it. 

that looks straight out of a Doom3 mod with model to brush designs and everything! 

What is this texture set? D3remix?
Sweet honeycomb pavements and lacy metal beams...
Fine lighthing.
Me want it! 

If anyone wants to make a map for this pack, without taking a ton of effort, I suggest my recently GPL'ed base map for the task :D 

It's nice to see how good you use Doom3 texture set ;)
You rock ! 

...thanx for the encouragement, I'm putting this one at the top of the "to finish" list.