Hot Rod, v1588

Bug report by Okom1

Date: 13 Sep, 2024

Feedback notes: -

Map link: Hot Rod

Priority 1 = Must fix:
Exploits, gameplay stalling issues and non-standard functionality.

Priority 2 = Should fix:
Recommendations, major visual issues and balance issues.

Priority 3 = Suggestion:
Inconsistencies, minor visual issues and optimization tips.

Positional values are described in the order: X, Y, Z.

Object references are described like so: Object name.

0. Layout

Unintended hiding spots present on the map:

Position: 334, 623, 1032 Entry spot to hiding spot
Position: -18, 626, 1032 Entry spot to hiding spot
Position: 211, 538, 1147 Multiple similar around the same area
Position: 102, 538, 1148 Multiple similar around the same area
Position: 166, 570, 1179 Multiple similar around the same area
Position: 178, 531, 1038 Multiple similar around the same area
Position: 143, 918, 1097 Inside No Collision object
Position: 141, 858, 1065 Inside No Collision object
Position: 205, 886, 1166
Position: 257, 618, 1071
Position: 257, 618, 1030
Position: 57, 614, 1071
Position: 57, 614, 1030
Position: 157, 546, 1174
Position: 157, 548, 1034
Position: 102, 893, 1166

Prevent access to the listed hiding spots.

Dropped sandbox or gameplay items can become unreachable under No Collision map geometry:

Position: 184, 659, 1098 Multiple silmar around the same area

Prevent the ability for items to become unreachable due to the listed holes in the map geometry.

Confirm this by dropping a weapon or a gameplay object on the listed area after fixing. Grenades or shot projectiles do not pass through No Collision geometry.

Movement hitches can be experienced around some positions:

Position: 157, 673, 1145
Position: 234, 794, 1142

Smooth out movement in these areas by either removing collision from the objects that cause the movement hitches or by adding blockers or other collision objects around the area.

1. Spawning

Some Spawn Points are positioned unexpectedly:

Spawn Point [Respawn] 19 Jarring visuals after spawn
Spawn Point [Respawn] 20 Jarring visuals after spawn
Spawn Point [Respawn] 21 Jarring visuals after spawn
Spawn Point [Respawn] 22 Jarring visuals after spawn
Spawn Point [Respawn] 27 Spawn doesn't flow well
Spawn Point [Respawn] 29 Spawn doesn't flow well
Spawn Point [Respawn] 33 Spawn doesn't flow well
Spawn Point [Respawn] 36 Spawn doesn't flow well
Spawn Point [Respawn] 38 Intersecting geometry
Spawn Point [Respawn] 39 Intersecting geometry
Spawn Point [Respawn] 42 Vertical rotation causes weird aim vector position
Spawn Point [Respawn] 43 Vertical rotation causes weird aim vector position
Spawn Point [Respawn] 47 Jarring visuals after spawn
Spawn Point [Respawn] 51 Jarring visuals after spawn
Spawn Point [Respawn] 73 Intersecting geometry
Spawn Point [Respawn] 74 Intersecting geometry
Spawn Point [Respawn] 76 Spawn doesn't flow well
Spawn Point [Respawn] 77 Spawn doesn't flow well
Spawn Point [Respawn] 78 Spawn doesn't flow well
Spawn Point [Respawn] 79 Spawn doesn't flow well
Spawn Point [Respawn] 80 Spawn doesn't flow well
Spawn Point [Respawn] 81 Spawn doesn't flow well
Spawn Point [Respawn] 90 Jarring visuals after spawn
Spawn Point [Respawn] 91 Jarring visuals after spawn
Spawn Point [Respawn] 92 Intersecting geometry
Spawn Point [Respawn] 93 Intersecting geometry

Adjust the positioning of the listed Spawn Points so they are positioned correctly.

Spawn Points positioned on a dynamic blocker may cause players who initially spawn on them to bounce in the air due to the blocker's outward push force which disturbs the camera movement during the match intro sequence. Replace the dynamic blocker with a scalable blocker to mitigate the issue.

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] 9 Player runs into a wall
Spawn Point [Respawn] 12 Player runs into a wall
Spawn Point [Respawn] 28 Player falls off a ledge
Spawn Point [Respawn] 30 Player falls off a ledge
Spawn Point [Respawn] 48 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.

2. Sandbox

Some sandbox spawners have non-standard Item Selection Properties:

Weapon Rack Class/Tier set to "Any"
Weapon Rack 1 Class/Tier set to "Any"
Weapon Rack 2 Class/Tier set to "Any"
Weapon Rack 3 Class/Tier set to "Any"
Weapon Rack 4 Class/Tier set to "Any"
Weapon Rack 5 Class/Tier set to "Any"
Weapon Rack 6 Class/Tier set to "Any"
Weapon Rack 7 Class/Tier set to "Any"
Weapon Rack 8 Class/Tier set to "Any"
Weapon Rack 9 Class/Tier set to "Any"
Weapon Rack 10 Class/Tier set to "Any"
Weapon Rack 11 Class/Tier set to "Any"

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 have non-standard Spawn Properties:

Weapon Rack Spawn Properties set to "Custom"
Weapon Rack 1 Spawn Properties set to "Custom"
Weapon Rack 2 Spawn Properties set to "Custom"
Weapon Rack 3 Spawn Properties set to "Custom"
Weapon Pad 13 Spawn Properties set to "Custom" and Spawn Properties other than Spawn Time deviate from the 343 Default standard

Adjust the Spawn Properties to be inline with set standards.

The Spawn Properties should be "343 Default" as it is the standard used in built-in maps and it allows for the spawner logic to change depending on the gamemode.

A value of "Custom" is allowed if it is used only to be able to change the Spawn Time of a spawner holding a Power Weapon or Power Equipment while replicating the rest of the properties that the Spawn Properties "343 Default" would result in.

A value of "Custom" is allowed in Ranked-only sandbox spawners where the property is used to only adjust certain Spawn Logic, Ammo Multiplier/Charge Multiplier or Spawn Time values of the item while replicating the rest of the Spawn Properties that would occur with the value of "343 Default".

A value of "Custom" is allowed on Equipment Pods and Weapon Pods if they are setup as BTB Ordnance Pods.

A high Initial Spawn Delay on an item may confuse players as the item only shows up for the first time a while into the match. The highest suggested Initial Spawn Delay is "30.00".

Some sandbox spawners have non-standard Advanced Properties:

Weapon Pad 1Selective Channel set to something other than "None". Seed Sequence Key doesn't match the standard Key used for the spawner type

Adjust the Advanced Properties to be inline with set standards.

The Selective Channel should be set to "None" on sandbox spawners other than Weapon Pods and Equipment Pods.
The Seed Sequence Key should be set according to the sandbox spawner type:

Equipment Dispenser, Classic Equipment Spawn = EquipmentPadPlacementKey
? = GeneralPlacementKey
Grenade Dispenser, Classic Grenade Spawn = GrenadePadPlacementKey
Equipment Pod, Weapon Pod = OrdnancePodPlacementKey
Power Equipment Pad = PowerUpPadPlacementKet
Weapon Pad = PowerWeaponPadPlacementKey
? = VehicleDropPlacementKey
Vehicle Pad, Classic Vehicle Spawn = VehiclePadPlacementKey
Weapon Rack, Classic Weapon Spawn = WeaponRackPlacementKey
Weapon Trunk = WeaponTrunkPlacementKey

The Selective Channel on Ordnance Pods should be set according to the following standards:

Equipment Pod, Eagle, Default = Juliet
Equipment Pod, Eagle, Event = Foxtrot
Equipment Pod, Cobra, Default = India
Equipment Pod, Cobra, Event = Gamma
Equipment Pod, Middle = Hotel
Equipment Pod, Last Spartan Standing = Delta
Weapon Pod, Eagle, Default = Juliet
Weapon Pod, Cobra, Default = India
Weapon Pod, Middle, Default = Hotel

Some sandbox spawners are too high in elevation:

Weapon Rack
Weapon Rack 1
Weapon Rack 2
Weapon Rack 3
Weapon Rack 10
Weapon Rack 11

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
Weapon Rack 8

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 sticking out too much from geometry:

Weapon Rack 5
Weapon Rack 8
Weapon Rack 9

Fix the depth on the listed Weapon Racks so that they don't stick out of the wall and block movement nor look visually distracting.

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

3. Gamemodes

Some Capture Zones are missing Zone Capture Plate objects:

KOTH Capture Zone 6

Add a Zone Capture Plate inside the boundary of each listed Capture Zone. Add the correct Labels to the Zone Capture Plate.

Strongholds = "Strongholds Include", "Strongholds Plate"
King of the Hill = "KOTH Include", "King of the Hill Plate"
Land Grab = "Land Grab Include", "Land Grab AI Plate"

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

KOTH Capture Zone 6

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

Adjust the origin point of the KOTH Capture Zones 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.

Some gamemode objects are too high in elevation:

Power Seed Spawn 5

Fix the elevation on the listed objects so they are positioned correctly on the ground.

Gamemode objects positioned at the correct height

Some gamemode objects are too low in elevation:

Zone Capture Plate 1
Zone Capture Plate 2
Zone Capture Plate 4
Zone Capture Plate 23

Fix the elevation on the listed objects so they are positioned correctly on the ground.

Some gamemode objects are redundant as they do not serve any essential purpose for the gameplay in their current state:

Zone Capture Plate 7

Remove the excess gamemode objects to gain back object budget.

4. Nav Mesh

The Nav Mesh on the map doesn't reflect the current geometry of the map.

Rebuild Nav Mesh.

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 lifts or launchers do not have pathfinding support for Bots to use them:

Kinetic Launcher Banished
Kinetic Launcher Banished 1

Add a Bot Movement One Way Nav helper connecting the entry point of the lift/launcher to the intended landing spot. Rebuild Nav Mesh afterwards.

The Length-value of the Nav helper should be set to "1.00" and positioned width-wise in the middle of the lift/launcher path so that Bots will use it accurately from the middle.

A Bot Movement One Way Nav helper setup correctly for Bots to be able to use a launcher

A Bot Movement One Way Nav helper setup correctly for Bots to be able to use a lift

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

Nav Cutter

Remove the excess Nav Cutters to gain back object budget.

5. Lighting

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

Position: 140, 810, 1154 Light overlap
Position: 187, 810, 1154 Light overlap

Reduce light or shadow 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.

6. Misc. setup

There are some areas with missing Named Location Volumes:

No Named Locations present on the map

Cover up the listed areas with Named Location Volumes.