My mistake then. Didn't read carefully enough. 

Yeh, but the line about trying to extract them without breaking things implied a need for software linkage...

What tool you making Willem? Or is this a new feature of Toetag? 

I have a WAD editor I'm working on

I win reading 

I'm redoing ToeTag as an editing suite so it'll have a level editor, WAD editor, MDL editor, PAK editor, and a bunch of other stuff. It's a longer term project but it's steaming along.

I want to also add stuff like editing sprite files, QuakeC editing/compiling, etc. 

i was expecting more of a challenge, texmex is fast

i found an email for on the web comic he is doing (http://emotel.comicgenesis.com/)but if i do not get a replay ill most likely just use them w/o discreetness to see if i get a hollah

anyways, ToeTag looks cool from the screen shots i have seen, is it still only for mac things though?:O

anywaysanyways, thanks for the helps, cos this did help..in some way :D 

Can someone point me in a direction here... I need to get a few zombies (and by a few I mean a horde) to play dead until triggered, ambushed, whatever, then get up, rise from the grave as it were, and start attacking.

Crucifying them is fun and all but gets boring after awhile. I'd like to try some necromancy.

Thoughts? 

http://www.gamers.org/pub/idgames2/quakec/monsters/4zombies.txt

http://www.gamers.org/pub/idgames2/quakec/monsters/4zombies.zip

It should do what you want, though you'll probably need to refine some stuff. 

wait, are you the same guy i told the half-zombie idea to? but i digress:

http://www.gamers.org/pub/idgames2/quakec/monsters/

has some zombie stuff in it, it *might* have what you are looking for, but if not than maybe look for the zerstroer source, it has that kind [i guess i mean they do wait till a trigger or somfin then the rise ...right?

http://retroquake.planetquake.gamespy.com/blog/?p=177 

 

would it be possible to do this:

1. make normal zombie.
2. make a func_door with the skip texture right on the zombie's hitbox.
3. make door 'startopen' so that it spawns in the ground under the zombie.
4. make trigger_hurt over zombie with enough damage to make it fall
(at a certain level of damage, the zombie is coded to fall down 100% of the time)
5. right after, killtarget trigger_hurt
6. trigger door to 'open' so it is now blocking the zombie from standing.
(there's code to check whether a zombie can stand or not and will not do so if blocked)
7. when ready, killtarget the door and the zombie will stand up again.

it's really complex, but it could be used if you had a one off thing somewhere and didn't want to code anything up. 

posted at the same time you did :S

necros looks like hes got his act together :O 

I'm pretty sure you could swap the door setup for a wall that blocks the zombie the whole time, which you then killtarget when you want the zombie to wake up. It'll still fall down from damage if it is blocked. 

If you place the func_wall so that it covers the origin of the zombie, then you can prevent splash damage from killing the zombie. Direct hits will still be fatal though, so be careful about letting the player kill the zombies before they get woken up, since that will leave an invisible wall which players might hit.

It might be possible to circumvent that problem by setting the touch function on the wall to knight_die3*. It depends on there being no touch event generated between wall and zombie, both if the zombie tries to stand up and anything sets force_retouch. I think the first case is actually safe, but not so sure about the second. Walking through a teleporter sets force_retouch, so a testmap could be made easily.


* Astute readers may have expected SUB_Remove here instead of knight_die3. The reason we use the latter is that you must not remove entities during a touch function. So instead we use part of a monster death sequence, which does nothing but change the frame(no effect on a skip textured wall) except to make the entity non-solid. 

ijed & meTch: Thanks. I'm going to end up doing some code in this project anyway, this may be a good start for it.

necros, Preach: That is absolutely dizzying. I considered a group of events for this but couldn't come up with a reliable sequence. :\
OK this gives me a lot of experimentation in both directions. Thanks again :D back to Radiant to try to make some magic happen. 

the mid'st of the nite, is it possible to make a trigger_push blow you [uh huhuh uuuuh huh huh]in a slant-y-diagonal-y direction? im in QuArK dong this, i tried to set so a first push would blow you [heh heheheh heh heheh] upward, and a second one above it to the side, but it didn't quite work

[huh huh hu he said blow]

//sorry it has nothing to do with zombies not standing up though :S 

use 'angles' instead of 'angle' and set as a vector. 

What's the project? 

a little themed sp adventure, something to pass the time. :D 

http://g.imagehost.org/0163/vsyncorwhat.jpg
I noticed in two engines that if I look at void and move my view, the geometry tears and spasms as you can see on that screenshot (for example in tyr-glquake).
In other engines the void stays clear of the rest and there is no such tearing. (for example Fitzquake (sdl 0.80) and DP.

First I thought it was VSync disabled but vid_vsync is 0 in Fitzquake. In DP it is also disabled. Also forcing it in the video driver did not change a thing.

What is this? 

is fitzquake 0.85 one of the problem engines? if so i'd like to see your bsp to see if i can figure it out. 

Fitzquake SDL 0.80 is fine so I assume any Fitzquake is fine. For me it is any map when I look at void (eg noclip outside the map) and move/look around.

I'll try it in Windows on the weekend. 

Spirit: some sort of gl_clear issue?

Preachcros: Nice one, keep em coming! :) 

gl_clear 1 -- clear the void with a solid color
gl_clear 0 -- hall-of-mirrors effect 

The tearing appears also with gl_clear 0. It's hard to explain. Try tyr-glquake and gl_clear 1, then noclip out into the void. If it happens to you too, that's where you see it best. 

Can someone give me the item bits for the SG please. All I need to complete the coag3_start is the weapon remove hack and then we can release, but while I've found the BackpackTouch hack info, I can't find a list of item bits and the example removes everything except axe...

I'm assuming 125 should add every weapon (value of 1 for axe, value of 2 for shotgun) except SG&Axe, but I'd like some kinda confirmation for someone who's mapped for Q1 within the last 7 years...