:) 

Haha! :D Thanks for assistence! :D 

Is there any documentation on these two AD entities? I can't find them in the ad_v1_70P1_documentation.txt, and I can't get the func_insidevolume to detect the pushable and send an output to a func_door, even though I have the "pushable" flag checked. 

These were added/modified very close to release. Probably why no information.

Did you open the "test_pushable" map to see how to set it up? 

1)Create a brush then --> tie to entity > func_pushable, no other parameters needed.

2)Create second brush then --> tie to entity > func_door, then give the door a name Ex: "PushableOpens".

3)Create your last brush and --> tie to entity > func_insidevolume, give it a Target(fully inside) of: "PushableOpens". Uncheck all flags but Pushable.

Tada!

Now I don't remember the specific conversation with sock but there was concern for this: "Name of target(s) to trigger when something is FULLY INSIDE the volume (fires every 0.1s)."

Namely, the constant firing. I think that's why there's more complex setups for these. But you could select "Only ONCE" for "wait", for the func_insidevolume if that will work for you?

hth's 

Or if it does do constant firing, just target a trigger_relay set to once. Only have the trigger_relay target the actual door.

My guess is it has to do with needing the pushable fully inside rather than just touching like a trigger. 

Thanks! You hit the nail right on the head - I did not know the pushable had to be completely inside for it to work. Did a few more tests and it worked exactly as it should.
I'm a bit annoyed that pushables, that doesn't move, don't block gasshooters but this allows me to do a workaround for that. 

You could use Target2 also, which is when a pushable is "partially inside" the volume ;)

Also, I'm a bit confused on the pushables that "don't move" comment? Maybe you mean when you are not pushing them? 

I tested it. Yeah, pushables are not solid to the gasshooter at all.

Seems an isolated case, versus the other trap types I tested('nades, spikes etc). Prolly not that hard to "fix". 

Hi. Do someone know if there's a way to create longer messages than one line? and maybe change its colour? 

Yes, you can just move to another line by adding \n.
Just like this. “Hello, this is my message \n how do you like it?”
In game it will be seemed like this:
Hello, this is my message
how do you like it? 

Thank you very mutch! 

Color is possible in Darkplaces but you only use normal white or orange (bold) in all other engines like this:
\bImportant Message!\b\nNotice, thank you for noticing\n this notice.

For Darkplaces or QuakeLive engines:
The color codes are as follows:
^1 = Red
^2 = Green
^3 = Yellow
^4 = Blue
^5 = Light Blue
^6 = Magenta
^7 = White

E.g:

^4BLUE TEXTBOOK\n^7Normal white message. 

Does anyone know where to find some good sky textures? I looked through most of the wads on Quaddicted's wads section but only found a few skies, none of which matched what I was looking for. 

http://www.quaketastic.com/files/texture_wads/skies.wad 

Hi!

Have some good links here.
Best wishes.



https://www.reddit.com/r/gamedev/comments/3ys4vg/a_month_ago_i_released_a_free_space_skybox/

https://www.quake3world.com/forum/viewtopic.php?t=9242

https://gamebanana.com/textures/cats/62

http://www.custommapmakers.org/skyboxes.php

http://gfx.quakeworld.nu/browse/other/skyboxes/ 

Thanks OTP. And GunSgtHighway, although I should've clarified I was looking for old-school style sky textures rather than skyboxes. 

Hi!

I'm getting crazy on this.
Is there a way to turn for example lights on and of or turn it on with two buttons and turn it off again? Thought I can handle this with trigger_relays or an info_notnull but I have no coding practise. Is there a tutorial or a manual for coding, spawnflags,...? 

turn lights on and off -- give light(s) a targetname, give button that matching target, make sure the button has a wait that is not -1.

same lights with two buttons -- if you want either button to do it, just give both buttons the same target value.

same light with two buttons, where you have to press both -- both buttons have wait = -1, they both target a trigger_counter, which triggers the light. This setup is not repeatable.

two buttons that you have to press both and then the light turns off and then you press them both again and it turns on -- a complicated setup with logic gates probably. 

Not sure if this exactly what Sgt wanted, but here's a light that requires pressing two buttons (order doesn't matter) to be turned on or off. The buttons stay depressed until the other is pressed at which point the light toggles and they both reset. Demonstration here, bsp and map here. As metlslime suggested, it's done with some logic gates, a setup that could be cleaned up a lot by someone more skilled with gate optimization who doesn't rely on babby-mode spike shooters like I do, or just using a custom progs set, not to mention fixing up the timing on the button and trigger resets a bit. 

Thanks for answers.

What I want to do is to put a little more riddles in my maps.
Means I made three buttons. Two of them have to be pushed for activating something, the other on sets them and the activating thing back to zero and you can push them again.

I don't know if quake supports this logic things with IF and THEN. But hopefully there might be a way. @Spud I'm hoping to find time today or tommorow to check your map out. Big thanks anyway! 

Quake doesn't support that kind of logic internally (at least, not in terms of what one can normally use in the map, other than predefined setups i.e. "open door if player has key, else don't open door"), but you can use the various entities to make physical logic gates including if, then, all sorts of and, nand, and so on, and combine them all to do all sorts of tricksy logic stuff that you'd never expect to be possible. Some of them involve other types of map hacks (info_notnulls and InitTriggers and so on), but the most basic form just needs a spike shooter trap, a door, and a button- a simple if gate. From there everything spirals outwards, and you can even save a couple entities/edicts by using further hacks in the gate itself.

There's some great reading material to be found around, including the QuakeWiki entity pages and the QuakeC source, but here's a couple offhand:
New Logic Gate Design (2013) and part two of the same article,, along with Logic Gates for 2017, all hosted at the Tome of Preach, a most excellent site run by Preach that's absolutely chock-full of crazy map hacks. Those articles primarily focus on gates themselves; there's a number of other pages on the site that go into detail about specific hacks, some of which require gates, others that don't.

Not coincidentally, the last page above also links to a relatively ancient example of the aforementioned trap-shooter logic gate in Quake 2, penned by metlslime, whose post is a couple paragraphs up, and whose thread we're posting in, not to mention whose board we're posting on. Maximum respect to the old guard for figuring this stuff out years ago so us noobs don't have to.

The Teaching Old Progs.dat New Tricks thread is an enormous and fantastic source of information and hacks for the vanilla (id1) codebase, many of which aren't collected anywhere else and some of which are only discussed in the thread in throwing-science-at-the-wall form, but would be refined and used by mappers months or even years later. Ctrl+f is your friend, and sometimes stuff shows up in other threads like this one instead; if that thread doesn't have it, I find just Googling "topic or hack you're looking for here" site:celephais.net often works very well.

Lastly, dumptruck_ds (whose videos relating to Trenchbroom you've likely seen once or a dozen times) created and runs a Quake mapping help/discussion Discord channel along with a number of long-time or experienced mappers, if you're into the instant-response* type of help. You can't say how fucking awesome someone's newest screenshot or mod might be, though, because apparently we aren't all consenting adults there.

*instant response may be less than instant depending on time of day and interest level of whoever's online