Map Feedback - Pride and Joy, v1670

Unintended hiding spots present on the map:

Position: -22, -30, 796
Position: 173, -40, 787
Position: 76, -33, 779
Position: 193, -61, 784

Prevent access to the listed hiding spots.

The Spawn Volumes used to block the opposite team's spawns are not covering enough area per side:

Spawn Volume [Respawn]
Spawn Volume [Respawn] 1

Each team's Spawn Volume should prevent the enemy team spawning past the middle divider of the map in 4v4 sized maps. In larger maps, the divider can be pulled back somewhat, leaving a zone where both teams can spawn in the middle.

Only 32 Respawn Points present on the map, which can easily lead to predictable spawns.

Add a sufficient amount of Respawn Points on the map to give more varying locations for respawns.
Recommended amount of Respawn Points per player count:

2v2: 40-70
4v4: 60-100
8v8: 80-110
12v12: 120-150

Some Spawn Points are positioned in a way where the player will not have enough time to react to something happening shortly after spawning on them:

Spawn Point [Respawn] 20 Player runs into a wall
Spawn Point [Respawn] 24 Player runs into a wall
Spawn Point [Respawn] 25 Player runs into a wall
Spawn Point [Respawn] 39 Player runs into a wall
Spawn Point [Respawn] 40 Player runs into a wall
Spawn Point [Respawn] 41 Player runs into a wall
Spawn Point [Respawn] 44 Player runs into a wall
Spawn Point [Respawn] 45 Player runs into a wall
Spawn Point [Respawn] 46 Player runs into a wall
Spawn Point [Respawn] 47 Player runs into a wall
Spawn Point [Respawn] 48 Player runs into a wall
Spawn Point [Respawn] 49 Player runs into a wall
Spawn Point [Respawn] 50 Player runs into a wall

Reposition the listed Spawn Points so that they don't lead to actions that a player spawning on them can't react to quickly enough.

Some sandbox spawners have non-standard Item Selection Properties:

Weapon Rack Class/Tier set to "Any". Static Selection set to "Enabled" in non-BTB modes. Symmetrical Channel set to "None" or is different from the other team's counterpart
Weapon Rack 1 Class/Tier set to "Any". Static Selection set to "Enabled" in non-BTB modes. Symmetrical Channel set to "None" or is different from the other team's counterpart
Weapon Rack 2 Class/Tier set to "Any". Static Selection set to "Enabled" in non-BTB modes. Symmetrical Channel set to "None" or is different from the other team's counterpart
Weapon Rack 3 Class/Tier set to "Any". Static Selection set to "Enabled" in non-BTB modes. Symmetrical Channel set to "None" or is different from the other team's counterpart
Weapon Rack 5 Class/Tier set to "Any". Static Selection set to "Enabled" in non-BTB modes
Weapon Rack 6 Class/Tier set to "Any". Static Selection set to "Enabled" in non-BTB modes

Symmetrical Channel set to "None" or is different from the other team's counterpart. Symmetrical Channel value is the same as another spawner of the same Class on the same side

Adjust the Item Selection properties to be inline with set standards.

The Class/Tier should be some other value than "Any" as it doesn't have a functional "343 Default" Spawn Property mapping. The standard is to use the same Class that the Weapon in the Static Item Selection belongs to. The Weapon in the Static Selection can be different from the Class it belongs to if it is intended for that weapon to spawn only in Ranked modes, which force the Static Selection to "Enabled". In a situation where the Static Selection is "Enabled", the Weapon class is determined by the static Weapon set in the spawner.
The Static Selection on Weapon Racks should be "Disabled" in all modes with the exception of BTB where "Enabled" is allowed. Grenade Dispensers, Equipment Dispensers, Vehicle Pads and Classic Vehicle Spawns should be set to "Enabled" in all modes. For spawners only included in Ranked modes, "Enabled" is allowed, but has no difference to "Disabled" as Ranked modes force all spawner Static Selections to "Enabled" via gamemode rule. Fiesta modes will force the Static Selection to "Disabled".
The Symmetrical Channel should be set to Alpha for each sandbox spawner that relies on a Class-based item pool and has a symmetrical counterpart for it. If the same Class of item shows up more than once per side, a different Symmetrical Channel should be used for each of them. For items with Static Selection "Enabled", the Symmetrical Channel should be set to "None" to provide more randomness in Fiesta modes.

Some sandbox spawners do not have a Ranked variant with Ranked-specific properties:

Equipment Dispenser 1 Thruster
Equipment Dispenser 2 Repulsor

Add a Ranked variant for each of the listed sandbox spawners. Remember to put the Label "Ranked Exclude" on the non-Ranked variants of the sandbox spawners that require a Ranked variant.

Rocket Launcher = Label: "Ranked Include", Spawn Properties: "Custom", Ammo Multiplier: "50%", Spawn Logic: Static (Time), Spawn Time: User Defined, default is "120.00", Max Deployed: "0.00"
Drop Wall, Shroud Screen, Threat Seeker = Label: "Ranked Include", Spawn Properties: "Custom", Charge Multiplier: "50%", Spawn Logic: Dynamic (Expired), Spawn Time: "60.00", Max Deployed: "0.00"
Grappleshot, Repair Field, Repulsor, Threat Sensor, Thruster = Label: "Ranked Include", Spawn Properties: "Custom", Charge Multiplier: "100%", Spawn Logic: Dynamic (Expired), Spawn Time: "60.00", Max Deployed: "0.00"

In situations where there are two equipment of the same type on the map that require a Ranked variant, slightly different Spawn Properties are required for them due to a bug:

Label: "Ranked Include", Spawn Properties: "Custom", Charge Multiplier: From the list above, Spawn Logic: Dynamic (Pickup), Spawn Time: "60.00", Max Deployed: "1.00"

Some sandbox spawners are too high in elevation:

Weapon Pad 1
Weapon Rack 5
Weapon Rack 6

Fix the elevation on the listed objects so they are either correctly on the ground or at a standard height on the wall.

Weapon Racks should be 5.15 units up from the ground level.

Sandbox spawners positioned at a correct height

Some sandbox spawners are too low in elevation:

Grenade Dispenser 2
Grenade Dispenser 3
Equipment Dispenser 1
Weapon Rack
Weapon Rack 1
Weapon Rack 2
Weapon Rack 3

Fix the elevation on the listed objects so they are either correctly on the ground or at a standard height on the wall.

Weapon Racks should be 5.15 units up from the ground level.

Some Weapon Racks are merged too deep in geometry:

Weapon Rack 5

Fix the depth on the listed Weapon Racks so that the back plate of the Weapon Rack doesn't get merged in geometry when a Weapon is taken from it.

Weapon Racks should be just far enough out of the wall so the metal back plate inside the object does not intersect the wall.

Close-up shot of a Weapon Rack merged too deep in the wall

Close-up shot of a Weapon Rack at a correct depth in the wall

Some Capture Zones are too high or low in elevation from ground level so the nav marker displaying the zone letter shows up in an unexpected position from the zone capture area, which can confuse players:

KOTH Capture Zone 6
KOTH Capture Zone 8
KOTH Capture Zone 10
KOTH Capture Zone 11
Stronghold Capture Zone
Stronghold Capture Zone 2

Adjust the origin points of the listed Capture Zones to be level with the most common surface inside the boundary that a player would capture the zone from.

Image of a KOTH boundary floating off the ground

Image of a KOTH boundary level with the ground

Some KOTH Capture Zones have portions of the hill boundary that allow the castle pattern on the bottom of the hill to show higher or lower than ideal. This could be either the hill being too high off or low in the ground or there being parts where the bottom part of the hill boundary is extended to meet the ground level, causing the pattern to extend downwards:

KOTH Capture Zone 6
KOTH Capture Zone 8
KOTH Capture Zone 10
KOTH Capture Zone 11

Adjust the origin point of the KOTH Capture Zone to be level with the lowest point that the boundary reaches so the pattern won't block line-of-sight as much or be hidden.

No Bot Nav Markers set up for exploration purposes so Bots will just run around in select locations of the map in a janky fashion if there are no ambitions like sandbox item spawns, gamemode objectives or enemy players nearby that interest them.

Add Bot Nav Markers on the map to make Bots traverse between them if nothing else interests them.

Place Bot Nav Markers in highlight areas of your map, set their Behavior to "Explore" and connect them together by adding other Bot Nav Markers as Neighbors to each Bot Nav Marker.
It's a good idea to name each Bot Nav Marker uniquely so it's easier to distinguish them when choosing Neighbors.

Some Nav helpers aren't generating their hints correctly because some of the four bottom corners of the Nav helper boundary aren't connecting to traversable geometry:

Bot Jump Hint Two Way 17
Bot Jump Hint Two Way 18
Bot Jump Hint Two Way 19

Make sure all four bottom corners of the Nav helper boundary are connecting to traversable geometry. The corners should not be too deep in or too high off the geometry. Rebuild Nav Mesh afterwards.

Image of a Nav helper that is not generating the hint

Some Nav helpers are generated in a way where bots will use them, but won't successfully complete the traversal action:

Bot Jump Hint Two Way 20

Reposition the Nav helpers in a way where bots traversing in the direction of the helper can successfully traverse through it.

With Jump Hints, bots will keep jumping for the entire duration of them using the Nav helper.

Some Nav helpers are redundant as they do not serve any essential purpose for the Nav Mesh in their current state, bots are ignoring the Nav helper or there is already a sufficient Nav hint generated without them:

Bot Jump Hint One Way
Bot Jump Hint One Way 1
Bot Jump Hint One Way 2
Bot Jump Hint One Way 3
Bot Jump Hint One Way 4
Bot Jump Hint One Way 5
Bot Jump Hint One Way 8
Bot Jump Hint One Way 9
Bot Jump Hint One Way 10
Bot Jump Hint One Way 11
Bot Jump Hint One Way 12
Bot Jump Hint One Way 13
Bot Jump Hint One Way 14
Bot Jump Hint One Way 15
Bot Jump Hint One Way 16
Bot Jump Hint One Way 17
Bot Jump Hint One Way 18
Bot Jump Hint One Way 19
Bot Jump Hint One Way 20
Bot Jump Hint One Way 21

Remove the excess Nav helpers to gain back object budget.

Some Nav Seed Points are redundant on the map as the Nav data already connects to all required areas without them or the Nav Seed Point is not affecting the pathfinding in a useful way in its current position:

All Nav Seed Point objects

Remove the excess Nav Seed Points to gain back object budget.

Spawn Points serve the same purpose as Nav Seed Points in that they spread the Nav Mesh from their origin position.
Read the TSG Forge Wiki article about this topic

Some Nav Cutters are redundant as they do not serve any essential purpose for the Nav Mesh in their current state:

All Nav Cutter objects

Remove the excess Nav Cutters to gain back object budget.

Excessive light overlap is present in some areas, but it doesn't cause noticeable performance issues:

Around the middle of the map

Reduce light overlap by adjusting the settings of the individual light objects that emit the light.

The most common property that leads to said overlap issues is having the Light Range value too high on the light objects.

Some essential gameplay setup objects are missing:

Winning Team Outro

Add the listed missing essential gameplay setup objects.

The player can Mark outside the playable area to reveal locations with no name.

A good idea is to add a Named Location Volume covering a large portion of the map with some generic name like "Outside" so when a player Marks outside of the playable area, it will still have some generic name instead of showing no name.

Smaller volumes will take priority if they are located inside a larger volume so this won't affect the Named Location Volumes inside your playspace.

Pride and Joy, v1670

0. Layout

1. Spawning

2. Sandbox

3. Gamemodes

4. Nav Mesh

5. Lighting

6. Misc. setup