Skip to content

Commit 26e3c2c

Browse files
Create 4a.md
1 parent b807595 commit 26e3c2c

1 file changed

Lines changed: 64 additions & 0 deletions

File tree

4a.md

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
# 4a. Introduction to Level Design for ZAMNHLMP
2+
*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.
3+
4+
## First things first.
5+
1. You should be familiar with GitHub Desktop & Branches. These are explained in the earlier training modules.
6+
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.
7+
3. You must use Jackhammer. Not Trenchbroom as it is awful for remote-working, and doesn't support RMF.
8+
4. **You must save your maps in RMF. NOT JMF. This is for backward compatibility and future-proofing.**
9+
5. Seriously. DON'T SAVE in JMF. RMF. Cheers pal.
10+
11+
## Where are ZAMNHLMP's RMFs kept?
12+
I'm glad you asked. The Git repository you're looking for is Aura-SE. In GitHub Desktop, clone the Aura-SE repository.
13+
14+
<img width="787" height="870" alt="image" src="https://github.com/user-attachments/assets/0029b89b-4569-4647-baea-b0bff619ff23" />
15+
16+
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.**
17+
18+
<img width="1319" height="689" alt="image" src="https://github.com/user-attachments/assets/5a54ba62-1dd5-4bfd-9405-7c2c502117b3" />
19+
20+
21+
## Where is the FGD?
22+
It's in the developer repository, which you should have cloned to Cross Product/zamnhlmp_dev. If you haven't, do it.
23+
24+
<img width="779" height="856" alt="image" src="https://github.com/user-attachments/assets/54c1085b-249f-437d-95fa-f0d993ce1ce3" />
25+
26+
>[!IMPORTANT]
27+
> Don't forget to add `_dev` to the end of the folder path as shown above. Thanks buddy
28+
29+
The FGD is in zamnhlmp_dev\fgd\aura.fgd. Add this to your config.
30+
31+
Oh, also, we don't make new maps for patches. **Set your branch to `dev`, please.**
32+
33+
<img width="1332" height="914" alt="image" src="https://github.com/user-attachments/assets/874e3ef0-d963-4802-85db-ca0548659c9f" />
34+
35+
36+
## Game config in JACK
37+
1. Add the Aura FGD and ZHLT FGD, which is in the JACK installdir.
38+
<img width="483" height="627" alt="image" src="https://github.com/user-attachments/assets/d8ab24fa-2697-4148-aa9b-b6e0629b4306" />
39+
2. <img width="483" height="627" alt="image" src="https://github.com/user-attachments/assets/441b1097-9489-483f-a1f8-000bc91cbead" />
40+
3. Basically every WAD in the zamnhlmp_dev dir except for cached.wad and tempdecal.wad.
41+
<img width="483" height="627" alt="image" src="https://github.com/user-attachments/assets/6d8b4101-d392-4eea-845e-aedd0cf7b4c1" />
42+
4. These should be the ones included with JACK.
43+
<img width="483" height="627" alt="image" src="https://github.com/user-attachments/assets/7582b6d9-dabb-4114-b2e1-ab5efc8963a2" />
44+
45+
## Saving your maps
46+
Save them **AS AN RMF** in **`Aura-SE\MapFiles`.**
47+
48+
>[!IMPORTANT]
49+
> 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!
50+
51+
Neat, that should be everything you need! Oh, wait. Committing.
52+
53+
## Syncing with the rest of us (hivemind)
54+
Yeah, you need to push your changes to your RMFs and BSP.
55+
56+
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".**
57+
58+
Then push your RMF. Switch to Aura-SE, same ol same ol, and push. Pull if you have to.
59+
60+
If you have any conflicts or something, and you don't know how to resolve it, yeah you should contact Sabian.
61+
62+
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.**
63+
64+

0 commit comments

Comments
 (0)