I'm pretty sure doing co-op flags progs side will make them as effective as the engine side flags, as long as you make sure the removal code preceeds any precaches the entity code has. All the bmodels in the map are cached regardless of whether the entities that use them are spawned or not - you can check this with the mcache command. So it's only precaches of external files that are reduced by spawnflags, and these are the ones a co-op flag would help. 

i like this a lot!!!

"force fields" 

i was refereing to bmodels. 

and i didn't know that! (wish i could edit posts...) 

You are both so sexy when you talk Quoth. Meanwhile -- ooh, dibs on starting the coop pack idea again! 

It's great to hear from both of you again, and a relief to know that you are still interested in finishing up the Quoth pak1 content.

I've been doing some optimisations to my big map myself, and have managed to add a couple of new enemies without going over the limit for precache models, but I have a lot of secrets that need triggers (more than red777 ;) so that trigger code is going to be a life saver.

I'd really appreciate the head model disable worldspawn flag if it's not too big a deal to implement.

By the way, the info_trap works really nicely - I set them up in my map last night. The only thing it's lacking right now is the ability to set custom models (I really want to use lava balls). There is a lot of flexibility there otherwise - seems like one might be able to make some really nasty surprises for the player with some creative use of the entity.

I think I've asked Metlslime multiple times about increasing limits in Fitzquake, but I don't think he's been working on FQ lately for whatever reason. I'd prefer the max marksurfs were knocked up over the precache models though... that's the real killer right now :/ 35577 :(

By the way, I've been doing a fair bit of texture modification for both my basemap and the knave map, and haven't noticed any problems with texmex's colour conversion or removal of fullbrites. Generally it seems pretty good. 

i will look into the head model disable option. i'm not a fan cause that would just be so ugly, but i can understand the need to scrounge precache slots. on the other hand, entity triggers may be all you need...

also, info_trap was never finished, and it will definatly have the ability to have custom models (sprites and mdl) as well as as much flexibility that is possible. 

And what about new monsters (i.e scourge, ogre_flak, eliminator, pyro, sentinel...) Will they be included finally ? 

I got the bright idea of checking hotmail.com to see if I could find a working copy of your map since the msn file was mangled, and it does have a working file (guess that means msn and hotmail use different means of storage, kinda interesting).

I'll beta test it first thing tomorrow evening when I settle in. 

I saw your email this morning, and I have just sent the stuff again ;P Check your mail box ! 

I'll write up a report soon. I have a lot of comments, but at the moment I'm a bit stuck (in the sludge corridors). It may be something flakey
I've done to screw it up, so I'm going to replay it tomorrow. Maybe with a fresh run I'll have a better idea what the problem may be. 

I'm a bit stuck (in the sludge corridors)

he he he... so you didn't find the exit... I think you still need to explore it a little bit more ;) 

I think that ent based triggers will be all I need to stay under the limits so long as I can use most trigger types in this way... trigger_multiple, void (not so important), once, secret and hurt (again, not so important) support would be nice, but if that's not possible, then once and multiple would be the obvious choices.

By the way, do you have any plans on how the triggers will be implemented? Will we enter the min and max coordinates, or a width and height about the origin of the entity? Either way seems ok to me - I'm really looking forward to implementing them in my big map :)

Also, I think I've found a tiny bug with the monster path follow code. I think this code was modified in a previous version of Quoth so that monsters would face the right way when stopping at a path point. I've noticed that with the ogre at least, there is a barely audible high pitched noise that plays when it gets near a path_corner and continues to play whilst it is near. I'll set you up a map with this in if you can't reproduce it and don't know what the cause is. 

c/d 

the ogre is wierd in that the saw dragging sound gets played whenever it hits a path corner in the old progs. it's possible that that's interfering with the new path corner stuff. i don't really understand what you mean though, but i'll look into it for sure.

also, there's no reason not to support all trigger types as entity triggers. 

ELEK�s unfinished SP "Technophobia" has nice "techy" monster skins, maybe they would fit well into the pack ?

http://tertiary.planetquake.gamespy.com/
http://shub-hub.quaddicted.com/files/maps_singleplayer/techphob.zip 

no.

I'm the first to admit I'm not the greatest skinner ever, but I can do a bit better than slapping some generic Q2 bollox onto the Q1 monsters who, frankly, don't deserve such abuse.

Also, any base map that uses Enya as an ambient sound is to be treated with caution :P 

ELEK did have nice sense of style, nevertheless :-) 

I just completed the level. I'm writing up a report right this moment.

Cheers 

Bob is better implemented in the base beta pack. He feels more like a dangerous and nasty minion instead of a boss monster in a sentry's drag as he does in standard Quoth. 

Thanks! I'm gonna check my mailbox ;) 

So that's why everyone hates the b0b. Never had a problem myself - the dodging thing isn't too difficult once you recognise the pattern.

Hm, pattern = boss. 

I think Bob just has too many HP for a floating drone. He shouldn't be tougher than a grunt. He's just a cheap, mass produced robot. 

I'd like something exactly like the flyers in Q2, that's what I meant to say. 

The bob drone was my least favorite of the Quoth monsters. The model just doesn't look 'Quakey' enough.