Potential Bug: sync url in general section may not be propagating to sync.targets.default section

[retrieving123]

if a user inputs a sync url/token in the general section, it does not propagate to the [sync.targets.default] section of the toml/vars file

secondary issue (or possibly the actual root cause), [sync.targets.default] section might be ignored and only [sync.targets.nextspocksclub] (and possibly [sync.targets.spocksclub]) is actually used by the vars file.

Steps to reproduce:
specify token/url in the general section (only) of the modconfig.pages.dev site
copy/paste to toml file
launch stfc
kill fkr hostile
refresh next.spocks.club syncing section, no change in rep

text from toml file

#  <[===================================================================]> 
#                                                                          
#       ****           *                    ****                           
#       *   *   ***   ***     ***          *      *   *  ***     ***       
#       *   *      *   *         *          ***    ****  *  *   *          
#       *   *   ****   *      ****             *      *  *  *   *          
#       ****    ****   **     ****         ****    ***   *  *    ***       
#                                                                          
#  <[===================================================================]> 

[sync]
# The url of the server to proxy the connection through
proxy = ""

# The token that is used to provide authentication
token = "<redacted>"

# The url of the server to send data to
url = "https://next.spocks.club/sync/ingress/"

# Subgroup: Data
# --------------

battlelogs = true
buffs = true
buildings = true
inventory = true
jobs = true
missions = true
officer = true
research = true
resources = true
ships = true
slots = true
tech = true
traits = true

# Subgroup: Diagnostics
# ---------------------

debug = false
logging = false

# Subgroup: Network
# -----------------

resolver_cache_ttl = "300"
verify_ssl = true

text from VARS file

[sync]
battlelogs = false
buffs = false
buildings = false
debug = false
inventory = false
jobs = false
logging = false
missions = false
officer = false
proxy = ''
research = false
resolver_cache_ttl = 300
resources = false
ships = false
slots = false
tech = false
traits = false
verify_ssl = true

    [sync.targets]

[ui]
always_skip_reveal_sequence = true
disable_escape_exit = true
disable_first_popup = false
disable_galaxy_chat = false
disable_move_keys = false
disable_preview_locate = false
disable_preview_recall = false
disable_toast_banners = false
disable_veil_chat = false
disabled_banner_types = ''
extend_donation_max = 80
extend_donation_slider = true
show_armada_cargo = true
show_cargo_default = true
show_hostile_cargo = true
show_player_cargo = true
show_station_cargo = true

[Guffawaffle]

Hey @retrieving123 — a fix for this has been submitted in PR #127.

What was happening

When you put your url and token under the top-level [sync] section (the "legacy" format), the mod was converting it into a named target under [sync.targets] — but it was only copying the URL and token, not the data sync booleans (battlelogs, officers, research, etc.). That's why your vars file showed everything as false and [sync.targets] was empty.

What the fix does

The legacy conversion now inherits all your sync options (battlelogs, buffs, buildings, inventory, jobs, missions, officer, research, resources, ships, slots, tech, traits, plus proxy/debug/logging/ssl settings) into the converted target. Your existing TOML config should just work as-is.

How to test

The CI build should produce a downloadable artifact you can grab:

1. Go to PR #127
2. Click the Checks tab (or look for the CI status at the bottom of the PR)
3. Click through to the Build workflow run
4. Download the stfc-community-mod artifact — it contains version.dll
5. Copy version.dll into your game folder (e.g. C:\Games\Star Trek Fleet Command\default\game\)
6. Launch the game, kill a hostile, and check your sync dashboard on next.spocks.club

If the CI artifact isn't available, you can also wait for the PR to be merged into an upcoming release.

Your TOML config looks correct — no changes needed on your end. Would you be able to give it a try and let us know if sync data starts coming through?

[Guffawaffle]

Actually... the build workflow might need an approval from netniv. Not sure, let me know if that doesn't work.