From reading ericw's post it sounds like AD can simply spawn monsters on demand. If so, this may be a better option for what you want to do instead of teleporting them in from somewhere else. 

How are the cool kids capturing for youtube upload nowadays?

Fraps? 

Look the screenshot

What I need to change in the value "other.items2"? In general what I need to change with the unknown values in the compiler?

(If qc is so hard to me, who knows about who can help me to doing a HUGE progs.dat 

) 

I use Nvidia Shadowplay to capture game screens. I would probably use Bandicam, OBS, or the like if I used ATI.

Fraps always works but I find it to be so resource heavy. 

you have to define/declare other.items2

there is no hipdefs.qc on your progs.src screens

or just put this
// have to use a new items flag because we ran out of bits in the original
.float items2;

inside your defs.qc (to the very bottom of the file) 

Much as I love a good google search, my efforts are proving fruitless for what I am hunting for. Does anyone know of a place to download all quake textures in a raw portable format such as png, jpg, tga, etc. 

Just open wad, select all textures, then file -> export 

Easy sneezy 

oops, I removed that hipdefs.qc 

A small search for how to create ent files for quake ended here. 

I use Arcade Dimension mod, using quakespasm engine. I made gas trap and placed the enemy near to it, let assume it is fixing it or something. I use button to activate it, trap starts shooting its gas/poison/fire but enemy doesn't get hurt, how to deal in this situation? I also used button that can be fired by shooting it, enemy reacts to a noise and turns around and dies to that trap. 

I've found that MHColouredLight(light.exe) does NOT work under win98se ! @#gulp#@

error: light.exe requires newer Windows version

Other light.exe(with colour) ?

thank 

Really you are gonna post that?

And if your only computer is a Windows 98 computer ... don't you think you have more pressing problems than whether or not MHColorLight will run on it. 

What?

Fitzquake only problem? 

Sv_touchlinks: Next != L-Next

Well, I had to go back five revisions before I found a copy of the map where that odd message doesn't pop up.

It looks like it started when a specific door was added or the direction it opened was changed. What's really strange is that the message appears when I touch the trigger for a completely different door which has been in the map and working fine for years.

Another funny thing is that it doesn't happen every time. I can reload the map and go through the exact the same way and about half the time there's no message.

I'm pretty sure I've never run across this before. If it actually is just a Fitzquake bug, I wonder if I should just ignore it. 

I think it's an engine bug; there are some details here (sounds like you can trigger it in vanilla quake):
http://forums.insideqc.com/viewtopic.php?f=3&t=4920&p=45279&hilit=SV_TouchLinks#p45279 

If I recall, that error occurs whenever you have two touching doors with one checked to "Don't link" and the other not. 

After more checking it looks like it was changing the direction the new door moved that caused the sv_touchlinks message. I can live with that door moving up/down instead of sideways if necessary. It isn't really needed at all, it was only added to make an encounter a bit more interesting.

If I recall, that error occurs whenever you have two touching doors with one checked to "Don't link" and the other not.

I'll go back and look at this. The door that was added does indeed touch the pre-existing door which now causes the message when triggered. I normally check "door don't link" without thinking, but maybe I left one unchecked. The new door needs to move, but the older one just needs to go away. It could easily be a func_wall that gets killed. 

Btw this might be a Fitzquake 0.85 only bug, or at least you might get a different message in other engines. I would at least check quakespasm to compare 

Though a question: aside from the message do you get any broken behavior? 

Okay, I was wrong. Changed the older door to a func wall and gave it a new name and brand new trigger_once killtarget. Now neither of those doors have a connection to the trigger that's generating the sv_touchlinks message. And the message is still appearing. 

<BAKER> Obviously I have a "modern" pc too but I usually map on my Pentium2 at least for Quake.

So I really don't understand why mh-light.exe does not run on win98.. some ideas ?

Are there any colored-light.exe that could work ? 

It probably has a trivial dependency on the Windows API that wasn't available in Windows 98 or requires a .dll that isn't available/can't be available on Windows 98.

It is really hard to compile something to ensure it works on an old platform that isn't used by an appreciable number of people.

I don't know when mh-light was compiled, probably in 2010 or 2011, but even 10 years ago Windows 98 was pretty scarce.

It is almost impossible to compile an executable today that would work on Windows 98 unless someone used tools of that era (i.e. Visual Studio 6) and tested it specifically on Windows 98 and almost no developer is going to have a such an old machine.