Because BSP2 > 2PSB and supporting 2PSB makes compiler and engine programmers cry in their sleep. 

Because BSP2 > 2PSB and supporting 2PSB makes compiler and engine programmers cry in their sleep.

Is that just your opinion or do you know that for a fact? Have you asked the people who create engines and compilers if they get 2PSB nightmares? :) 

Why support 2 standards that are similar if one will do the job? It's unnecessary overhead and code maintenance. 

Can this be done? I want to cast a Q symbol but I don't want the brush to be seen. 

 

With that new compiler that lets you cast shadows from brush entities, you can give the brushes the classname "info_null" and set "_shadow" "1". Does waste a model precache though... 

You could potentially use a bunch of negative lights too, but that would likely look like ass and be a pain to do. 

I always thought it would be cool if someone made an engine where you could go round the map and "spraypaint" the lightmaps. Basically just go round with a dynamic light that never went away. Then you could add a negative "brush" that subtracted rather than added light, and you could use it to fix up glitches or do weird effects. It'd probably be hard to make it robust in the face of recompiling the map, perhaps you could replay a demo to repeat any painting you performed. Anyway, that's my mad thought for the day... 

 

Um...hesitant to ask, but...

Is there any sort of maybe legal issue with using something from the mission packs? I know Quoth used the Scourge(the scorpion to you heathens who don't know) from hipnotic's pak (hipnothetically, of course), but is this legal? And to what extend? If someone hosts the entire mission pack in the zip along with a custom map so that someone can play it, is it illegal?

Methinks melord thou art a theif. Y/N 

Don't host the entire mission pack; it's copyrighted (and actively being sold on steam) - that would be illegal.

Including a few assets from the mission packs in a Quake mod is probably fine, but the copyright on those assets (models, textures, whatever) is still held by whoever owns the rights to the mission packs. So you're working under the assumption that they are OK with what you're doing, which they probably are. 

I'd agree that including the scorpion in a mod like Quoth without permission is strictly speaking illegal. It's the same for maps that use texture sets from other games like Quake 3 or Daikatana, taking an art resource and re-purposing it in a similar setting, essentially is a act of redistribution without permission.

Morally speaking, I'd say what differentiates it from including the entire pak and all the maps is a matter of substitution. Including all the maps would make your mod a complete substitute for the mission pack. Someone who downloaded that would have no reason to buy the mission pack, harming that product's potential sales. Including the monster in a different mod doesn't do that; the value of Scourge of Armagon is preserved.

I guess it's kind of a map-centric view of things, but I think the experience of the mission pack is "play through these particular maps", rather than "play against this monster in some notional maps which may or may not include the maps supplied". If a cease-and-desist order were made, we'd comply without hesitation, but for a free mod I doubt we'll ever see one. 

you can just say it's a parody and get off scott free... that's how I got away with all those murder rapes. 

The Mapper's Ethic for Other Mod Inclusion:
I won't include the maps.
I won't include the demos.

I will include the monsters I want.
I will include the items I want.
I will include the code I want.
I will hide them in the .pak file(s).
I will include a "Special Thanks" in my readme.txt, whatever it may be called.

I might consider notifying the author before releasing my map...
...if I can find their contact info.

I won't release if the author doesn't want me to, but they will have to act fast.

I will revoke a release if the author of content I have used wishes me to do so.

Signature___________ Date________

Here's a pen ./

Side question: Didn't the Drake Mod use the Quoth Drole? 

A. The castle will rise from its vortal depths... 

it doesn't need to be so complicated. ask before using stuff, if they say no, don't use it. if you can't contact them and you've done due diligence, just use it-- it's likely a really old asset anyway. 

Aside from hiding the brushes casting the shadow inside a sky brush or behind a func_wall there is another way but you need to be sure that the brushes involved are well out of the way of game play because even though you cannot see them the engine WILL treat them as a solid (invisible) brush so you and the monsters cannot walk or shoot through them.

You will need a BSP compiler that supports the skip texture and detail brushes (Tyranns does using the entity name, func_detail).

Make whatever shape that you want to cast a shadow and make them all func_detail (you can group them and then do it all at once) making sure that you use ONLY the skip texture. Viola, an invisible brush that casts a shadow. A solid (as far as light is concerned anyway) clip brush so to speak.

An additional benefit of this is because the compiler changes the func_detail into a plain old everyday brush it has no effect on the number of entities\models used in-game.

This works for two reasons. All detail brushes are rendered so that vis compiler will ignore them but the light compiler will see them as a solid brush. By adding the skip texture the bsp compiler will not let them get drawn in game. If you simply did a skip on a solid brush it wouldn't cast a shadow but this trick, where an entity (func_detail) is turned into a solid in the middle of the compile process does work so that the light compiler "Sees" the brushes even though the player does not.

But like I said, it's an invisible solid brush so you need to be absolutely sure that's it's out of the way (rocket launchers and Skraggs are an obvious no-no here and probably tar babies and fiends as well, oh, and no way for any enemy to shoot at you or jump on you from above). It also cannot be touching "Anything" aside from itself (in other words it must be free floating, it can be a collection of any number of func_detail + skip brushes touching each other but that's it) otherwise the contact points will give you a HOM effect.

Have fun! 

I went for the age old method of hiding the brushes inside the sky volume though I enjoyed all the different methods suggested.

I'm not 100% sure about using the Q symbol in the way I have in the end, the area I used it in seems a bit busy now. 

Tyrann's tools
_shadow 1 with skip texture shove it anywhere 

Adds to your entity count. Func_detail does not because it gets converted into a regular brush during the compile process. 

That's why I suggested using an info_null, which will get removed. Both ways still add a model precache though. 

Is there a limit to the number of precaches? 

What's the limit for engines nowadays? 

Personally I prefer the "fuck the limits" option and go for full bsp2 support. Quakespasm is my current favorite for this. Afaik it has no limitation on precaches. 

255 is the maximum that will work in all engines. Lots of leading engines do increase this limit, but because it requires a protocol change it's not trivial to do. This means lots of minor source ports don't have the feature.