Changing Levels

Tutorials > Half-Life > Intermediate > Changing Levels

By kol (More from this user)
2nd November, 2003
Intermediate
,info_landmark,trigger_changelevel,level change,transition,
(3 votes)

File Info: ZIP, 42.52KB
Contents: map1.bsp, map1.rmf, map1.map, map2.bsp, map2.rmf, map2.map

Changing Levels

A quick and dirty guide to perfect level changes

Level changes are often over explained, and too complicated for their own good. There really is nothing to them and if you follow this tutorial step by step, you should have absolutely no trouble whatsoever.

1. A level change is, simply put, a transition or displacement from one map (.bsp file) to another. And the reason you're reading this is because you're lost or trying to get a level change to work properly.

2. Why do I need level changes? I can get by without them, and save my self a lot of hassle...

Ok... Half-Life maps have limits. These limits should NEVER be reached or pushed, You can read more about these at Slackillers web page, go to the Tommy14 link and look at the error tutorial: general MAX_MAP limits.

3. What does that have to do with level changes?

It means, that if your levels are getting too big you should consider splitting them into 2 or more separate levels. This can be really useful for reducing r_speeds when working with two or more complex areas, or just to help you keep track of where you are in your map. Huge detailed maps are really difficult to work with in Hammer, as you probably already know.

4. Tell me what I need to know...

There are 3 types of level changes:

Seamless: The simplest level change you can have - walk through a corridor, see some loading text, end up in another map, but your position in the corridor and the environment around you does not change. The place you end up in is a carbon copy of the place you have come from.

Displacement: Same as above only the environment changes - i.e. go through a corridor in a lab and end up in your office/classroom searching for the 'check for problems' button in your life...It is a bit like teleporting, but you are doing it across maps.

One-way: You can get there, but you can never return.

6. So, What exactly do I do for a simple seamless level change?

Before we start these things are very important:

NEVER test level changes by running your map through Hammer using F9 or running it through any other editor, always use the console to load your map or start your map from a shortcut. You can get more information on how to do this by reading SKEEVE'S How to run a hl.bsp file tutorial.

ALWAYS put names of maps and info_landmarks in lowercase!!! And do not use spaces or other characters except numbers and letters, _ underscores are ok.

Right.

The only entities you'll need - since you just want a simple level change - will be tigger_changelevel (one in each map) and an info_landmark (the same one in each map)

Start by making a suitable corridor:

A suitably suitable corridor

*VERY IMPORTANT STUFF*

The info_landmark:

The info_landmark sets up a constant point of reference in the origin and destination maps. It must appear in both maps otherwise the level change will not work correctly. The origin and destination info_landmark must both have the same Name (targetname)

So basically, it's the same info_landmark in both maps.

Landmark

The Origin map trigger_changelevel:

Set these properties you need to change:

New map name: map2
Landmark Name: landmark1 (or whatever you called your two identical landmarks - one in each map)

The Destination map trigger_changelevel:

Set these properties you need to change:

New map name: map1
Landmark Name: landmark1 (or whatever you called your two identical landmarks - one in each map)

Trigger

Now, compile the maps through hammer or any other front-end compiler but remember not to run the game!, fire up hl with the console, and test the transition. If you did this correctly you should seamlessly jump from one map to the next no matter how you enter the trigger_changelevel.

One Way Changes

You would think a one way level change would only require one trigger_changelevel?

Wrong.

You have to set the level change up exactly as you would for a normal change. The difference is that in the second map, reduce the size of the trigger_changelevel brush and move it somewhere that the player cannot get to it. That is what stops the player from going back. You can also check the Use Only Flag just to make sure those NoClipping players still can't get back.

Well done, now drink some water - it helps re-hydrate your brain.

Comments

bjox says: 23rd July 2008, 23:43 PM

great tutorial ;)

GameMasterPau10 says: 3rd August 2008, 09:59 AM

When I loaded the next level, I was outside of the map. Can anyone help me? :(

Skals says: 5th October 2008, 16:40 PM

couldnt be explained clearer.

Source_SDK says: 24th January 2009, 14:30 PM

it crashes when i get on the 2nd map

Captain Terror says: 10th June 2009, 19:56 PM

great tutorial thanks! i set up everything the way you said, but i get "stuck" when i arrive at map2, that is, i can't move, even with noclipping!

Dimbark says: 14th September 2009, 00:19 AM

Why don't I have trigger_changlevel?

You must be logged in to comment.