"The monster and the trigger_teleport get the same "targetname" field."

I haven't named the monsters but I don't think it matters since 90% of these spawns work fine without targetnames.

"Did you get skills messed up"

No. The monsters are there - they just don't spawn.

All the spawns are in a separate room, each monster having his own telebox and so on.

Developer 1 doesn't show anything relevant.

Anywayz, this had me wonder:
"The trigger_teleports can be any size, it's enough if the monster touches them."

"You stick the monster you want to spawn halfway into a trigger_teleport."

What do you mean by "halfway" in this context? 

The monster and the trigger_teleport get the same "targetname" field.

This isn't required, but does have the benefit of making sure the monster wakes up as soon as he spawns in (instead of waiting until he sees the player) 

Halfway means, the monster and the trigger overlap. You shove the monster 16 or 32 units into the trigger.

Perhaps you should mail the map to somebody else, perhaps AguirRe, and ask if he can take a look at it? 

What are the maximum and minimum X, Y, Z coordinates for a standard Quake compatible map?

If I recall, I think maps have dimension limits of 4096 x 4096 x 4096 but this might be wrong.

Is the answer -2048, -2048, -2048 to 2048, 2048, 2048?

Part B:

What are max/mins in aguirRe's engine and DarkPlaces?

I have an idea for maze generator or possibly a dungeon maker for Quake that writes the .map randomly (for all practical purposes) and then compiles it and it should be rather easy to make [because I have the source for such a program and just need to make it output the brush coordinates]... I just need to know the limits.

Thanks to whoever knows the answer. 

One third of Darkplaces' maximum: http://urre.quakedev.com/stuff/spcscr_test1.pk3 

is +/-4096 in all directions, i.e. a box with 8192 unit sides. Most engines (including mine) are using those limits, while I think DP has (+/-)64k.

I'd rather not think about a maze that challenges any of those limits ... 

I'm laughing, like for real. ;)

That would be the most frustrating map ever. Even with 8192 it still may be the case. 

I already made three of those (8192) :P 

I'm debating making a 8192^3 level... using special tools of course. 

By special tools I mean writing some evolutionary search method to design levels. I really doubt it'd actually be 8192^3, but that could potentially happen if the algorithm is designed in the right way. I don't have the time to work on this any time soon, but the idea seems like it could have merit for game designers, in order to generate... well, whatever is desired. Practically speaking it would be incredibly difficult to "get right," but whatever.

I can think of some func'ers who would be interested in implementing this... 

 

"I seriously think I might make a map using a tool that doesn't exist and that I don't know how to write, but I imagine someone else on func will write it for me." 

One last question: is it possible to make an elevator (func_door) so that when it goes down (activated by a button), it stays down, and has to be once again activated (by another button) to go back up? I tried the "Stays open" value but that prevented it from going back up altogether. 

it will do what you want. :) 

Tyrlight 99c is crashing on a specific plane in my map, consistently, only in colored light mode. Is there any way I can trace that back to a brush, or whatever else might be causing it? I really don't have the patience to just start fucking with random brushes and 'jiggling the handle' until I maybe get a result. 

 

I asked previously (#6385) about how to take screenshots so that the weapon doesn't show and I received a reply in #6386. However, is there any way to fly/walk around the level in a spectator mode so that the monsters cannot see you? I'd like to snap a few shots with monsters posing in them but so that they're not trying to shoot me. 

i think if you type 'notarget' they won't see you. also set crosshair 0, r_drawviewmodel 0, viewsize 120, and fov 105 or something. afterwards you'll probably need to brighten the shots up a bit in photoshop (play with curves). 

shrinking the map down to smaller and smaller bits to isolate the cause of the error didn't help. tyrlite -lit crashes within the first few dozen faces no matter what map I compile with it, even maps with no lights.

trying other BSPers in advance doesn't help, so it's probably not a compatibility issue there. tyrlite 0.99c has in fact been confirmed to work when compiling a map with a .lit, right? 

bamb is getting the same crash in a different map on a different computer. apparently it's tyrann's fault! 

...as am I. Thank goodness I'm not as stupid as I thought. It crashes out at 12-20 faces for me. 

look up the Quake cheat codes(noclip/notarget), and set sv_altnoclip 1 (works in Fitz and aguirRe�s engine), then you can fly around using the mouse like in Q2. 

Well, the map is finally done and I no longer have to bug you with stupid questions! See the news section for details (well, in a moment at least).

Thank you all for help. 

Hey guys, I might not hang out here much anymore, but I still take bug reports. Someone email me a map which is killing my light util and I'll fix it. 

are we using it wrong?