Guillotine, v1424

Bug report by Okom1

Date: 15 Aug, 2024

Feedback notes: -

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: 471, 160, 697
Position: 486, 71, 694
Position: 574, 70, 689
Position: 488, 55, 696
Position: 538, -29, 696
Position: 324, -57, 693
Position: 457, -53, 677
Around multiple of the "Trim Beam B" objects that act as trim on the sides of the buildings.

Prevent access to the listed hiding spots.

Movement hitches can be experienced around some positions:

Position: 352, -30, 638 Clutter pile
Position: 284, -21, 633 Clutter pile
Position: 307, 19, 633 Clutter pile
Position: 322, 37, 622 Clutter pile
Position: 472, 44, 630 Clutter pile
Position: 235, -32, 627 Clutter pile
Position: 419, 38, 656 Clutter pile
Position: 440, 60, 656 Clutter pile
Position: 460, 25, 638 Foliage section could use a blocker to smooth out ledge

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] 27 Intersecting geometry
Spawn Point [Respawn] 37 Too high off the ground
Spawn Point [Respawn] 55 Intersecting geometry
Spawn Point [Respawn] 57 Intersecting geometry
Spawn Point [Respawn] 58 Intersecting geometry

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

Only 45 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: 50-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] 37 Player falls off a ledge
Spawn Point [Respawn] 41 Player runs into a wall
Spawn Point [Respawn] 42 Player gets stuck on geometry
Spawn Point [Respawn] 43 Player runs into a wall
Spawn Point [Respawn] 44 Player runs into a wall
Spawn Point [Respawn] 60 Player runs into a wall
Spawn Point [Respawn] 61 Player runs into a wall
Spawn Point [Respawn] 62 Player runs into a wall
Spawn Point [Respawn] 64 Player gets stuck on geometry
Spawn Point [Respawn] 65 Player gets stuck on geometry

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 Spawn Properties:

Weapon Pad 8 Spawn Properties set to "Custom"

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 Rack Selective Channel set to something other than "None". Seed Sequence Key doesn't match the standard Key used for the spawner type.
Weapon Rack 3 Selective Channel set to something other than "None". Seed Sequence Key doesn't match the standard Key used for the spawner type.
Weapon Rack 7 Selective Channel set to something other than "None". Seed Sequence Key doesn't match the standard Key used for the spawner type.
Weapon Rack 8 Selective Channel set to something other than "None". Seed Sequence Key doesn't match the standard Key used for the spawner type.
Weapon Rack 9 Selective Channel set to something other than "None". Seed Sequence Key doesn't match the standard Key used for the spawner type.
Weapon Rack 11 Selective Channel set to something other than "None". Seed Sequence Key doesn't match the standard Key used for the spawner type.
Weapon Rack 12 Selective 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

Miscelaneous issues that don't fall into the usual categories:

Weapon Rack 4 & Weapon Rack 8 Overlap each other, and both spawners are present in all gamemodes.

Resolve the issues according to the issue explanations.

Some sandbox spawners are too high in elevation:

Weapon Rack
Weapon Rack 8
Weapon Rack 9

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:

Power Equipment Pad 3
Weapon Pad 8
Weapon Pad 10
Weapon Rack 11
Weapon Rack 12

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

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.

Image of a KOTH boundary floating off the ground

Image of a KOTH boundary level with the ground

Some Capture Zones have their top zone height too low where players jumping inside the zone at certain spots can accidentally exit them:

KOTH Capture Zone 2
KOTH Capture Zone 3

Increase the top zone height of the listed Capture Zones. Test jumping and jump-crouching inside the zone boundary afterwards in a custom game to confirm that the issue does not persist.

4. Nav Mesh

Some areas of the map have fragmented Nav Mesh data so bots either will take longer than usual or cannot traverse through them at all:

Position: 493, 96, 633
Position: 430, 3, 645
Position: 276, -41, 631
Position: 319, -1, 630
Position: 280, 39, 623

Adjust the Nav Mesh data in the listed positions to allow bots to traverse through them smoothly.

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 Bot Nav Markers around the map have their Behavior set to "Hide" which will make Bots that reach them crouch and refuse to move away from them if they are holding the Objective which could stall a game:

Bot Nav Marker
Bot Nav Marker 1
Bot Nav Marker 2
Bot Nav Marker 3
Bot Nav Marker 4
Bot Nav Marker 5
Bot Nav Marker 6

Remove the listed objects or change their Behavior to "Explore" and connect them to neighboring Bot Nav Markers.

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 7

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 Cutters are redundant as they do not serve any essential purpose for the Nav Mesh in their current state:

Nav Cutter 1
Nav Cutter 2
Nav Cutter 3
Nav Cutter 4
Nav Cutter 5
Nav Cutter 6
Nav Cutter 7
Nav Cutter 8
Nav Cutter 9
Nav Cutter 10
Nav Cutter 11
Nav Cutter 12
Nav Cutter 13
Nav Cutter 14
Nav Cutter 15
Nav Cutter 16

Remove the excess Nav Cutters to gain back object budget.

5. Lighting

No issues found!

6. Misc. setup

Some Map Intro Cameras have incorrect settings, resulting in unideal behavior:

Map Intro Camera 1 Duplicate Sequence Order
Map Intro Camera 4 Duplicate Sequence Order
Map Intro Camera 5 Duplicate Sequence Order
Map Intro Camera 6 Duplicate Sequence Order

Adjust the settings of the listed Map Intro Cameras to follow set standards.

Starting Camera = Sequence Order: Lower than the ending Camera, Camera Blend: "Start".
Ending Camera = Sequence Order: Higher than the starting Camera, Camera Blend: "End".

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.

Some screenshot have redundant information shown on them, presumably on accident:

(1) thumbnail FPS Counter and Network Statistics visible in the top right corner
(2) hero Network Statistics visible in the top right corner
(3) screenshot1 FPS Counter and Network Statistics visible in the top right corner
(4) screenshot2 Network Statistics visible in the top right corner
(5) screenshot3 Network Statistics visible in the top right corner

Replace the listed screenshots with updated ones that don't have redundant information showing.