Remnant, v1542

Bug report by Okom1

Date: 25 Sep, 2024

Feedback notes: -

Map link: Remnant

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: -262, -61, 1467 Full map break. Requires Grappleshot
Position: 367, -388, 1434 Full map break. Requires Grappleshot
Position: 200, 112, 1486 Full map break. Requires Grappleshot
Position: 329, -403, 1410 Requires Grappleshot
Position: 429, -504, 1410 Requires Grappleshot
Position: 265, 199, 1308 Requires Grappleshot

Prevent access to the listed hiding spots.

Dropped sandbox or gameplay items can become unreachable due to holes in the map geometry:

Position: 178, 77, 1356

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.

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

Position: 181, -276, 1372 Inside No Collision corner piece. Multiple similar 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: 167, -297, 1346 Stair object collision extends further than visually noticeable
Position: 215, -259, 1342 Stair object collision extends further than visually noticeable
Position: 159, -212, 1347 Stair object collision extends further than visually noticeable
Position: 134, -234, 1347 Stair object collision extends further than visually noticeable
Position: -68, -126, 1364 Occasional bumping in staircase
Position: 50, -9, 1364 Occasional bumping in staircase
Position: -77, -252, 1364 Transition from no blocker to blocker
Position: -53, -298, 1337 Some object on the ground

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] 38 Spawn doesn't flow well
Spawn Point [Respawn] 40 Spawn doesn't flow well
Spawn Point [Respawn] 42 Spawn doesn't flow well
Spawn Point [Respawn] 45 Spawn doesn't flow well

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] 3 Player runs into a wall
Spawn Point [Respawn] 7 Player runs into a wall
Spawn Point [Respawn] 8 Player runs into a wall
Spawn Point [Respawn] 9 Player runs into a wall
Spawn Point [Respawn] 10 Player runs into a wall
Spawn Point [Respawn] 12 Player runs into a wall
Spawn Point [Respawn] 13 Player runs into a wall
Spawn Point [Respawn] 16 Player runs into a wall
Spawn Point [Respawn] 15 Player runs into a wall
Spawn Point [Respawn] 19 Player runs into a wall
Spawn Point [Respawn] 23 Player runs into a wall
Spawn Point [Respawn] 25 Player runs into a wall
Spawn Point [Respawn] 26 Player runs into a wall
Spawn Point [Respawn] 39 Player runs into a wall
Spawn Point [Respawn] 41 Player runs into a wall
Spawn Point [Respawn] 50 Player runs into a wall
Spawn Point [Respawn] 53 Player falls off a ledge
Spawn Point [Respawn] 54 Player falls off a ledge

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 4 Class/Tier set to "Any"
Weapon Rack 5 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"

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 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 7 Spawn Properties set to "Custom"
Weapon Rack 8 Spawn Properties set to "Custom"
Weapon Rack 9 Spawn Properties set to "Custom"
Weapon Rack 10 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 are too high in elevation:

Weapon Rack 10

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
Grenade Dispenser 4
Equipment Dispenser
Equipment Dispenser 1

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 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
KOTH Capture Zone 2
KOTH Capture Zone 3
KOTH Capture Zone 5

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.

Some gamemode objects are too high in elevation:

Ball Stand 1
Power Seed Spawn 1
Power Seed Spawn 2
Power Seed Spawn 3
Power Seed Spawn 4
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:

Flag Delivery Plate 3
Flag Delivery Plate 4
Flag Spawn Sand 3
Flag Spawn Sand 4
Zone Capture Plate 1
Zone Capture Plate 2

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: 40, 26, 1365 Decal object negatively affects Nav Mesh data shape
Position: 169, -318, 1352
Position: 200, -310, 1360
Position: 233, -277, 1361
Position: 242, -245, 1353

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

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 3
Bot Nav Marker 4
Bot Nav Marker 5
Bot Nav Marker 6
Bot Nav Marker 7
Bot Nav Marker 8

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

Nav Mesh data is generating outside the play space. This causes excess Nav Mesh complexity which leads to longer load times for players.

Prevent Nav Mesh data from generating in unintended areas. Rebuild Nav Mesh.
- Hide the objects that Nav Mesh data is generating on for the duration of building the Nav Mesh
- Cover the areas with Nav Cutters
This is often caused by Invisible Backup Spawn Points

Some Bot Nav Markers are redundant as there are already enough of them for bots to naturally traverse the map:

56 Bot Nav Markers in total, when a working amount is usually around 20.

Remove the excess Bot Nav Markers to gain back object budget.

Place Bot Nav Markers in the highlight areas of the map, set their behavior to "Explore" and make neighboring connections between them.

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

There are some areas with missing Named Location Volumes:

Position: 220, 30, 1339
Position: -106, -301, 1337
Position: -102, -108, 1364
Position: -7, -109, 1372
Position: 32, 11, 1364
Position: 33, -69, 1372
Position: 193, -168, 1348
Position: 93, -270, 1384

Cover up the listed areas with Named Location Volumes.

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.