that was simpler than i thought it would be 

how to make a teleporter? I have a block with the *teleport and its classname is trigger_teleport, but I don't know how to make It link up with a teleport destination? 

Make an info_teleport_destination point entity, then set the destination's targetname field to match the teleporter's target. Unless the teleporter is going to be delayed-use (only activates at a certain point), don't give the teleporter itself a targetname; that tells the game that it shouldn't teleport anything until it's activated by another entity and that's a common mistake people can make when getting into mapping, due to the habit of naming everything so you remember what's what and how unlike teleporters, buttons will still function properly with an unused targetname key. 

thanks 

seriously, this work over the last few months. Valve220 mode has been quite fun to play with! 

i have no clue what happened there:

"seriously, cheers to sleep and eric for all this hard work over the last few months. Valve220 mode has been quite fun to play with! " 

there's a brush entity called trigger_changelevel and i'm guessing it's how you make the level change,if it is how you make it change, I want to know how to set it up to change to a different level 

and also how to make it so when the level ends and its doing intermission it has the camera type thing, where it shows off part of the level 

Correct, trigger_changelevel is basically your map's exit.

Create a brush, right-click --> Create Brush Entity --> Trigger --> changelevel. Then go to the "Entity" tab on the right, and give the key "map" a value which is the name of the map you want to load when the player exist your level. E.g. if you want the player to go to the start map, you'd give "map" the value "start". Note that the trigger_changelevel entity will be invisible in your map. So if you want the player to exit through e.g. a teleporter, you'd need to create a separate world brush textured with the teleport texture.

and also how to make it so when the level ends and its doing intermission it has the camera type thing, where it shows off part of the level

What you're looking for is info_intermission. Right-click where you want to add it --> Create Point Entity --> Info --> intermission. This is basically the camera that you point at whatever you want to show when the player finishes the level. See here for more info on how to configure it further.

Note that you don't have to have an info_intermission in your map; Quake will automatically show some part of your map at the intermission screen (I think it defaults to the position of info_player_start). But with info_intermission you can specify what it shows. 

thanks 

One of the best things you can do as a new mapper is to download the .map files of the original Quake. You can find them below. It's easy to see how "id did it."

https://www.quaddicted.com/files/tools/quake_map_source.zip 

https://github.com/kduske/TrenchBroom/releases/tag/v2.0.0-RC7

Just goes to show you should never call something "almost done" or "final". Have at it! 

TrenchBroom 2 final is out! Trailer: https://youtu.be/shcAvnYp9ow | Download: https://github.com/kduske/TrenchBroom/releases/tag/untagged-36806b2ebb6bc0e45023 

TrenchBroom 2 has been in the making for more than four years. I have dug out the first message here on func where I talked about it: http://celephais.net/board/view_thread.php?id=60908&start=1054

Back then, I did not expect it to take this long. The main reasons for the delays were the fact that I thought it would be a good idea to do a rewrite (not the best of ideas), that I let too many features creep into the release, and that I got very busy with real life issues. But with the help of many contributors, we managed to get over this hump, finally!

So I'd like to take the time to thank a few people in particular.

The initial versions of TrenchBroom were shaped by feedback and input by necros, so I'd like to thank him for helping me make TB's UI what it is today.

ericwa helped out with invaluable contributions, bug fixes, and code reviews. Without his efforts, TB would be nowhere near as stable as it is now!

dumptruck_ds has just started a video tutorial series for TrenchBroom, available here: https://www.youtube.com/watch?v=gONePWocbqA and I expect these videos to help drive more people to TrenchBroom and Quake mapping in general.

Then there were a couple of other contributors who submitted patches and bug fixes.

Furthermore, I'd like to thank the numerous users who supported TrenchBroom by filing issues on github, by tweeting about it, and thereby creating a community around TrenchBroom.

And finally, I'm sure there are people who I should also thank, but whom I have forgotten to name since it's late and I'm tired ;-). I hope you guys don't begrudge my forgetfulness.

With all that said, I'd also like to talk a bit about the future of TrenchBroom. Now that this release is out, it will be time to groom the backlog to clean up and select those issues which should be included in the next releases.

After some deliberation, I have decided to focus on expanding TB's user base in the immediate future. This means that I will not be working on new features right away, but rather I will add support for more games with Quake 3 being the first game to be added.

I believe that adding more users to TrenchBroom is essential to the future of the editor, as this will likely bring more contributors as well. TrenchBroom has become a large and complex project, and I'll need all the help I can get in the future.

Besides the addition of more games, I would also like to focus on one particular issue, which is the performance of selection. Selection is an operation that depends on the size of the map, so it becomes slower the bigger the map becomes, and that is of course not acceptable in the long run. Both ericwa and I have some ideas on how to tackle this, and we have already written some code to fix it. So I expect this to be part of one of the next point releases as well.

I will create new milestones for the next three point releases in the coming days, and then I will start adding issues to these milestones. I plan on adding only a few issues to each milestones in order to have frequent releases in the future. Hopefully, we won't have to wait years for the next release this time ;-).

That's it for now. Thanks again to everyone who got involved in this project over the years. It has been a lot of fun, and a very satisfying hobby for me. The greatest thing for me has been to see how many releases have been made with TrenchBroom, and how many new mappers have joined this community because of it. Let's hope that TB will keep driving people to pick up Quake mapping in the future! 

 

Thanks a lot, Kristian. It's hard to know exactly how many maps your hard work has helped to create, but you can at least count mine among them - I doubt I ever would have started mapping for Quake if TB hadn't come along and made what was once a daunting, hostile task into one that I found approachable and enjoyable!

I hope you have a chance to relax and take a well-deserved break for a while, you've earned it! 

 

https://youtu.be/Wr9FR1W1JFE

And dumptrucks video series is awesome news! 

Congrats on the release Kristian. Thank you for all of the time you've put into this excellent project. I've spend thousands of hours in this editor since it's first incarnation.

My biggest suggestion is to try to make compiling it less of a pain (but at least GNU/Linux packages exist now.) 

 

Excuse me Mr. Duske, but I have seen that you have taken interest in packaging Trenchbroom for other GNU/Linux distributions once the final build of 2.0 came out. I have created a package for Slackware Linux, and I would like to submit it to you if you would be interested in it. I'm not very well versed with the whole GitHub thing, but if you're willing to grab it, please let me know what I should do. Thanks. 

Here's a link to the TrenchBroom Discord.

There are a few people who can probably assist you with GitHub. 

Any support for star trek: elite force? 

I assisted with the linux packaging and while I can't speak for Sleep I think there are two thing to consider.

One, in order to distribute a package he will have to build it himself and cannot take a pre-built package from "somebody on the internet". No offense though.

The other thing is that there are already 5 distribution packages to manage for every release. Before adding another one it might be wise to look at a cross distribution build and repository service like the one from opensuse. (https://build.opensuse.org/) 

Request it on github