Skip to content

Move main to v1.1.10.0 - #381

Merged
netniV merged 76 commits into
mainfrom
codex/release-1.1.10.0
Nov 15, 2026
Merged

netniV merged 76 commits into
mainfrom
codex/release-1.1.10.0

Conversation

@netniV

@netniV netniV commented Nov 15, 2026

Copy link
Copy Markdown
Collaborator
  • feat: arrow navigation to switch docks

  • feat: enter to assign ship

  • refactor: match ship names via the game's localized display names

Resolves the exact name the game UI shows by looking up the ship's
locale id (ILocaId) with identifier ship_name_ through the game's
Localizer, replacing HullSpec.Name/IdStr matching plus every manual
alias. Config entries are matched against that display name so pinned
ships and instant-warp filters accept the names used in game (and
listed on stfc.space).* feat: arrow navigation to switch docks

  • feat: enter to assign ship

  • refactor: match ship names via the game's localized display names

Resolves the exact name the game UI shows by looking up the ship's
locale id (ILocaId) with identifier ship_name_ through the game's
Localizer, replacing HullSpec.Name/IdStr matching plus every manual
alias. Config entries are matched against that display name so pinned
ships and instant-warp filters accept the names used in game (and
listed on stfc.space).

GingerNinja-STFC and others added 30 commits September 19, 2026 20:19
* feat: arrow navigation to switch docks

* feat: enter to assign ship

* refactor: match ship names via the game's localized display names

Resolves the exact name the game UI shows by looking up the ship's
locale id (ILocaId) with identifier ship_name_<id> through the game's
Localizer, replacing HullSpec.Name/IdStr matching plus every manual
alias. Config entries are matched against that display name so pinned
ships and instant-warp filters accept the names used in game (and
listed on stfc.space).
* Update proto files; add planetary base support

* Add Haven support to sync configuration

* Add support for planetary base and map data synchronization

* Use existing string conversion to silence warning

* Enable core sync categories by default
* Preserve Unicode ship names and 64-bit locale IDs

* Match mod compiler extensions in the macOS ship-name fixture

* Keep ship locale fix focused on the managed 64-bit return type
* Show cargo totals immediately using native text snap

* Correct documented cargo hook instruction window size

* Remove exact-client pin from instant cargo hook
…ist (#310)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Preview automatic warp choice on system course button

* Add shared IL2CPP runtime boundary helpers with contract tests

* Narrow shared invocation helpers around existing loading screens

* Guard existing IL2CPP class lookup when metadata is unavailable
* Arbitrate WASD movement through configurable hotkeys

* Preserve held-arrow ownership without blocking movement bindings
…n to the HUD (#299)

* Add opt-in Galactic Anomaly countdown below system name

* Move anomaly countdown below the upper-right action buttons

* Frame the anomaly countdown and cache its manager

* Keep anomaly timer invocation guards local to the feature

* Reuse existing helpers in anomaly timer
…315)

Client build 267 (2026-09-29) delivers battle result headers as entity
group 219 (BattleResultHeadersResponse) and owned ships as group 251
(PlayerShipsResponse) instead of the Json group.

Implement the 219 processor and add a 251 processor, sharing helpers with
the Json handlers. Add the client's EntityGroup values 242-252, and declare
only the proto fields that are read.

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
* feat(sync): add away_assignments sync option

Add SyncConfig::Type::AwayAssignments as the first enumerator (mirrors
Jobs/Missions/Traits naming), a corresponding away_assignments member
(default false, matching every other sync data flag), and its
SyncOptions row so TOML loading, per-target overrides, runtime.vars
write-back and JSON type serialization all pick it up automatically.
config.cc needs no changes since everything iterates SyncOptions.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* feat(sync): forward away team assignments

Add processors::away_assignments_list (EntityGroup 111,
AwayAssignmentUserListResponse) and processors::away_assignment_instance
(EntityGroup 113, bare AwayAssignmentInstance), following the same
two-processors-plus-shared-helper split used for entity_slots /
entity_slots_data + single_slot_locked, since no entity group carries a
single-instance wrapper here.

away_assignment_event() builds the sync event for one instance and only
emits it when a hash of its observable fields changes, tracked in the
new trackers::away_assignment_states map (mirrors slot_states). The
list processor also prunes ids that drop out of the response and emits
a collected_away_assignment event for each, mirroring how jobs() prunes
completed jobs.

Wire both entity groups into HandleEntityGroup's dispatcher as the
first (alphabetical) block, gated by the new away_assignments option.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* feat(sync): include away assignment jobs and officer away status

jobs(): add JOBTYPE_AWAYASSIGNMENT so away-team jobs flow through the
existing job/completed_job events with an "aid" pointing at the
instance, in the same style as the other job-type cases.

officers(): surface Officer.awayAssignmentInstanceId as
"away_assignment_id" on the officer event. The officer de-dup state is
a struct local to officers() (kept separate from the shared
RankLevelShardsState used by forbidden_tech) so this extra field
doesn't change forbidden tech's comparison at all, while still causing
an officer to re-emit if only their away assignment changes.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* docs(config): add away_assignments to example settings

Add the away_assignments key as the first entry of the [sync]
"Subgroup: Data" block in all 10 localized example config files,
matching the existing comment/blank-line rhythm of the other data
keys. da/de/es/fr/nl/ru translations follow each file's own missions
line pattern and are best-effort; tlh follows the file's established
"Do you want Daq  sync X De'?" template. The unsuffixed pointer file
and [sync.targets.*] example blocks are intentionally left untouched,
matching how every other sync data key (e.g. traits) is handled there.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* fix(sync): stable officer order, drop unverified instance group

officerIds is a protobuf map, whose iteration order does not match
slot order (observed e.g. 2=.., 0=.., 1=..). Sort by slot index before
emitting officer_ids so the array, and the de-dup hash built from it,
are stable run to run.

Remove the AwayAssignmentsInstance (group 113) processor and dispatch
case: it was never observed on the wire during probing (not at login,
not on opening the screen, not on collect), so its payload shape is
unverified and we should not ship unverified parsing. AwayAssignmentsList
(group 111) is the only observed source of away assignment sync data
and remains the single caller of away_assignment_event(), whose
comment now states plainly that the caller must hold
trackers::away_assignment_states_mtx.

Also runs clang-format over the touched line ranges in config.h and
sync.cc to keep the branch's own added/changed lines clean.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* fix(sync): emit away assignments on start, drop officer change

Address sync maintainer review feedback on PR #295:

- Revert processors::officers() to be byte-identical to dev. Away
  assignment status stays off officer events; slot order isn't
  available in that hook, so instead of losing it we emit assignment
  starts through a dedicated event (see below).
- Drop a redundant static_cast in away_assignment_event(): std::hash
  already returns size_t, matching away_assignment_states's value type.
- Restore processors::away_assignment_instance for EntityGroup 113
  (AwayAssignmentsInstance), parsed as a bare AwayAssignmentInstance and
  routed through the existing away_assignment_event()/
  away_assignment_states_mtx so list and instance updates share one
  de-dup state and the slot-ordered officer_ids. Live capture against
  the Windows client confirms group 113 fires when an assignment is
  started: first at state=1 (READYTOSTART) with officerIds already
  populated and an empty jobUuid, then ~1.5s later at state=2
  (INPROGRESS) with jobUuid set. Wired into HandleEntityGroup's
  dispatcher right after the existing AwayAssignmentsList case, gated
  by the same away_assignments option.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* Restore battle log and ship sync for the current client (build 267)

Client build 267 (2026-09-29) delivers battle result headers as entity
group 219 (BattleResultHeadersResponse) and owned ships as group 251
(PlayerShipsResponse) instead of the Json group.

Implement the 219 processor and add a 251 processor, sharing helpers with
the Json handlers. Add the client's EntityGroup values 242-252, and declare
only the proto fields that are read.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Adds officer_traits, critical_trait_scores, success_chance, critical_success_chance,
max_critical_success_chance, key_stat, max_assignable_officers and the attack/defense/health
weights, all from the AwayAssignmentInstance the event already parses. On a fresh offer
critical_trait_scores is [] and the chances are 0 until officers are assigned. The chance fields
are in the de-dup hash, so an assignment re-emits when they change.

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
* Add option to hide artifact Exchange All button

* Resolve artifact visibility through current Unity wrappers
netniV and others added 26 commits October 17, 2026 15:10
When several same-hull ships tied on level matched one pinned_ships entry,
the winner was whichever ship the active sort listed first. Query
ForbiddenTechManager (the same path the ship tech indicators use) for the
ship's forbidden/chaos tech slots and let the ship with tech applied win the
tie. The check is memoized per sort and only runs on actual level ties;
bindings are lazily resolved and validated once, degrading to the previous
behaviour with a single warning if unavailable.

Adds HullId and Ship accessors to the prime FleetPlayerData header.
Add a ui.auto_confirm_alliance_contribution TOML setting (default false)
that skips the level-60 warning popup shown before contributing to a
max-level alliance.

The warning's MessageBox callback
(AllianceContributionViewController.<>c__DisplayClass72_0.<RequestAction>b__0)
only proceeds on MessageBox.ButtonResult.Yes (= 3, verified against the
client disassembly), so the existing shared MessageBox.Show detours now
invoke it with Yes instead of showing the popup. The detours are
consolidated behind the existing install gate, which now triggers on
either the Forbidden Tech or the new setting.

Cherry-picked from stfc-mod-personal (3f202ff). Adapted to this tree's
design: the MessageBox hooks stay installed unconditionally via the
[patches] installForbiddenTechConfirmationHooks toggle with the feature
setting checked inside the hook, and the patch entry label is renamed to
MessageBoxConfirmations since the detours now own two auto-confirm
behaviors.
* perf: scope galactic anomaly owner discovery

* fix: include Hub diagnostic prerequisite

* fix: reject destroyed anomaly singleton owners
Add an opt-in sync type, store_offers, that emits store_offer events.
Offers come from Platform service responses seen by the existing response
detour, and are routed only when the option is on. One snapshot is built
for the factions category and re-sent when its content changes.
Resource.amount is corrected to fixed32 in the Platform content proto.

Refs #301

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
* Hook the shared player-title implementation instead of bind thunks

* Make this really work on MacOS

---------

Co-authored-by: netniV <netniv@hotmail.com>
New opt-in sync type `profile`: one `profile` event with level, xp,
military_might and planetary_base_unlocked, plus the player's own uid. Source
is the UserProfiles entity group the client already receives; other players'
records are never read or forwarded. Sent at first sight and when level, Power
or the Haven flag change. The server record's level is 0, so level is read from
the in-memory local profile and can lag one response after a level-up.

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
…m) (#349)

The interior zoom-out hook keyed its native-radius capture and restore by the
OrbitFrameProvider instance. That provider is recreated across scene/section
transitions, but the Constraint.FloatData radius object it drives persists and is
shared with the exterior station camera. When a widened provider was torn down
before it next ticked outside the interior, the widened radius was inherited by a
freshly created exterior provider the hook had never captured, so the restore
branch (find(provider) miss) never fired and the exterior stayed pinned at
scale*native: zoomed out and un-zoomable.

Key the capture and restore by the radius object instead of the provider, so any
provider that later presents that radius restores it to native on its first
exterior frame (and a stuck state self-heals). The map key stays compare-only and
the stored value is plain floats, so no stale-object access is introduced.

Follow-up to #332.
* Use the canonical STFC-Mod/mod upstream location

* Preserve the documented clone directory
* Resolve anomaly HUD owners through their registered canvases

* Retain inactive owner recovery and cache whole displayed seconds

* Invoke the non-generic anomaly owner component overload
* Sync: add opt-in live fleet state ("fleet" records, config key "fleets")

Subscribe to fleet_watch from the sync patches when any target enables
`fleets`, and queue one record per FleetState transition:

  {"type":"fleet","fid":<fleet id>,"slot":<0-9>,"hull_id":<hull or 0>,
   "level":<ship level>,"state":<FleetState>,"state_name":"Mining",
   "prev_state":<FleetState>,"t":<unix seconds>}

A full snapshot of all occupied slots is queued as a first sync
(X-PRIME-SYNC: 2) whenever fleet_watch establishes a baseline (login,
fleet topology change) and whenever another category's first sync is
queued. Callbacks run on the game thread and only build JSON and queue
it; HTTP stays on the existing sync worker.

fleet_watch gains an optional Subscription::on_baseline callback.
Default off; documented in every example config.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DNMkDr9v6waKrZ538gutCK

* Sync: widen hull ids as unsigned in fleet records

HullSpec::Id is read as a 32-bit long and hull ids exceed 2^31 (Kumari is
3005922948), so widening the signed value put negative ids in the records
and name lookups failed for those hulls.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DNMkDr9v6waKrZ538gutCK

* Sync: include prev_state_name in fleet records

* Sync: add live cargo and mining state to client fleet records

Client records now carry the home/mining/repairing flags, cargo, and while
mining the node, amount mined and the game's own due time (mining_due).
Repairing fleets carry repair_due. Missing values are left out.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DNMkDr9v6waKrZ538gutCK

* Sync: send the server's deployed-fleet data as fleet records

MyDeployedFleets is parsed into src=server fleet records: system, node,
hull/shield, cargo cap, warp range, strength and pursued_by. No other
players' ids. Only fleets that changed are sent.

MyDeployedFleetsResponse lives in its own stfc.sync.proto because the game
doesn't declare it, and regenerating the Digit protos would drop it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DNMkDr9v6waKrZ538gutCK

* Sync: link repair jobs to their fleet

Repair jobs carry the fleet id. They're only sent with fleets on, so
jobs-only receivers see nothing new.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DNMkDr9v6waKrZ538gutCK

* Sync: send hull damage and re-read a fleet when the server updates it

Client records carry hull_damage while the fleet is docked or destroyed;
the client doesn't keep it current in space, where the server's hull
points are the live value.

The client fills in some values (mining and travel timers, damage) from
server data that arrives after the state change. When the server sends
new data for a fleet, or drops it from the deployed list, or a repair job
arrives for it, that fleet is re-read a second later and resent if those
values changed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DNMkDr9v6waKrZ538gutCK

* Sync: send the travel timer with fleet records

While a fleet charges, warps or moves on impulse, client records carry
travel_due, the arrival time from the fleet's timer.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DNMkDr9v6waKrZ538gutCK

---------

Co-authored-by: ProgenyAlpha <shawngraves@gmail.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
fix: set first sync flag for Haven
* Enable Kirshara recovery and queue protection on macOS

* Remove redundant Kirshara platform guards

* Use portable JSON parsing for fleet sync numbers
Use portable JSON parsing for fleet sync numbers
* Fix galaxy map drag momentum and inline pan delta

* Preserve pan momentum falloff with native hotkeys
)

* Fix Alliance Games Store research actions and purchase refresh

* Use portable JSON parsing for fleet sync numbers

* Retry Store CI after artifact service failure
* Fix wave joining, and auto-open chat

* Add missing files
* Fix wave joining, and auto-open chat

* Add missing files

* Prepare for release
@netniV
netniV added this pull request to the merge queue Nov 15, 2026
Merged via the queue into main with commit 8b7013e Nov 15, 2026
3 of 4 checks passed
@netniV
netniV deleted the codex/release-1.1.10.0 branch November 15, 2026 17:14
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.

9 participants