InsideQC Forums

frag.machine wrote:monster_army (and monster_enforcer IIRC) are the exceptions, they'll try to kill another of their kind

Nope. Enforcers are "smart" enough not to.

Currently working on a tutorial for QExpo that will, among other things, explain how to make monsters use coffee_move()

Indeed, this is at least a temporary solution to this problem. Should I expect nasty side effects if I increase the body limit to 200 and play on a large map? It would be nice if all the bodies stayed.
Assuming the map doesn't give you a no free edicts error when you load it, there's no guarantee ...

3.) Body and head gib disappearing
This is the most important finding !
You can kill 4 monsters and wait for as long as you want. The body or head gib will never disappear.
BUT: If you kill the 5th monster, the 1st of the 4 already killed will disappear.
This is absolutely reproducable.
Only 4 ...

Jump velocity is specified in the QuakeC (player.qc, PlayerPreThink() I believe).

When was the last time you looked at your config files?

leilei knows eir stuff with these things. Check your config files. Make sure that every alias does what it's supposed to. You have a stray +forward somewhere...

It might be easier to have a model of a tracer, and fire that as a projectile.

Since sp4x0r put all of the groundwork into getting the right answer, and then got it wrong at the end:

0.1 (or 0.04, to use the number that FireShotgun() uses) isn't directly an angle measurement at all. It's "for every unit that the pellet moves forward, it can move left or right (or up or down ...

ET also has issues where certain things (I forget what exactly, as it's been a while, but I think that uniform changing is one of them) happen at the wrong speed if sv_fps isn't 20.

Nothing in the engine should write outside of the Quake folder, period. The person who downloads your engine in investing an awful lot of trust in you and you better repay that trust with responsibility.
I'm not very Linuxy but don't some of the distros by default disallow writing in the Quake ...

1: Make a pallete image

2: Load it in Fimg, and export it as whatever format the engine expects.

3: With Fimg still open, export a colormap of the palette.

4: Put them all where the engine expects.

5: Modify all of your assets to use the new palette.

Also for 8-bit colored lighting, you might want to look at the Vavoom engine. It's a quake-based doom port that uses quake's rendering as a base and has neat stuff implmenented in 8-bit color software, and even has new ASM code for drawing colored lighting surfaces in software.
Depending on how ...

1: I tend to watch speedruns, and people playing games that I'm interested in.
2: Not really, no.
3: I prefer watching when there is being some "skill" exhibited. Not necessarily "best in the world", but at least "reasonable". As for what I like to watch, I tend to stick to FPS games and puzzle ...

Overloading .owner like that will cause problems, because it affects collision detection. Using a float field is probably enough.