Map Feedback - Dynasty, v339

Dynasty, v339

Bug report by Okom1

Date: 19 Jan, 2024

Feedback notes: Feedback made with only 4v4 CTF, King of the Hill and Strongholds 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

Unintended hiding spots present on the map:

Position: -34, 1368, 818
Position: -35, 1213, 818
Position: 20, 1191, 823
Position: 19, 1390, 823

Prevent access to the listed hiding spots.

Movement hitches can be experienced around some positions:

176, 1246, 739
174, 1334, 739

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 in a way where the player will not have enough time to react to something happening shortly after spawning on them:

Spawn Point [Respawn] 168 Player runs into a wall
Spawn Point [Respawn] 169 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 Spawn Properties:

Weapon Pad 1 Spawn Properties set to "Custom" and Spawn Properties other than Spawn Time deviate from the 343 Default standard. An unusually high Initial Spawn Delay of "60.00" is present
Weapon Pad 2 Spawn Properties set to "Custom" and Spawn Properties other than Spawn Time deviate from the 343 Default standard
Weapon Pad 3 Spawn Properties set to "Custom" and Spawn Properties other than Spawn Time deviate from the 343 Default standard. An unusually high Initial Spawn Delay of "60.00" is present

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 Weapon Pads have a non-standard Weapon on the Static Item Selection:

Weapon Pad 1 BR75
Weapon Pad 3 BR75

Adjust the Weapon selection to be inline with set standards:

Only Tier 1 Legendary, Tier 2 and Tier 3 Weapons are allowed on Weapon Pads.
Tier 1 = BR75, VK78 Commando, Pulse Carbine, MA40 AR, M392 Bandit, Bandit Evo, Disruptor, Mangler, MK50 Sidekick, Plasma Pistol
Tier 2 = Shock Rifle, Stalker Rifle, Bulldog Shotgun, Heatwave, Hydra, Ravager, Sentinel Beam, Needler
Tier 3 = S7 Sniper, Skewer, M41 SPNKr, Cindershot, Energy Sword, Gravity Hammer

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

Equipment Dispenser 3 Repulsor
Equipment Dispenser 4 Repulsor
Equipment Dispenser 5 Shroud Screen
Weapon Pad 2 Rocket Launcher

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"

3. Gamemodes

Some gamemode objects are too high in elevation:

Zone Capture Plate 2

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:

Flag Spawn 1
Flag Delivery Plate 1
Zone Capture Plate 12

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

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: 8, 1167, 799

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

Some useful areas of the map are inaccessible by bots due to a missing Nav hint:

Position: -91, 1286, 779

Add Nav helpers to the listed areas so that bots can traverse to them.

5. Lighting

Excessive light or shadow overlap is present in some areas, which is affecting performance negatively:

Position: 18, 1191, 764
Position: 17, 1393, 764

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.

An unnecessary amount of Light Probes present on the map leading to unexpectedly long map load times for players:

Light Probe Count: 13656. Level Bound Probes are spaced unnecessarily close

Increase the spacing of the Light Probes to lower the total Light Probe count. This makes the ligthing data file size smaller which leads to faster map load times.

The Probe Spacing can be reduced on either the Light Probe Marker or under Map Options > Level Bound Probes.

Bad Light Probe data is being blended to some surfaces inside the playspace which cause artifacting that looks visually confusing:

Position: 119, 1316, 746
Position: 119, 1265, 746
Position: 134, 1291, 795
Position: 124, 1460, 767
Position: 135, 1290, 767

Adjust Light data generation setup or Light Probe Spacing and rebuild Lighting.

This issue is often caused by a Light Probe behind a surface that is majorly different in color compared to the Light Probes in front of the surface.
Temporarily hide the objects that cause the bad Light Probes to get colored unideally due to the objects blocking light from getting to it. Rebuild lighting, unhide the objects and check for the bad artifacting.

A section of a map with bad Light Probe artifacting visible, no objects hidden

A section of a map with bad Light Probe artifacting visible, obstructive objects hidden

A section of a map with no Light Probe artifacting, obstructive objects hidden

Adjusting the Light Probe Spacing so the bad Light Probe causing the issue isn't the nearest one being used can also help alleviate the artifacting.

6. Misc. setup

There are some areas with missing Named Location Volumes:

Position: -54, 1323, 821
Position: -54, 1258, 821

Cover up the listed areas with Named Location Volumes.

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

Map Intro Camera 7 Camera Blend set to "Start" instead of "End"

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".