RUST: Ways to Prevent Leaks Last edited 1 year ago2022-09-29 07:54:00 UTC


If your level doesn't compile because it has a leak, then you need to find the leak and delete. This tutorial helps define methods to find and eliminate leaks

Prevent leaks

The best way to fix a leak is to prevent it in the first place. Better map building is the solution. The ways to prevent leaks are:
  1. Don't make a big box around your level. Ever. Let me repeat that, because it bears repeating. Don't make a big box around your level. That is the wuss way out, and it has so many bad effects on your map (like high r_speeds) that it's probably one of the worst mapping habits ever.
  2. Don't carve. Unless you really know what you're doing, carving causes a lot more problems than it solves. Avoid carving and you'll avoid leaks. Some times WC will split up a carved block so crazy-like it will cause a leak.
  3. Don't work in grid size 1. To the common n00b, grid size 1 might look like the best size to work in because it allows the most freedom. Wrong! You will make so many mistakes in grid size 1 that you'll end up having more leaks than you know what to do with. I'm talking about things like connecting a floor and a wall. In grid size 1, you'll probably miss and there will be a crack between them. You should work in grid size 8 or 16 most of the time.

Finding leaks:

Well none of the above worked, or you didn't pay attention and now you have a leak. I tried to warn you! Here are some helpful ways to finding a rogue leak:
  1. The point file. In WC, you may load the point file of a leaky map. It will show a crazy red line in the 2d views, and this line can be traced to the source of the leak. If there is no red line when you load the point file, then you probably have a point entity outside the map.
  2. Look at the log. The compile log will tell you the name and coordinates of the closest point entity to the leak. Use this to narrow down your search.
  3. Big Block method. Surround part of your map with a big, solid block and compile. If the leak errors are gone, then the leak must be in that area of the map. If not, move the block to another area and compile again. This will really help you narrow down your search.
  4. Big Purple Sky method. Surround your map with a giant hollow block with the sky texture, and make your light_enviroment bright purple (or other noticeable color). Compile the map and run it. Walk around every nook and cranny of the map. If you see a space in the map where purple light shines through, then a leak is there. It also might help to temporarily get rid of all your other lights so the purple light is more noticeable.
  5. 3-D view method. In worldcraft, make the 3D view nice and big (I use independent window configs). Put it on solid. Fly around the outside of your map, looking for the spot were the colors change strangly or the perspective is screwed up. Now, this may sound like a bad method, but combined with experience, I can locate any leak in minutes and be on my way while you are still flying down a pointfile
  6. Advanced method. The pointfile can get quite large and I find the 2d-only pointfile in WC is useless. To get around this:
    1. Copy the broken bsp and pts files into Halflife and load your map.
    2. In worldcraft,In the console type POINTFILE to load it. If it complains about not enough particles then add -particles 65000 to your halflife launch for debugging. This is easily done in WC compiler settings.
    3. However, the pointfile can still be outrageously long and take some patience to trace.
    4. The pointfile stops when it encounters a pointbased entity (light, playerstart, monster, weapon, ammo, etc). For the compiler this is the very definiton of a leak, a point-based entity is encountered by the pointfile. It passes through brush based ones unnoticed.
    5. You can shorten your pointfile by increasing the number of point-based entities in the map. Player deathmatch starts or gman around. Place them in each major room, hallway. When the pointfile enters it will encounter an entity sooner and will stop closer to the actual problem.
    6. Having gmen around also gives you a perspective of what player will look like in a room.
This article was originally published on RUST.
The original URL of the article was
The archived page is available here.
TWHL only publishes archived articles from defunct websites, or with permission. For more information on TWHL's archiving efforts, please visit the TWHL Archiving Project page.


You must log in to post a comment. You can login or register a new account.