Skip to content

Add support for custom locations and VECTOR command#572

Draft
dharmab wants to merge 8 commits intomainfrom
vectors
Draft

Add support for custom locations and VECTOR command#572
dharmab wants to merge 8 commits intomainfrom
vectors

Conversation

@dharmab
Copy link
Owner

@dharmab dharmab commented Apr 22, 2025

No description provided.

@dharmab dharmab force-pushed the vectors branch 5 times, most recently from 7346468 to 7b0adae Compare June 19, 2025 16:18
dharmab and others added 2 commits March 22, 2026 00:05
Adapt Bullseye usage to interface type: remove pointer-to-interface
patterns, fix dereference of interface values, and update test call
signatures for the new Parser.New parameters.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
dharmab and others added 6 commits March 22, 2026 00:51
- Refactor Vector/Bullseye/BRA/BRAA from interfaces to public structs
  following idiomatic Go "return structs, accept interfaces"
- Remove redundant conf.Location; use locations.Location directly
- Load locations from file and pass to parser and controller
- Validate reserved location names ("tanker", "bullseye") at startup
- Mark --locations-file as filename flag for shell completion
- Remove unnecessary loc import alias
- Add missing godocs on public symbols
- Fix double comment in vector.go
- Update LOCATIONS.md wording for non-server users

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add AirRefuelingMethod type with FlyingBoom and ProbeAndDrogue constants.
Tankers now indicate which method they provide, and receivers indicate
which method they require. This enables matching receivers to compatible
tankers.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
When a player requests "vector to tanker", the system looks up the
player's aircraft refueling method, finds the nearest compatible
friendly tanker, and responds with BRA (bearing, range, altitude),
track direction, and the tanker's in-game callsign.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Accept both JSON and YAML for the locations file by trying JSON
first and falling back to YAML. Update documentation with YAML
examples and add a custom locations section to the admin guide.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Update documentation examples to match actual composer code behavior:
- PICTURE: use controller callsign instead of player callsign
- SPIKED/STROBE: remove "single contact" (code omits count for single)
- STROBE: use "strobe range" instead of "spike range"
- SPIKED clean: use subtitle format with numeric bearing and period
- VECTOR: remove extra controller callsign, add comma before bearing
- VECTOR tanker: use "nearest tanker" BRA format with altitude/track
- DECLARE: add missing "group" label
- SNAPLOCK: use numeral "2 contacts" instead of "two contacts"
- README: add VECTOR to supported commands list

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@dharmab dharmab changed the title WIP: Custom locations and VECTOR command Add support for custom locations and VECTOR command Mar 23, 2026
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