Skip to content

4a.md

Latest commit

 

History

History
67 lines (40 loc) · 4.01 KB

4a.md

File metadata and controls

67 lines (40 loc) · 4.01 KB

4a. Introduction to Level Design for ZAMNHLMP

Half-Life: Cross Product Multiplayer is arguably the second-most important item on Phoenix's portfolio - and today, you'll get to make maps for it.

First things first.

  1. You should be familiar with GitHub Desktop & Branches. These are explained in the earlier training modules.
  2. You should have the game's developer repository downloaded and set to the dev branch. Seriously. Do this. The developer repository is NOT the Steam version distributed publicly.
  3. You must use Jackhammer. Not Trenchbroom as it is awful for remote-working, and doesn't support RMF.
  4. You must save your maps in RMF. NOT JMF. This is for backward compatibility and future-proofing.
  5. Seriously. DON'T SAVE in JMF. RMF. Cheers pal.

Where are ZAMNHLMP's RMFs kept?

I'm glad you asked. The Git repository you're looking for is Aura-SE. In GitHub Desktop, clone the Aura-SE repository.

image

Then, switch it to the dev branch. Zeke won't be impressed if you don't. We don't make new maps for patches either, and very rarely to we update them in a patch.

image

Where is the FGD?

It's in the developer repository, which you should have cloned to Cross Product/zamnhlmp_dev. If you haven't, do it.

image

Important

Don't forget to add _dev to the end of the folder path as shown above. Thanks buddy

The FGD is in zamnhlmp_dev\fgd\aura.fgd. Add this to your config.

Oh, also, we don't make new maps for patches. Set your branch to dev, please.

image

Game config in JACK

  1. Add the Aura FGD and ZHLT FGD, which is in the JACK installdir.

    image
  2. image

  3. Basically every WAD in the zamnhlmp_dev dir except for cached.wad and tempdecal.wad.

    image

  4. These should be the ones included with JACK.

    image

Saving your maps

Save them AS AN RMF in Aura-SE\MapFiles.

Important

REMEMBER THE NAMING SCHEME. We start each word with a capital letter and we try to keep maps names to one word. For example - Mapname.rmf, not dm_mapname_v1_whatever_poopy.rmf or whatever. Keep it consistent, kids!

Neat, that should be everything you need! Oh, wait. Committing.

Syncing with the rest of us (hivemind)

Yeah, you need to push your changes to your RMFs and BSP.

In GitHub Desktop, switch to the zamnhlmp repository and write a commit message for your changes. Remember to uncheck your SCR files. Also remember that commit messages should be written in the future tense - "Update Crossfire" should be the msg, not "Updated Crossfire".

Then push your RMF. Switch to Aura-SE, same ol same ol, and push. Pull if you have to.

If you have any conflicts or something, and you don't know how to resolve it, yeah you should contact Sabian.

Lastly - only one person should be working on a map at a time. Why? Because they are binary files. If one person edits an RMF and so does another, and they both push one after another, changes will be lost. One person per map at a time. So, for example, if Rafael is working on Sewers, no one else can work on it until he gives the greenlight.