Skip to content

Add convar for spectate order#1079

Draft
anf3is wants to merge 2 commits into
ReactiveDrop:reactivedrop_betafrom
anf3is:feat/spectate-prio
Draft

Add convar for spectate order#1079
anf3is wants to merge 2 commits into
ReactiveDrop:reactivedrop_betafrom
anf3is:feat/spectate-prio

Conversation

@anf3is
Copy link
Copy Markdown
Contributor

@anf3is anf3is commented Jun 7, 2026

This PR aims to support custom spectating order (for example: Jaeger → Wildcat → Vegas → [other/fallback]).
The configured order should be respected when cycling between marines while preserving the current behavior that all alive marines remain valid spectate targets.

WIP Info

  • SpectateNextMarine is server-side. Because of that we need to send client's spectate order to server.
  • newmapsettings.cfg is too early for rd_set_spectate_order 😭
  • rd_set_spectate_order operates on CASW_Player. Do we need to call rd_set_spectate_order after client is fully connected and CASW_Player for this client is created?

Tasks

  • Add client-side rd_spectate_order for storing client's preferences
  • Find a place to automatically call rd_set_spectate_order if rd_spectate_order is set
  • Mark rd_set_spectate_order as hidden

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant