 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
monster in Quake mapping, other than the guardian from Dissolution of Eternity, both creatures get worse press than they deserve, and conversely the ogres are way overrated.
Ogres are overused because they're fairly multifunctional, apart from the aforementioned aiming dumbness.
I never really played the expansions much, I always preferred the community stuff. Think I'll give them a look now though for resources / ideas. A monster that leaps quickly and spastically at you, but also explodes fatally when you kill it, is pretty clearly a bad idea. It's telling that Romero's main intent when he came up with them was "this'll really fuck with the keyboarders!"
I'd do one or the other, but not both in one monster. The kamikazes in Serious Sam lent some nice tension without being overly cruel, even if the sequences they were in were pretty stiff shooting galleries, and the fast headcrabs in HL2 were also good without also killing you when you finally nailed one with the shotgun. I forsee a revival of the original plan for the vomitus - a slow but deadly exploding monster that vomits out the small fast spawns that don't explode. (Isn't 'tarbaby' kind of a racial pejorative?) I've revived a version of the Vomitus that gobs zombie gibs and bursts into damaging gibs when it dies - kind of like a polyp, but has a bigger splat if gibbed with a rocket.
It was originally supposed to create spawns? Bloody hell. I like exploding tarbabies / spawn - although granted, for keyboarders they're probably not much fun. The name Tarbaby - kind of like Goomba's. And I reckon this thread is the place for heresey. There's a hipqc on quake's, but you have to search
http://www.gamers.org/pub/idgames2/idstuff/quake/ meanwhile, here you are... http://members.home.nl/gimli/HIPSPIKE.QC Cool:
Spawn (being well used these days) Vomitus Ogres Spike Mines Uncool: DOE Guardians (crappy, ugly, badly themed anti-Quake bollox) Jury's still out: Z-Axis Ogres or whatever the fuck they're called. I've downloaded the source now, but the qc that you looks to be the gremlin or fiend - odd.
The guardian - thats the egyptian enemy? always thought they were crap, tbh. And a bit gay. The Vomitus and Zombies are also z-aware, though I'm thinking to cap their max throw distance so they hit the ceiling less. (Isn't 'tarbaby' kind of a racial pejorative?)
It comes from folk lore: http://en.wikipedia.org/wiki/Br'er_Rabbit term refers to a type of trap which describes the hellspawn though they don't actually stick to you. The id guys were probably thinking of a bugs bunny version of this where the tarbaby was a lit piece of dynamite that the antogonist could not shake off once he grabbed it. Boom! used to be the enemy everybody hated. But, they can be used (and as shambler says, have been used) well, and they are great for causing panic.
Also, spike mines are simple and cool. Sweet mother of christ when will this madness stop?!?!
Actually I think they'd be a lot better balanced as z-aware than the Ogres would... when I'm soberer
Inertia, like I'm always banging the drum for - lazarus q2. They had damage groups. When an enemy gets hit by another it gets angry at it, damage groups meant that one group could get angry at a singular other enemy. It was meant so that a player couldn't snipe a group with the railgun without the others waking up. Thanks for the link Madfox, I'll check try and integrate it tommorow, on hangover sunday. I think that making ogres z-aware shouldn't be the same thing as making them infallible, continuous dropshot lobbing monsters. Sometimes it looks a bit odd when they're actually firing down a flat long corridor and the regular shot would work fine, but they lob into the ceiling instead. What I would try is:
1. Have them check the intersection point of the regular shot trajectory with the ground level they are standing on (might have to go 1 unit below to deal with the edge case). If this is solid, then take a regular shot, and if it's non solid assume you need to lob. This is obviously a fairly crude decision process, but places it might break down like broken ground/uphill will only look as odd as it did before one way or the other. 2. Have the ogre decide the elevation in advance. Make a separate function that calculates elevation, and call it from say two attack frames before the grenade is fired(is that ogre_nail2 ?). Then store that elevation in an unused field on the ogre, and use the value when you fire. Of course, y-axis yaw should still be tracked accurately, that would be a penalty too far. I'll admit I've not gone away to create and test an ogre like this, but I think it might help them feel less robotic in the way they aim. At the same time, it wouldn't revert back to the point of being safe from an ogre simply by putting a chasm between it and you.
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2026 John Fitzgibbons. All posts are copyright their respective authors. |