Configuration modes

After generating the config by starting/joining a lobby, each moon will have an entry in config (under Moon Overrides). Most of these will be set to Auto, which means the shading of the map will be calculated based on the mesh when the moon loads.

If you change the mode to Manual, then re-generate your config again, you'll have many more options to customize that moon more precisely.

If you want to leave a moon completely unchanged (if it's causing issues or has an existing contour map you prefer), change the mode to Ignore.

Quick and easy moon changes

There are a few immediate options for tweaking contour maps for specific moons in Moon Overrides while they're still in Auto mode:

• Show Radar Objects: Generates meshes for large objects on the moon and display them on the radar screen (will usually make things like large obstacles, buildings, or foliage visible).

• More Translucent Radar Objects For moons with very dense sets of objects (often when a moon has a large interior section), the radar meshes will be more transparent and thus won't be as overly bright when many are layered on top of each other.

• Broader Height Range: This is the first thing to try toggling if the shading on a moon appears to get too bright too quickly. It will spread out the shading over a longer stretch of elevations.

• Opacity Multiplier: Increase or decrease this to multiply the overall opacity level of the map's shading (higher values make the shading lighter). Note that since this is multiplication, if the shading is already almost black, multiplying it won't do much since it's already so low.

• Line and Shading Colour: Change up the colour of your contour map by changing this colour hex code.

In Automatic Settings there are some global settings for how all moons (with mode set to Auto) will automatically generate their contour maps:

• Line Spacing: The vertical height that will separate each contour line (lower this to add more lines, increase it to make fewer lines).

• Line Thickness: How thick the contour lines should be (be aware that setting this higher will make errors in contour lines much more noticeable, and also will have less and less impact on thickness with larger values).

• Max Opacity: How light the very highest parts of a contour map should be (higher for lighter).

Other than Broader Height Range, the Opacity Multiplier and Max Opacity are the most useful for troubleshooting. Note that the Max Opacity will only stop the shading from getting any brighter, but if you multiply the shading enough, it might reach that maximum before the actual target height for the map. If you're setting the maximum opacity to something below 0.9, you might want to try setting the Opacity Multiplier to the same thing, which should keep the multiplier from getting too ahead of the maximum.

Full manual customization

If you switch to the Manual mode in Moon Overrides, you can change all the above mentioned values for that moon specifically, as well as:

• Minimum and Maximum Height: The heights where shading starts and ends (from black at the minimum to fully light at the maximum).

These are usually automatically computed, so if you want to try changing them yourself, you'll probably want a reference for where they're usually calculated at. Enable the Log Automatic Values setting in Automatic Settings and land on the moon you're interested in customizing. Check the logs for the maximum and minimum values it generates, and use those as a starting point.

Additional config

There are also a handful of general configs for what types of radar objects should show up and more fine-tuning, but they're mostly self-explanatory. So, just give the config a read over if you want to change something.

Existing contour maps

By default, Universal Radar will disable any existing contour maps when it introduces its own. Moons can be set to Ignore in config to leave all their assets untouched. If you want the default values changed, see that section down below.

Contour map compatibility

If you want to ensure your moon's terrain will be selected and used adequately, here's some tips:

• If possible, use TerraMesh to convert your terrain to a mesh if you haven't already (you can find more info in the Lethal Company Modding Discord), as this will significantly reduce load times when first landing on the moon with this mod (and is probably a good idea regardless to make terrain look nice).

• Make sure your intended terrain objects have "terrain" in their name (and are either a Unity terrain object or have a mesh collider), and if there's any terrain you don't want to be mapped, make sure either the object or one of its parents has "OutOfBounds" somewhere in its name (neither of these are case sensitive).

  • I automatically detect terrain based on a bunch of factors, so it can work without doing this, but you might as well guarantee it.

• Clean up your nav mesh so it isn't going excessively out of bounds. I use the nav mesh to refine down the height range for terrains, so if the nav mesh is going way too high up the height shading will be off, and if it goes too far out a lot of out of bounds terrains or objects might have meshes generated for them.

• Make sure your terrain is on the Room layer (which it already should be).

Radar object compatibility

If you're having issues with non-terrain objects not showing up on your moon, here are some things to note:

• I check for objects of a certain size (based on the size threshold in config) on the Room, Default, and Collider layers (plus Foliage and Terrain if a specific config is enabled), so make sure you're objects aren't really small and are on the right layers.

  • Specifically, it looks at the area of the bounding box of the object when seen from above.

• Meshes are found based on colliders, so your mesh renderers shouldn't be too far from your colliders in the hierarchy. Specifically, the mesh renderer should be either a parent, a grandparent, or on the same object as the collider (if this is too inconvenient, you can just give the colliders mesh renderers and they'll act as an outline for the missing mesh).

• Certain key words are used to include certain meshes regardless of their size: "catwalk" (anywhere in the object's path), "bridge" (anywhere in the object's path), or "floor" (specifically in the name of the mesh renderer), all not case-sensitive.

• Like with terrain, "outofbounds" in the path of an object will also exclude it from being used.

• I avoid certain components on objects, such as animators, network objects, and skinned mesh renderers, so note that mesh renderers associated with those won't be used.

  • If you really need a radar object to move with an animation, try making it a child object without an actual animator, that should work fine.

• For water, I just look for materials with names containing "water" and a shader name also containing "water". As far as I know this works for both vanilla and modded water blocks.

Changing default values

If contour maps or radar objects aren't generating nicely with default Auto settings, I have some LLL content tags in place to make some adjustments. Simply make a content tag and set the "Content Tag Name" to one of the following and add it to your extended level to change the default config values:

• UniversalRadarExtendHeight: Equivalent to the Broden Height Range config, will increase the maximum level for shading. This is a common fix for contour shading being too bright or transitioning too quickly.

• UniversalRadarHideObjects: Equivalent to (disabling) the Show Radar Objects config, use this if you want radar object meshes to not generate on your moon by default.

• UniversalRadarLowOpacityObjects: Equivalent to the More Translucent Radar Objects config, use this if you have lots of layered radar objects that make things look way too bright.

• UniversalRadarIgnore: Equivalent to setting the mode of a moon to Ignore. This will mean Universal Radar won't change this moon at all by default.

• UniversalRadarLineColor: Determines the colour of the contour lines (and radar objects if present) on your moon. Set this using the "Content Tag Color" field.

• UniversalRadarBaseColor: Determines the colour of the contour shading on your moon. Set this using the "Content Tag Color" field.

These all still keep the moon in Auto mode, though. So, if you really need more fine control, you can either ask me to change the default values for you or patch the return value of this method in my mod yourself.

Making radar sprites

Specifically for vanilla moons, I've made a bunch of custom radar sprites to populate the radar while still maintaining the original feel. If you want to try using these for your own moon, all the sprite assets/colours I used are publicly available here. Just ask me if you need any tips or want to know how I made certain sprites.