There is something like this in Quark.
The big difference with quark vs (afaik) all other editors is that there is a tree view of the entire map where you see individual entities and brushes as nodes in the tree, grouped by brush entities or user made group folders.

entities that are defined in a certain way (for example: trigger_relay, trigger_counter) do not appear in the map at all, only in the tree view. Since quark407 was the first editor I used, I was really confused about how script entities were like when I went over to radiant.
I actually still find them very cumbersome having all these boxes floating around with lines going everywhere. They are a very poor method of doing any kind of scripting.

There is a downside though: when you load a map like this in other editors, you end up with a giant pile of overlapping script entities all at '0 0 0'. :\ 

This looks really interesting! Is there any plans to support other closely related Quake1-engine games? Specifically: Hexen 2?
I REALLY need a better editor for the levels I am making... 

Quake 2 and 3 are on my todo list. You're the second person to ask for Hexen 2 support. I have no idea what would be necessary to support that game though. But I'll look into it once I start supporting other games. 

I think all it takes to make it support a wide variety of (id-engine) games are surface/brush flags and patches (curves). Everything else is a matter of having a proper fgd. Quest 2.4, for instance, supported HL, Hexen 2, Sin, and several Q1-3 mods out of the box with this additional fuctionality.

Having some visual representation of entity linking would be nice (target#/killtarget#->targetname#) of course, it would have to be toggleable to avoid a mess. necros, I usually place script entities close to their area of action for easier accessiblity. But, yes, things like relay and counters can be at 0 0 0, or even lack an origin field altogether. However, the editor must have an entity list then (TB needs one, too, if it doesn't have it already). 

There will be a Quark-like tree of everything the map contains in a future version.

Target link visualization is also on my todo list. 

Again can't run.
In log file many lines like:
5228 2013-03-05 14:28:30: Loading 'progs/player.mdl' (searching )
5228 2013-03-05 14:28:30: Unable to find MDL 'progs/player.mdl'

In the end:
WARNING: 30:1: implicit cast from int to float
5228 2013-03-05 14:28:31: Fragment shader(s) linked, vertex shader(s) linked.
5228 2013-03-05 14:28:31: Fragment shader(s) linked, vertex shader(s) linked.
WARNING: 30:1: implicit cast from int to float
5228 2013-03-05 14:28:31: Fragment shader(s) linked, vertex shader(s) linked.

And then there is the same window with an error that is repeated many times 

Sorry if I asked you before, but what's your OS, graphics card and driver? I'll create a report for it, maybe I can fix it. 

Windows 7 Pro
ATI Mobility Radeon HD 4650 Series
Driver:
Provider: ATI Technologies Inc.
date: 04.08.2009
Version: 8.635.0.0 

Win 7 x64 

I suggest you update it. I have seen crash bugs go away for several people after they updated their drivers. Just ask Scampie ;-)

http://support.amd.com/us/gpudownload/windows/legacy/Pages/legacy-radeonaiw-vista64.aspx 

Yes, now run. Thanks! 

Have fun with it! 

 

A paypal donate button on the main Trenchbroom page. 

Why is it called Trenchbroom anyway? 

Ah, I forgot about Quark. Only used it briefly since I started with WC. Tree view sounds about right.

Maybe to mitigate the downside new logic entities could be offset 16 units, even though they're not seen. 

This is just a hobby for me, and I'm happy if people like the editor (and use it to create maps). I doubt I'd get a lot of money from it, and I don't really need it, either. Not that I'm rich, but I have a job that's paid well enough to support me and my family. 

Nobody has asked because these crusty Quake senior citizens already know the answer.

Back in the day, one of the most popular and respected deathmatch map review sites was RAMSHACKLE. You can view an archive of the site here: http://bit7.org/quake/mirrors/ramshackle/

The author of the reviews, Jeff Yost, was quite fond of using the term 'Trench Broom' to describe the double-barreled shotgun. Of course, the phrase has its origins elsewhere, but Jeff placed in the collective Quake consciousness via his entertaining reviews. 

The name "TrenchBroom" is in reference to The Ramshackle, a Quake DM map review site by Jeff Yost. He kept referring to one of the Quake weapons (either the Shotgun or the GL) as "TrenchBroom".

I like the sound of the word, also it's rare enough that it's google friendly, and it references a Quake website that has been defunct for > 10 years now.

What's not to like? 

First of all, good work with the editor! I love the simplified 1-view only interface.
So, I decided to make something for Q1 again after 10+ years and one thing that confuses me are entity properties. I know I can add new keys, but shouldn't there be some predefined keys for let's say trigger_once? Is there any way to find which keys a specific entity has? 

Ok, I was lazy and didn't bother to read previous comments.
Only the last question remains: Is there any way to find which keys a specific entity has? Or should I check other editors for reference?

Thanks and keep on with the work :) 

Right now, this information is not displayed in TB. I plan to greatly improve entity editing support, but it will take a while. For now, you can open the Quake.fgd file and look at it. 

It also brings about a decent productivity boost.

Firstly, the answer to the question of whether or not to translate an object created by using the standard duplicate operation is quite obvious. You should always move it away from the original object. Don't get me wrong, I fully understand why people want it to remain in place for faster re-positioning, but I don't think this is the answer - the danger of leaving objects on top of each other is too high. Yes, if you're paying attention you're fine, but there's always a chance that you'll hit duplicate accidentally (or repeatedly), or that you'll get distracted for a while and forget you've cloned the object when you return. You are then left with unwanted brushes which you will not be aware of - as far as I can tell, brushes in TrenchBroom don't z-fight if they are placed on top of each other either (even if they have different textures applied). This makes it impossible to know there's a problem if you're not looking for it.

Mr Fribbles, I don't want to hear problems, I want to hear solutions!

OK, here's the answer (or a suggestion, at any rate): an additional set of commands (and corresponding shortcuts) to duplicate and offset the selected object(s) in one go. I would suggest the hotkey set listed below (opinion alert, I'd also remap some of the current ones!)

LEFTARROW: move object left
RIGHTARROW: move object right
UPARROW: move object forward
DOWNARROW: move object back

CTRL+LEFTARROW: rotate object left
CTRL+RIGHTARROW: rotate object right
CTRL+UPARROW: move object up
CTRL+DOWNARROW: move object down

CTRL+SHIFT+LEFTARROW: duplicate object and move the clone left
CTRL+SHIFT+RIGHTARROW: duplicate object and move the clone right
CTRL+SHIFT+UPARROW: duplicate object and move the clone up
CTRL+SHIFT+DOWNARROW: duplicate object and move the clone down

Naturally you'd offset the object by the current grid amount (if snap to grid is on). If grid snap was off, pick your poison (a sensible default distance, or perhaps something clever such as offsetting the object by its width in the chosen direction!) 

Maybe the entire concept is not so good. Maybe it would be better to always duplicate objects just by dragging them, e.g. Ctrl+Drag will create a clone and move that.

OTOH, I wanted to use Ctrl+Drag to select multiple objects in a future version. But that could still be achieved if the drag starts with an unselected object. If it starts with a selected object, the selected objects would be cloned. 

I could add keyboard shortcuts as well, of course.