Skip to content

Change cap zone distance to account for the cap radius - #2061

Merged
DESTROYGIRL merged 1 commit into
NeotokyoRebuild:masterfrom
DESTROYGIRL:71_cap_radius_distance
Aug 11, 2026
Merged

Change cap zone distance to account for the cap radius#2061
DESTROYGIRL merged 1 commit into
NeotokyoRebuild:masterfrom
DESTROYGIRL:71_cap_radius_distance

Conversation

@DESTROYGIRL

Copy link
Copy Markdown
Contributor

Description

The distance from the cap zone now shows the distance from the cap radius rather than the origin. Currently in gameplay, players are not given any information about how large the radius is, which can lead to frustration from missed or unexpected caps. I think this would be a minimal but effective change that reduces cases like this.

This is a diversion from parity, so feel free to debate this change

Toolchain

  • Windows MSVC VS2022

@DESTROYGIRL DESTROYGIRL added this to the QoL milestone Aug 10, 2026
@DESTROYGIRL
DESTROYGIRL requested a review from a team August 10, 2026 17:10
@DESTROYGIRL DESTROYGIRL added UI/HUD Relates to the HUD, NeoUI, menus, etc Gameplay Stuff that isn't gamemode or weapon specific, such as spectating, audio, configs. labels Aug 10, 2026

@Agiel Agiel left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea.

@Agiel
Agiel requested a review from a team August 10, 2026 17:32
@DESTROYGIRL

Copy link
Copy Markdown
Contributor Author

I'm gonna let this sit for a day just in case

@DESTROYGIRL
DESTROYGIRL merged commit de22665 into NeotokyoRebuild:master Aug 11, 2026
7 checks passed
@DESTROYGIRL
DESTROYGIRL deleted the 71_cap_radius_distance branch August 11, 2026 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Gameplay Stuff that isn't gamemode or weapon specific, such as spectating, audio, configs. UI/HUD Relates to the HUD, NeoUI, menus, etc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants