Map Feedback - Conflux, v3022

Conflux, v3022

Bug report by Okom1

Date: 5 Jan, 2024

Feedback notes: Feedback made with only 4v4 CTF and Slayer in mind.

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

No issues found!

1. Spawning

No issues found!

2. Sandbox

Some sandbox spawners have non-standard Spawn Properties:

Weapon Pad 3 Spawn Properties set to "Custom" in all modes except Ranked. A Custom Spawn Time of "120.00" deviates majorly from the 343 Default of "240.00" for a "Melee" Class Power Weapon.

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 in Ranked-only sandbox spawners where the property is used to only adjust certain Spawn Logic or Ammo/Charge Multiplier values of the item while replicating the rest of the Spawn Properties that would occur with the value of "343 Default".
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".

All Weapon Racks are merged too deep in geometry.

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

3. Gamemodes

Some gamemode objects are too high in elevation:

Flag Spawn
Flag Spawn 1

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

Gamemode objects positioned at the correct height

4. Nav mesh

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 1
Bot Nav Marker 2
Bot Nav Marker 4
Bot Nav Marker 5
Bot Nav Marker 6
Bot Nav Marker 7
Bot Nav Marker 9
Bot Nav Marker 10
Bot Nav Marker 11

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

Some Nav helper objects 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 & Bot Jump Hint Two Way 8

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

Nav mesh data is generating on the floor of the canvas. This causes excess Nav mesh complexity which leads to longer load times for players.

If your map doesn't use the canvas floor for playspace, place one Accents > Glass > Glass Transparent 10% object at position: 0, 0, 504, scale: 2910, 2910, 7 (minimum X & Y, can be larger), rotation: 0, 0, 0. This will block all of the 9 invisible Backup Spawn Points at Z: 505 so they can't spread the Nav mesh. This will also block players spawning on those Backup Spawn Points.
- Alternatively if you can't have a large object on the canvas floor, you can place 9 Nav Cutters at positions:
  0, 0, 505
  0, -1450, 505
  0, 1450, 505
  -1450, 0, 505
  1450, 0, 505
  -1450, -1450, 505
  -1450, 1450, 505
  1450, -1450, 505
  1450, 1450, 505
  
  each with a size of: 12, 12, 12 to block the spread of Nav mesh from the Backup Spawn Points. This will not block players from spawning on them, although players should be excluded from spawning on them anyways.
- Read the TSG Forge Wiki article about this topic

Some Bot Nav Markers set to "Explore" Behavior do not have any Bot Nav Markers connected to them as Neighbors:

Bot Nav Top Mid

Connect Neighboring Bot Nav Markers to the listed objects so Bots traversing to the listed objects know where to traverse next.

All Nav Cutters on the map are redundant in the way that their effectiveness could be replaced by removing the Nav Cutters and hiding the objects that are being covered by the Nav Cutters for the duration of generating Nav Mesh.

Remove all current Nav Cutters and move objects that don't affect Bot Pathfinding into a folder that should be hidden for the duration of generating Nav Mesh. Hiding an object serves the same purpose as a Nav Cutter covering that object, but costs less budget as there is no Nav Cutter object.

All Bot Walk One Way objects are redundant on the map as they aren't generating their hint and also are not required in front of lifts/launchers for Bots to use the lift/launcher.

Remove the excess Bot Walk One Way objects to gain back object budget.

5. Lighting

No issues found!

6. Misc. setup

Constant wind audio can be heard throughout the map, even in deep interior spaces.

Remove the "Wind Storm" sound effect under Map Options > Ambient Sound > Secondary Sound

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.