VanishedOne

Right, test results: You can't 'backstab' a lanternbot; steambots have a sneak_attack_mult of 1.0. However, it doesn't immediately blow the whistle on being damaged (I'm not quite sure why it doesn't react more: its only senses are auditory, but according to the console it enters a pain state on taking damage), so you can probably get in the second blow right away, though it may have time to turn around and light you up. The sword is louder than the blackjack: with a human AI about 340 units away, knocking out the lanternbot provoked no barks, 'killing' it provoked a bark and on higher auditory acuity settings he became more likely to turn around. Lanternbots shed blood and sometimes make fleshy noises when slain. Not as drastic as I feared, but not a trivial change from when maps with it were designed, tested and released either. The last point makes me wonder how extensively attacking lanternbots has been tested by anybody.

According to the descriptions given in the game console, image_usePrecompressedTextures is the cvar to 'use .dds files if present'. If your only TGAs are things like light textures (which tend to have forceHighQuality set in the material) and cubemaps, image_useCompression shouldn't make much difference, but working with TGA assets I haven't compressed to DDS yet, I found they had horrible colour banding on my system and only looked decent with image_useCompression turned off.

The language of 'overpowered' and 'balance' does seem to me to be curiously placed here. If you're making a shooter, and one weapon is so much more effective than others that they don't even see situational use; or if you're making an RPG with selectable abilities, and nobody wants to invest in +1 damage against mud elementals when +10% evasion against everything has the same cost, then okay, you have a balance problem. That the feature to make moving ragdolls over distance more practical is chosen by players intending to move ragdolls over distance doesn't strike me as the same kind of thing. Edit: to add a more positive note, I think this perceived problem may relate to the fact that players are most often dealing with human bodies. In Thief a dead/blackjacked crayman just can't be moved from its spot, which means you choose your spot carefully if others are around. In TDM, if anything is like that it's... the horse? But in TDM you also have AI you can drag but not shoulder: so, the lanternbot. Also spiders but you're unlikely to want to hide a spider corpse. I see the new werebeast is also set not to be shoulderable but it remains to be seen what effect that has in gameplay.

Ah, the old 'grass edge' problem. Are you using patches for the grass? Your best bet is vertex blending but it requires using a model; DR has an export script that's supposed to help with this. Failing that, there's this.

Thanks, but I wasn't asking as a question of law, I was asking because I wanted to know the answer.

Is the assets SVN public now? I knew the glprogs had been made part of the public source code at https://svn.thedarkmod.com/publicsvn/darkmod_src/trunk/ but hadn't heard of any opening of the assets SVN.

Were signals of no use? That looks to be how you're 'expected' to find out whether a mover has arrived or been blocked.

The fog of memory having cleared a bit, I think what specifically got me an error was making an entity target itself, before anything could get as far as actually triggering anything.

One of the mysteries of Doom 3's development is the shadowDraw keyword. In D3 it exists in shaderdemos/shadowDrawLight in shaderDemo.mtr but the code to recognise it seems to have been stripped out at some point. shaderdemos/shadowDrawLight { // this would default the same if not specified lightFalloffImage makeintensity( lights/squarelight1a.tga ) { // this stage will be drawn normally map lights/squarelight1.tga colored zeroClamp } { // this stage will be drawn on the shadows, still modulated by the lightFalloffImage shadowDraw map lights/squarelight1.tga rgb 0.5 blend GL_ZERO, GL_ONE_MINUS_SRC_COLOR } } The leaked Doom 3 E3 demo comes with a variant of this material and will accept the keyword, but doesn't do anything with it that my eyes could discover. My guess is that id was experimenting with it as a way of reducing the black shadow effect on some lights. I've only played through D3BFG, which apparently brightened some scenes, and when I played the leaked E3 demo I was struck by how oppressive its darkness was atmospherically. There is no flashlight in the demo; instead you can spawn light grenades from the console that work similarly to T2's flares. Constantine would have approved.

You could try putting a path_flee_point_rats in your map, but it seems fish have to be pretty close to the blast to want to flee it. Edit: setting is_civilian seems to make them keener to flee, but I don't know whether that's all the spawnarg controls or whether it's also involved in 'Don't kill innocents' objectives. I notice rats don't have it. Disabling unarmed_melee also seemed to help. Despite having been able to injure one with the blackjack before, I'm now finding them remarkably resistant to melee weapons... Edit: ... which is an unexpected result of having af_push_moveables turned off. The rat and tiny spider have it disabled too, so arguably it's the default setting for ambient AI even on land, but if you want to slice up fish you should re-enable it.

And I've discovered why my initial attempt to disable searching had no effect: the spawnarg is canSearch, not can_search as in can_drown or can_unlock. And I put the wrong one in the updated def, so I'll need to change the download again. Coming momentarily. Edit: done.

I once tried to make an entity trigger itself via S/R and got an error message saying entities aren't supposed to trigger themselves; so I had it trigger another entity, which had a Response to trigger it right back.

Thanks for the help. I imagine they might be missing something that the search internals expect; I didn't give them an AIUse value, for example, but they inherit visual and communication S/R so maybe they ought to have one.

Maybe turning af_push_moveables off has just made my mine better at killing them all because they're no longer so good at pushing each other out of the way. With enough survivors I get a crash too, and assigning a search anim in the model decl doesn't prevent it. Edit: updated download is live.

On its own? I'd already tried that but thought it hadn't worked. Anyway, I'll update the download shortly with both spawnargs set in the def.