I had same results as Spud. As he and others posted, explodbox did no damage to the trigger. 

https://www.dropbox.com/s/bn8jj6asslpvq7u/explodo.zip?dl=0 

Strange, I'm using what should by all means be the exact same setup and it doesn't work. I thought maybe it was related to entity order but my test has the explobox listed before the trigger_once, just like you do. 

You can compile the map I uploaded and it works? 

The only id Tech-based game I've ever mapped for is Prey. I like its way to manage movers from its scripting system, where triggers call a scripted function that specifies which movers will have to move, in which direction, how long the movement must take, how many degrees they must rotate...

With the recent news of 3DRealms releasing a Darkplaces-based FPS soon, I started using GTKRadiant to map for Darkplaces. While the process of building the architecture for a level is quite similar to Preditor (because Preditor was based on GTKRadiant), there is no func_mover to select. So how do I add moving brushes in Darkplaces levels? 

Yeah, compiled it using ericw's tools and it worked just fine, player_start health buffer and all. 

This will be specific to the Wrath gamecode, not the DP engine code. For now, just mackle up placeholder movers using the vanilla Quake progs, using func_door, func_train or whatever, and then when 3DR release a dev kit for their game you'll have to convert your placeholder movers over to whatever system they are using. 

Oh. Then, I imagine there's no guarantee it's even gonna be possible to use something similar to Prey's movers, because 3DRealms had made a big deal about making everything with QuakeC, for authenticity's sake.
Which leads me to ask another question: is it possible to use QuakeC to move around models (e.g. .md3 models) instead? 

my trigger_once - no problems.. I set the health to 2, put the trigger inside (and outside) the box... works fine. 

Ladies and Gentlemen, you've truly gone above and beyond to satisfy my question, and I appreciate it very much.

TL;DR - So far, so good!

I tried trigger_once outside of my explobox, mostly satisfied, but in 1% of my playtests, a monster would trigger it and the wall sequence would fail.

My .map currently has a shootbutton underneath the explobox and it has triggered as intended in 100% of playtests so far. Today, I realized the button is making the typical button sound, and I'd rather not have that.

I'll try the trigger_once INSIDE the explobox, thanks again for the stream of suggestions. If I can't get it to work, I'll fall back to the button and accept the additional sound effect.

I just noticed there was further discussion about my question, so I felt the need to chime in. I do intend to post my map eventually, but it's my first "complete" map. I don't want to spam your board with numerous iterations of this cornball, amateur, mess of polygons. 

#20058: closed wall that explodes, no matter how many monsters walk aside.
Just reset the path_corners somewhere behind the surface, or they will z-brush. 

Mostly empty map in which I test new textures. And it seems that some of them are causing problems, 'cause when I fill the level with standard texture, it compiles. One texture at a time it also compiles. But when there are many (no more than 10, actually), it doesn't. Is there a way to pin point the problem (without hours of combinations checking)? I would guess it's something to do with the name, but names are pretty standarad, like: snowed_rock and burned_wood.

line 6: Unrecognised string escape - \S
line 6: Unrecognised string escape - \s
line 6: Unrecognised string escape - \c
line 6: Unrecognised string escape - \Q
line 6: Unrecognised string escape - \I
line 6: Unrecognised string escape - \q
line 6: Unrecognised string escape - \И
line 6: Unrecognised string escape - \T
line 6: Unrecognised string escape - \G
line 6: Unrecognised string escape - \B
line 6: Unrecognised string escape - \S
line 6: Unrecognised string escape - \s
line 6: Unrecognised string escape - \c
line 6: Unrecognised string escape - \Q
line 6: Unrecognised string escape - \I
line 6: Unrecognised string escape - \s
line 6: Unrecognised string escape - \S
line 6: Unrecognised string escape - \s
line 6: Unrecognised string escape - \c
line 6: Unrecognised string escape - \Q
line 6: Unrecognised string escape - \I
line 6: Unrecognised string escape - \f

BTW, what would happen if I'd had textures with the same name? I'm asking, 'cause 2 my of wads have different textures named dry_wood.

---

Texture screen: https://drive.google.com/open?id=1mDFK8cLOlgiFY5CqVha5hmsoY_FGeh-i (they are mostly from Tomb Raider xD) 

eh, I just copied parts of the map into the new file and it works... >_> 

I have looked in here but....couldn't get a conclusion.

[19:36] Shambler: can you give me the top ten causes and top ten cures for massive greyscale in quakespasm in this day and age?

[19:36] Shambler: i get a fuck off big lump of it in one area of a map i am working on

[19:37] Shambler: the map is sealed and vises, the other areas are fine, this area is not looking towards an excessively detailed / open view

[19:37] Shambler: there's a lot of func_detail, backed up with worldspawn where it needs sealing

[19:39] Shambler: it occured during testing but not after tinkering with this area in particular (well i was tinkering with a gameplay element but not changing architecture there) 

[21:18] madfox : When I first entered this board in 1999 I was afraid Shambler was really developper of the monster in Quake.
[21:20] madfox : Later on I realized it was just a nickname.
[21:22] madfox: Maybe it's because I'm a foreigner who has to register to post.

Not sure who's Shambler anymore.., 

Shambler.map is like madfox.mdl. The two of you should team up... or maybe you've been one and the same all this time! 

 

Any screenshots? Also have you tried older versions of ericw's tool to see if there's a difference? 

Is there any reason why when I walk down a long hallway, suddenly the nearby geometry goes invisible and I can see through to the other side of the map? Compiled with and without vis, same result.

I've uploaded a clip:
https://gfycat.com/ThatInnocentCrayfish 

Your map goes out of bounds, so to speak. Nothing can go beyond the -4096 and +4096 coordinates on each axis. 

Shots from discord:

Before moving into greyflash area:
https://cdn.discordapp.com/attachments/292236297173467138/558959023597289495/spasm0005.png

After moving:
https://cdn.discordapp.com/attachments/292236297173467138/558959051493605377/spasm0006.png

Greyflash area from other side:
https://cdn.discordapp.com/attachments/292236297173467138/558959083273584640/spasm0004.png

I've tried compiling with a new dev build ericw linked me, same issue.

BUT...


[10:24] Shambler: now i just checked and when i delete my big prefab-filled box, it works fine
[10:24] Shambler: prefab box is sealed with func_group (for easy access obvz), not worldspawn
[10:25] Shambler: but that should still stop it being drawn?
[10:25] Shambler: n.b. in image 2, that pillar is func_group or worldspawn now, not func_detail - i changed it cus there is a corridor behind and i was worried about line of sight....makes no difference ofc

It seems to be, in the words of Kinn "the engine hitting the limit of the number of faces it is allowed to draw"??

Obvz I will remove prefab box before release, and I can trim down some designs....but I've got plenty more detail to add....if there is other stuff I can do with func_whatevers....that is useful. 

the engine hitting the limit of the number of faces it is allowed to draw

This was always an issue in WinQuake (had to stick beefed up r_maxedges and r_maxsurfs in the config file).

...but, I would have expected QuakeSpasm has this pretty damn high (as in: "you'll never need to worry about it" high) by default??

Do these faces flicker on and off if you move around, shums? 

Thank you #20088, there is clearly some fat I can trim from that level