diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index acffd4f1..bc31635c 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -40,6 +40,12 @@ jobs: # assets) AND `git push origin ` (auto-tag the merge commit on # branch-push trigger). contents: write + # Required for the build provenance attestation. + id-token: write + attestations: write + env: + # The VirusTotal step runs only when this secret is set. + VT_KEY_SET: ${{ secrets.VIRUSTOTAL_API_KEY != '' }} steps: - name: Checkout (at tag, branch HEAD, or dispatch input) @@ -279,6 +285,17 @@ jobs: git tag -a $tag -m "Release $tag (auto-tagged by release.yml on merge to ${{ github.ref_name }})" git push origin $tag + - name: Attest build provenance + # Records that these exact files were built by this workflow from + # this commit. Anyone can check a download with + # `gh attestation verify --repo Osiris-DevWorks/smart-citizen`. + if: steps.gate.outputs.skip == 'false' + uses: actions/attest-build-provenance@v2 + with: + subject-path: | + ${{ steps.artifacts.outputs.installer_path }} + ${{ steps.artifacts.outputs.portable_path }} + - name: Publish GitHub Release if: steps.gate.outputs.skip == 'false' uses: softprops/action-gh-release@v2 @@ -294,6 +311,24 @@ jobs: draft: false prerelease: false + - name: Scan release files on VirusTotal + # Uploads both files to VirusTotal and adds the scan links to the + # end of the release notes, so users can check the results + # themselves. Runs only when the VIRUSTOTAL_API_KEY secret is set + # (a free VirusTotal account's key is enough). A VirusTotal outage + # never fails a release that is already published. + if: steps.gate.outputs.skip == 'false' && env.VT_KEY_SET == 'true' + uses: crazy-max/ghaction-virustotal@d34968c958ae283fe976efed637081b9f9dcf74f # v4.2.0 + with: + vt_api_key: ${{ secrets.VIRUSTOTAL_API_KEY }} + github_token: ${{ secrets.GITHUB_TOKEN }} + update_release_body: true + request_rate: 4 + files: | + ${{ steps.artifacts.outputs.installer_path }} + ${{ steps.artifacts.outputs.portable_path }} + continue-on-error: true + - name: Post Discord notification # Inlined here because the standalone release-notify.yml workflow # — which subscribes to `release: published` — is blocked from diff --git a/CLAUDE.md b/CLAUDE.md index 5709103b..7e93cdc3 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -77,14 +77,14 @@ Per-layer decisions live in the per-directory guides above. The ones below span The cached global source is saved as `base.ini` (not `global.ini`) to avoid confusion with the game's `global.ini` at `LIVE/data/Localization/english/global.ini`. ### Threading model -I/O-bound work (file loads, network, P4K extraction) runs in `QThread` workers in `src/gui/workers.py` (lone exception: `AppUpdateCheckWorker` in `src/utils/app_updater.py`, next to its companion logic). Workers emit `finished()`; cleanup needs `quit()` + `wait()`. Never block the main thread on file or network I/O. Wrap bulk table updates in `setUpdatesEnabled(False)`. `AppSettings` is thread-safe — use from main or worker. Worker logger names: `src.gui.workers` post-extraction (`src.gui.main_window` pre-extraction) — matters when grepping logs. +I/O-bound work (file loads, network, P4K extraction) runs in `QThread` workers in `src/gui/workers.py` (lone exception: `AppUpdateCheckWorker` in `src/utils/app_updater.py`, next to its companion logic). The one plain `threading.Thread` in `workers.py` is `LanguageNameTablesRead` (#569): `perform_merge_and_reload` reads the other languages' base.ini files on it beside its own merge and waits for it just before the rebuild. A reload that stops before that (no sources, or a merge that fails) leaves it running, and a `QThread` dropped while it runs aborts the app, where this daemon thread just finishes. Workers emit `finished()`; cleanup needs `quit()` + `wait()`. Never block the main thread on file or network I/O. Wrap bulk table updates in `setUpdatesEnabled(False)`. `AppSettings` is thread-safe — use from main or worker. Worker logger names: `src.gui.workers` post-extraction (`src.gui.main_window` pre-extraction) — matters when grepping logs. ### Startup initialization On first run, the app sets up user data dirs, validates the SC install path, and may show a startup dialog to guide config. Later runs check source freshness and apply any pending DataForge cache updates. ### DataForge extraction is a four-step pipeline The "Extract DataForge from P4K" button triggers, in order: -1. Unpack Data.p4k → entity XMLs via `src/utils/pak_extractor.py`. The bundled unp4k and unforge are .NET tools from the `odw-fast-unp4k` fork: unp4k reads Data.p4k's directory once and extracts through the archive it opened for the listing (on every core when there are several matches), and unforge reads the records on every core, leaving out the record folders the generator never reads (perf proposal; which commits the bundled exes are built from is in `src/utils/CLAUDE.md` → `pak_extractor.py`). unp4k and unforge work in a per-run folder beside the DataForge cache rather than in `%TEMP%` (#471; `%TEMP%` is only the fallback for a cache on OneDrive, a network share, a removable or network drive, or nested too deep), and closing the app stops them; see `src/utils/CLAUDE.md` → `pak_extractor.py`. +1. Unpack Data.p4k → entity XMLs via `src/utils/pak_extractor.py`. The bundled unp4k and unforge are .NET tools from the `odw-fast-unp4k` fork: unp4k reads Data.p4k's directory once and extracts through the archive it opened for the listing (on every core when there are several matches), and unforge reads the records on every core, leaving out the record folders the generator never reads (#522 and #529; which commits the bundled exes are built from is in `src/utils/CLAUDE.md` → `pak_extractor.py`). unp4k and unforge work in a per-run folder beside the DataForge cache rather than in `%TEMP%` (#471; `%TEMP%` is only the fallback for a cache on OneDrive, a network share, a removable or network drive, or nested too deep), and closing the app stops them; see `src/utils/CLAUDE.md` → `pak_extractor.py`. 2. Apply declarative patches from `patches/` via `src/utils/dataforge_patcher.py` to fix upstream CIG data bugs. Idempotent; runs on the extracted cache even when step 1 is skipped as fresh. 3. Run `scripts/generate_enhancements_ini.py` over the XMLs for every enabled category. Every file it writes is replaced in one step (`src/utils/atomic_io.py`), so a run cut off part-way leaves each file whole, old or new. Closing the app stops it at its next job boundary, never during its writes (see `src/gui/CLAUDE.md` → *Closing stops a running extraction*). Nothing hashes the cache any more: the old diff manifest, which nothing read, is gone (#495). 4. Reload all strings to refresh the table. @@ -98,7 +98,7 @@ Sources merge in user-defined order. Later sources overwrite earlier ones; user Two independent layers share one selected language (`AppSettings.get_selected_language()`, set from the Config tab): 1. **UI chrome** is translated via `src/utils/i18n.py`: `tr("dot.path.key", **kwargs)` reads `languages/{lang}/ui.json`, overlaid on English so missing keys fall back (then to the bare key). A runtime switch re-merges strings, and `MainWindow.retranslate_ui()` (with each tab's own `retranslate_ui`) sets the built widgets' texts again, the texts a refresh or a load writes included, so a switch shows what a restart in that language shows. `tests/test_language_switch_text.py` compares the two text by text, in both views with nothing loaded, and fails on a text there that has no `retranslate_ui` line (#540). Languages whose `ui.json` is a stub (only `_comment`) are hidden from the selector by `get_available_languages()`. -2. **Game strings**: English `base.ini` comes from local P4K extraction; every other language downloads a community `global.ini` per `languages/sources.json` (per-user URL override via the Config tab's *Map Language File* dialog). Caches are per-language: English at `{channel}\cache\base.ini`, others at `{channel}\cache\lang\{language}\base.ini` (`get_base_ini_path(language)`). The `global` merge source follows the selected language by one rule, `AppSettings.get_global_source_base_ini()` (the language's own base.ini when this channel has it, otherwise the English one), at startup, after a channel switch or a data-folder change and after a successful global.ini extraction (#502). +2. **Game strings**: English `base.ini` comes from local P4K extraction; every other language downloads a community `global.ini` per `languages/sources.json` (per-user URL override via the Config tab's *Map Language File* dialog). Caches are per-language: English at `{channel}\cache\base.ini`, others at `{channel}\cache\lang\{language}\base.ini` (`get_base_ini_path(language)`). The `global` merge source follows the selected language by one rule, `AppSettings.get_global_source_base_ini()` (the language's own base.ini when this channel has it, otherwise the English one), at startup, after a channel switch or a data-folder change and after a successful global.ini extraction (#502). The Blueprint Tracker's Owned set holds display names, so each load renames an owned name saved in another language to the loaded one through its loc key, read from one cached base.ini per other language (whichever channel has it), and a scan and Import Owned Blueprints do the same with their names (#569, see `src/gui/CLAUDE.md`). Enhancements are language-aware: generated INIs live next to that language's `base.ini` (`get_enhancements_dir()`), and a `.dataforge_stamp` marker per language triggers regeneration on switch when stale (English included). A generation empties that stamp just before the generator's `main()` runs (a failure before that keeps the old one) and writes it when `main()` returns, so the startup check also offers to regenerate a set whose last run was cut off or failed. Generator annotation paths always parse the *English* base.ini, so stat blocks stay English by design; mixed values (e.g. `Role: Cannoniere`) are intentional. The apply side is language-aware too: `get_global_ini_path()` writes `Localization\{sc_id}\global.ini` and `ensure_user_cfg_language()` sets `g_language` to match, both via `SC_LANGUAGE_IDS` (app folder name `portuguese_br` → game id `portuguese_(brazil)`). Turkish borrows `polish_(poland)` and Russian borrows `korean_(south_korea)`, because the game accepts neither language's own id; Russian and Korean sharing one slot is the one deliberate exception to "a borrowed slot is never shared" (the Korean font is the only in-game font with Cyrillic), so applying either replaces the other's `global.ini`. @@ -133,14 +133,14 @@ Anchor examples already in-tree: `COL_*` constants in `src/gui/string_table_mode | User data root (portable build) | `/data/` when frozen; `/portable_data/` unfrozen | | **Per-channel data** | `{user_data_root}\{LIVE\|PTU\|EPTU\|HOTFIX\|TECH-PREVIEW}\` — 0.9.3+ nests user.ini / cache / backups / dataforge under the active channel so each SC channel is isolated. Migrator: `AppSettings.migrate_game_path_to_channel_layout()`. | | User overrides | `{user_data_root}\{active_channel}\user.ini` (legacy `overrides.ini` auto-migrated) | -| Cached sources | `{user_data_root}\{active_channel}\cache\` — only `base.ini` post-1.0 (four legacy URL sources retired in 0.7.0), with its `.base_ini_stamp` (the size of the Data.p4k it was extracted from and base.ini's own size, perf proposal); enhancement INIs live here too. Non-English languages cache their downloaded base.ini at `cache\lang\{language}\base.ini` (2.0); resolved via `AppSettings.get_base_ini_path(language)` | -| DataForge cache | `%LOCALAPPDATA%\Smart Citizen\{active_channel}\cache\dataforge\` by default (entity XMLs from Data.p4k); overrideable independently of the user-data root via the `CACHE_DIR` registry key (1.4.1+ — `AppSettings.get_cache_dir_override()` / `set_cache_dir()`, wired to the Config tab's *DataForge Cache Folder*; the cache override does *not* fall back to the user-data override). Moved out of `Documents\` in 1.x — `migrate_dataforge_cache_to_local()` relocates the legacy `…\cache\dataforge\` tree on first launch. Resolved via `AppSettings.get_dataforge_cache_dir()`, which creates it, only where the folder is meant to be made (the migrator, an extraction about to fill it or work beside it, a newly picked folder in the Config tab), and via `get_dataforge_cache_leaf()`, which creates nothing, everywhere else: every status check, Clear Cache (#479), and the enhancement generator, which writes into a cache its launcher has already checked is there. So a folder Windows refuses or a drive that is gone reads as not extracted (#494). An extraction works in a sibling `…\cache\dataforge.extracting-XXXXXXXX\` folder (up to about 4.5 GB free while it runs, checked before any tool starts (#482), deleted when it ends, or after a successful DataForge run in the background while enhancements are generated, with the old cache set aside in it (perf proposal); the global.ini extraction in `globalini.extracting-XXXXXXXX`) so the heavy writes land on the cache's drive (#471). A cache on OneDrive, a network share, a removable or network drive, or nested too deep sends the run to `%TEMP%\SmartCitizen-DataForge-XXXXXXXX\` instead (`SmartCitizen-GlobalIni-` for global.ini). A DataForge run there first makes and removes one empty `dataforge.extracting-` folder beside the cache folder, so a folder that would not let the wipe make the cache folder again is refused before any tool runs, with the old cache kept (#494). A cache folder that is itself a junction or a symbolic link is refused before an extraction runs, with the old cache and the link kept, because nothing is deleted through a link (#491). | +| Cached sources | `{user_data_root}\{active_channel}\cache\` — only `base.ini` post-1.0 (four legacy URL sources retired in 0.7.0), with its `.base_ini_stamp` (the size of the Data.p4k it was extracted from and base.ini's own size, #522); enhancement INIs live here too. Non-English languages cache their downloaded base.ini at `cache\lang\{language}\base.ini` (2.0); resolved via `AppSettings.get_base_ini_path(language)` | +| DataForge cache | `%LOCALAPPDATA%\Smart Citizen\{active_channel}\cache\dataforge\` by default (entity XMLs from Data.p4k); overrideable independently of the user-data root via the `CACHE_DIR` registry key (1.4.1+ — `AppSettings.get_cache_dir_override()` / `set_cache_dir()`, wired to the Config tab's *DataForge Cache Folder*; the cache override does *not* fall back to the user-data override). Moved out of `Documents\` in 1.x — `migrate_dataforge_cache_to_local()` relocates the legacy `…\cache\dataforge\` tree on first launch. Resolved via `AppSettings.get_dataforge_cache_dir()`, which creates it, only where the folder is meant to be made (the migrator, an extraction about to fill it or work beside it, a newly picked folder in the Config tab), and via `get_dataforge_cache_leaf()`, which creates nothing, everywhere else: every status check, Clear Cache (#479), and the enhancement generator, which writes into a cache its launcher has already checked is there. So a folder Windows refuses or a drive that is gone reads as not extracted (#494). An extraction works in a sibling `…\cache\dataforge.extracting-XXXXXXXX\` folder (up to about 4.5 GB free while it runs, checked before any tool starts (#482), deleted when it ends, or after a successful DataForge run in the background while enhancements are generated, with the old cache set aside in it (#522); the global.ini extraction in `globalini.extracting-XXXXXXXX`) so the heavy writes land on the cache's drive (#471). A cache on OneDrive, a network share, a removable or network drive, or nested too deep sends the run to `%TEMP%\SmartCitizen-DataForge-XXXXXXXX\` instead (`SmartCitizen-GlobalIni-` for global.ini). A DataForge run there first makes and removes one empty `dataforge.extracting-` folder beside the cache folder, so a folder that would not let the wipe make the cache folder again is refused before any tool runs, with the old cache kept (#494). A cache folder that is itself a junction or a symbolic link is refused before an extraction runs, with the old cache and the link kept, because nothing is deleted through a link (#491). | | Crash dumps + log exports | `{user_data_root}\logs\` (NOT per-channel — a crash can fire before the channel context is established, e.g. during startup migrators). Resolved via `AppSettings.get_logs_dir()`; created lazily on first crash or export. | | Enhancement INIs | next to the active language's base.ini via `AppSettings.get_enhancements_dir(language)`: `{user_data_root}\{active_channel}\cache\` for English, `cache\lang\{language}\` otherwise (`ships_desc_enhancements.ini`, `components_desc_enhancements.ini`, `ship_weapons_desc_enhancements.ini`, `fps_weapons_desc_enhancements.ini` (also carries the #492 armor weight tags), `mission_rewards_enhancements.ini`, `commodity_crafting_enhancements.ini`, `journal_enhancements.ini`, `missile_enhancements.ini`, `medical_consumables_enhancements.ini`; plus the `.dataforge_stamp` freshness marker and the `.tag_config_stamp` Tag Builder marker, and `crafting_index.json` for the overlay drawer's Crafting search, written whenever Commodities or Journal is generated) | | Overlay scan samples | `{user_data_root}\logs\sco_samples\` (not per-channel): a crop of each distinct signature reading while the overlay's scan decoder runs, at most 200 per session, and a session's first save prunes the folder to the newest 1000 (`sco_overlay.prune_samples`), so misreads can become reference glyphs. Tuning only: written only when the `SMART_CITIZEN_SCO_SAMPLES` environment variable (`sco_overlay.SAVE_SAMPLES_ENV`) is set when the app starts; players never get it and the app has no switch for it. Resolved via `AppSettings.get_sco_samples_dir()` at save time | | SCO Item Finder shop list | `{user_data_root}\{active_channel}\cache\uex_shops.json` (`uex_shops.SHOP_CACHE_FILE`): the shops that sell each item and their prices, trimmed from UEX's `items_prices_all` and `terminals?type=item` answers, fetched at most every 12 hours (`MAX_AGE_S`) while the overlay runs with its Item Finder on, and used as it is when UEX cannot be reached (#606) | | Backups | `{user_data_root}\{active_channel}\backups\` (max 5, oldest auto-deleted) | -| Game file | `{sc_install_root}\{active_channel}\data\Localization\{sc_language_id}\global.ini` — `AppSettings.get_global_ini_path()` (language dir follows the selected language via `SC_LANGUAGE_IDS`) | +| Game file | `{sc_install_root}\{active_channel}\data\Localization\{sc_language_id}\global.ini` — `AppSettings.get_global_ini_path()` (language dir follows the selected language via `SC_LANGUAGE_IDS`); `get_applied_global_ini(channel_dir)` names it in any channel's install folder | | UI translations + language source map | `languages/{language}/ui.json` (UI strings) and `languages/sources.json` (per-language base.ini download URLs). Bundled via both `SmartCitizen.spec` and `scripts/build/build_exe.py` | | P4K tools | `assets/unp4k/` (`unp4k.exe`, `unforge.exe`), built from `odw-fast-unp4k` (the commits are in `src/utils/CLAUDE.md` → `pak_extractor.py`) | | DataForge patches | `patches/` (JSON files mirroring DataForge layout; applied post-extraction) | @@ -167,14 +167,14 @@ Anchor examples already in-tree: `COL_*` constants in `src/gui/string_table_mode | Change backup behavior | `src/gui/main_window.py` | `manage_backups()` | | Modify P4K extraction | `src/utils/pak_extractor.py` | `extract_dataforge()` | | Change the extraction free-space check | `src/utils/pak_extractor.py` | `_require_free_space()`, `_dataforge_needs()`, `_require_room_for_new_cache()`, the #482 constants | -| Change how a folder tree is deleted (working folder, old cache, Clear Cache, queued cleanup) | `src/utils/pak_extractor.py` | `robust_rmtree()`, `_delete_files_first()` (the threaded file pass, perf proposal), `_DELETE_THREADS` | +| Change how a folder tree is deleted (working folder, old cache, Clear Cache, queued cleanup) | `src/utils/pak_extractor.py` | `robust_rmtree()`, `_delete_files_first()` (the threaded file pass, #522), `_DELETE_THREADS` | | Change enhancements generation | `scripts/generate_enhancements_ini.py` | (standalone script) | | Add performance profiling | `src/utils/perf.py` | `@timed` decorator | | Change user data paths | `src/utils/settings.py` | `AppSettings.get_user_data_dir()` | | Change DataForge freshness | `src/utils/settings.py`, `src/gui/main_window.py` | `dataforge_cache_is_fresh()` | | Change how generated files are written | `src/utils/atomic_io.py` | `atomic_writer()`, `atomic_write_text()`, `read_bytes_retrying()` (the enhancement INIs, `crafting_index.json`, both stamps, the lookup pickles and patched cache XMLs are swapped in whole, never written in place) | | Change the enhancements out-of-date check | `src/utils/settings.py`, `src/gui/main_window.py`, `src/gui/workers.py` | `enhancements_built_from_current_dataforge()` (the one definition of "current", shared by the startup check, the Generate button and the language switch), `_check_enhancements_freshness()`, `EnhancementsGeneratorWorker.run()` (empties `.dataforge_stamp` before the generator runs, writes it after) | -| Change base.ini freshness (the Extract prompt and the Extract button's red nudge) | `src/utils/pak_extractor.py` | `base_ini_is_fresh()`, `BASE_INI_STAMP` (perf proposal: Data.p4k's size, as #209 for DataForge, with base.ini's own size so the stamp speaks only for the base.ini it was written for; read by `MainWindow._check_p4k_freshness` and `ConfigTab._refresh_p4k_status`) | +| Change base.ini freshness (the Extract prompt and the Extract button's red nudge) | `src/utils/pak_extractor.py` | `base_ini_is_fresh()`, `BASE_INI_STAMP` (#522: Data.p4k's size, as #209 for DataForge, with base.ini's own size so the stamp speaks only for the base.ini it was written for; read by `MainWindow._check_p4k_freshness` and `ConfigTab._refresh_p4k_status`) | | Change Run in Background or the job lock | `src/gui/main_window.py`, `src/gui/config_tab.py`, `src/gui/enhancements_tab.py`, `src/gui/simple_mode_widget.py`, `src/gui/theme.py` | `_confirm_stop_dataforge_extraction()`, `_send_dataforge_run_to_background()`, `_confirm_stop_generation()` (the same question on the generation dialog), `_stop_generation_from_dialog()`, `_send_generation_to_background()`, `_job_running()`, `_closing_would_wait()` (what Import Settings and an update's install ask: `_job_running()` plus a background working-folder delete), `_refresh_job_lock()`, `_dataforge_run_matches_settings()`, `_ask_after_the_job()` (a startup question a job put off, asked again after the load that ends it), `ConfigTab.set_data_locations_locked()`, `EnhancementsTab.set_changes_locked()`, `SimpleModeWidget.set_busy(busy, reason)`, `theme.needs_apply_style()`, `theme.dimmed_color()` (#483) | | Change stats/favorites UI | `src/gui/enhancements_tab.py` | `setup_ui()` | | Manage Config tab UI | `src/gui/config_tab.py` | `setup_ui()`, drag-drop hierarchy | @@ -182,7 +182,8 @@ Anchor examples already in-tree: `COL_*` constants in `src/gui/string_table_mode | Manage Blueprint Tracker tab UI | `src/gui/blueprint_tracker_tab.py` | `setup_ui()`, `set_blueprint_items()`, `_render_blueprint_lists()` | | Change blueprint type/class/size/grade classification | `src/utils/blueprint_meta.py` | `build_blueprint_metadata()`, `blueprint_type_from_key()` | | Add a blueprint every player starts with (never logged, never a mission reward) | `src/utils/blueprint_meta.py`, `src/gui/main_window.py` | `DEFAULT_OWNED_BLUEPRINTS` (by loc key, English name as fallback), `_seed_default_owned_blueprints()` (adds each to Owned once, on the first scan after it is declared, recorded by loc key, #416); their mission label `DEFAULT_OWNED_MISSION_LABEL` stays English in the metadata and shows translated through `mission_display_name()` | -| Change the "Scan Logs for Owned Blueprints" log parsing | `src/utils/blueprint_log_scanner.py` | `extract_blueprint_names()`, `find_log_files()` | +| Change the "Scan Logs for Owned Blueprints" log parsing | `src/utils/blueprint_log_scanner.py`, `src/gui/main_window.py` | `parse_events()`, `scan_files()`, `find_log_files()`, `notification_templates()` (the notification in the language the game shows, #564), `main_window._blueprint_notification_files()` (the loc files its text is read from) | +| Change the owned-name repair (names another editor left, #372; items' short labels, #570; names saved in another language, #569) | `src/utils/owned_items.py`, `src/utils/blueprint_meta.py`, `src/utils/settings.py`, `src/gui/main_window.py` | `resolve_against_catalogue()`, `repair_foreign_owned_names()`, `drop_short_labels()` (keeps a label another language uses as an item's name), `rename_across_languages()` (through the loc key), `known_item_names()` (every real item name, short labels left out), `short_label_names()`, `item_name_sets()` (both, and each item's name by loc key, in one pass, what a load uses), `item_keys_by_name()` (another language's names, from its base.ini), `other_language_files()` (one cached copy per language but the loaded one), `read_item_keys_by_name()` (reads only new or changed files), `AppSettings.get_cached_base_ini_paths()` (every channel), `workers.read_language_name_tables()` (never on the GUI thread: the loader's thread, or `LanguageNameTablesRead` beside a synchronous reload), `MainWindow._repair_foreign_owned_names()` (on every load), `MainWindow._rename_from_other_languages()` (the load, a scan's names and Import Owned Blueprints), `BlueprintTrackerTab.set_name_renamer()` | | Change in-app logging | `src/gui/log_tab.py` | `LogTab`, `_QtLogHandler` | | Change user.cfg behavior | `src/utils/user_cfg.py` | `ensure_user_cfg_language()` | | Fix an upstream DataForge data bug | `patches//.../.patch.json`, `src/utils/dataforge_patcher.py` | `apply_patches()` | @@ -196,6 +197,7 @@ Anchor examples already in-tree: `COL_*` constants in `src/gui/string_table_mode | Change what unforge leaves out of the DataForge cache | `src/utils/dataforge_exclude.py`, `src/utils/pak_extractor.py` | `DATAFORGE_EXCLUDE_SUBPATHS` (never a `DATAFORGE_KEEP_SUBPATHS` path, one under it or one above it), `_write_unforge_exclude_list()`, `_unlisted_records()` | | Change Export Loc-Pack zip behavior | `src/utils/locpack_exporter.py` | `default_locpack_filename()`, `write_locpack_zip()` | | Change apply-time launcher watermark | `src/gui/main_window.py` | `_stamp_frontend_version()`, `_FRONTEND_VERSION_KEY`, `_FRONTEND_VERSION_STAMP_RE` | +| Change the main-menu Play button reminder | `src/gui/main_window.py` | `_add_play_button_reminder()`, `_PLAY_BUTTON_KEY`, `_PLAY_BUTTON_REMINDER` (a replaced wording must stay in `_PLAY_BUTTON_REMINDER_RE`), `_centre_menu_lines()`, the button's fonts `_BLENDER_PRO_MEDIUM` and `_NOTO_SANS` (for `_NOTO_SANS_SLOTS`, picked by `_ApplyMergeInputs.sc_language_id`) (#566) | | Change Modified/Enhanced/Unmodified/New status logic | `src/parser/ini_parser.py` | `_determine_status_from_source()` | | Adjust close-time user.ini autosave guard | `src/utils/user_ini_manager.py` | `should_autosave_user_ini()` | | Change "Reset user.ini" tool behavior | `src/utils/user_ini_manager.py`, `src/gui/config_tab.py` | `reset_user_ini()` (+ Config-tab button wiring) | @@ -212,7 +214,7 @@ Anchor examples already in-tree: `COL_*` constants in `src/gui/string_table_mode | Add or fix a translated UI string | `languages/{language}/ui.json`, `src/utils/i18n.py` | `tr()`, `set_language()` (dot-path keys; English is the fallback base) | | Change the language-switch flow | `src/gui/config_tab.py`, `src/gui/main_window.py` | `language_changed` signal, `MainWindow._on_language_changed()` (retranslate chrome, repoint the `global` source, download base.ini when a URL is mapped, regen stale enhancements, reload) | | Change per-language base.ini download / URL mapping | `src/gui/workers.py`, `src/utils/settings.py`, `languages/sources.json` | `LanguageBaseDownloadWorker`, `get_language_base_url()`, `LanguageSourceDialog` (Config tab's *Map Language File*) | -| Change per-language cache or enhancements layout | `src/utils/settings.py` | `get_base_ini_path(language)`, `get_enhancements_dir(language)`, `get_/set_enhancements_stamp()` (the setters' `folder=` takes the folder a generation started with), `invalidate_enhancements_stamp()` | +| Change per-language cache or enhancements layout | `src/utils/settings.py` | `get_base_ini_path(language)` (and `get_base_ini_leaf(language, channel)`, the same file for any channel with no folder made, #564), `get_enhancements_dir(language)`, `get_/set_enhancements_stamp()` (the setters' `folder=` takes the folder a generation started with), `invalidate_enhancements_stamp()` | | Toggle mission-detail fields per user | `src/gui/enhancements_tab.py`, `src/utils/settings.py` | `_MISSION_FIELD_SETTING` (per-field show/hide for mission bodies, #121); the `route` key adds the haul route to titles (#166) | | Change hauling/delivery route-in-title | `scripts/generate_enhancements_ini.py` | `_derive_route_fragment()` / `_route_token_role()` / `_title_route_token()` / `_expand_nested_route_vars()` (#166, reworked in #200: |Address default, comma-listed endpoints, one-level `*Token` expansion, per-body intersection; applied in both the contractgen title loop and the pu-only second pass; placed before the [BP]/XP tags via the mission_titles TagConfig) | | Change stock-title shortening (Mission Titles) | `src/utils/tag_builder.py`, `scripts/generate_enhancements_ini.py` | `SHORTEN_PHRASE_OPTIONS` (phrase→shorter-phrase) + `REMOVE_WORD_OPTIONS` (Cargo/Haul/Rank word removal, Rank merged to one checkbox covering both dash- and comma-led contexts) + `abbreviate_title()`; `RANK_SEPARATORS` (None/Dash/Pipe/Colon rendered after the Rank position regardless of removal; "none" default, "space" omitted as indistinguishable from "none" post-normalization); `SIZE_ABBREVIATIONS` + `_size_abbreviation_overrides()` (cargo-grade words to XS/S/M/L via loc-key overrides, each size independently opted in via `TagConfig.shortened_sizes`); word/phrase removal gated by `TagConfig.abbreviated_phrases` (empty by default), applied at both title-emission sites (#200 follow-up, generalized) | @@ -266,6 +268,8 @@ The branching model above is enforced by GitHub settings, not just convention. D 6. Create the GitHub release and attach `dist/SmartCitizen-{VERSION}-Setup.exe` (installer only; portable onefile exe is retired). 7. Open the next `release/X.Y.(Z+1)` off `main` and bump `VERSION.TXT` — the new integration target. +**Download checks**: every release gets a build provenance attestation for the installer and the portable zip (`gh attestation verify --repo Osiris-DevWorks/smart-citizen`), and, when the `VIRUSTOTAL_API_KEY` secret is set, a VirusTotal scan whose links are added to the release notes. Security reports go through `SECURITY.md` (GitHub private vulnerability reporting). + Discord notification fires via GitHub Actions (`scripts/discord_notify.py`) when `DISCORD_RELEASE_WEBHOOK_URL` secret is set. **Tester pre-release installers**: `.github/workflows/installer-preview.yml` builds a downloadable `SmartCitizen-{VERSION}-Setup.exe` artifact outside the standard release flow. Triggers: (1) `workflow_dispatch` from the Actions tab against any branch, (2) adding the `build-installer` label to a PR (later pushes to the labeled PR rebuild via `synchronize`; remove the label to stop rebuilds). In the integration-branch model this is the *primary* signal that a release is near test sign-off — when the user adds the label, treat the active release branch as approaching ship. Artifact: `smartcitizen-installer-{SHA}`, 30-day retention (testers need lead time vs. CI's 7). The `concurrency` group cancels in-flight builds when a newer commit lands on the same PR / branch. diff --git a/README.md b/README.md index a68b3b61..e4cf85e5 100644 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ A Windows desktop app for customizing Star Citizen's localization strings. Layer - **Auto-Generated Enhancements**: Stat overlays for ships, ship components, ship weapons, FPS weapons, missions (with `[BP]`/`[BP?]` blueprint reward tags + structured detail blocks), journal entries, commodity crafting cross-references, and medical consumable effects — all togglable per category in the Enhancements tab. Stat blocks can sit above or below the description. Mission XP names the reputation track it feeds, Battaglia scan/mine titles carry `[RS ####]` resource-signature tags, and the Mining Compendium journal lists each ore's base RS. - **Tag Builder & Mission Titles**: Customize the bracketed name tags on components, missiles, ship weapons, commodities, and armor, and lead hauling mission titles with their route (e.g. `Area18 > Lorville`) — configurable placement, arrow, separator, and location detail, plus optional stock-title shortening, with a live preview. - **Blueprint Tracker**: A dedicated tab for marking the crafting blueprints you already own. Shuttle items between Available and Owned, narrow the list with search and Mission / Type / Class / Size / Grade filters, and owned items get a blue `[Owned]` tag in mission blueprint lists. **Scan Logs for Owned Blueprints** reads your Star Citizen log files to populate ownership automatically, importing only what's new since the last scan. It always reads LIVE, plus HOTFIX when installed (they share one account progression), and never the PTU, EPTU or TECH-PREVIEW test servers; a **Rescan all logs** checkbox forces a full re-read when something looks off. **Auto-scan logs on startup** (off by default) runs the same scan every time the app starts. **Export / Import Owned Blueprints** moves your owned list between PCs (JSON or CSV; imports only ever add, and scmdb.net exports work too). -- **Smart Citizen Overlay**: Optional windows over the game (borderless windowed). A mining scan decoder reads the scan signature under your radar and shows the deposit behind it (e.g. `3 × Lindinium`), with an alert for minerals or salvage you watch. A drawer, with its own hotkey, searches your blueprints, where minerals are found, and which items a mineral crafts into. It only captures the screen and reads `Game.log`: nothing touches the game's memory or sends input. +- **Smart Citizen Overlay**: Optional windows over the game (borderless windowed). A mining scan decoder reads the scan signature under your radar and shows the deposit behind it (e.g. `3 × Lindinium`), with an alert for minerals or salvage you watch. A drawer, with its own hotkey, searches your blueprints, where minerals are found, and which items a mineral crafts into. It only captures the screen, reads `Game.log`, asks Windows which window is in front and whether the mouse pointer shows and, if you set a drawer hotkey, whether its key and the Ctrl, Alt, Shift and Win keys are down: nothing touches the game's memory or sends input. - **Declarative CIG Data-Bug Patches**: A patch system applies fixes to known DataForge bugs at extraction time so the in-game text reads correctly without waiting on CIG. - **Search & Filter**: Free-text search, category filter (Ships, Ship Items, Missions, Gear, Commodities, Journal, Other), modified/unmodified status, per-column filter rows under every header, and a **Ship/Vehicle Names Only** toggle that narrows the table to the ship name rows favoriting applies to. - **Ship Favorites**: Star a ship to prepend a configurable prefix (default `*`) so your favorites sort to the top of the in-game ASOP terminal. @@ -77,6 +77,9 @@ Download the **`SmartCitizen-{VERSION}-Setup.exe`** installer and run it. The ap Smart Citizen runs on Linux through the same Wine prefix as Star Citizen — see **[LINUX.md](docs/LINUX.md)** for the full guide (download the portable build, then point a launch script at the Wine runner your game uses). +> [!IMPORTANT] +> **The Smart Citizen Overlay needs an X11 session, not Wayland.** If you want the overlay on Linux, log out and pick the **X11** (or **Xorg**) session on your login screen. Steps are in [LINUX.md](docs/LINUX.md). + ### For Developers See **[docs/CONTRIBUTOR_GUIDE.md](docs/CONTRIBUTOR_GUIDE.md)** for local setup (prerequisites, clone, install, run). @@ -217,6 +220,7 @@ Thanks to those who've contributed code to Smart Citizen: - [**scubamount**](https://github.com/scubamount) - **hkstrongside** - [**odw-okano**](https://github.com/odw-okano) +- [**RWolfyo**](https://github.com/RWolfyo) ## Acknowledgments diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 00000000..8684fae5 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,25 @@ +# Security Policy + +## Reporting a problem + +Please don't report security problems in a public issue. + +Use GitHub's private reporting instead: open the repository's **Security** tab and click **Report a vulnerability**. Only the maintainer sees the report. + +Include what you found, the Smart Citizen version, and steps to reproduce it if you can. You'll get a reply within a week. + +## Supported versions + +Only the latest release gets security fixes. Please update before reporting. + +## Checking a download + +Download Smart Citizen only from the [GitHub releases page](https://github.com/Osiris-DevWorks/smart-citizen/releases). + +Each release lists VirusTotal scan links for its files in the release notes. You can also check that a file was built by this repository's release workflow: + +``` +gh attestation verify SmartCitizen-X.Y.Z-Setup.exe --repo Osiris-DevWorks/smart-citizen +``` + +Windows Defender sometimes flags new, unsigned apps with a machine-learning guess such as "Bearfoos.A!ml". That is a false positive. Code signing is planned for a future release. diff --git a/assets/tutorial.json b/assets/tutorial.json index cc7a7674..81c550ab 100644 --- a/assets/tutorial.json +++ b/assets/tutorial.json @@ -22,7 +22,7 @@ { "id": "enh_categories", "title": "3. Enhancements: Categories", - "description": "Toggle which enhancement categories run when you Generate. Ships, components, ship weapons, FPS weapons, missions, mission rewards, commodity crafting, and medical consumables can each be enabled independently.", + "description": "Toggle which enhancement categories run when you Generate: Ships, Ship Items, Gear, Missions, Commodities, Journal, Medical Consumables. Ship Items covers components, ship weapons and missiles; Gear covers FPS weapons and armor tags. Each category can be turned on or off on its own.", "preferred_side": "right" }, { @@ -88,7 +88,7 @@ { "id": "cfg_appearance", "title": "14. Config: Appearance", - "description": "Pick the app theme (Default / Light / Dark / ODW) and optionally disable the auto-tour on new versions.", + "description": "Pick the app theme (Default / Light / Dark / ODW) and the font size (Small / Medium / Large, applied after a restart), and optionally turn off the auto-tour on new versions.", "preferred_side": "right" }, { @@ -112,12 +112,24 @@ { "id": "cfg_tools", "title": "18. Config: Tools", - "description": "Import an external INI into your overrides via the conflict-resolution dialog, or reset your user.ini for the active channel (auto-backed-up before clearing).", + "description": "Import an external INI into your overrides through the conflict-resolution dialog. Reset your user.ini for the active channel (backed up first), or bring back an earlier copy with Restore user.ini. Preview Apply shows what Apply would write, and Check for Updates looks for a new version.", + "preferred_side": "right" + }, + { + "id": "cfg_backup", + "title": "19. Config: Settings Backup", + "description": "Export Settings saves your preferences, tag setups, Star Citizen folder and custom strings for every channel into one file. Import Settings brings them back, on a new PC or after a fresh install.", + "preferred_side": "right" + }, + { + "id": "cfg_sc_tools", + "title": "20. Config: Star Citizen Tools", + "description": "Clear Shader Cache lists the game's shader cache folders, one per game build. Clean deletes the shaders and keeps your graphics settings; Remove deletes the whole folder. Close Star Citizen first.", "preferred_side": "right" }, { "id": "help", - "title": "19. Help & feedback", + "title": "21. Help & feedback", "description": "The Help button opens a side-panel with the full guide, a Known Issues list, and a feedback link to the Smart Citizen Discord channel. That's everything you need to get started — good luck, citizen.", "preferred_side": "below" } diff --git a/docs/3.0.1-RELEASE-NOTES.md b/docs/3.0.1-RELEASE-NOTES.md new file mode 100644 index 00000000..703160d3 --- /dev/null +++ b/docs/3.0.1-RELEASE-NOTES.md @@ -0,0 +1,39 @@ +# Smart Citizen 3.0.1 + +> ⚠️ **If Windows blocks the installer:** Smart Citizen isn't code-signed yet, so Windows 11's **Smart App Control** blocks it (Unblock in Properties doesn't help). Go to **Settings → Privacy & security → Windows Security → App & browser control → Smart App Control settings**, set it to **Off**, run `SmartCitizen-3.0.1-Setup.exe`, then turn it back on if you like. + +**Download:** [latest release](https://github.com/Osiris-DevWorks/smart-citizen/releases/latest). `SmartCitizen-3.0.1-Setup.exe` is the installer; `SmartCitizen-Portable-v3.0.1.zip` runs without installing (and [on Linux through Wine](https://github.com/Osiris-DevWorks/smart-citizen/blob/main/docs/LINUX.md)). Existing installs will offer the update at launch. + +## Highlights + +### Mining scan decoder + +- Reads the scan signature at a wide field of view, in small cockpits, on bright planets and snow, and with Windows HDR on. + +### Smart Citizen Overlay + +- Firing while you aim no longer clicks the drawer and takes focus away from the game. +- Closing the drawer with its tab gives the mouse and keyboard back to the game, like the hotkey does. +- The drawer hotkey no longer sees your other key presses. In game, it only checks its own keys. + +> **Linux users:** the overlay works on X11 but not on Wayland. To use it, log out and pick the X11 (or Xorg) session on the login screen. Run `echo $XDG_SESSION_TYPE` to see which one you're on. The rest of Smart Citizen works on both. See the [Linux guide](https://github.com/Osiris-DevWorks/smart-citizen/blob/main/docs/LINUX.md). + +## New + +- **Play button reminder:** after Apply, the main menu's Play button says "Run Smart Citizen after every patch". +- **Guided tour:** updated for 3.0, with steps for Settings Backup and Star Citizen Tools. + +## Fixes + +- The blueprint scan and the overlay find blueprints when the game is in Spanish or another language. +- The Owned list follows your language. A blueprint no longer shows twice, and old armor names no longer turn into set names like "Dust Devil". +- Aphorite, Dolivine and Hadanite rocks get their [CF] tag before you fracture them. +- Carrack map room labels no longer show ship stats. + +**After updating:** run **Generate Enhancements**, then **Apply Enhancements**. + +## Credits + +**Stealrull** did most of this release. **RWolfyo** joins as a new contributor with the scan decoder fix for bright planets and HDR. Thanks to **RussoJr** for reporting the hotkey issue, and to everyone who sent logs and screenshots. + +Bugs or questions: the **[Osiris DevWorks Discord](https://discord.gg/BNzRegKZ7k)**. Attach your log (**Log** tab → **Export**). diff --git a/docs/ABOUT.md b/docs/ABOUT.md index d39fea08..30854287 100644 --- a/docs/ABOUT.md +++ b/docs/ABOUT.md @@ -29,6 +29,7 @@ Thanks to those who've contributed code to Smart Citizen: - **scubamount** - **hkstrongside** - **odw-okano** +- **RWolfyo** ## Translators @@ -113,7 +114,7 @@ The non-English game strings are community translations: - **Mission Titles**: Lead hauling titles with their route (e.g. `Area18 > Lorville`) — configurable placement, arrow, separator, and location detail, plus optional stock-title shortening, with a live preview - **Stats Above or Below**: Choose whether a stat block sits at the top or the bottom of the description - **Blueprint Tracker**: A dedicated tab for marking the crafting blueprints you already own. Shuttle items between Available and Owned, filter by Mission / Type / Class / Size / Grade, and owned items get a blue `[Owned]` tag in mission blueprint lists. **Scan Logs for Owned Blueprints** populates ownership automatically from your Star Citizen log files, importing only what's new since the last scan (or automatically on startup, when **Auto-scan logs on startup** is on), and **Export / Import Owned Blueprints** moves the owned list between PCs (JSON or CSV; imports only ever add, and scmdb.net exports work too) -- **Smart Citizen Overlay**: Optional windows over the game (borderless windowed). A mining scan decoder shows the deposit behind a signature (`3 × Lindinium`) and can glow, flash or chime for minerals or salvage you watch; a drawer, with its own hotkey, searches your blueprints, where minerals are found, and what they craft; and blueprints you earn are marked owned from `Game.log` while it runs. Screen pixels, `Game.log` and an optional hotkey only: no injection, memory reads, or input +- **Smart Citizen Overlay**: Optional windows over the game (borderless windowed). A mining scan decoder shows the deposit behind a signature (`3 × Lindinium`) and can glow, flash or chime for minerals or salvage you watch; a drawer, with its own hotkey, searches your blueprints, where minerals are found, and what they craft; and blueprints you earn are marked owned from `Game.log` while it runs. Screen pixels, `Game.log`, which window is in front, whether the pointer shows and an optional hotkey only: no injection, memory reads, or input - **Mission Labels**: Rename the section headers (MISSION DETAILS, POTENTIAL BLUEPRINTS, etc.), the XP label, and the emphasis tag used for headers - **Declarative CIG Data-Bug Patches**: A patch system applies fixes to known DataForge bugs at extraction time so in-game text reads correctly without waiting on CIG - **Selective Categories**: Enable or disable each enhancement category independently from the Enhancements tab diff --git a/docs/FAQ.md b/docs/FAQ.md index 89c4c670..eb82e007 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -15,7 +15,7 @@ Your personal edits live in `user.ini` in your Smart Citizen data folder, separa Smart Citizen only edits localization text (the words the game shows you), it doesn't touch game logic, give you any advantage, or talk to CIG's servers. Our modifications **should** be fine. -The optional **Smart Citizen Overlay** (Overlay tab) works the same hands-off way. It draws ordinary windows on top of the game, reads pixels from your screen like a screenshot tool does, and reads the game's `Game.log` file. It never injects into or hooks the game, never opens the game's process or reads its memory, and never sends keyboard or mouse input. If you set a drawer hotkey, it registers that one key combination with Windows, the standard way a program asks for a hotkey. Star Citizen keeps registered hotkeys from other programs while it has focus, so while a hotkey is set the overlay also takes the keyboard's raw input, the read-only way Windows tells a background program about key presses. That is not a keyboard hook: it holds up, changes and sends no key, keeps no record, and acts only on your combination. CIG has not said anything about overlays like this, so the same at-your-own-risk note below applies. +The optional **Smart Citizen Overlay** (Overlay tab) works the same hands-off way. It draws ordinary windows on top of the game, reads pixels from your screen like a screenshot tool does, and reads the game's `Game.log` file. While its drawer shows, it also asks Windows which window is in front and whether the mouse pointer shows, so your shots pass through the drawer while you aim. It never injects into or hooks the game, never opens the game's process or reads its memory, and never sends keyboard or mouse input. If you set a drawer hotkey, it registers that one key combination with Windows, the standard way a program asks for a hotkey. Star Citizen keeps registered hotkeys from other programs while it has focus, so while the game is in front the overlay also asks Windows whether that combination's key is down and, only while it is, whether Ctrl, Alt, Shift or Win is held. It asks about no other key, is never sent what you type in the game or another program, and never holds up, changes or sends a key. CIG has not said anything about overlays like this, so the same at-your-own-risk note below applies. CIG has publicly backed community localization. Their [Community Localization Update](https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/star-citizen-community-localization-update) post lays out official support for player-made translations, which we understand to explicitly allow the kind of localization editing Smart Citizen does. diff --git a/docs/HELP.md b/docs/HELP.md index 7771974b..27643ec5 100644 --- a/docs/HELP.md +++ b/docs/HELP.md @@ -80,6 +80,8 @@ The button's color tells you where you stand: **red** means something changed si Smart Citizen also stamps a small watermark onto the launcher version string (`Frontend_PU_Version`), appending `\nLocalizations Enhanced with Smart Citizen v{VERSION}` on its own line. That's how you can confirm in-game that your loc-pack is active — look at the version label on the Star Citizen main menu. The stamp is rewritten on each apply, so it never piles up across versions. +Apply also adds a second line to the main menu's **Play Star Citizen** button (`Frontend_play_star_citizen`), `Run Smart Citizen after every patch`, with both lines centered. A game patch leaves the applied `global.ini` in place, but the keys the patch added show as raw `@key` names until you run Smart Citizen and apply again, so the reminder is on the menu the first time the game starts after a patch. Like the stamp, it is rewritten on each apply, and it stays in English whatever language you play in. + ## 8. Restore a Backup Open the **More** menu on the toolbar and choose **Restore Backup** to revert to a previous version. Smart Citizen keeps up to **5 automatic backups** — the oldest is pruned as new ones are created. @@ -166,11 +168,11 @@ Track which crafting blueprints you already own, and see it reflected in-game: o ## Overlay Tab -The **Smart Citizen Overlay** draws two small windows over Star Citizen: a mining scan decoder and a drawer of searches. Start and stop it with **Start Overlay** on this tab or the toolbar's **Overlay** button. Run the game in borderless windowed mode on your main screen, or the overlay can't show on top of it. The overlay only reads your screen and `Game.log` and, if you set a drawer hotkey, watches key presses for that one combination; it never touches the game itself. +The **Smart Citizen Overlay** draws two small windows over Star Citizen: a mining scan decoder and a drawer of searches. Start and stop it with **Start Overlay** on this tab or the toolbar's **Overlay** button. Run the game in borderless windowed mode on your main screen, or the overlay can't show on top of it. The overlay only reads your screen and `Game.log`, asks Windows which window is in front and whether the mouse pointer shows (so your shots pass through the drawer while you aim) and, if you set a drawer hotkey, whether its key and the Ctrl, Alt, Shift and Win keys are down; it never touches the game itself. - **Mining scan decoder** reads the scan signature under your radar and shows the deposit type and count just below it (for example `3 × Lindinium`). The label only changes after the same number is read twice in a row, so a one-frame misread doesn't flash. **Scan text size** makes the label smaller or bigger. A round number such as 12,000 can be salvage or a surface deposit (ROC or FPS mining); salvage is listed first and the others are marked surface only, because in space salvage is the only one it can be. - **When a watched mineral or salvage is scanned**: pick how the label tells you. **Glow** and **Flash** are on by default; **Change text color** (bright green), **Bigger text** and **Play a sound** can be added. The flash and the sound come when the target is first read, not again while it stays on screen. With **Play a sound** on, **Alert sound** picks the sound: **Smart Citizen Default** (a short chime), a spoken voice (US, UK, Australian, Irish or Nigerian English) or one of the Windows sounds, and **Preview** plays it. A Windows sound follows your Windows sound scheme, so one set to (None) there stays silent. -- **Overlay drawer** puts tabbed sections at the edge of the screen. Click a tab to open its section, click it again to close. **Drawer position** picks one of eight spots (middle right by default). **Drawer hotkey** sets a key combination that opens the drawer from the game on the section you used last, and pressing it again closes it. In game you still hold F to use the mouse in it, because Windows does not let the overlay take the mouse from Star Citizen. Star Citizen still gets those keys, so pick a combination you don't use in game. It needs Ctrl, Alt or Win, unless it is an F key or Pause. **Clear** removes it. If another program already has it, the tab says so. +- **Overlay drawer** puts tabbed sections at the edge of the screen. Click a tab to open its section, click it again to close. **Drawer position** picks one of eight spots (middle right by default). **Drawer hotkey** sets a key combination that opens the drawer from the game on the section you used last, and pressing it again closes it. In game you still hold F to use the mouse in it, because Windows does not let the overlay take the mouse from Star Citizen. Star Citizen still gets those keys, so pick a combination you don't use in game. In game, hold the keys for a moment: a very quick press, such as a Stream Deck button with no hold time, can be missed. If Star Citizen runs as administrator, Smart Citizen has to as well, or the hotkey does nothing in game. It needs Ctrl, Alt or Win, unless it is an F key or Pause. **Clear** removes it. If another program already has it, the tab says so. - **Blueprints**: search blueprints, see which missions reward them, and tick the ones you own (same owned list as the Blueprint Tracker tab). - **Minerals**: type a mineral to see where it is found, grouped by star system, or a location to see its minerals. Tick a mineral, or **Salvage** at the bottom of the list, to watch for it: the scan label alerts you when a scan finds it. The decoder can be switched on and off here too. - **Crafting**: type a mineral to see which items use it, or an item to see the minerals it needs. Filled when you generate enhancements with **Commodities** or **Journal** ticked. diff --git a/docs/LEGAL.md b/docs/LEGAL.md index c3cf00d0..cc3117f4 100644 --- a/docs/LEGAL.md +++ b/docs/LEGAL.md @@ -48,6 +48,17 @@ Smart Citizen makes outbound network requests in only four circumstances: - **User-configured remote sources** — If you have configured a data source pointing at an `http(s)://` URL in the Config tab, Smart Citizen fetches that URL when refreshing source files. Out of the box this only applies to the `global` source's GitHub-raw URL form; the standard configuration since v1.0 reads `base.ini` from your local Data.p4k extraction instead. - **SCO Item Finder shop list** — While the overlay runs with its Item Finder section switched on, Smart Citizen downloads the list of shops and item prices from the [UEX](https://uexcorp.space) API (`api.uexcorp.uk`), at most once every 12 hours. It is two plain requests that carry only the app's name and version; nothing from your machine is sent. The list is cached locally. Switch the Item Finder off on the Overlay tab to stop it. +### The Smart Citizen Overlay + +The overlay is off until you start it. While it runs, everything it reads stays on your computer: + +- **Screen** — it captures a small area around the mining scanner's readout to read the signal number. Captures are read in memory and not saved. +- **Game.log** — it reads Star Citizen's log to find blueprints you receive. +- **Windows** — it asks Windows which window is in front and whether the mouse pointer shows, so the drawer lets your clicks through to the game while you aim. +- **Drawer hotkey** — only if you set one. While Star Citizen is in front, it asks Windows whether the hotkey's key is down, and the Ctrl, Alt, Shift and Win keys only when it is. It asks about no other key and never receives what you type. + +It never reads the game's memory, never hooks or injects into the game, and never sends input to it. + ### What Smart Citizen does **not** do - No telemetry, analytics, or usage reporting of any kind. diff --git a/docs/LINUX.md b/docs/LINUX.md index c08e6ad4..1a0b769a 100644 --- a/docs/LINUX.md +++ b/docs/LINUX.md @@ -4,6 +4,15 @@ This guide explains how to run Smart Citizen on Linux through the same Wine pref > Originally contributed by [@PinkFloyd1213](https://github.com/PinkFloyd1213) in [issue #33](https://github.com/Osiris-DevWorks/smart-citizen/issues/33#issuecomment-4460305053). +> [!IMPORTANT] +> **The Smart Citizen Overlay needs an X11 session, not Wayland.** It does not work on Wayland. If you want the overlay to work: +> +> 1. Log out of your desktop. +> 2. On the login screen, pick your user, then use the session menu (often a gear icon) to choose the **X11** or **Xorg** session (for example "Plasma (X11)" or "GNOME on Xorg"). +> 3. Log in and run Star Citizen and Smart Citizen as usual. +> +> To check which one you're on, run `echo $XDG_SESSION_TYPE` in a terminal: it prints `x11` or `wayland`. The rest of Smart Citizen works on either. + ## Prerequisites You need a working Star Citizen installation on Linux before installing Smart Citizen. If you haven't set that up yet, we strongly recommend the **[Star Citizen LUG](https://wiki.starcitizen-lug.org/)** community — they maintain scripts (notably the LUG-Helper) and have an active community that makes running SC on Linux relatively painless. @@ -79,8 +88,8 @@ Smart Citizen should now launch. From there, usage is identical to the Windows v ## Troubleshooting -**Don't run Star Citizen and Smart Citizen at the same time:** -Smart Citizen modifies the game's files (translations, etc.) and is not meant to run alongside the game — once your changes are applied, you can close it before launching Star Citizen. On top of that, running two applications concurrently inside the same Wine prefix tends to cause conflicts. Always run one *or* the other, never both at once. +**Apply your changes with Star Citizen closed:** +Smart Citizen changes the game's files (translations, etc.), so apply your changes before you launch Star Citizen, not while it's running. The **Smart Citizen Overlay** is the exception: it's meant to run alongside the game, so keep Smart Citizen open while you play if you use it (on an X11 session, see the note at the top of this guide). If you don't use the overlay, you can close Smart Citizen once your changes are applied. Running two apps in the same Wine prefix can sometimes cause conflicts, so if either one misbehaves while both are open, close Smart Citizen. **Smart Citizen doesn't detect the Star Citizen installation:** This should be auto-detected since both apps share the same Wine prefix. If it isn't, point Smart Citizen manually to the Star Citizen install folder inside the prefix (typically `/drive_c/Program Files/Roberts Space Industries/StarCitizen/`). diff --git a/languages/TRANSLATIONS.md b/languages/TRANSLATIONS.md index dc45501e..5d6822e1 100644 --- a/languages/TRANSLATIONS.md +++ b/languages/TRANSLATIONS.md @@ -82,6 +82,65 @@ them against the new source. ## Backfill log +- **3.0.1 cycle (2026-11-17, Claude Opus 5.5):** pre-release, the Legal + tab's privacy section gained a "The Smart Citizen Overlay" subsection + (`docs/LEGAL.md`, before "What Smart Citizen does not do"): what the overlay + reads (a screen area around the scanner readout, Game.log), what it asks + Windows (the window in front, whether the pointer shows, and with a drawer + hotkey set its key and the modifier keys while Star Citizen is in front), + and what it never does. AI-written in all 11 translated `LEGAL.md` files, + with each `ui.json`'s names for the overlay, drawer and hotkey and the + modifier key names the #587 entry lists. No `ht` exists for LEGAL. Not + back-translated. +- **3.0.1 cycle (2026-11-17, Claude Opus 5.5):** #587, the drawer hotkey no + longer takes the keyboard's raw input: while Star Citizen is in front the + overlay asks Windows whether the hotkey's key and the modifier keys are + down. One English text changed, `overlay.desc` (with a drawer hotkey set, + the overlay asks whether its key and the Ctrl, Alt, Shift and Win keys are + down, where it said it watches key presses for that one combination), and + the overlay paragraph in `docs/HELP.md` and the overlay bullet in + `README.md` say the same. In `docs/FAQ.md` the privacy paragraph's two + sentences on raw input became two on the key check: the combination's key, + and the modifier keys only while it is down, no other key, and nothing + typed in the game or another program sent to the app. HELP's drawer hotkey + bullet gained two sentences: hold the keys a moment in game (a very quick + press can be missed), and run Smart Citizen as administrator when Star + Citizen runs that way. AI `at` in all 11 other languages. None had an `ht` + on `overlay.desc`, so nothing needs human re-review. The 11 translated + `HELP.md` and `FAQ.md` files gained the same words, naming the modifier + keys as each `ui.json` does (Strg and Umschalt in German, Maj in French, + Maiusc in Italian, Mayús in Spanish, Shift elsewhere), and + chinese_traditional's through OpenCC s2twp from chinese, keeping its + files' 快速鍵 for the hotkey where s2twp gives 熱鍵. Checked by a script: each + old text matched once and every line ending was kept. Not back-translated. +- **3.0.1 cycle (2026-11-17, Claude Opus 5.5):** #582, the overlay drawer + now lets clicks pass through to the game while the player aims (a player + lost the game's focus that way, 2026-11-16), and for it the overlay asks + Windows which window is in front and whether the mouse pointer shows. One English + text changed, `overlay.desc` (the overlay only reads the screen and + Game.log, asks Windows those two things and, with a drawer hotkey set, + watches key presses for that one combination), and the overlay paragraph + in `docs/HELP.md` and `docs/FAQ.md` and the overlay bullet in + `docs/ABOUT.md` say the same. AI `at` in all 11 other languages. None had + an `ht` on `overlay.desc`, so nothing needs human re-review. The 11 + translated copies of the three docs gained the same words, with each + `ui.json`'s own names for the overlay, the drawer and the hotkey. Checked + by a script: each old text matched once and every line ending was kept. + Not back-translated. +- **3.0.1 cycle (2026-11-13, Claude Opus 5.5):** #566, the Play button + reminder. HELP section 7 gains a paragraph after the watermark one in all + eleven translated `HELP.md` files, AI-translated: Apply also adds + `Run Smart Citizen after every patch` as a second line on the main menu's + Play button, because a patch leaves the applied `global.ini` without the + keys it added. The reminder and the `Frontend_play_star_citizen` key stay + in English, since the game shows the reminder in English in every + language, as it does the watermark. Each file's own words for patch, apply + and the watermark. Checked by a script against English: every paragraph + keeps the key, the reminder, `global.ini` and `@key` as code, runs 1.05 to + 1.16 times the English length (0.47 to 0.64 in chinese, + chinese_traditional, japanese and korean), and the korean has no sentence + end run straight into the next syllable. Not back-translated. No + `ui.json` changed. - **3.0.0 cycle (2026-10-30, Claude Opus 5.5, pre-release language check):** two gaps filled. (1) New key `enhancements.blueprints_default_owned_mission`, the starter blueprints' mission label ("Default blueprint (every player has @@ -390,6 +449,18 @@ them against the new source. cihazından" (the pack uses "üretici" for a manufacturer) and "mevcut listeye", and italian says "la loro ricezione" instead of "di averli ricevuti", which made the game the receiver. +- **3.0.1 cycle (2026-11-04, Claude Opus 5.5):** the guided tour caught up + with 3.0.0. `tutorial.enh_categories`, `tutorial.cfg_appearance` and + `tutorial.cfg_tools` were reworded in `assets/tutorial.json` (the category + names as the checkboxes show them, which stay English; the font size; Restore + user.ini, Preview Apply and Check for Updates), and two steps were added + after Tools: `tutorial.cfg_backup` (Export / Import Settings) and + `tutorial.cfg_sc_tools` (Clear Shader Cache). The tour is now 21 steps, so + every title from 19 on was renumbered. AI `at` written or refreshed in all + eleven languages, none of which has a human `ht` for these keys; each + keeps its file's own words for the theme names, the font sizes and + overrides, and the new titles are built from its `config.backup_group` and + `config.sc_tools_group`. - **3.0.0 cycle (2026-10-15, Claude Opus 5.5):** #492 added `enhancements.tag_mapping_tooltip_weight` (the Edit mapping tooltip on the Tag Builder's Armor > Weight row) and reworded `enhancements.cat_desc_gear`. diff --git a/languages/chinese/ABOUT.md b/languages/chinese/ABOUT.md index e6e3e4ef..8e61c213 100644 --- a/languages/chinese/ABOUT.md +++ b/languages/chinese/ABOUT.md @@ -29,6 +29,7 @@ - **scubamount** - **hkstrongside** - **odw-okano** +- **RWolfyo** ## 翻译者 @@ -113,7 +114,7 @@ - **任务标题**:以路线开头显示货运任务标题(例如 `Area18 > Lorville`)——可自定义位置、箭头、分隔符和地点详情,并可选缩短官方标题,带实时预览 - **数据统计置于上方或下方**:选择数据统计块位于描述的顶部还是底部 - **蓝图追踪器**:专门用于标记你已拥有的制作蓝图的标签页。在“可用”与“已拥有”之间移动物品,按任务/类型/等级/尺寸/品级筛选,已拥有物品会在任务蓝图列表中获得蓝色 `[已拥有]` 标签。**扫描日志以查找已拥有蓝图** 会根据你的《星际公民》日志文件自动填充已拥有状态,只导入自上次扫描以来的新内容(开启 **启动时自动扫描日志** 后也会在启动时自动进行),**导出/导入已拥有蓝图** 则可在不同电脑之间转移已拥有列表(JSON 或 CSV;导入只会添加内容,scmdb.net 的导出文件同样适用) -- **Smart Citizen 叠加层**:覆盖在游戏上方的可选窗口(无边框窗口模式)。采矿扫描解码器会显示信号背后的矿藏(`3 × Lindinium`),并可在发现你关注的矿物或打捞物时发光、闪烁或发出提示音;抽屉(可用自己的热键开关)可搜索你的蓝图、矿物的产地以及它们能制造什么;叠加层运行期间,你获得的蓝图会根据 `Game.log` 标记为已拥有。仅读取屏幕像素和 `Game.log`,外加可选的热键:不注入、不读取内存、不发送输入 +- **Smart Citizen 叠加层**:覆盖在游戏上方的可选窗口(无边框窗口模式)。采矿扫描解码器会显示信号背后的矿藏(`3 × Lindinium`),并可在发现你关注的矿物或打捞物时发光、闪烁或发出提示音;抽屉(可用自己的热键开关)可搜索你的蓝图、矿物的产地以及它们能制造什么;叠加层运行期间,你获得的蓝图会根据 `Game.log` 标记为已拥有。仅读取屏幕像素、`Game.log`、哪个窗口在最前面以及指针是否显示,外加可选的热键:不注入、不读取内存、不发送输入 - **任务标签**:重命名区块标题(任务详情、潜在蓝图等)、经验标签,以及用于标题的强调标签 - **声明式 CIG 数据错误补丁**:一个补丁系统会在提取时应用对已知 DataForge 错误的修正,让游戏内文本正确显示,无需等待 CIG 修复 - **分类可选**:在增强内容标签页中独立启用或禁用每个增强内容分类 diff --git a/languages/chinese/FAQ.md b/languages/chinese/FAQ.md index a88ffeb5..c17010e8 100644 --- a/languages/chinese/FAQ.md +++ b/languages/chinese/FAQ.md @@ -15,7 +15,7 @@ 智慧公民只编辑本地化文本(游戏显示给你看的文字),不涉及游戏逻辑,不提供任何优势,也不与 CIG 的服务器通信。我们的修改**应该**是安全的。 -可选的 **Smart Citizen 叠加层**(叠加层标签页)同样以不干预游戏的方式工作。它在游戏上方绘制普通窗口,像截图工具一样读取屏幕像素,并读取游戏的 `Game.log` 文件。它从不注入或挂钩游戏,从不打开游戏进程或读取其内存,也从不发送键盘或鼠标输入。如果你设置了抽屉热键,它会以程序申请热键的标准方式向 Windows 注册这一个组合键。Star Citizen 在拥有焦点时会挡住其他程序已注册的热键,所以设置了热键时,叠加层还会接收键盘的原始输入,这是 Windows 告知后台程序按键情况的只读方式。这不是键盘钩子:它不拦截、不更改、不发送任何按键,不做任何记录,只响应你的组合键。CIG 尚未就此类叠加层发表过任何说法,因此下文同样的“风险自负”说明也适用于它。 +可选的 **Smart Citizen 叠加层**(叠加层标签页)同样以不干预游戏的方式工作。它在游戏上方绘制普通窗口,像截图工具一样读取屏幕像素,并读取游戏的 `Game.log` 文件。抽屉显示时,它还会询问 Windows 哪个窗口在最前面以及鼠标指针是否显示,这样你瞄准时,射击会穿过抽屉。它从不注入或挂钩游戏,从不打开游戏进程或读取其内存,也从不发送键盘或鼠标输入。如果你设置了抽屉热键,它会以程序申请热键的标准方式向 Windows 注册这一个组合键。Star Citizen 在拥有焦点时会挡住其他程序已注册的热键,所以游戏在最前面时,叠加层还会询问 Windows 这个组合键的主键是否被按下,并且只在它被按下时才询问 Ctrl、Alt、Shift 或 Win 是否被按住。它从不询问其他任何按键,从不接收你在游戏或其他程序中输入的内容,也从不拦截、更改或发送任何按键。CIG 尚未就此类叠加层发表过任何说法,因此下文同样的“风险自负”说明也适用于它。 CIG 曾公开支持社区本地化。他们发布的[社区本地化更新](https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/star-citizen-community-localization-update)帖子明确表示官方支持玩家制作的翻译,我们理解这明确允许了智慧公民所做的这类本地化编辑。 diff --git a/languages/chinese/HELP.md b/languages/chinese/HELP.md index a71aefe7..f8a74959 100644 --- a/languages/chinese/HELP.md +++ b/languages/chinese/HELP.md @@ -80,6 +80,8 @@ 智慧公民还会在启动器版本字符串(`Frontend_PU_Version`)上打上一个小水印,在单独一行追加 `\nLocalizations Enhanced with Smart Citizen v{VERSION}`。这样你就可以在游戏内确认你的本地化包正在生效——查看《星际公民》主菜单上的版本标签。每次应用都会重新写入该水印,因此它不会在不同版本之间不断堆积。 +应用时,智慧公民还会在主菜单的“开始游戏”按钮(`Frontend_play_star_citizen`)上加上第二行 `Run Smart Citizen after every patch`,并让两行居中对齐。游戏补丁会保留已应用的 `global.ini`,但补丁新增的键在你运行智慧公民并重新应用之前,会显示为原始的 `@key` 名称,因此补丁后第一次启动游戏时,这条提醒就已经在菜单上了。与水印一样,它在每次应用时都会重新写入,并且无论选择哪种语言都保持英文。 + ## 8. 恢复备份 打开工具栏上的 **更多** 菜单,选择 **恢复备份** 即可回退到之前的版本。智慧公民最多保留 **5 个自动备份**——创建新备份时会清除最旧的一个。 @@ -166,11 +168,11 @@ ## 叠加层标签页 -**Smart Citizen 叠加层** 会在《星际公民》上方绘制两个小窗口:一个采矿扫描解码器和一个搜索抽屉。可在此标签页点击 **启动叠加层**,或使用工具栏的 **叠加层** 按钮来启动和停止它。请在主屏幕上以无边框窗口模式运行游戏,否则叠加层无法显示在游戏上方。叠加层只读取你的屏幕和 `Game.log`,并在你设置了抽屉热键时只为这一个组合键留意按键,从不接触游戏本身。 +**Smart Citizen 叠加层** 会在《星际公民》上方绘制两个小窗口:一个采矿扫描解码器和一个搜索抽屉。可在此标签页点击 **启动叠加层**,或使用工具栏的 **叠加层** 按钮来启动和停止它。请在主屏幕上以无边框窗口模式运行游戏,否则叠加层无法显示在游戏上方。叠加层只读取你的屏幕和 `Game.log`,询问 Windows 哪个窗口在最前面以及鼠标指针是否显示(这样你瞄准时,射击会穿过抽屉),并在你设置了抽屉热键时还询问它的按键以及 Ctrl、Alt、Shift、Win 键是否被按下,从不接触游戏本身。 - **采矿扫描解码器** 会读取雷达下方的扫描信号,并在其正下方显示矿藏类型和数量(例如 `3 × Lindinium`)。只有连续两次读到相同的数字后,标签才会更新,因此单帧误读不会造成闪烁。**扫描文字大小** 可以把标签调小或调大。像 12,000 这样的整数既可能是打捞物,也可能是地表矿藏(ROC 或 FPS 采矿);打捞物会列在第一行,其他的标为仅地表,因为在太空中只可能是打捞物。 - **扫描到关注的矿物或打捞物时**:选择标签提醒你的方式。**发光** 和 **闪烁** 默认开启;还可以加上 **更改文字颜色**(亮绿色)、**放大文字** 和 **播放提示音**。闪烁和提示音只在首次读到目标时出现,目标停留在屏幕上时不会重复。开启 **播放提示音** 后,可在 **提醒声音** 中选择声音:**Smart Citizen 默认**(一声短促的提示音)、一段英语语音(美国、英国、澳大利亚、爱尔兰或尼日利亚口音)或某个 Windows 声音,按 **试听** 即可播放。Windows 声音跟随你的 Windows 声音方案,在那里设为(无)的声音不会响。 -- **叠加层抽屉** 会在屏幕边缘放置带标签的分区。点击某个标签可打开其分区,再次点击则关闭。**抽屉位置** 可从八个位置中选择一个(默认为右侧中间)。**抽屉热键** 设置一个组合键,可在游戏中打开抽屉并停在你上次使用的分区,再按一次即可关闭。在游戏中仍需按住 F 才能用鼠标操作它,因为 Windows 不允许叠加层从 Star Citizen 手中接管鼠标。Star Citizen 仍会收到这些按键,所以请选一个游戏中不用的组合键。除 F 键和 Pause 外,组合键里需要有 Ctrl、Alt 或 Win。**清除** 可移除热键。如果其他程序已占用它,此标签页会提示。 +- **叠加层抽屉** 会在屏幕边缘放置带标签的分区。点击某个标签可打开其分区,再次点击则关闭。**抽屉位置** 可从八个位置中选择一个(默认为右侧中间)。**抽屉热键** 设置一个组合键,可在游戏中打开抽屉并停在你上次使用的分区,再按一次即可关闭。在游戏中仍需按住 F 才能用鼠标操作它,因为 Windows 不允许叠加层从 Star Citizen 手中接管鼠标。Star Citizen 仍会收到这些按键,所以请选一个游戏中不用的组合键。在游戏中请按住按键片刻:极短的按键,比如没有设置按住时间的 Stream Deck 按钮,可能会被漏掉。如果 Star Citizen 以管理员身份运行,Smart Citizen 也必须以管理员身份运行,否则该热键在游戏中不起作用。除 F 键和 Pause 外,组合键里需要有 Ctrl、Alt 或 Win。**清除** 可移除热键。如果其他程序已占用它,此标签页会提示。 - **蓝图**:搜索蓝图,查看哪些任务会奖励它们,并勾选你已拥有的蓝图(与蓝图追踪器标签页使用同一份已拥有列表)。 - **矿物**:输入一种矿物可查看它的产地(按星系分组),输入一个地点则可查看该地的矿物。勾选某种矿物,或列表底部的 **打捞**,即可关注它:扫描发现它时,扫描标签会提醒你。也可以在这里开关解码器。 - **制造**:输入一种矿物可查看哪些物品使用它,输入一个物品则可查看它需要哪些矿物。在勾选 **Commodities** 或 **Journal** 的情况下生成增强内容后,此分区才会有内容。 diff --git a/languages/chinese/LEGAL.md b/languages/chinese/LEGAL.md index 5ba27f4c..2d19b7e7 100644 --- a/languages/chinese/LEGAL.md +++ b/languages/chinese/LEGAL.md @@ -48,6 +48,17 @@ - **用户自定义的远程来源** —— 如果你在配置标签页中配置了指向 `http(s)://` 地址的数据来源,智慧公民会在刷新源文件时获取该地址。默认情况下,这仅适用于 `global` 来源的 GitHub-raw 地址形式;自 v1.0 起,标准配置改为从你本地的 Data.p4k 提取内容中读取 `base.ini`。 - **SCO 物品查找商店列表** — 在开启物品查找分区并运行覆盖层时,Smart Citizen 会从 [UEX](https://uexcorp.space) 的 API(`api.uexcorp.uk`)下载商店和物品价格列表,最多每 12 小时一次。这只是两个仅携带应用名称和版本的简单请求,不会发送你电脑上的任何内容。列表会缓存在本地。在覆盖层标签页关闭物品查找即可停止。 +### 智慧公民叠加层 + +叠加层在你启动它之前一直处于关闭状态。运行时,它读取的所有内容都留在你的电脑上: + +- **屏幕** — 它截取采矿扫描仪读数周围的一小块区域,用来读取信号数值。截图只在内存中读取,不会保存。 +- **Game.log** — 它读取 Star Citizen 的日志,以找到你获得的蓝图。 +- **Windows** — 它询问 Windows 哪个窗口在最前面以及鼠标指针是否显示,以便你瞄准时抽屉让点击穿透到游戏。 +- **抽屉热键** — 仅在你设置了热键时。当 Star Citizen 在最前面时,它询问 Windows 热键的按键是否被按下,只有在按下时才询问 Ctrl、Alt、Shift 和 Win 键。它不询问任何其他按键,也从不接收你输入的内容。 + +它从不读取游戏内存,从不挂钩或注入游戏,也从不向游戏发送输入。 + ### 智慧公民**不会**做的事 - 不进行任何形式的遥测、分析或使用情况报告。 diff --git a/languages/chinese/ui.json b/languages/chinese/ui.json index 8ca449c8..d4b6ddf9 100644 --- a/languages/chinese/ui.json +++ b/languages/chinese/ui.json @@ -2992,6 +2992,14 @@ "ht": "", "at": "Smart Citizen 无法在以下位置使用工作文件夹:\n{folder}\n\n{reason}\n\n提取未开始,因此未做任何更改。" }, + "contract_scan_failed": { + "ht": "", + "at": "增强内容生成已停止,因为 {total} 份任务合约中有 {skipped} 份无法读取。你现有的增强内容保持不变。请报告此问题,这通常是 Smart Citizen 的错误。\n\n第一份合约:\n{first}" + }, + "contract_scan_stopped": { + "ht": "", + "at": "增强内容生成已停止,因为任务合约扫描因错误而中断。你现有的增强内容保持不变。请报告此问题,这通常是 Smart Citizen 的错误。\n\n错误:\n{first}" + }, "cache_folder_refused": { "ht": "", "at": "Windows 拒绝了 Smart Citizen 在以下位置创建 DataForge 缓存的权限:\n{folder}\n\n提取未开始,因此未做任何更改。" @@ -3123,7 +3131,7 @@ }, "description": { "ht": "", - "at": "切换生成时运行的增强内容分类。飞船、组件、飞船武器、FPS 武器、任务、任务奖励、商品制作和医疗消耗品均可独立启用。" + "at": "选择点击生成时运行哪些增强类别:Ships, Ship Items, Gear, Missions, Commodities, Journal, Medical Consumables。Ship Items 包含组件、舰船武器和导弹;Gear 包含 FPS 武器和护甲标签。每个类别都可以单独开启或关闭。" } }, "enh_favorites": { @@ -3156,24 +3164,24 @@ "at": "构建添加到组件、导弹、飞船武器、商品和护甲上的括号名称标签。用 ▲/▼ 重新排序元素,取消勾选可排除,更改缩写长度,选择分隔符和括号,或将标签放在名称之后而不是之前。" } }, - "overlay": { + "blueprint_tracker": { "title": { "ht": "", - "at": "8. Smart Citizen 叠加层" + "at": "7. 蓝图追踪器" }, "description": { "ht": "", - "at": "在这里或用工具栏的“叠加层”按钮启动叠加层。它在游戏上方解码采矿扫描信号,打开一个抽屉来搜索你的蓝图、矿物和制作,并把你获得的蓝图标记为已拥有。请在主屏幕上以无边框窗口模式运行游戏。" + "at": "标记你拥有的蓝图。可按名称或任务搜索左侧列表,或按组件类型、等级、尺寸和品级缩小范围,然后用箭头将物品移动到你的已拥有列表。已拥有的蓝图在任务的潜在奖励中出现时会带有 [Owned] 标签,让你一眼就能看出哪些值得追求。" } }, - "blueprint_tracker": { + "overlay": { "title": { "ht": "", - "at": "7. 蓝图追踪器" + "at": "8. Smart Citizen 叠加层" }, "description": { "ht": "", - "at": "标记你拥有的蓝图。可按名称或任务搜索左侧列表,或按组件类型、等级、尺寸和品级缩小范围,然后用箭头将物品移动到你的已拥有列表。已拥有的蓝图在任务的潜在奖励中出现时会带有 [Owned] 标签,让你一眼就能看出哪些值得追求。" + "at": "在这里或用工具栏的“叠加层”按钮启动叠加层。它在游戏上方解码采矿扫描信号,打开一个抽屉来搜索你的蓝图、矿物和制作,并把你获得的蓝图标记为已拥有。请在主屏幕上以无边框窗口模式运行游戏。" } }, "edit": { @@ -3233,7 +3241,7 @@ }, "description": { "ht": "", - "at": "选择应用主题(默认 / 浅色 / 深色 / ODW),并可选择禁用新版本的自动教程。" + "at": "选择应用主题(默认 / 浅色 / 深色 / ODW)和字体大小(小 / 中 / 大,重启后生效),并可选择在新版本时关闭自动教程。" } }, "cfg_sc_install": { @@ -3273,13 +3281,33 @@ }, "description": { "ht": "", - "at": "通过冲突解决对话框将外部 INI 导入到你的覆盖项中,或重置当前频道的 user.ini(清除前会自动备份)。" + "at": "通过冲突处理对话框将外部 INI 导入你的覆盖项。重置当前频道的 user.ini(会先备份),或用“恢复 user.ini”找回之前的副本。预览会显示“应用”将写入的内容,“检查更新”会查找新版本。" + } + }, + "cfg_backup": { + "title": { + "ht": "", + "at": "19. 配置:设置备份" + }, + "description": { + "ht": "", + "at": "“导出设置”会把你的偏好、标签配置、Star Citizen 文件夹和所有频道的自定义字符串保存到一个文件中。“导入设置”可在新电脑上或全新安装后恢复它们。" + } + }, + "cfg_sc_tools": { + "title": { + "ht": "", + "at": "20. 配置:Star Citizen 工具" + }, + "description": { + "ht": "", + "at": "“清除着色器缓存”会列出游戏的着色器缓存文件夹,每个游戏版本一个。“清理”删除着色器并保留你的图形设置;“移除”删除整个文件夹。请先关闭 Star Citizen。" } }, "help": { "title": { "ht": "", - "at": "19. 帮助与反馈" + "at": "21. 帮助与反馈" }, "description": { "ht": "", @@ -3590,7 +3618,7 @@ }, "desc": { "ht": "", - "at": "显示在 Star Citizen 之上的窗口:采矿扫描解码器和蓝图抽屉。请以无边框窗口模式运行游戏。叠加层只读取屏幕和 Game.log,并在你设置了抽屉热键时只为这一个组合键留意按键,从不接触游戏进程。" + "at": "显示在 Star Citizen 之上的窗口:采矿扫描解码器和蓝图抽屉。请以无边框窗口模式运行游戏。叠加层只读取屏幕和 Game.log,询问 Windows 哪个窗口在最前面以及指针是否显示,并在你设置了抽屉热键时还询问它的按键以及 Ctrl、Alt、Shift、Win 键是否被按下,从不接触游戏进程。" }, "start_btn": { "ht": "", diff --git a/languages/chinese_traditional/ABOUT.md b/languages/chinese_traditional/ABOUT.md index 0fe07a2f..c0db98ed 100644 --- a/languages/chinese_traditional/ABOUT.md +++ b/languages/chinese_traditional/ABOUT.md @@ -29,6 +29,7 @@ - **scubamount** - **hkstrongside** - **odw-okano** +- **RWolfyo** ## 翻譯者 @@ -113,7 +114,7 @@ - **任務標題**:以路線開頭顯示貨運任務標題(例如 `Area18 > Lorville`)——可自定義位置、箭頭、分隔符和地點詳情,並可選縮短官方標題,帶實時預覽 - **資料統計置於上方或下方**:選擇資料統計塊位於描述的頂部還是底部 - **藍圖追蹤器**:專門用於標記你已擁有的製作藍圖的標籤頁。在“可用”與“已擁有”之間移動物品,按任務/型別/等級/尺寸/品級篩選,已擁有物品會在任務藍圖列表中獲得藍色 `[已擁有]` 標籤。**掃描日誌以查詢已擁有藍圖** 會根據你的《星際公民》日誌檔案自動填充已擁有狀態,只匯入自上次掃描以來的新內容(開啟 **啟動時自動掃描日誌** 後也會在啟動時自動進行),**匯出/匯入已擁有藍圖** 則可在不同電腦之間轉移已擁有列表(JSON 或 CSV;匯入只會新增內容,scmdb.net 的匯出檔案同樣適用) -- **Smart Citizen 疊加層**:顯示在遊戲上方的可選視窗(無邊框視窗模式)。採礦掃描解碼器會顯示訊號背後的礦藏(`3 × Lindinium`),並可在出現你關注的礦物或打撈物時發光、閃爍或發出提示音;抽屜(可用自己的快速鍵開關)可搜尋你的藍圖、礦物的產地以及它們可製造的物品;疊加層執行期間,你獲得的藍圖會根據 `Game.log` 標記為已擁有。僅讀取螢幕畫素和 `Game.log`,外加可選的快速鍵:不注入、不讀取記憶體、不模擬輸入 +- **Smart Citizen 疊加層**:顯示在遊戲上方的可選視窗(無邊框視窗模式)。採礦掃描解碼器會顯示訊號背後的礦藏(`3 × Lindinium`),並可在出現你關注的礦物或打撈物時發光、閃爍或發出提示音;抽屜(可用自己的快速鍵開關)可搜尋你的藍圖、礦物的產地以及它們可製造的物品;疊加層執行期間,你獲得的藍圖會根據 `Game.log` 標記為已擁有。僅讀取螢幕畫素、`Game.log`、哪個視窗在最前面以及指標是否顯示,外加可選的快速鍵:不注入、不讀取記憶體、不模擬輸入 - **任務標籤**:重新命名區塊標題(任務詳情、潛在藍圖等)、經驗標籤,以及用於標題的強調標籤 - **宣告式 CIG 資料錯誤補丁**:一個補丁系統會在提取時應用對已知 DataForge 錯誤的修正,讓遊戲內文字正確顯示,無需等待 CIG 修復 - **分類可選**:在增強內容標籤頁中獨立啟用或禁用每個增強內容分類 diff --git a/languages/chinese_traditional/FAQ.md b/languages/chinese_traditional/FAQ.md index eee4311e..6ce4d00d 100644 --- a/languages/chinese_traditional/FAQ.md +++ b/languages/chinese_traditional/FAQ.md @@ -15,7 +15,7 @@ 智慧公民只編輯本地化文字(遊戲顯示給你看的文字),不涉及遊戲邏輯,不提供任何優勢,也不與 CIG 的伺服器通訊。我們的修改**應該**是安全的。 -可選的 **Smart Citizen 疊加層**(疊加層標籤頁)同樣以不干涉遊戲的方式運作。它在遊戲上方繪製普通視窗,像截圖工具一樣從你的螢幕讀取畫素,並讀取遊戲的 `Game.log` 檔案。它從不注入或掛鉤遊戲,從不開啟遊戲程序或讀取其記憶體,也從不傳送鍵盤或滑鼠輸入。如果你設定了抽屜快速鍵,它會以程式申請快速鍵的標準方式向 Windows 註冊這一個組合鍵。Star Citizen 在擁有焦點時會擋住其他程式已註冊的快速鍵,所以設定了快速鍵時,疊加層還會接收鍵盤的原始輸入,這是 Windows 告知背景程式按鍵情況的唯讀方式。這不是鍵盤掛鉤:它不攔截、不更改、不傳送任何按鍵,不做任何記錄,只回應你的組合鍵。CIG 尚未對此類疊加層發表任何看法,因此下文同樣的“風險自負”說明也適用。 +可選的 **Smart Citizen 疊加層**(疊加層標籤頁)同樣以不干涉遊戲的方式運作。它在遊戲上方繪製普通視窗,像截圖工具一樣從你的螢幕讀取畫素,並讀取遊戲的 `Game.log` 檔案。抽屜顯示時,它還會詢問 Windows 哪個視窗在最前面以及滑鼠指標是否顯示,這樣你瞄準時,射擊會穿過抽屜。它從不注入或掛鉤遊戲,從不開啟遊戲程序或讀取其記憶體,也從不傳送鍵盤或滑鼠輸入。如果你設定了抽屜快速鍵,它會以程式申請快速鍵的標準方式向 Windows 註冊這一個組合鍵。Star Citizen 在擁有焦點時會擋住其他程式已註冊的快速鍵,所以遊戲在最前面時,疊加層還會詢問 Windows 這個組合鍵的主鍵是否被按下,並且只在它被按下時才詢問 Ctrl、Alt、Shift 或 Win 是否被按住。它從不詢問其他任何按鍵,從不接收你在遊戲或其他程式中輸入的內容,也從不攔截、更改或傳送任何按鍵。CIG 尚未對此類疊加層發表任何看法,因此下文同樣的“風險自負”說明也適用。 CIG 曾公開支援社群本地化。他們釋出的[社群本地化更新](https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/star-citizen-community-localization-update)帖子明確表示官方支援玩家制作的翻譯,我們理解這明確允許了智慧公民所做的這類本地化編輯。 diff --git a/languages/chinese_traditional/HELP.md b/languages/chinese_traditional/HELP.md index 57ef279a..12ad3a96 100644 --- a/languages/chinese_traditional/HELP.md +++ b/languages/chinese_traditional/HELP.md @@ -80,6 +80,8 @@ 智慧公民還會在啟動器版本字串(`Frontend_PU_Version`)上打上一個小水印,在單獨一行追加 `\nLocalizations Enhanced with Smart Citizen v{VERSION}`。這樣你就可以在遊戲內確認你的本地化包正在生效——檢視《星際公民》主選單上的版本標籤。每次應用都會重新寫入該水印,因此它不會在不同版本之間不斷堆積。 +應用時,智慧公民還會在主選單的“開始遊戲”按鈕(`Frontend_play_star_citizen`)上加上第二行 `Run Smart Citizen after every patch`,並讓兩行置中對齊。遊戲補丁會保留已應用的 `global.ini`,但補丁新增的鍵在你執行智慧公民並重新應用之前,會顯示為原始的 `@key` 名稱,因此補丁後第一次啟動遊戲時,這條提醒就已經在選單上了。與水印一樣,它在每次應用時都會重新寫入,而且無論選擇哪種語言都維持英文。 + ## 8. 恢復備份 開啟工具欄上的 **更多** 選單,選擇 **恢復備份** 即可回退到之前的版本。智慧公民最多保留 **5 個自動備份**——建立新備份時會清除最舊的一個。 @@ -166,11 +168,11 @@ ## 疊加層標籤頁 -**Smart Citizen 疊加層** 會在《星際公民》上方繪製兩個小視窗:一個採礦掃描解碼器和一個搜尋抽屜。在此標籤頁點選 **啟動疊加層**,或點選工具欄上的 **疊加層** 按鈕,即可啟動或停止它。請在主螢幕上以無邊框視窗模式執行遊戲,否則疊加層無法顯示在遊戲上方。疊加層只讀取你的螢幕和 `Game.log`,並在你設定了抽屜快速鍵時只為這一個組合鍵留意按鍵,從不觸碰遊戲本身。 +**Smart Citizen 疊加層** 會在《星際公民》上方繪製兩個小視窗:一個採礦掃描解碼器和一個搜尋抽屜。在此標籤頁點選 **啟動疊加層**,或點選工具欄上的 **疊加層** 按鈕,即可啟動或停止它。請在主螢幕上以無邊框視窗模式執行遊戲,否則疊加層無法顯示在遊戲上方。疊加層只讀取你的螢幕和 `Game.log`,詢問 Windows 哪個視窗在最前面以及滑鼠指標是否顯示(這樣你瞄準時,射擊會穿過抽屜),並在你設定了抽屜快速鍵時還詢問它的按鍵以及 Ctrl、Alt、Shift、Win 鍵是否被按下,從不觸碰遊戲本身。 - **採礦掃描解碼器** 會讀取雷達下方的掃描訊號,並在其正下方顯示礦藏類型和數量(例如 `3 × Lindinium`)。只有連續兩次讀到相同的數字後標籤才會更新,因此單幀的誤讀不會造成閃爍。**掃描文字大小** 可以把標籤調小或調大。像 12,000 這樣的整數既可能是打撈物,也可能是地表礦藏(ROC 或 FPS 採礦);打撈物會列在第一行,其他的標為僅地表,因為在太空中只可能是打撈物。 - **掃描到關注的礦物或打撈物時**:選擇標籤提醒你的方式。**發光** 和 **閃爍** 預設開啟;還可以加上 **變更文字顏色**(亮綠色)、**放大文字** 和 **播放提示音**。閃爍和提示音只在首次讀到目標時出現,目標停留在螢幕上時不會重複。開啟 **播放提示音** 後,可在 **提醒聲音** 中選擇聲音:**Smart Citizen 預設**(一聲短促的提示音)、一段英語語音(美國、英國、澳洲、愛爾蘭或奈及利亞口音)或某個 Windows 聲音,按 **試聽** 即可播放。Windows 聲音跟隨你的 Windows 音效配置,在那裡設為(無)的聲音不會響。 -- **疊加層抽屜** 會在螢幕邊緣放置帶標籤頁的分區。點選一個標籤頁即可開啟其分區,再次點選即可關閉。**抽屜位置** 可從八個位置中選擇一個(預設為右側置中)。**抽屜快速鍵** 設定一個組合鍵,可在遊戲中開啟抽屜並停在你上次使用的分區,再按一次即可關閉。在遊戲中仍需按住 F 才能用滑鼠操作它,因為 Windows 不允許疊加層從 Star Citizen 手中接管滑鼠。Star Citizen 仍會收到這些按鍵,所以請選一個遊戲中不用的組合鍵。除 F 鍵和 Pause 外,組合鍵裡需要有 Ctrl、Alt 或 Win。**清除** 可移除快速鍵。如果其他程式已佔用它,此標籤頁會提示。 +- **疊加層抽屜** 會在螢幕邊緣放置帶標籤頁的分區。點選一個標籤頁即可開啟其分區,再次點選即可關閉。**抽屜位置** 可從八個位置中選擇一個(預設為右側置中)。**抽屜快速鍵** 設定一個組合鍵,可在遊戲中開啟抽屜並停在你上次使用的分區,再按一次即可關閉。在遊戲中仍需按住 F 才能用滑鼠操作它,因為 Windows 不允許疊加層從 Star Citizen 手中接管滑鼠。Star Citizen 仍會收到這些按鍵,所以請選一個遊戲中不用的組合鍵。在遊戲中請按住按鍵片刻:極短的按鍵,比如沒有設定按住時間的 Stream Deck 按鈕,可能會被漏掉。如果 Star Citizen 以管理員身份執行,Smart Citizen 也必須以管理員身份執行,否則該快速鍵在遊戲中不起作用。除 F 鍵和 Pause 外,組合鍵裡需要有 Ctrl、Alt 或 Win。**清除** 可移除快速鍵。如果其他程式已佔用它,此標籤頁會提示。 - **藍圖**:搜尋藍圖,檢視哪些任務會獎勵它們,並勾選你已擁有的藍圖(與藍圖追蹤器標籤頁共用同一份已擁有列表)。 - **礦物**:輸入礦物名稱可檢視其產地(按星系分組),輸入地點可檢視該處的礦物。勾選一種礦物,或列表底部的 **打撈**,即可關注它:當掃描發現它時,掃描標籤會提醒你。也可以在這裡開啟或關閉解碼器。 - **製造**:輸入礦物可檢視哪些物品使用它,輸入物品可檢視它所需的礦物。勾選 **Commodities** 或 **Journal** 生成增強內容後,此分區才會填入資料。 diff --git a/languages/chinese_traditional/LEGAL.md b/languages/chinese_traditional/LEGAL.md index 1ddda23a..9ebecdde 100644 --- a/languages/chinese_traditional/LEGAL.md +++ b/languages/chinese_traditional/LEGAL.md @@ -48,6 +48,17 @@ - **使用者自定義的遠端來源** —— 如果你在配置標籤頁中配置了指向 `http(s)://` 地址的資料來源,智慧公民會在重新整理原始檔時獲取該地址。預設情況下,這僅適用於 `global` 來源的 GitHub-raw 地址形式;自 v1.0 起,標準配置改為從你本地的 Data.p4k 提取內容中讀取 `base.ini`。 - **SCO 物品搜尋商店清單** — 在開啟物品搜尋分區並執行覆蓋層時,Smart Citizen 會從 [UEX](https://uexcorp.space) 的 API(`api.uexcorp.uk`)下載商店和物品價格清單,最多每 12 小時一次。這只是兩個僅攜帶應用程式名稱和版本的簡單請求,不會傳送你電腦上的任何內容。清單會快取在本機。在覆蓋層分頁關閉物品搜尋即可停止。 +### 智慧公民疊加層 + +疊加層在你啟動它之前一直處於關閉狀態。執行時,它讀取的所有內容都留在你的電腦上: + +- **螢幕** — 它擷取採礦掃描器讀數周圍的一小塊區域,用來讀取訊號數值。擷取畫面只在記憶體中讀取,不會儲存。 +- **Game.log** — 它讀取 Star Citizen 的日誌,以找到你獲得的藍圖。 +- **Windows** — 它詢問 Windows 哪個視窗在最前面以及滑鼠指標是否顯示,以便你瞄準時抽屜讓點擊穿透到遊戲。 +- **抽屜快速鍵** — 僅在你設定了快速鍵時。當 Star Citizen 在最前面時,它詢問 Windows 快速鍵的按鍵是否被按下,只有在按下時才詢問 Ctrl、Alt、Shift 和 Win 鍵。它不詢問任何其他按鍵,也從不接收你輸入的內容。 + +它從不讀取遊戲記憶體,從不掛鉤或注入遊戲,也從不向遊戲傳送輸入。 + ### 智慧公民**不會**做的事 - 不進行任何形式的遙測、分析或使用情況報告。 diff --git a/languages/chinese_traditional/ui.json b/languages/chinese_traditional/ui.json index 9fc8a80a..e65f943d 100644 --- a/languages/chinese_traditional/ui.json +++ b/languages/chinese_traditional/ui.json @@ -2992,6 +2992,14 @@ "ht": "", "at": "Smart Citizen 無法在以下位置使用工作資料夾:\n{folder}\n\n{reason}\n\n提取未開始,因此未做任何更改。" }, + "contract_scan_failed": { + "ht": "", + "at": "增強內容生成已停止,因為 {total} 份任務合約中有 {skipped} 份無法讀取。你現有的增強內容保持不變。請回報此問題,這通常是 Smart Citizen 的錯誤。\n\n第一份合約:\n{first}" + }, + "contract_scan_stopped": { + "ht": "", + "at": "增強內容生成已停止,因為任務合約掃描因錯誤而中斷。你現有的增強內容保持不變。請回報此問題,這通常是 Smart Citizen 的錯誤。\n\n錯誤:\n{first}" + }, "cache_folder_refused": { "ht": "", "at": "Windows 拒絕了 Smart Citizen 在以下位置建立 DataForge 快取的權限:\n{folder}\n\n提取未開始,因此未做任何更改。" @@ -3123,7 +3131,7 @@ }, "description": { "ht": "", - "at": "切換生成時執行的增強內容分類。飛船、元件、飛船武器、FPS 武器、任務、任務獎勵、商品製作和醫療消耗品均可獨立啟用。" + "at": "選擇點擊產生時執行哪些增強類別:Ships, Ship Items, Gear, Missions, Commodities, Journal, Medical Consumables。Ship Items 包含元件、艦船武器和飛彈;Gear 包含 FPS 武器和護甲標籤。每個類別都可以單獨開啟或關閉。" } }, "enh_favorites": { @@ -3156,24 +3164,24 @@ "at": "構建新增到元件、導彈、飛船武器、商品和護甲上的括號名稱標籤。用 ▲/▼ 重新排序元素,取消勾選可排除,更改縮寫長度,選擇分隔符和括號,或將標籤放在名稱之後而不是之前。" } }, - "overlay": { + "blueprint_tracker": { "title": { "ht": "", - "at": "8. Smart Citizen 疊加層" + "at": "7. 藍圖追蹤器" }, "description": { "ht": "", - "at": "在這裡或用工具列的「疊加層」按鈕啟動疊加層。它在遊戲上方解碼採礦掃描訊號,開啟一個抽屜來搜尋你的藍圖、礦物和製作,並把你獲得的藍圖標記為已擁有。請在主螢幕上以無邊框視窗模式執行遊戲。" + "at": "標記你擁有的藍圖。可按名稱或任務搜尋左側列表,或按元件型別、等級、尺寸和品級縮小範圍,然後用箭頭將物品移動到你的已擁有列表。已擁有的藍圖在任務的潛在獎勵中出現時會帶有 [Owned] 標籤,讓你一眼就能看出哪些值得追求。" } }, - "blueprint_tracker": { + "overlay": { "title": { "ht": "", - "at": "7. 藍圖追蹤器" + "at": "8. Smart Citizen 疊加層" }, "description": { "ht": "", - "at": "標記你擁有的藍圖。可按名稱或任務搜尋左側列表,或按元件型別、等級、尺寸和品級縮小範圍,然後用箭頭將物品移動到你的已擁有列表。已擁有的藍圖在任務的潛在獎勵中出現時會帶有 [Owned] 標籤,讓你一眼就能看出哪些值得追求。" + "at": "在這裡或用工具列的「疊加層」按鈕啟動疊加層。它在遊戲上方解碼採礦掃描訊號,開啟一個抽屜來搜尋你的藍圖、礦物和製作,並把你獲得的藍圖標記為已擁有。請在主螢幕上以無邊框視窗模式執行遊戲。" } }, "edit": { @@ -3233,7 +3241,7 @@ }, "description": { "ht": "", - "at": "選擇應用主題(預設 / 淺色 / 深色 / ODW),並可選擇禁用新版本的自動教程。" + "at": "選擇應用程式主題(預設 / 淺色 / 深色 / ODW)和字型大小(小 / 中 / 大,重新啟動後生效),並可選擇在新版本時關閉自動教程。" } }, "cfg_sc_install": { @@ -3273,13 +3281,33 @@ }, "description": { "ht": "", - "at": "透過沖突解決對話方塊將外部 INI 匯入到你的覆蓋項中,或重置當前頻道的 user.ini(清除前會自動備份)。" + "at": "透過衝突處理對話框將外部 INI 匯入你的覆蓋項。重設目前頻道的 user.ini(會先備份),或用「恢復 user.ini」找回之前的副本。預覽會顯示「套用」將寫入的內容,「檢查更新」會尋找新版本。" + } + }, + "cfg_backup": { + "title": { + "ht": "", + "at": "19. 配置:設定備份" + }, + "description": { + "ht": "", + "at": "「匯出設定」會把你的偏好、標籤設定、Star Citizen 資料夾和所有頻道的自訂字串儲存到一個檔案中。「匯入設定」可在新電腦上或全新安裝後恢復它們。" + } + }, + "cfg_sc_tools": { + "title": { + "ht": "", + "at": "20. 配置:Star Citizen 工具" + }, + "description": { + "ht": "", + "at": "「清除著色器快取」會列出遊戲的著色器快取資料夾,每個遊戲版本一個。「清理」刪除著色器並保留你的圖形設定;「移除」刪除整個資料夾。請先關閉 Star Citizen。" } }, "help": { "title": { "ht": "", - "at": "19. 幫助與反饋" + "at": "21. 幫助與反饋" }, "description": { "ht": "", @@ -3590,7 +3618,7 @@ }, "desc": { "ht": "", - "at": "顯示在 Star Citizen 之上的視窗:採礦掃描解碼器和藍圖抽屜。請以無邊框視窗模式執行遊戲。疊加層只讀取螢幕和 Game.log,並在你設定了抽屜快速鍵時只為這一個組合鍵留意按鍵,從不接觸遊戲程序。" + "at": "顯示在 Star Citizen 之上的視窗:採礦掃描解碼器和藍圖抽屜。請以無邊框視窗模式執行遊戲。疊加層只讀取螢幕和 Game.log,詢問 Windows 哪個視窗在最前面以及指標是否顯示,並在你設定了抽屜快速鍵時還詢問它的按鍵以及 Ctrl、Alt、Shift、Win 鍵是否被按下,從不接觸遊戲程序。" }, "start_btn": { "ht": "", diff --git a/languages/english/ui.json b/languages/english/ui.json index ca7cf0ed..534d68fa 100644 --- a/languages/english/ui.json +++ b/languages/english/ui.json @@ -2992,6 +2992,14 @@ "ht": "Smart Citizen could not use a working folder in:\n{folder}\n\n{reason}\n\nThe extraction did not start, so nothing was changed.", "at": "" }, + "contract_scan_failed": { + "ht": "Enhancement generation stopped because {skipped} of {total} contracts could not be read. Your existing enhancements are unchanged. Please report this, as it is usually a fault in Smart Citizen.\n\nThe first contract:\n{first}", + "at": "" + }, + "contract_scan_stopped": { + "ht": "Enhancement generation stopped because the contract scan ended with an error. Your existing enhancements are unchanged. Please report this, as it is usually a fault in Smart Citizen.\n\nThe error:\n{first}", + "at": "" + }, "cache_folder_refused": { "ht": "Windows denied Smart Citizen permission to create the DataForge cache in:\n{folder}\n\nThe extraction did not start, so nothing was changed.", "at": "" @@ -3387,7 +3395,7 @@ "at": "" }, "desc": { - "ht": "Windows drawn over Star Citizen: the mining scan decoder and the blueprint drawer. Run the game in borderless windowed mode. The overlay only reads your screen and Game.log and, if you set a drawer hotkey, watches key presses for that one combination; it never touches the game process.", + "ht": "Windows drawn over Star Citizen: the mining scan decoder and the blueprint drawer. Run the game in borderless windowed mode. The overlay only reads your screen and Game.log, asks Windows which window is in front and whether the pointer shows and, if you set a drawer hotkey, whether its key and the Ctrl, Alt, Shift and Win keys are down; it never touches the game process.", "at": "" }, "start_btn": { diff --git a/languages/french/ABOUT.md b/languages/french/ABOUT.md index 88d4a339..3912b794 100644 --- a/languages/french/ABOUT.md +++ b/languages/french/ABOUT.md @@ -31,6 +31,7 @@ Merci à celles et ceux qui ont contribué au code de Smart Citizen : - **scubamount** - **hkstrongside** - **odw-okano** +- **RWolfyo** ## Traducteurs @@ -115,7 +116,7 @@ Les textes du jeu en langues autres que l'anglais sont des traductions communaut - **Titres de mission** : faites précéder les titres de transport par leur itinéraire (par ex. `Area18 > Lorville`) — placement, flèche, séparateur et niveau de détail du lieu configurables, plus un raccourcissement optionnel des titres d'origine, avec aperçu en direct - **Stats en haut ou en bas** : choisissez si le bloc de stats se place en tête ou en pied de description - **Suivi des plans** : un onglet dédié pour marquer les plans de fabrication que vous possédez déjà. Déplacez les éléments entre Disponibles et Possédés, filtrez par Mission / Type / Classe / Taille / Grade, et les objets possédés reçoivent une balise bleue `[Owned]` dans les listes de plans des missions. **Rechercher les plans possédés dans les journaux** remplit la collection automatiquement depuis vos fichiers journaux Star Citizen, en n'important que les nouveautés depuis la dernière recherche (ou automatiquement au démarrage, quand **Rechercher automatiquement dans les journaux au démarrage** est activé), et **Exporter / Importer les plans possédés** déplace la collection d'un PC à l'autre (JSON ou CSV ; les imports ne font qu'ajouter, et les exports de scmdb.net fonctionnent aussi) -- **Superposition Smart Citizen** : fenêtres optionnelles par-dessus le jeu (mode fenêtré sans bordure). Un décodeur de scan minier affiche le gisement derrière une signature (`3 × Lindinium`) et peut briller, clignoter ou sonner pour les minéraux ou la récupération que vous surveillez ; un tiroir, avec son propre raccourci, recherche vos plans, les lieux où trouver les minéraux et ce qu'ils permettent de fabriquer ; et les plans que vous obtenez sont marqués comme possédés depuis `Game.log` pendant qu'elle tourne. Uniquement les pixels de l'écran, `Game.log` et un raccourci optionnel : aucune injection, aucune lecture de mémoire, aucune saisie simulée +- **Superposition Smart Citizen** : fenêtres optionnelles par-dessus le jeu (mode fenêtré sans bordure). Un décodeur de scan minier affiche le gisement derrière une signature (`3 × Lindinium`) et peut briller, clignoter ou sonner pour les minéraux ou la récupération que vous surveillez ; un tiroir, avec son propre raccourci, recherche vos plans, les lieux où trouver les minéraux et ce qu'ils permettent de fabriquer ; et les plans que vous obtenez sont marqués comme possédés depuis `Game.log` pendant qu'elle tourne. Uniquement les pixels de l'écran, `Game.log`, la fenêtre au premier plan, la visibilité du pointeur et un raccourci optionnel : aucune injection, aucune lecture de mémoire, aucune saisie simulée - **Étiquettes de mission** : renommez les en-têtes de section (MISSION DETAILS, POTENTIAL BLUEPRINTS, etc.), le libellé d'XP et la balise d'emphase des en-têtes - **Correctifs déclaratifs des bugs de données CIG** : un système de correctifs applique à l'extraction des corrections aux bugs DataForge connus, pour que le texte en jeu soit correct sans attendre CIG - **Catégories sélectives** : activez ou désactivez chaque catégorie d'enrichissements indépendamment depuis l'onglet Enrichissements diff --git a/languages/french/FAQ.md b/languages/french/FAQ.md index 7a68186f..1df69bc9 100644 --- a/languages/french/FAQ.md +++ b/languages/french/FAQ.md @@ -15,7 +15,7 @@ Vos modifications personnelles se trouvent dans `user.ini`, dans votre dossier d Smart Citizen ne modifie que le texte de localisation (les mots affichés par le jeu) ; il ne touche pas à la logique du jeu, ne vous donne aucun avantage et ne communique pas avec les serveurs de CIG. Nos modifications **devraient** être sans risque. -La **Superposition Smart Citizen** optionnelle (onglet Superposition) fonctionne de la même façon, sans intervenir sur le jeu. Elle affiche des fenêtres ordinaires par-dessus le jeu, lit les pixels de votre écran comme le ferait un outil de capture d'écran, et lit le fichier `Game.log` du jeu. Elle n'injecte jamais rien dans le jeu et ne s'y accroche jamais (aucun hook), n'ouvre jamais le processus du jeu et ne lit jamais sa mémoire, et n'envoie jamais d'entrées clavier ou souris. Si vous définissez un raccourci pour le tiroir, elle enregistre cette seule combinaison de touches auprès de Windows, de la manière standard dont un programme demande un raccourci. Star Citizen empêche les raccourcis enregistrés par d'autres programmes de fonctionner tant qu'il a le focus, donc, tant qu'un raccourci est défini, la superposition reçoit aussi l'entrée brute du clavier (raw input), le moyen en lecture seule par lequel Windows informe un programme en arrière-plan des touches pressées. Ce n'est pas un hook clavier : elle ne retient, ne modifie et n'envoie aucune touche, n'enregistre rien et ne réagit qu'à votre combinaison. CIG ne s'est pas prononcé sur ce type de superposition : la même mise en garde « à vos propres risques » ci-dessous s'applique donc. +La **Superposition Smart Citizen** optionnelle (onglet Superposition) fonctionne de la même façon, sans intervenir sur le jeu. Elle affiche des fenêtres ordinaires par-dessus le jeu, lit les pixels de votre écran comme le ferait un outil de capture d'écran, et lit le fichier `Game.log` du jeu. Tant que son tiroir est affiché, elle demande aussi à Windows quelle fenêtre est au premier plan et si le pointeur de la souris est affiché, pour que vos tirs traversent le tiroir pendant que vous visez. Elle n'injecte jamais rien dans le jeu et ne s'y accroche jamais (aucun hook), n'ouvre jamais le processus du jeu et ne lit jamais sa mémoire, et n'envoie jamais d'entrées clavier ou souris. Si vous définissez un raccourci pour le tiroir, elle enregistre cette seule combinaison de touches auprès de Windows, de la manière standard dont un programme demande un raccourci. Star Citizen empêche les raccourcis enregistrés par d'autres programmes de fonctionner tant qu'il a le focus, donc, tant que le jeu est au premier plan, la superposition demande aussi à Windows si la touche de cette combinaison est enfoncée et, seulement quand elle l'est, si Ctrl, Alt, Maj ou Win est maintenue. Elle ne demande rien sur aucune autre touche, ne reçoit jamais ce que vous tapez dans le jeu ou un autre programme, et ne retient, ne modifie ni n'envoie jamais aucune touche. CIG ne s'est pas prononcé sur ce type de superposition : la même mise en garde « à vos propres risques » ci-dessous s'applique donc. CIG soutient publiquement la localisation communautaire. Leur billet [Community Localization Update](https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/star-citizen-community-localization-update) présente leur soutien officiel aux traductions faites par les joueurs, ce que nous comprenons comme autorisant explicitement le type de modification de localisation que fait Smart Citizen. diff --git a/languages/french/HELP.md b/languages/french/HELP.md index d0ddfb9f..ae658a85 100644 --- a/languages/french/HELP.md +++ b/languages/french/HELP.md @@ -82,6 +82,8 @@ La couleur du bouton vous indique où vous en êtes : **rouge** signifie que que Smart Citizen ajoute aussi un petit filigrane à la version affichée par le lanceur (`Frontend_PU_Version`), en ajoutant `\nLocalizations Enhanced with Smart Citizen v{VERSION}` sur sa propre ligne. C'est ainsi que vous pouvez confirmer en jeu que votre loc-pack est actif : regardez l'étiquette de version sur le menu principal de Star Citizen. Le filigrane est réécrit à chaque application, il ne s'accumule donc jamais d'une version à l'autre. +L'application ajoute aussi une deuxième ligne au bouton Jouer du menu principal (`Frontend_play_star_citizen`), `Run Smart Citizen after every patch`, et centre les deux lignes. Un patch du jeu laisse en place le `global.ini` appliqué, mais les clés ajoutées par le patch s'affichent comme des noms `@key` bruts jusqu'à ce que vous lanciez Smart Citizen et appliquiez à nouveau. Le rappel est donc dans le menu dès le premier lancement du jeu après un patch. Comme le filigrane, il est réécrit à chaque application, et il reste en anglais quelle que soit votre langue. + ## 8. Restaurer une sauvegarde Ouvrez le menu **Plus** de la barre d'outils et choisissez **Restaurer une sauvegarde** pour revenir à une version précédente. Smart Citizen conserve jusqu'à **5 sauvegardes automatiques** ; la plus ancienne est supprimée à mesure que de nouvelles sont créées. @@ -168,11 +170,11 @@ Suivez les plans de fabrication que vous possédez déjà, et retrouvez cette in ## Onglet Superposition -La **Superposition Smart Citizen** affiche deux petites fenêtres par-dessus Star Citizen : un décodeur de scan minier et un tiroir de recherches. Démarrez-la et arrêtez-la avec **Démarrer la superposition** dans cet onglet ou avec le bouton **Superposition** de la barre d'outils. Lancez le jeu en mode fenêtré sans bordure sur votre écran principal, sinon la superposition ne peut pas s'afficher par-dessus. La superposition se contente de lire votre écran et `Game.log` et, si vous définissez un raccourci pour le tiroir, de surveiller les touches pressées pour cette seule combinaison ; elle ne touche jamais au jeu lui-même. +La **Superposition Smart Citizen** affiche deux petites fenêtres par-dessus Star Citizen : un décodeur de scan minier et un tiroir de recherches. Démarrez-la et arrêtez-la avec **Démarrer la superposition** dans cet onglet ou avec le bouton **Superposition** de la barre d'outils. Lancez le jeu en mode fenêtré sans bordure sur votre écran principal, sinon la superposition ne peut pas s'afficher par-dessus. La superposition se contente de lire votre écran et `Game.log`, de demander à Windows quelle fenêtre est au premier plan et si le pointeur de la souris est affiché (pour que vos tirs traversent le tiroir pendant que vous visez) et, si vous définissez un raccourci pour le tiroir, si sa touche et les touches Ctrl, Alt, Maj et Win sont enfoncées ; elle ne touche jamais au jeu lui-même. - **Décodeur de scan minier** : lit la signature de scan sous votre radar et affiche juste en dessous le type et le nombre de gisements (par exemple `3 × Lindinium`). L'étiquette ne change qu'une fois le même nombre lu deux fois de suite, pour qu'une erreur de lecture sur une seule image ne la fasse pas clignoter. **Taille du texte du scan** rend l'étiquette plus petite ou plus grande. Un nombre rond comme 12,000 peut être de la récupération ou un gisement de surface (minage ROC ou FPS) ; la récupération est listée en premier et les autres sont marqués surface uniquement, car dans l'espace seule la récupération est possible. - **Quand un minéral surveillé ou de la récupération est scanné** : choisissez comment l'étiquette vous prévient. **Lueur** et **Clignotement** sont activés par défaut ; **Changer la couleur du texte** (vert vif), **Texte plus grand** et **Jouer un son** peuvent s'y ajouter. Le clignotement et le son viennent quand la cible est lue pour la première fois, pas de nouveau tant qu'elle reste à l'écran. Avec **Jouer un son** activé, **Son d'alerte** choisit le son : **Smart Citizen par défaut** (un court carillon), une voix en anglais (accent américain, britannique, australien, irlandais ou nigérian) ou l'un des sons Windows, et **Écouter** le joue. Un son Windows suit votre modèle de sons Windows : un son réglé sur (Aucun) reste muet. -- **Tiroir de la superposition** : place des sections à onglets au bord de l'écran. Cliquez sur un onglet pour ouvrir sa section, cliquez de nouveau pour la fermer. **Position du tiroir** propose huit emplacements (au milieu à droite par défaut). **Raccourci du tiroir** définit une combinaison de touches qui ouvre le tiroir depuis le jeu sur la dernière section utilisée ; une nouvelle pression le ferme. En jeu, maintenez toujours F pour vous servir de la souris dedans, car Windows ne laisse pas la superposition prendre la souris à Star Citizen. Star Citizen reçoit quand même ces touches : choisissez donc une combinaison que vous n'utilisez pas en jeu. Elle doit comporter Ctrl, Alt ou Win, sauf s'il s'agit d'une touche F ou de Pause. **Effacer** supprime le raccourci. Si un autre programme l'utilise déjà, l'onglet le signale. +- **Tiroir de la superposition** : place des sections à onglets au bord de l'écran. Cliquez sur un onglet pour ouvrir sa section, cliquez de nouveau pour la fermer. **Position du tiroir** propose huit emplacements (au milieu à droite par défaut). **Raccourci du tiroir** définit une combinaison de touches qui ouvre le tiroir depuis le jeu sur la dernière section utilisée ; une nouvelle pression le ferme. En jeu, maintenez toujours F pour vous servir de la souris dedans, car Windows ne laisse pas la superposition prendre la souris à Star Citizen. Star Citizen reçoit quand même ces touches : choisissez donc une combinaison que vous n'utilisez pas en jeu. En jeu, maintenez les touches un instant : un appui très bref, comme un bouton de Stream Deck sans durée de maintien, peut être manqué. Si Star Citizen tourne en tant qu'administrateur, Smart Citizen doit aussi tourner ainsi, sinon le raccourci ne fait rien en jeu. Elle doit comporter Ctrl, Alt ou Win, sauf s'il s'agit d'une touche F ou de Pause. **Effacer** supprime le raccourci. Si un autre programme l'utilise déjà, l'onglet le signale. - **Plans** : cherchez des plans, voyez quelles missions les donnent, et cochez ceux que vous possédez (la même collection que dans l'onglet Suivi des plans). - **Minéraux** : tapez un minéral pour voir où le trouver, regroupé par système stellaire, ou un lieu pour voir ses minéraux. Cochez un minéral, ou **Récupération** en bas de la liste, pour le surveiller : l'étiquette du scan vous prévient quand un scan le détecte. Le décodeur peut aussi être activé ou désactivé ici. - **Fabrication** : tapez un minéral pour voir les objets qui l'utilisent, ou un objet pour voir les minéraux qu'il demande. Se remplit quand vous générez les enrichissements avec **Commodities** ou **Journal** coché. diff --git a/languages/french/LEGAL.md b/languages/french/LEGAL.md index e7c2d611..aaec8a74 100644 --- a/languages/french/LEGAL.md +++ b/languages/french/LEGAL.md @@ -50,6 +50,17 @@ Smart Citizen n'effectue de requêtes réseau sortantes que dans quatre cas : - **Sources distantes configurées par l'utilisateur** : si vous avez configuré une source de données pointant vers une URL `http(s)://` dans l'onglet Paramètres, Smart Citizen consulte cette URL lors de l'actualisation des fichiers sources. Par défaut, cela ne concerne que la forme URL GitHub-raw de la source `global` ; la configuration standard depuis la v1.0 lit `base.ini` depuis votre extraction locale de Data.p4k. - **Liste des boutiques de la recherche d'objets SCO** — Tant que l'overlay tourne avec sa section Recherche d'objets activée, Smart Citizen télécharge la liste des boutiques et des prix depuis l'API [UEX](https://uexcorp.space) (`api.uexcorp.uk`), au plus toutes les 12 heures. Ce sont deux requêtes simples qui n'envoient que le nom et la version de l'application ; rien de votre machine n'est envoyé. La liste est mise en cache localement. Désactivez la Recherche d'objets dans l'onglet Overlay pour l'arrêter. +### La superposition Smart Citizen + +La superposition reste désactivée tant que vous ne la lancez pas. Pendant qu'elle tourne, tout ce qu'elle lit reste sur votre ordinateur : + +- **Écran** — elle capture une petite zone autour de l'affichage du scanner minier pour lire le nombre du signal. Les captures sont lues en mémoire et ne sont pas enregistrées. +- **Game.log** — elle lit le journal de Star Citizen pour trouver les plans que vous recevez. +- **Windows** — elle demande à Windows quelle fenêtre est au premier plan et si le pointeur de la souris est affiché, pour que le tiroir laisse passer vos clics vers le jeu pendant que vous visez. +- **Raccourci du tiroir** — seulement si vous en définissez un. Quand Star Citizen est au premier plan, elle demande à Windows si la touche du raccourci est enfoncée, et les touches Ctrl, Alt, Maj et Win seulement quand elle l'est. Elle ne demande l'état d'aucune autre touche et ne reçoit jamais ce que vous tapez. + +Elle ne lit jamais la mémoire du jeu, ne s'y accroche ni ne s'y injecte jamais, et ne lui envoie jamais d'entrée. + ### Ce que Smart Citizen ne fait **pas** - Aucune télémétrie, analyse d'usage ou rapport d'utilisation d'aucune sorte. diff --git a/languages/french/ui.json b/languages/french/ui.json index 68864a4d..44203713 100644 --- a/languages/french/ui.json +++ b/languages/french/ui.json @@ -2992,6 +2992,14 @@ "ht": "", "at": "Smart Citizen n'a pas pu utiliser un dossier de travail dans :\n{folder}\n\n{reason}\n\nL'extraction n'a pas démarré, donc rien n'a été modifié." }, + "contract_scan_failed": { + "ht": "", + "at": "La génération des enrichissements s'est arrêtée, car {skipped} contrats sur {total} n'ont pas pu être lus. Vos enrichissements existants n'ont pas changé. Merci de le signaler : il s'agit généralement d'une erreur de Smart Citizen.\n\nPremier contrat :\n{first}" + }, + "contract_scan_stopped": { + "ht": "", + "at": "La génération des enrichissements s'est arrêtée, car la lecture des contrats a échoué. Vos enrichissements existants n'ont pas changé. Merci de le signaler : il s'agit généralement d'une erreur de Smart Citizen.\n\nErreur :\n{first}" + }, "cache_folder_refused": { "ht": "", "at": "Windows a refusé à Smart Citizen l'autorisation de créer le cache DataForge dans :\n{folder}\n\nL'extraction n'a pas démarré, donc rien n'a été modifié." @@ -3123,7 +3131,7 @@ }, "description": { "ht": "", - "at": "Choisissez les catégories d'enrichissements exécutées lors de la génération. Vaisseaux, composants, armes de vaisseau, armes FPS, missions, récompenses de mission, fabrication de marchandises et consommables médicaux peuvent être activés indépendamment." + "at": "Choisissez les catégories d'enrichissements exécutées lors de la génération : Ships, Ship Items, Gear, Missions, Commodities, Journal, Medical Consumables. Ship Items couvre les composants, les armes de vaisseau et les missiles ; Gear couvre les armes FPS et les étiquettes d'armure. Chaque catégorie s'active ou se désactive séparément." } }, "enh_favorites": { @@ -3156,6 +3164,26 @@ "at": "Composez les balises entre crochets ajoutées aux noms des composants, missiles, armes de vaisseau, marchandises et armures. Réordonnez les éléments avec ▲/▼, décochez pour exclure, changez la longueur des abréviations, choisissez le séparateur et les crochets, ou placez la balise après le nom plutôt qu'avant." } }, + "blueprint_tracker": { + "title": { + "ht": "", + "at": "7. Suivi des plans" + }, + "description": { + "ht": "", + "at": "Marquez les plans que vous possédez. Cherchez dans la liste de gauche par nom ou par mission, ou affinez par Type, Classe, Taille et Grade de composant, puis utilisez les flèches pour déplacer des éléments vers votre liste de possédés. Les plans possédés reçoivent une étiquette [Owned] partout où ils apparaissent dans les récompenses potentielles d'une mission, pour voir d'un coup d'œil ce qui vaut la peine d'être chassé." + } + }, + "overlay": { + "title": { + "ht": "", + "at": "8. Superposition Smart Citizen" + }, + "description": { + "ht": "", + "at": "Démarrez la superposition ici ou avec le bouton Superposition de la barre d'outils. Par-dessus le jeu, elle décode les signatures de scan minier, ouvre un tiroir pour chercher vos plans, minéraux et fabrications, et marque comme possédés les plans que vous obtenez. Lancez le jeu en mode fenêtré sans bordure sur votre écran principal." + } + }, "edit": { "title": { "ht": "", @@ -3213,7 +3241,7 @@ }, "description": { "ht": "", - "at": "Choisissez le thème de l'application (Défaut / Clair / Sombre / ODW) et désactivez si vous le souhaitez la visite automatique à chaque nouvelle version." + "at": "Choisissez le thème de l'application (Défaut / Clair / Sombre / ODW) et la taille du texte (Petite / Moyenne / Grande, appliquée après un redémarrage), et désactivez si besoin la visite automatique lors des nouvelles versions." } }, "cfg_sc_install": { @@ -3253,37 +3281,37 @@ }, "description": { "ht": "", - "at": "Importez un INI externe dans vos modifications via la boîte de dialogue de résolution de conflits, ou réinitialisez votre user.ini pour le canal actif (sauvegardé automatiquement avant l'effacement)." + "at": "Importez un INI externe dans vos modifications via la fenêtre de résolution des conflits. Réinitialisez le user.ini du canal actif (sauvegardé avant) ou récupérez une copie précédente avec Restaurer user.ini. L'aperçu montre ce qu'Appliquer écrirait, et Rechercher des mises à jour vérifie s'il existe une nouvelle version." } }, - "help": { + "cfg_backup": { "title": { "ht": "", - "at": "19. Aide et retours" + "at": "19. Paramètres : Sauvegarde des paramètres" }, "description": { "ht": "", - "at": "Le bouton Aide ouvre un panneau latéral avec le guide complet, la liste des problèmes connus et un lien vers le canal Discord de Smart Citizen pour vos retours. Vous avez tout ce qu'il faut pour démarrer : bonne chance, citoyen." + "at": "Exporter les paramètres enregistre vos préférences, vos réglages d'étiquettes, votre dossier Star Citizen et vos textes personnalisés de tous les canaux dans un seul fichier. Importer les paramètres les restaure, sur un nouveau PC ou après une installation propre." } }, - "overlay": { + "cfg_sc_tools": { "title": { "ht": "", - "at": "8. Superposition Smart Citizen" + "at": "20. Paramètres : Outils Star Citizen" }, "description": { "ht": "", - "at": "Démarrez la superposition ici ou avec le bouton Superposition de la barre d'outils. Par-dessus le jeu, elle décode les signatures de scan minier, ouvre un tiroir pour chercher vos plans, minéraux et fabrications, et marque comme possédés les plans que vous obtenez. Lancez le jeu en mode fenêtré sans bordure sur votre écran principal." + "at": "Vider le cache des shaders liste les dossiers de cache de shaders du jeu, un par version. Nettoyer supprime les shaders et garde vos réglages graphiques ; Supprimer efface le dossier entier. Fermez Star Citizen avant." } }, - "blueprint_tracker": { + "help": { "title": { "ht": "", - "at": "7. Suivi des plans" + "at": "21. Aide et retours" }, "description": { "ht": "", - "at": "Marquez les plans que vous possédez. Cherchez dans la liste de gauche par nom ou par mission, ou affinez par Type, Classe, Taille et Grade de composant, puis utilisez les flèches pour déplacer des éléments vers votre liste de possédés. Les plans possédés reçoivent une étiquette [Owned] partout où ils apparaissent dans les récompenses potentielles d'une mission, pour voir d'un coup d'œil ce qui vaut la peine d'être chassé." + "at": "Le bouton Aide ouvre un panneau latéral avec le guide complet, la liste des problèmes connus et un lien vers le canal Discord de Smart Citizen pour vos retours. Vous avez tout ce qu'il faut pour démarrer : bonne chance, citoyen." } } }, @@ -3590,7 +3618,7 @@ }, "desc": { "ht": "", - "at": "Fenêtres affichées par-dessus Star Citizen : le décodeur de scan minier et le tiroir des plans. Lancez le jeu en mode fenêtré sans bordure. La superposition lit seulement votre écran et Game.log et, si vous définissez un raccourci pour le tiroir, surveille les touches pressées pour cette seule combinaison ; elle ne touche jamais au processus du jeu." + "at": "Fenêtres affichées par-dessus Star Citizen : le décodeur de scan minier et le tiroir des plans. Lancez le jeu en mode fenêtré sans bordure. La superposition lit seulement votre écran et Game.log, demande à Windows quelle fenêtre est au premier plan et si le pointeur est affiché et, si vous définissez un raccourci pour le tiroir, si sa touche et les touches Ctrl, Alt, Maj et Win sont enfoncées ; elle ne touche jamais au processus du jeu." }, "start_btn": { "ht": "", diff --git a/languages/german/ABOUT.md b/languages/german/ABOUT.md index 9f404291..6e82914a 100644 --- a/languages/german/ABOUT.md +++ b/languages/german/ABOUT.md @@ -29,6 +29,7 @@ Danke an alle, die Code zu Smart Citizen beigetragen haben: - **scubamount** - **hkstrongside** - **odw-okano** +- **RWolfyo** ## Übersetzer @@ -113,7 +114,7 @@ Die nicht-englischen Spieltexte sind Community-Übersetzungen: - **Missionstitel**: Frachtmissionstitel mit ihrer Route einleiten (z. B. `Area18 > Lorville`) — konfigurierbare Platzierung, Pfeil, Trennzeichen und Ortsdetail, plus optionale Kürzung des Originaltitels, mit Live-Vorschau - **Werte oberhalb oder unterhalb**: Wähle, ob ein Statistikblock oben oder unten in der Beschreibung sitzt - **Bauplan-Tracker**: Ein eigener Tab zum Markieren der Herstellungs-Baupläne, die du bereits besitzt. Gegenstände zwischen Verfügbar und Besessen verschieben, nach Mission / Typ / Klasse / Größe / Grad filtern, und besessene Gegenstände erhalten ein blaues `[Owned]`-Tag in Missions-Bauplan-Listen. **Protokolle nach besessenen Bauplänen durchsuchen** füllt den Besitz automatisch aus deinen Star-Citizen-Protokolldateien, wobei nur importiert wird, was seit dem letzten Scan neu ist (oder automatisch beim Start, wenn **Protokolle beim Start automatisch durchsuchen** aktiviert ist), und **Eigene Baupläne exportieren / importieren** überträgt die Besessen-Liste zwischen PCs (JSON oder CSV; Importe fügen immer nur hinzu, und auch scmdb.net-Exporte funktionieren) -- **Smart Citizen Overlay**: Optionale Fenster über dem Spiel (randloser Fenstermodus). Ein Bergbau-Scan-Decoder zeigt das Vorkommen hinter einer Signatur (`3 × Lindinium`) und kann bei beobachteten Mineralien oder Bergungsgut leuchten, blinken oder einen Ton abspielen; eine Schublade mit eigenem Tastenkürzel durchsucht deine Baupläne, die Fundorte von Mineralien und was sich aus ihnen herstellen lässt; und Baupläne, die du verdienst, werden aus `Game.log` als besessen markiert, solange das Overlay läuft. Nur Bildschirmpixel, `Game.log` und ein optionales Tastenkürzel: keine Injektion, kein Auslesen von Speicher, keine Eingaben +- **Smart Citizen Overlay**: Optionale Fenster über dem Spiel (randloser Fenstermodus). Ein Bergbau-Scan-Decoder zeigt das Vorkommen hinter einer Signatur (`3 × Lindinium`) und kann bei beobachteten Mineralien oder Bergungsgut leuchten, blinken oder einen Ton abspielen; eine Schublade mit eigenem Tastenkürzel durchsucht deine Baupläne, die Fundorte von Mineralien und was sich aus ihnen herstellen lässt; und Baupläne, die du verdienst, werden aus `Game.log` als besessen markiert, solange das Overlay läuft. Nur Bildschirmpixel, `Game.log`, das Fenster im Vordergrund, ob der Zeiger sichtbar ist, und ein optionales Tastenkürzel: keine Injektion, kein Auslesen von Speicher, keine Eingaben - **Missionsbezeichnungen**: Die Abschnittsüberschriften (MISSIONSDETAILS, MÖGLICHE BAUPLÄNE usw.), die XP-Bezeichnung und das für Überschriften verwendete Hervorhebungs-Tag umbenennen - **Deklarative CIG-Datenfehler-Patches**: Ein Patch-System wendet Korrekturen für bekannte DataForge-Fehler zur Extraktionszeit an, sodass der In-Game-Text korrekt angezeigt wird, ohne auf CIG warten zu müssen - **Selektive Kategorien**: Jede Erweiterungskategorie unabhängig im Erweiterungen-Tab aktivieren oder deaktivieren diff --git a/languages/german/FAQ.md b/languages/german/FAQ.md index 2779ffe4..a3aa1b39 100644 --- a/languages/german/FAQ.md +++ b/languages/german/FAQ.md @@ -15,7 +15,7 @@ Deine persönlichen Bearbeitungen liegen in `user.ini` in deinem Smart-Citizen-D Smart Citizen bearbeitet nur Lokalisierungstext (die Worte, die dir das Spiel zeigt), es greift nicht in die Spiellogik ein, verschafft dir keinen Vorteil und kommuniziert nicht mit CIGs Servern. Unsere Änderungen **sollten** unbedenklich sein. -Das optionale **Smart Citizen Overlay** (Overlay-Tab) funktioniert genauso, ohne ins Spiel einzugreifen. Es zeichnet gewöhnliche Fenster über das Spiel, liest Pixel von deinem Bildschirm, wie es ein Screenshot-Werkzeug tut, und liest die Datei `Game.log` des Spiels. Es injiziert nie etwas ins Spiel und hakt sich nie darin ein, öffnet nie den Spielprozess, liest nie dessen Speicher und sendet nie Tastatur- oder Mauseingaben. Legst du ein Tastenkürzel für die Schublade fest, meldet es genau diese eine Tastenkombination bei Windows an, auf dem üblichen Weg, auf dem ein Programm ein Tastenkürzel anfordert. Star Citizen hält angemeldete Tastenkürzel anderer Programme zurück, solange es den Fokus hat, deshalb empfängt das Overlay, solange ein Tastenkürzel gesetzt ist, auch die Roheingabe der Tastatur (Raw Input), den lesenden Weg, auf dem Windows ein Programm im Hintergrund über Tastendrücke informiert. Das ist kein Tastatur-Hook: Es hält keine Taste auf, ändert oder sendet keine, zeichnet nichts auf und reagiert nur auf deine Kombination. CIG hat sich zu Overlays dieser Art bisher nicht geäußert, daher gilt auch hier der Hinweis zur Nutzung auf eigenes Risiko weiter unten. +Das optionale **Smart Citizen Overlay** (Overlay-Tab) funktioniert genauso, ohne ins Spiel einzugreifen. Es zeichnet gewöhnliche Fenster über das Spiel, liest Pixel von deinem Bildschirm, wie es ein Screenshot-Werkzeug tut, und liest die Datei `Game.log` des Spiels. Solange seine Schublade angezeigt wird, fragt es Windows außerdem, welches Fenster im Vordergrund ist und ob der Mauszeiger sichtbar ist, damit deine Schüsse beim Zielen durch die Schublade gehen. Es injiziert nie etwas ins Spiel und hakt sich nie darin ein, öffnet nie den Spielprozess, liest nie dessen Speicher und sendet nie Tastatur- oder Mauseingaben. Legst du ein Tastenkürzel für die Schublade fest, meldet es genau diese eine Tastenkombination bei Windows an, auf dem üblichen Weg, auf dem ein Programm ein Tastenkürzel anfordert. Star Citizen hält angemeldete Tastenkürzel anderer Programme zurück, solange es den Fokus hat, deshalb fragt das Overlay Windows, solange das Spiel im Vordergrund ist, auch, ob die Taste dieser Kombination gedrückt ist, und nur solange sie es ist, ob Strg, Alt, Umschalt oder Win gehalten wird. Nach keiner anderen Taste fragt es, was du im Spiel oder in einem anderen Programm tippst, bekommt es nie, und es hält keine Taste auf, ändert oder sendet keine. CIG hat sich zu Overlays dieser Art bisher nicht geäußert, daher gilt auch hier der Hinweis zur Nutzung auf eigenes Risiko weiter unten. CIG hat Community-Lokalisierung öffentlich unterstützt. Ihr Beitrag [Community Localization Update](https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/star-citizen-community-localization-update) legt die offizielle Unterstützung für von Spielern erstellte Übersetzungen dar, die unserem Verständnis nach ausdrücklich die Art von Lokalisierungsbearbeitung erlaubt, die Smart Citizen vornimmt. diff --git a/languages/german/HELP.md b/languages/german/HELP.md index bacbbef3..4525bb02 100644 --- a/languages/german/HELP.md +++ b/languages/german/HELP.md @@ -80,6 +80,8 @@ Die Farbe des Knopfs zeigt dir, wo du stehst: **Rot** bedeutet, dass sich seit d Smart Citizen stempelt außerdem ein kleines Wasserzeichen in die Launcher-Versionszeichenfolge (`Frontend_PU_Version`) und hängt `\nLocalizations Enhanced with Smart Citizen v{VERSION}` in einer eigenen Zeile an. So kannst du im Spiel bestätigen, dass dein Loc-Pack aktiv ist — schau dir das Versionslabel im Star-Citizen-Hauptmenü an. Der Stempel wird bei jedem Anwenden neu geschrieben, sodass er sich über Versionen hinweg nicht anhäuft. +Beim Anwenden bekommt außerdem die Spielen-Schaltfläche im Hauptmenü (`Frontend_play_star_citizen`) eine zweite Zeile, `Run Smart Citizen after every patch`, und beide Zeilen werden zentriert. Ein Spiel-Patch lässt die angewendete `global.ini` an ihrem Platz, aber die Schlüssel, die der Patch hinzugefügt hat, erscheinen als rohe `@key`-Namen, bis du Smart Citizen startest und erneut anwendest. So steht die Erinnerung schon beim ersten Spielstart nach einem Patch im Menü. Wie der Stempel wird sie bei jedem Anwenden neu geschrieben, und sie bleibt in jeder Sprache englisch. + ## 8. Eine Sicherung wiederherstellen Öffne das Menü **Mehr** in der Symbolleiste und wähle **Sicherung wiederherstellen**, um zu einer früheren Version zurückzukehren. Smart Citizen bewahrt bis zu **5 automatische Sicherungen** auf — die älteste wird entfernt, sobald eine neue erstellt wird. @@ -166,11 +168,11 @@ Verfolge, welche Herstellungs-Baupläne du bereits besitzt, und sieh es im Spiel ## Overlay-Tab -Das **Smart Citizen Overlay** zeichnet zwei kleine Fenster über Star Citizen: einen Bergbau-Scan-Decoder und eine Schublade mit Suchfunktionen. Starte und stoppe es mit **Overlay starten** auf diesem Tab oder mit der Schaltfläche **Overlay** in der Symbolleiste. Starte das Spiel im randlosen Fenstermodus auf deinem Hauptbildschirm, sonst kann das Overlay nicht darüber angezeigt werden. Das Overlay liest nur deinen Bildschirm und `Game.log` und achtet, wenn du ein Tastenkürzel für die Schublade festlegst, auf Tastendrücke für genau diese Kombination; das Spiel selbst berührt es nie. +Das **Smart Citizen Overlay** zeichnet zwei kleine Fenster über Star Citizen: einen Bergbau-Scan-Decoder und eine Schublade mit Suchfunktionen. Starte und stoppe es mit **Overlay starten** auf diesem Tab oder mit der Schaltfläche **Overlay** in der Symbolleiste. Starte das Spiel im randlosen Fenstermodus auf deinem Hauptbildschirm, sonst kann das Overlay nicht darüber angezeigt werden. Das Overlay liest nur deinen Bildschirm und `Game.log`, fragt Windows, welches Fenster im Vordergrund ist und ob der Mauszeiger sichtbar ist (damit deine Schüsse beim Zielen durch die Schublade gehen), und, wenn du ein Tastenkürzel für die Schublade festlegst, ob seine Taste und die Tasten Strg, Alt, Umschalt und Win gedrückt sind; das Spiel selbst berührt es nie. - **Bergbau-Scan-Decoder** liest die Scan-Signatur unter deinem Radar und zeigt Vorkommenstyp und Anzahl direkt darunter an (zum Beispiel `3 × Lindinium`). Die Anzeige ändert sich erst, wenn dieselbe Zahl zweimal hintereinander gelesen wurde, sodass eine Fehllesung in einem einzelnen Frame nicht aufblitzt. **Textgröße des Scans** macht die Anzeige kleiner oder größer. Eine runde Zahl wie 12,000 kann Bergungsgut oder ein Oberflächenvorkommen sein (ROC- oder FPS-Bergbau); Bergungsgut steht zuerst, die anderen sind als nur Oberfläche markiert, denn im All kann es nur Bergungsgut sein. - **Wenn ein beobachtetes Mineral oder Bergungsgut gescannt wird**: Wähle, wie die Anzeige dich darauf hinweist. **Leuchten** und **Blinken** sind standardmäßig an; **Textfarbe ändern** (hellgrün), **Größerer Text** und **Ton abspielen** lassen sich dazunehmen. Blinken und Ton kommen, wenn das Ziel zum ersten Mal gelesen wird, nicht erneut, solange es auf dem Bildschirm bleibt. Ist **Ton abspielen** an, wählt **Alarmton** den Ton: **Smart Citizen Standard** (ein kurzer Klang), eine englische Stimme (US-amerikanisch, britisch, australisch, irisch oder nigerianisch) oder einen der Windows-Töne, und **Vorhören** spielt ihn ab. Ein Windows-Ton folgt deinem Windows-Soundschema; ein dort auf (Kein) gesetzter Ton bleibt stumm. -- **Overlay-Schublade** setzt Bereiche mit Reitern an den Bildschirmrand. Klicke auf einen Reiter, um seinen Bereich zu öffnen, und erneut, um ihn zu schließen. **Position der Schublade** wählt eine von acht Stellen (standardmäßig Mitte rechts). **Tastenkürzel der Schublade** legt eine Tastenkombination fest, die die Schublade aus dem Spiel heraus mit dem zuletzt genutzten Bereich öffnet; ein erneuter Druck schließt sie. Im Spiel hältst du weiterhin F gedrückt, um die Maus darin zu nutzen, denn Windows lässt das Overlay Star Citizen die Maus nicht wegnehmen. Star Citizen bekommt diese Tasten trotzdem, also wähle eine Kombination, die du im Spiel nicht nutzt. Sie braucht Strg, Alt oder Win, außer bei einer F-Taste oder Pause. **Löschen** entfernt das Tastenkürzel. Belegt sie schon ein anderes Programm, sagt der Tab es dir. +- **Overlay-Schublade** setzt Bereiche mit Reitern an den Bildschirmrand. Klicke auf einen Reiter, um seinen Bereich zu öffnen, und erneut, um ihn zu schließen. **Position der Schublade** wählt eine von acht Stellen (standardmäßig Mitte rechts). **Tastenkürzel der Schublade** legt eine Tastenkombination fest, die die Schublade aus dem Spiel heraus mit dem zuletzt genutzten Bereich öffnet; ein erneuter Druck schließt sie. Im Spiel hältst du weiterhin F gedrückt, um die Maus darin zu nutzen, denn Windows lässt das Overlay Star Citizen die Maus nicht wegnehmen. Star Citizen bekommt diese Tasten trotzdem, also wähle eine Kombination, die du im Spiel nicht nutzt. Halte die Tasten im Spiel einen Moment gedrückt: Ein sehr kurzer Druck, etwa eine Stream-Deck-Taste ohne Haltezeit, kann übersehen werden. Läuft Star Citizen als Administrator, muss auch Smart Citizen als Administrator laufen, sonst tut das Tastenkürzel im Spiel nichts. Sie braucht Strg, Alt oder Win, außer bei einer F-Taste oder Pause. **Löschen** entfernt das Tastenkürzel. Belegt sie schon ein anderes Programm, sagt der Tab es dir. - **Baupläne**: Baupläne suchen, sehen, welche Missionen sie belohnen, und die abhaken, die du besitzt (dieselbe Besessen-Liste wie im Bauplan-Tracker-Tab). - **Mineralien**: Gib ein Mineral ein, um zu sehen, wo es vorkommt, gruppiert nach Sternensystem, oder einen Ort, um seine Mineralien zu sehen. Hake ein Mineral ab, oder **Bergung** unten in der Liste, um danach Ausschau zu halten: Die Scan-Anzeige weist dich darauf hin, wenn ein Scan es findet. Der Decoder lässt sich auch hier ein- und ausschalten. - **Herstellung**: Gib ein Mineral ein, um zu sehen, welche Gegenstände es verwenden, oder einen Gegenstand, um die benötigten Mineralien zu sehen. Wird gefüllt, wenn du Erweiterungen mit aktiviertem **Commodities** oder **Journal** erstellst. diff --git a/languages/german/LEGAL.md b/languages/german/LEGAL.md index c211cb73..d1eea512 100644 --- a/languages/german/LEGAL.md +++ b/languages/german/LEGAL.md @@ -48,6 +48,17 @@ Smart Citizen stellt ausgehende Netzwerkanfragen nur in vier Fällen: - **Benutzerdefinierte Remote-Quellen** — Wenn du im Konfiguration-Tab eine Datenquelle konfiguriert hast, die auf eine `http(s)://`-URL verweist, ruft Smart Citizen diese URL beim Aktualisieren von Quelldateien ab. Standardmäßig gilt dies nur für die GitHub-Raw-URL-Form der `global`-Quelle; die Standardkonfiguration liest seit v1.0 stattdessen `base.ini` aus deiner lokalen Data.p4k-Extraktion. - **Shopliste der SCO-Gegenstandssuche** — Solange das Overlay mit eingeschalteter Gegenstandssuche läuft, lädt Smart Citizen die Liste der Shops und Gegenstandspreise von der [UEX](https://uexcorp.space)-API (`api.uexcorp.uk`), höchstens alle 12 Stunden. Es sind zwei einfache Anfragen, die nur den Namen und die Version der App mitsenden; nichts von deinem Rechner wird gesendet. Die Liste wird lokal zwischengespeichert. Schalte die Gegenstandssuche im Overlay-Tab aus, um das zu beenden. +### Das Smart-Citizen-Overlay + +Das Overlay ist aus, bis du es startest. Während es läuft, bleibt alles, was es liest, auf deinem Computer: + +- **Bildschirm** — es nimmt einen kleinen Bereich um die Anzeige des Bergbau-Scanners auf, um die Signalzahl zu lesen. Die Aufnahmen werden im Speicher gelesen und nicht gespeichert. +- **Game.log** — es liest das Log von Star Citizen, um Baupläne zu finden, die du erhältst. +- **Windows** — es fragt Windows, welches Fenster im Vordergrund ist und ob der Mauszeiger sichtbar ist, damit die Schublade deine Klicks beim Zielen zum Spiel durchlässt. +- **Tastenkürzel der Schublade** — nur wenn du eins festlegst. Während Star Citizen im Vordergrund ist, fragt es Windows, ob die Taste des Kürzels gedrückt ist, und die Tasten Strg, Alt, Umschalt und Win nur dann, wenn sie es ist. Es fragt nach keiner anderen Taste und empfängt nie, was du tippst. + +Es liest nie den Speicher des Spiels, hängt sich nie ins Spiel ein und schleust nichts ein, und es sendet nie Eingaben an das Spiel. + ### Was Smart Citizen **nicht** tut - Keine Telemetrie, Analyse oder Nutzungsberichte jeglicher Art. diff --git a/languages/german/ui.json b/languages/german/ui.json index cfc93dfb..8addebee 100644 --- a/languages/german/ui.json +++ b/languages/german/ui.json @@ -2992,6 +2992,14 @@ "ht": "", "at": "Smart Citizen konnte in diesem Ordner keinen Arbeitsordner verwenden:\n{folder}\n\n{reason}\n\nDie Extraktion wurde nicht gestartet, daher wurde nichts geändert." }, + "contract_scan_failed": { + "ht": "", + "at": "Die Erzeugung der Erweiterungen wurde gestoppt, weil {skipped} von {total} Aufträgen nicht gelesen werden konnten. Deine vorhandenen Erweiterungen bleiben unverändert. Bitte melde das, denn meist liegt es an einem Fehler in Smart Citizen.\n\nDer erste Auftrag:\n{first}" + }, + "contract_scan_stopped": { + "ht": "", + "at": "Die Erzeugung der Erweiterungen wurde gestoppt, weil das Lesen der Aufträge mit einem Fehler abgebrochen ist. Deine vorhandenen Erweiterungen bleiben unverändert. Bitte melde das, denn meist liegt es an einem Fehler in Smart Citizen.\n\nDer Fehler:\n{first}" + }, "cache_folder_refused": { "ht": "", "at": "Windows hat Smart Citizen die Berechtigung verweigert, den DataForge-Cache in diesem Ordner zu erstellen:\n{folder}\n\nDie Extraktion wurde nicht gestartet, daher wurde nichts geändert." @@ -3123,7 +3131,7 @@ }, "description": { "ht": "", - "at": "Schalte um, welche Erweiterungskategorien beim Erstellen ausgeführt werden. Schiffe, Komponenten, Schiffswaffen, FPS-Waffen, Missionen, Missionsbelohnungen, Rohstoffherstellung und medizinische Verbrauchsgüter können jeweils unabhängig aktiviert werden." + "at": "Schalte um, welche Erweiterungskategorien beim Erstellen laufen: Ships, Ship Items, Gear, Missions, Commodities, Journal, Medical Consumables. Ship Items umfasst Komponenten, Schiffswaffen und Raketen; Gear umfasst FPS-Waffen und Rüstungs-Tags. Jede Kategorie lässt sich einzeln ein- oder ausschalten." } }, "enh_favorites": { @@ -3156,24 +3164,24 @@ "at": "Erstelle die eingeklammerten Namens-Tags für Komponenten, Raketen, Schiffswaffen, Rohstoffe und Rüstungen. Elemente mit ▲/▼ neu anordnen, zum Ausschließen deaktivieren, Abkürzungslänge ändern, Trennzeichen und Klammern wählen oder das Tag statt davor dahinter platzieren." } }, - "overlay": { + "blueprint_tracker": { "title": { "ht": "", - "at": "8. Smart Citizen Overlay" + "at": "7. Bauplan-Tracker" }, "description": { "ht": "", - "at": "Starte das Overlay hier oder mit der Overlay-Schaltfläche in der Werkzeugleiste. Über dem Spiel entschlüsselt es Bergbau-Scan-Signaturen, öffnet eine Schublade zum Durchsuchen deiner Baupläne, Mineralien und Herstellung und markiert Baupläne, die du erhältst, als besessen. Starte das Spiel im randlosen Fenstermodus auf deinem Hauptbildschirm." + "at": "Markiere die Baupläne, die du besitzt. Durchsuche die linke Liste nach Name oder Mission, oder grenze sie nach Komponententyp, Klasse, Größe und Grad ein, und verschiebe dann mit den Pfeilen Gegenstände in deine Besessen-Liste. Besessene Baupläne erhalten ein [Owned]-Tag, wo immer sie in den möglichen Belohnungen einer Mission erscheinen, damit du auf einen Blick siehst, was sich zu verfolgen lohnt." } }, - "blueprint_tracker": { + "overlay": { "title": { "ht": "", - "at": "7. Bauplan-Tracker" + "at": "8. Smart Citizen Overlay" }, "description": { "ht": "", - "at": "Markiere die Baupläne, die du besitzt. Durchsuche die linke Liste nach Name oder Mission, oder grenze sie nach Komponententyp, Klasse, Größe und Grad ein, und verschiebe dann mit den Pfeilen Gegenstände in deine Besessen-Liste. Besessene Baupläne erhalten ein [Owned]-Tag, wo immer sie in den möglichen Belohnungen einer Mission erscheinen, damit du auf einen Blick siehst, was sich zu verfolgen lohnt." + "at": "Starte das Overlay hier oder mit der Overlay-Schaltfläche in der Werkzeugleiste. Über dem Spiel entschlüsselt es Bergbau-Scan-Signaturen, öffnet eine Schublade zum Durchsuchen deiner Baupläne, Mineralien und Herstellung und markiert Baupläne, die du erhältst, als besessen. Starte das Spiel im randlosen Fenstermodus auf deinem Hauptbildschirm." } }, "edit": { @@ -3233,7 +3241,7 @@ }, "description": { "ht": "", - "at": "Wähle das App-Design (Standard / Hell / Dunkel / ODW) und deaktiviere optional die automatische Tour bei neuen Versionen." + "at": "Wähle das App-Design (Standard / Hell / Dunkel / ODW) und die Schriftgröße (Klein / Mittel / Groß, gilt nach einem Neustart) und deaktiviere optional die automatische Tour bei neuen Versionen." } }, "cfg_sc_install": { @@ -3273,13 +3281,33 @@ }, "description": { "ht": "", - "at": "Importiere eine externe INI über den Konfliktlösungsdialog in deine Überschreibungen, oder setze deine user.ini für den aktiven Kanal zurück (wird vor dem Leeren automatisch gesichert)." + "at": "Importiere eine externe INI über den Konfliktdialog in deine Überschreibungen. Setze die user.ini des aktiven Kanals zurück (vorher gesichert) oder hole mit user.ini wiederherstellen eine frühere Kopie zurück. Die Vorschau zeigt, was Anwenden schreiben würde, und Nach Updates suchen prüft auf eine neue Version." + } + }, + "cfg_backup": { + "title": { + "ht": "", + "at": "19. Konfiguration: Einstellungssicherung" + }, + "description": { + "ht": "", + "at": "Einstellungen exportieren speichert deine Einstellungen, Tag-Konfigurationen, deinen Star Citizen-Ordner und deine eigenen Texte aller Kanäle in einer Datei. Einstellungen importieren holt sie zurück, auf einem neuen PC oder nach einer Neuinstallation." + } + }, + "cfg_sc_tools": { + "title": { + "ht": "", + "at": "20. Konfiguration: Star Citizen-Werkzeuge" + }, + "description": { + "ht": "", + "at": "Shader-Cache leeren listet die Shader-Cache-Ordner des Spiels auf, einen pro Spielversion. Bereinigen löscht die Shader und behält deine Grafikeinstellungen; Entfernen löscht den ganzen Ordner. Schließe Star Citizen vorher." } }, "help": { "title": { "ht": "", - "at": "19. Hilfe & Feedback" + "at": "21. Hilfe & Feedback" }, "description": { "ht": "", @@ -3590,7 +3618,7 @@ }, "desc": { "ht": "", - "at": "Fenster über Star Citizen: der Bergbau-Scan-Decoder und die Bauplan-Schublade. Starte das Spiel im randlosen Fenstermodus. Das Overlay liest nur deinen Bildschirm und Game.log und achtet, wenn du ein Tastenkürzel für die Schublade festlegst, auf Tastendrücke für genau diese Kombination; den Spielprozess berührt es nie." + "at": "Fenster über Star Citizen: der Bergbau-Scan-Decoder und die Bauplan-Schublade. Starte das Spiel im randlosen Fenstermodus. Das Overlay liest nur deinen Bildschirm und Game.log, fragt Windows, welches Fenster im Vordergrund ist und ob der Zeiger sichtbar ist, und, wenn du ein Tastenkürzel für die Schublade festlegst, ob seine Taste und die Tasten Strg, Alt, Umschalt und Win gedrückt sind; den Spielprozess berührt es nie." }, "start_btn": { "ht": "", diff --git a/languages/italian/ABOUT.md b/languages/italian/ABOUT.md index 71b6048b..99ad2f79 100644 --- a/languages/italian/ABOUT.md +++ b/languages/italian/ABOUT.md @@ -29,6 +29,7 @@ Grazie a chi ha contribuito al codice di Smart Citizen: - **scubamount** - **hkstrongside** - **odw-okano** +- **RWolfyo** ## Traduttori @@ -113,7 +114,7 @@ I testi di gioco in lingue diverse dall'inglese sono traduzioni della community: - **Titoli di missione**: fai precedere i titoli di trasporto dal loro percorso (es. `Area18 > Lorville`) — posizionamento, freccia, separatore e livello di dettaglio della località configurabili, più un accorciamento opzionale dei titoli originali, con anteprima live - **Statistiche sopra o sotto**: scegli se il blocco statistiche si trova in cima o in fondo alla descrizione - **Tracciatore Blueprint**: una scheda dedicata per contrassegnare i blueprint di crafting che possiedi già. Sposta gli elementi tra Disponibili e Posseduti, filtra per Missione / Tipo / Classe / Dimensione / Grado, e gli oggetti posseduti ottengono un tag blu `[Owned]` negli elenchi di blueprint delle missioni. **Analizza i log per i blueprint posseduti** popola automaticamente la proprietà dai tuoi file di log di Star Citizen, importando solo le novità dall'ultima analisi (o automaticamente all'avvio, quando **Analizza automaticamente i log all'avvio** è attivo), ed **Esporta / Importa blueprint posseduti** sposta la lista dei posseduti tra PC (JSON o CSV; le importazioni si limitano ad aggiungere, e funzionano anche le esportazioni da scmdb.net) -- **Overlay di Smart Citizen**: finestre opzionali sopra il gioco (in modalità finestra senza bordi). Un decodificatore delle scansioni minerarie mostra il giacimento dietro una firma (`3 × Lindinium`) e può illuminarsi, lampeggiare o suonare per i minerali o il recupero che tieni d'occhio; un cassetto, con la sua scorciatoia, cerca tra i tuoi blueprint, dove si trovano i minerali e cosa permettono di fabbricare; e mentre è in esecuzione i blueprint che ottieni vengono segnati come posseduti a partire da `Game.log`. Solo pixel dello schermo, `Game.log` e una scorciatoia opzionale: nessuna iniezione, nessuna lettura della memoria, nessun input +- **Overlay di Smart Citizen**: finestre opzionali sopra il gioco (in modalità finestra senza bordi). Un decodificatore delle scansioni minerarie mostra il giacimento dietro una firma (`3 × Lindinium`) e può illuminarsi, lampeggiare o suonare per i minerali o il recupero che tieni d'occhio; un cassetto, con la sua scorciatoia, cerca tra i tuoi blueprint, dove si trovano i minerali e cosa permettono di fabbricare; e mentre è in esecuzione i blueprint che ottieni vengono segnati come posseduti a partire da `Game.log`. Solo pixel dello schermo, `Game.log`, la finestra in primo piano, la visibilità del puntatore e una scorciatoia opzionale: nessuna iniezione, nessuna lettura della memoria, nessun input - **Etichette di missione**: rinomina le intestazioni di sezione (MISSION DETAILS, POTENTIAL BLUEPRINTS, ecc.), l'etichetta dell'XP e il tag di enfasi usato per le intestazioni - **Patch dichiarative per i bug di dati CIG**: un sistema di patch applica correzioni a bug DataForge noti al momento dell'estrazione, così il testo in gioco risulta corretto senza dover attendere CIG - **Categorie selettive**: attiva o disattiva ogni categoria di miglioramento in modo indipendente dalla scheda Miglioramenti diff --git a/languages/italian/FAQ.md b/languages/italian/FAQ.md index 4cb08a6f..0be28fdb 100644 --- a/languages/italian/FAQ.md +++ b/languages/italian/FAQ.md @@ -15,7 +15,7 @@ Le tue modifiche personali si trovano in `user.ini`, nella cartella dati di Smar Smart Citizen modifica solo il testo di localizzazione (le parole che il gioco ti mostra): non tocca la logica di gioco, non ti dà alcun vantaggio e non comunica con i server di CIG. Le nostre modifiche **dovrebbero** essere tranquille. -L'**Overlay di Smart Citizen** opzionale (scheda Overlay) funziona allo stesso modo, senza mettere mano al gioco. Disegna normali finestre sopra il gioco, legge i pixel del tuo schermo come fa uno strumento per screenshot e legge il file `Game.log` del gioco. Non si inietta mai nel gioco né si aggancia a esso, non apre mai il processo del gioco né ne legge la memoria, e non invia mai input da tastiera o mouse. Se imposti una scorciatoia per il cassetto, registra presso Windows solo quella combinazione di tasti, nel modo standard con cui un programma chiede una scorciatoia. Star Citizen blocca le scorciatoie registrate da altri programmi mentre ha il focus, quindi, finché una scorciatoia è impostata, l'overlay riceve anche l'input grezzo della tastiera (raw input), il modo in sola lettura con cui Windows informa un programma in background dei tasti premuti. Non è un hook della tastiera: non trattiene, non modifica e non invia alcun tasto, non registra nulla e reagisce solo alla tua combinazione. CIG non si è espressa su overlay di questo tipo, quindi vale anche qui l'avvertenza sull'uso a tuo rischio riportata più sotto. +L'**Overlay di Smart Citizen** opzionale (scheda Overlay) funziona allo stesso modo, senza mettere mano al gioco. Disegna normali finestre sopra il gioco, legge i pixel del tuo schermo come fa uno strumento per screenshot e legge il file `Game.log` del gioco. Mentre il cassetto è visibile, chiede anche a Windows quale finestra è in primo piano e se il puntatore del mouse è visibile, così i tuoi colpi attraversano il cassetto mentre miri. Non si inietta mai nel gioco né si aggancia a esso, non apre mai il processo del gioco né ne legge la memoria, e non invia mai input da tastiera o mouse. Se imposti una scorciatoia per il cassetto, registra presso Windows solo quella combinazione di tasti, nel modo standard con cui un programma chiede una scorciatoia. Star Citizen blocca le scorciatoie registrate da altri programmi mentre ha il focus, quindi, mentre il gioco è in primo piano, l'overlay chiede anche a Windows se il tasto di quella combinazione è premuto e, solo mentre lo è, se Ctrl, Alt, Maiusc o Win sono tenuti premuti. Non chiede nulla di nessun altro tasto, non riceve mai ciò che digiti nel gioco o in un altro programma e non trattiene, non modifica né invia mai alcun tasto. CIG non si è espressa su overlay di questo tipo, quindi vale anche qui l'avvertenza sull'uso a tuo rischio riportata più sotto. CIG ha sostenuto pubblicamente la localizzazione della community. Il loro post [Community Localization Update](https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/star-citizen-community-localization-update) illustra il supporto ufficiale alle traduzioni create dai giocatori, che a nostro avviso consente esplicitamente il tipo di modifica alla localizzazione fatta da Smart Citizen. diff --git a/languages/italian/HELP.md b/languages/italian/HELP.md index d7b66e4a..ccc77070 100644 --- a/languages/italian/HELP.md +++ b/languages/italian/HELP.md @@ -80,6 +80,8 @@ Il colore del pulsante ti indica a che punto sei: **rosso** significa che qualco Smart Citizen aggiunge anche una piccola filigrana alla stringa di versione del launcher (`Frontend_PU_Version`), aggiungendo `\nLocalizations Enhanced with Smart Citizen v{VERSION}` su una riga propria. È così che puoi confermare in gioco che il tuo loc-pack è attivo — guarda l'etichetta di versione nel menu principale di Star Citizen. La filigrana viene riscritta a ogni applicazione, quindi non si accumula mai tra le versioni. +L'applicazione aggiunge anche una seconda riga al pulsante Gioca del menu principale (`Frontend_play_star_citizen`), `Run Smart Citizen after every patch`, con entrambe le righe centrate. Una patch del gioco lascia al suo posto il `global.ini` applicato, ma le chiavi aggiunte dalla patch compaiono come nomi `@key` grezzi finché non avvii Smart Citizen e applichi di nuovo, quindi il promemoria è nel menu la prima volta che il gioco si avvia dopo una patch. Come la filigrana, viene riscritto a ogni applicazione, e resta in inglese in qualsiasi lingua. + ## 8. Ripristinare un backup Apri il menu **Altro** sulla barra degli strumenti e scegli **Ripristina Backup** per tornare a una versione precedente. Smart Citizen conserva fino a **5 backup automatici** — il più vecchio viene eliminato man mano che se ne creano di nuovi. @@ -166,11 +168,11 @@ Tieni traccia dei blueprint di crafting che possiedi già, e vedi il riscontro i ## Scheda Overlay -L'**Overlay di Smart Citizen** disegna due piccole finestre sopra Star Citizen: un decodificatore delle scansioni minerarie e un cassetto di ricerche. Avvialo e fermalo con **Avvia overlay** in questa scheda o con il pulsante **Overlay** della barra degli strumenti. Esegui il gioco in modalità finestra senza bordi sullo schermo principale, altrimenti l'overlay non può comparire sopra di esso. L'overlay legge solo il tuo schermo e `Game.log` e, se imposti una scorciatoia per il cassetto, osserva i tasti premuti solo per quella combinazione; non tocca mai il gioco in sé. +L'**Overlay di Smart Citizen** disegna due piccole finestre sopra Star Citizen: un decodificatore delle scansioni minerarie e un cassetto di ricerche. Avvialo e fermalo con **Avvia overlay** in questa scheda o con il pulsante **Overlay** della barra degli strumenti. Esegui il gioco in modalità finestra senza bordi sullo schermo principale, altrimenti l'overlay non può comparire sopra di esso. L'overlay legge solo il tuo schermo e `Game.log`, chiede a Windows quale finestra è in primo piano e se il puntatore del mouse è visibile (così i tuoi colpi attraversano il cassetto mentre miri) e, se imposti una scorciatoia per il cassetto, se il suo tasto e i tasti Ctrl, Alt, Maiusc e Win sono premuti; non tocca mai il gioco in sé. - **Decodificatore scansioni minerarie** legge la firma di scansione sotto il tuo radar e mostra subito sotto il tipo di giacimento e la quantità (per esempio `3 × Lindinium`). L'etichetta cambia solo dopo che lo stesso numero è stato letto due volte di fila, così una lettura errata di un singolo fotogramma non la fa lampeggiare. **Dimensione del testo della scansione** rende l'etichetta più piccola o più grande. Un numero tondo come 12,000 può essere materiale di recupero o un giacimento in superficie (estrazione ROC o FPS); il recupero è elencato per primo e gli altri sono segnati come solo in superficie, perché nello spazio può essere solo recupero. - **Quando viene scansionato un minerale osservato o materiale di recupero**: scegli come l'etichetta ti avvisa. **Bagliore** e **Lampeggio** sono attivi per impostazione predefinita; puoi aggiungere **Cambia colore del testo** (verde brillante), **Testo più grande** e **Riproduci un suono**. Il lampeggio e il suono arrivano quando il bersaglio viene letto per la prima volta, non di nuovo mentre resta sullo schermo. Con **Riproduci un suono** attivo, **Suono di avviso** sceglie il suono: **Smart Citizen predefinito** (un breve suono), una voce in inglese (accento statunitense, britannico, australiano, irlandese o nigeriano) o uno dei suoni di Windows, e **Ascolta** lo riproduce. Un suono di Windows segue la combinazione di suoni di Windows: uno impostato su (Nessuno) resta muto. -- **Cassetto dell'overlay** colloca delle sezioni a schede sul bordo dello schermo. Clicca su una scheda per aprirne la sezione, cliccaci di nuovo per chiuderla. **Posizione del cassetto** sceglie uno di otto punti (al centro a destra per impostazione predefinita). **Scorciatoia del cassetto** imposta una combinazione di tasti che apre il cassetto dal gioco sull'ultima sezione usata; premendola di nuovo si chiude. In gioco tieni comunque premuto F per usare il mouse al suo interno, perché Windows non lascia che l'overlay tolga il mouse a Star Citizen. Star Citizen riceve comunque quei tasti, quindi scegli una combinazione che non usi in gioco. Deve contenere Ctrl, Alt o Win, a meno che non sia un tasto F o Pausa. **Cancella** rimuove la scorciatoia. Se un altro programma la usa già, la scheda te lo dice. +- **Cassetto dell'overlay** colloca delle sezioni a schede sul bordo dello schermo. Clicca su una scheda per aprirne la sezione, cliccaci di nuovo per chiuderla. **Posizione del cassetto** sceglie uno di otto punti (al centro a destra per impostazione predefinita). **Scorciatoia del cassetto** imposta una combinazione di tasti che apre il cassetto dal gioco sull'ultima sezione usata; premendola di nuovo si chiude. In gioco tieni comunque premuto F per usare il mouse al suo interno, perché Windows non lascia che l'overlay tolga il mouse a Star Citizen. Star Citizen riceve comunque quei tasti, quindi scegli una combinazione che non usi in gioco. In gioco, tieni premuti i tasti per un attimo: una pressione molto breve, come un pulsante dello Stream Deck senza tempo di pressione, può sfuggire. Se Star Citizen è avviato come amministratore, deve esserlo anche Smart Citizen, altrimenti la scorciatoia non fa nulla in gioco. Deve contenere Ctrl, Alt o Win, a meno che non sia un tasto F o Pausa. **Cancella** rimuove la scorciatoia. Se un altro programma la usa già, la scheda te lo dice. - **Blueprint**: cerca i blueprint, vedi quali missioni li danno come ricompensa e spunta quelli che possiedi (la stessa lista dei posseduti della scheda Tracker Blueprint). - **Minerali**: digita un minerale per vedere dove si trova, raggruppato per sistema stellare, oppure una località per vederne i minerali. Spunta un minerale, o **Recupero** in fondo alla lista, per tenerlo d'occhio: l'etichetta della scansione ti avvisa quando una scansione lo trova. Da qui puoi anche attivare e disattivare il decodificatore. - **Fabbricazione**: digita un minerale per vedere quali oggetti lo usano, oppure un oggetto per vedere i minerali di cui ha bisogno. Si riempie quando generi i miglioramenti con **Commodities** o **Journal** spuntato. diff --git a/languages/italian/LEGAL.md b/languages/italian/LEGAL.md index 20dd0e83..7a8488f1 100644 --- a/languages/italian/LEGAL.md +++ b/languages/italian/LEGAL.md @@ -48,6 +48,17 @@ Smart Citizen effettua richieste di rete in uscita solo in quattro circostanze: - **Fonti remote configurate dall'utente** — Se hai configurato una fonte dati che punta a un URL `http(s)://` nella scheda Config, Smart Citizen recupera quell'URL durante l'aggiornamento dei file di origine. Di base questo riguarda solo la forma URL GitHub-raw della fonte `global`; la configurazione standard a partire dalla v1.0 legge invece `base.ini` dalla tua estrazione locale di Data.p4k. - **Elenco negozi di Cerca oggetti SCO** — Mentre l'overlay è attivo con la sezione Cerca oggetti accesa, Smart Citizen scarica l'elenco dei negozi e dei prezzi dall'API di [UEX](https://uexcorp.space) (`api.uexcorp.uk`), al massimo ogni 12 ore. Sono due semplici richieste che inviano solo il nome e la versione dell'app; nulla del tuo computer viene inviato. L'elenco viene salvato in locale. Disattiva Cerca oggetti nella scheda Overlay per fermarlo. +### L'overlay di Smart Citizen + +L'overlay resta spento finché non lo avvii. Mentre è attivo, tutto ciò che legge rimane sul tuo computer: + +- **Schermo** — cattura una piccola area intorno al display dello scanner minerario per leggere il numero del segnale. Le catture vengono lette in memoria e non salvate. +- **Game.log** — legge il log di Star Citizen per trovare i blueprint che ricevi. +- **Windows** — chiede a Windows quale finestra è in primo piano e se il puntatore del mouse è visibile, così il cassetto lascia passare i tuoi clic al gioco mentre miri. +- **Scorciatoia del cassetto** — solo se ne imposti una. Mentre Star Citizen è in primo piano, chiede a Windows se il tasto della scorciatoia è premuto, e i tasti Ctrl, Alt, Maiusc e Win solo quando lo è. Non chiede di nessun altro tasto e non riceve mai ciò che digiti. + +Non legge mai la memoria del gioco, non si aggancia né si inietta mai nel gioco e non gli invia mai input. + ### Cosa Smart Citizen **non** fa - Nessuna telemetria, analisi o segnalazione di utilizzo di alcun tipo. diff --git a/languages/italian/ui.json b/languages/italian/ui.json index 82433768..5ce898e8 100644 --- a/languages/italian/ui.json +++ b/languages/italian/ui.json @@ -2992,6 +2992,14 @@ "ht": "", "at": "Smart Citizen non è riuscito a usare una cartella di lavoro in:\n{folder}\n\n{reason}\n\nL'estrazione non è stata avviata, quindi non è stato modificato nulla." }, + "contract_scan_failed": { + "ht": "", + "at": "La generazione dei miglioramenti si è interrotta perché {skipped} contratti su {total} non sono stati letti. I miglioramenti esistenti non sono cambiati. Segnalalo, perché di solito è un errore di Smart Citizen.\n\nIl primo contratto:\n{first}" + }, + "contract_scan_stopped": { + "ht": "", + "at": "La generazione dei miglioramenti si è interrotta perché la lettura dei contratti ha dato un errore. I miglioramenti esistenti non sono cambiati. Segnalalo, perché di solito è un errore di Smart Citizen.\n\nL'errore:\n{first}" + }, "cache_folder_refused": { "ht": "", "at": "Windows ha negato a Smart Citizen l'autorizzazione a creare la cache DataForge in:\n{folder}\n\nL'estrazione non è stata avviata, quindi non è stato modificato nulla." @@ -3123,7 +3131,7 @@ }, "description": { "ht": "", - "at": "Attiva o disattiva quali categorie di miglioramenti vengono eseguite quando generi. Navi, componenti, armi delle navi, armi FPS, missioni, ricompense delle missioni, fabbricazione delle merci e beni di consumo medici possono essere abilitati ciascuno in modo indipendente." + "at": "Scegli quali categorie di miglioramenti vengono eseguite con Genera: Ships, Ship Items, Gear, Missions, Commodities, Journal, Medical Consumables. Ship Items comprende componenti, armi di nave e missili; Gear comprende armi FPS e tag delle armature. Ogni categoria si attiva o disattiva separatamente." } }, "enh_favorites": { @@ -3156,24 +3164,24 @@ "at": "Crea i tag tra parentesi aggiunti ai nomi di componenti, missili, armi delle navi, merci e armature. Riordina gli elementi con ▲/▼, deseleziona per escludere, cambia la lunghezza dell'abbreviazione, scegli il separatore e le parentesi, oppure posiziona il tag dopo il nome invece che prima." } }, - "overlay": { + "blueprint_tracker": { "title": { "ht": "", - "at": "8. Overlay di Smart Citizen" + "at": "7. Blueprint Tracker" }, "description": { "ht": "", - "at": "Avvia l'overlay qui o con il pulsante Overlay della barra degli strumenti. Sopra il gioco decodifica le firme delle scansioni minerarie, apre un cassetto per cercare blueprint, minerali e crafting, e segna come posseduti i blueprint che ottieni. Avvia il gioco in modalità finestra senza bordi sullo schermo principale." + "at": "Contrassegna i blueprint che possiedi. Cerca nell'elenco a sinistra per nome o missione, oppure restringilo per Tipo, Classe, Dimensione e Grado del componente, poi usa le frecce per spostare gli elementi nel tuo elenco posseduti. I blueprint posseduti ricevono un tag [Owned] ovunque compaiano tra le possibili ricompense di una missione, così puoi capire a colpo d'occhio cosa vale la pena inseguire." } }, - "blueprint_tracker": { + "overlay": { "title": { "ht": "", - "at": "7. Blueprint Tracker" + "at": "8. Overlay di Smart Citizen" }, "description": { "ht": "", - "at": "Contrassegna i blueprint che possiedi. Cerca nell'elenco a sinistra per nome o missione, oppure restringilo per Tipo, Classe, Dimensione e Grado del componente, poi usa le frecce per spostare gli elementi nel tuo elenco posseduti. I blueprint posseduti ricevono un tag [Owned] ovunque compaiano tra le possibili ricompense di una missione, così puoi capire a colpo d'occhio cosa vale la pena inseguire." + "at": "Avvia l'overlay qui o con il pulsante Overlay della barra degli strumenti. Sopra il gioco decodifica le firme delle scansioni minerarie, apre un cassetto per cercare blueprint, minerali e crafting, e segna come posseduti i blueprint che ottieni. Avvia il gioco in modalità finestra senza bordi sullo schermo principale." } }, "edit": { @@ -3233,7 +3241,7 @@ }, "description": { "ht": "", - "at": "Scegli il tema dell'app (Predefinito / Chiaro / Scuro / ODW) e, facoltativamente, disattiva il tour automatico per le nuove versioni." + "at": "Scegli il tema dell'app (Predefinito / Chiaro / Scuro / ODW) e la dimensione del testo (Piccola / Media / Grande, applicata dopo un riavvio) e, se vuoi, disattiva il tour automatico nelle nuove versioni." } }, "cfg_sc_install": { @@ -3273,13 +3281,33 @@ }, "description": { "ht": "", - "at": "Importa un INI esterno nelle tue sovrascritture tramite la finestra di risoluzione dei conflitti, oppure reimposta il tuo user.ini per il canale attivo (viene eseguito un backup automatico prima dello svuotamento)." + "at": "Importa un INI esterno nelle tue sovrascritture tramite la finestra di risoluzione dei conflitti. Reimposta lo user.ini del canale attivo (con backup prima) o recupera una copia precedente con Ripristina user.ini. L'anteprima mostra cosa scriverebbe Applica, e Controlla aggiornamenti verifica se c'è una nuova versione." + } + }, + "cfg_backup": { + "title": { + "ht": "", + "at": "19. Configurazione: Backup Impostazioni" + }, + "description": { + "ht": "", + "at": "Esporta impostazioni salva preferenze, configurazioni dei tag, cartella di Star Citizen e testi personalizzati di tutti i canali in un unico file. Importa impostazioni li ripristina, su un nuovo PC o dopo un'installazione pulita." + } + }, + "cfg_sc_tools": { + "title": { + "ht": "", + "at": "20. Configurazione: Strumenti di Star Citizen" + }, + "description": { + "ht": "", + "at": "Svuota cache shader elenca le cartelle della cache shader del gioco, una per versione. Pulisci elimina gli shader e mantiene le impostazioni grafiche; Rimuovi elimina l'intera cartella. Chiudi prima Star Citizen." } }, "help": { "title": { "ht": "", - "at": "19. Guida e feedback" + "at": "21. Guida e feedback" }, "description": { "ht": "", @@ -3590,7 +3618,7 @@ }, "desc": { "ht": "", - "at": "Finestre disegnate sopra Star Citizen: il decodificatore delle scansioni minerarie e il cassetto dei blueprint. Avvia il gioco in modalità finestra senza bordi. L'overlay legge solo lo schermo e Game.log e, se imposti una scorciatoia per il cassetto, osserva i tasti premuti solo per quella combinazione; non tocca mai il processo del gioco." + "at": "Finestre disegnate sopra Star Citizen: il decodificatore delle scansioni minerarie e il cassetto dei blueprint. Avvia il gioco in modalità finestra senza bordi. L'overlay legge solo lo schermo e Game.log, chiede a Windows quale finestra è in primo piano e se il puntatore è visibile e, se imposti una scorciatoia per il cassetto, se il suo tasto e i tasti Ctrl, Alt, Maiusc e Win sono premuti; non tocca mai il processo del gioco." }, "start_btn": { "ht": "", diff --git a/languages/japanese/ABOUT.md b/languages/japanese/ABOUT.md index b9e0525d..513ef0b7 100644 --- a/languages/japanese/ABOUT.md +++ b/languages/japanese/ABOUT.md @@ -29,6 +29,7 @@ Smart Citizen にコードを貢献してくださった方々に感謝します - **scubamount** - **hkstrongside** - **odw-okano** +- **RWolfyo** ## 翻訳者 @@ -113,7 +114,7 @@ Smart Citizen は、以下の上流ツールも同梱しています。 - **ミッションタイトル**: 運送タイトルの先頭にルートを表示(例:`Area18 > Lorville`)— 配置、矢印、区切り文字、地点の詳細を設定でき、任意で標準タイトルの短縮も可能。ライブプレビュー付き - **ステータスを上か下に**: ステータスブロックを説明の上部と下部のどちらに置くかを選択 - **ブループリントトラッカー**: すでに所有しているクラフトブループリントをマークする専用タブ。アイテムを Available と Owned の間で移動し、ミッション/タイプ/クラス/サイズ/グレードでフィルタリング。所有済みアイテムには、ミッションのブループリントリストで青い `[Owned]` タグが付きます。**ログから所有ブループリントをスキャン**は、Star Citizen のログファイルから所有状況を自動的に取り込み、前回のスキャン以降の新しいものだけをインポートします(**起動時にログを自動スキャン**が有効な場合は起動時に自動で実行)。**所有ブループリントのエクスポート / インポート**は、所有リストを PC 間で移動します(JSON または CSV。インポートは追加のみで、scmdb.net からのエクスポートも使えます) -- **Smart Citizen オーバーレイ**: ゲームの上に表示される任意のウィンドウ(ボーダーレスウィンドウモード)。採掘スキャンデコーダーがシグネチャの背後にある鉱床(`3 × Lindinium`)を表示し、ウォッチ中の鉱物やサルベージを、光や点滅、音で知らせます。専用のホットキーで開閉できるドロワーでは、ブループリント、鉱物の産出場所、それらでクラフトできるものを検索できます。さらに実行中は、獲得したブループリントが `Game.log` から所有済みとしてマークされます。使うのは画面のピクセルと `Game.log`、任意のホットキーだけで、インジェクション、メモリの読み取り、入力操作は行いません +- **Smart Citizen オーバーレイ**: ゲームの上に表示される任意のウィンドウ(ボーダーレスウィンドウモード)。採掘スキャンデコーダーがシグネチャの背後にある鉱床(`3 × Lindinium`)を表示し、ウォッチ中の鉱物やサルベージを、光や点滅、音で知らせます。専用のホットキーで開閉できるドロワーでは、ブループリント、鉱物の産出場所、それらでクラフトできるものを検索できます。さらに実行中は、獲得したブループリントが `Game.log` から所有済みとしてマークされます。使うのは画面のピクセル、`Game.log`、最前面のウィンドウ、ポインターの表示状態、任意のホットキーだけで、インジェクション、メモリの読み取り、入力操作は行いません - **ミッションラベル**: セクションヘッダー(MISSION DETAILS、POTENTIAL BLUEPRINTS など)、XP ラベル、ヘッダーに使う強調タグの名称を変更 - **宣言的な CIG データバグパッチ**: パッチシステムが、既知の DataForge バグへの修正を抽出時に適用するため、CIG を待たずにゲーム内テキストが正しく読めます - **カテゴリーの選択**: Enhancements タブから、各拡張カテゴリーを個別に有効/無効化 diff --git a/languages/japanese/FAQ.md b/languages/japanese/FAQ.md index 232db217..25d8169e 100644 --- a/languages/japanese/FAQ.md +++ b/languages/japanese/FAQ.md @@ -15,7 +15,7 @@ Smart Citizen はローカライズのテキスト(ゲームが表示する文言)のみを編集し、ゲームのロジックには一切触れず、優位性を与えることもなく、CIG のサーバーと通信することもありません。私たちの変更は**問題ない**はずです。 -オプションの **Smart Citizen オーバーレイ**(オーバーレイタブ)も、同じくゲームに手を加えない方式で動作します。ゲームの上に通常のウィンドウを描画し、スクリーンショットツールと同じように画面のピクセルを読み取り、ゲームの `Game.log` ファイルを読み込みます。ゲームへのインジェクションやフックは一切行わず、ゲームのプロセスを開いたりメモリを読み取ったりすることもなく、キーボードやマウスの入力を送ることもありません。ドロワーのホットキーを設定した場合は、プログラムがホットキーを登録する標準的な方法で、そのキーの組み合わせ 1 つだけを Windows に登録します。Star Citizen はフォーカスがある間、ほかのプログラムが登録したホットキーを止めてしまうため、ホットキーを設定している間は、オーバーレイがキーボードの生入力(Raw Input)も受け取ります。これは、Windows がバックグラウンドのプログラムにキー入力を知らせる読み取り専用の仕組みです。キーボードフックではなく、キーを止めたり変えたり送ったりせず、何も記録せず、設定した組み合わせにだけ反応します。CIG はこのようなオーバーレイについて何も表明していないため、下記と同じく自己責任でのご利用となります。 +オプションの **Smart Citizen オーバーレイ**(オーバーレイタブ)も、同じくゲームに手を加えない方式で動作します。ゲームの上に通常のウィンドウを描画し、スクリーンショットツールと同じように画面のピクセルを読み取り、ゲームの `Game.log` ファイルを読み込みます。ドロワーの表示中は、最前面のウィンドウとマウスポインターが表示されているかも Windows に問い合わせ、照準中の射撃がドロワーを通り抜けるようにします。ゲームへのインジェクションやフックは一切行わず、ゲームのプロセスを開いたりメモリを読み取ったりすることもなく、キーボードやマウスの入力を送ることもありません。ドロワーのホットキーを設定した場合は、プログラムがホットキーを登録する標準的な方法で、そのキーの組み合わせ 1 つだけを Windows に登録します。Star Citizen はフォーカスがある間、ほかのプログラムが登録したホットキーを止めてしまうため、ゲームが最前面にある間は、オーバーレイはその組み合わせのキーが押されているかどうかも Windows に問い合わせ、そのキーが押されている間だけ、Ctrl、Alt、Shift、Win が押されているかどうかを問い合わせます。ほかのキーについては一切問い合わせず、ゲームやほかのプログラムで入力した内容を受け取ることもなく、キーを止めたり変えたり送ったりすることもありません。CIG はこのようなオーバーレイについて何も表明していないため、下記と同じく自己責任でのご利用となります。 CIG はコミュニティによるローカライズを公式に支持しています。彼らの [Community Localization Update](https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/star-citizen-community-localization-update) の投稿では、プレイヤーによる翻訳への公式なサポートが示されており、これは Smart Citizen が行うようなローカライズ編集を明示的に許可していると私たちは理解しています。 diff --git a/languages/japanese/HELP.md b/languages/japanese/HELP.md index 528dd2d4..75486b4c 100644 --- a/languages/japanese/HELP.md +++ b/languages/japanese/HELP.md @@ -80,6 +80,8 @@ Smart Citizen は 2 つのモードのいずれかで開き、いつでも切り Smart Citizen はまた、ランチャーのバージョン文字列(`Frontend_PU_Version`)に小さな透かしを刻印し、`\nLocalizations Enhanced with Smart Citizen v{VERSION}` を独立した行として追加します。これにより、あなたのロックパックが有効になっていることをゲーム内で確認できます — Star Citizen のメインメニューのバージョンラベルを見てください。この刻印は適用のたびに書き直されるため、バージョンをまたいで積み重なることはありません。 +適用時には、メインメニューのプレイボタン(`Frontend_play_star_citizen`)にも 2 行目として `Run Smart Citizen after every patch` を追加し、両方の行を中央揃えにします。ゲームのパッチは適用済みの `global.ini` をそのまま残しますが、パッチで追加されたキーは、Smart Citizen を実行して再度適用するまで生の `@key` 名として表示されます。そのため、パッチ後に初めてゲームを起動したときにも、このリマインダーはメニューに表示されます。刻印と同じく適用のたびに書き直され、どの言語を選んでも英語のままです。 + ## 8. バックアップの復元 ツールバーの **その他** メニューを開き、**バックアップを復元** を選んで以前のバージョンに戻します。Smart Citizen は最大 **5 つの自動バックアップ** を保持します — 新しいものが作成されると、最も古いものが削除されます。 @@ -166,11 +168,11 @@ Config タブの **アップデートを確認** で、いつでも手動で確 ## オーバーレイタブ -**Smart Citizen オーバーレイ** は、Star Citizen の上に 2 つの小さなウィンドウを表示します。採掘スキャンデコーダーと、検索用のドロワーです。このタブの **オーバーレイを開始**、またはツールバーの **オーバーレイ** ボタンで開始・停止します。ゲームはメイン画面でボーダーレスウィンドウモードで実行してください。そうでないと、オーバーレイをゲームの上に表示できません。オーバーレイが読み取るのは画面と `Game.log` だけで、ドロワーのホットキーを設定した場合は、その組み合わせのためだけにキー入力を確認します。ゲーム本体には一切触れません。 +**Smart Citizen オーバーレイ** は、Star Citizen の上に 2 つの小さなウィンドウを表示します。採掘スキャンデコーダーと、検索用のドロワーです。このタブの **オーバーレイを開始**、またはツールバーの **オーバーレイ** ボタンで開始・停止します。ゲームはメイン画面でボーダーレスウィンドウモードで実行してください。そうでないと、オーバーレイをゲームの上に表示できません。オーバーレイが行うのは、画面と `Game.log` の読み取りと、最前面のウィンドウとマウスポインターが表示されているかの Windows への問い合わせ(照準中の射撃がドロワーを通り抜けるようにするため)だけで、ドロワーのホットキーを設定した場合は、そのキーと Ctrl、Alt、Shift、Win が押されているかどうかも問い合わせます。ゲーム本体には一切触れません。 - **採掘スキャンデコーダー** は、レーダーの下にあるスキャンシグネチャを読み取り、そのすぐ下に鉱床の種類と数を表示します(例:`3 × Lindinium`)。同じ数値が 2 回続けて読み取られたときにだけラベルが変わるため、1 フレームだけの読み取りミスでちらつくことはありません。**スキャン文字の大きさ** でラベルを小さくも大きくもできます。12,000 のような切りのよい数値は、サルベージの場合も地表の鉱床(ROC や FPS 採掘)の場合もあります。サルベージを先頭に表示し、ほかは「地表のみ」と示します。宇宙空間ではサルベージしかありえないためです。 - **注目中の鉱物またはサルベージをスキャンしたとき**:ラベルでの知らせ方を選びます。**光らせる** と **点滅** はデフォルトでオンです。**文字色を変える**(明るい緑)、**文字を大きく**、**音を鳴らす** を追加できます。点滅と音は対象を最初に読み取ったときだけで、画面に表示され続けている間は繰り返しません。**音を鳴らす** がオンのときは、**アラート音** で音を選べます:**Smart Citizen 既定**(短いチャイム)、英語の音声(米国・英国・オーストラリア・アイルランド・ナイジェリア)、または Windows のサウンドのどれかで、**試聴** で再生できます。Windows のサウンドは Windows のサウンド設定に従うため、そこで (なし) にしたものは鳴りません。 -- **オーバーレイのドロワー** は、画面の端にタブ付きのセクションを配置します。タブをクリックするとそのセクションが開き、もう一度クリックすると閉じます。**ドロワーの位置** で 8 か所から 1 つを選べます(デフォルトは右側中央)。**ドロワーのホットキー** には、ゲーム中にドロワーを最後に使ったセクションで開くキーの組み合わせを設定します。もう一度押すと閉じます。Windows はオーバーレイが Star Citizen からマウスを奪うことを許さないため、ゲーム中にマウスで操作するには、これまでどおり F を押し続けてください。これらのキーは Star Citizen にも届くので、ゲームで使わない組み合わせを選んでください。F キーと Pause 以外は、Ctrl、Alt、Win のいずれかを含める必要があります。**クリア** でホットキーを外せます。別のプログラムがすでに使っている場合は、タブに表示されます。 +- **オーバーレイのドロワー** は、画面の端にタブ付きのセクションを配置します。タブをクリックするとそのセクションが開き、もう一度クリックすると閉じます。**ドロワーの位置** で 8 か所から 1 つを選べます(デフォルトは右側中央)。**ドロワーのホットキー** には、ゲーム中にドロワーを最後に使ったセクションで開くキーの組み合わせを設定します。もう一度押すと閉じます。Windows はオーバーレイが Star Citizen からマウスを奪うことを許さないため、ゲーム中にマウスで操作するには、これまでどおり F を押し続けてください。これらのキーは Star Citizen にも届くので、ゲームで使わない組み合わせを選んでください。ゲーム中はキーを少しの間押し続けてください。押下時間のない Stream Deck のボタンのように、ごく短い押下は見逃されることがあります。Star Citizen を管理者として実行している場合は、Smart Citizen も管理者として実行しないと、ゲーム中にホットキーが反応しません。F キーと Pause 以外は、Ctrl、Alt、Win のいずれかを含める必要があります。**クリア** でホットキーを外せます。別のプログラムがすでに使っている場合は、タブに表示されます。 - **ブループリント**:ブループリントを検索し、どのミッションの報酬になっているかを確認して、所有しているものにチェックを入れます(ブループリントトラッカータブと同じ所有リストです)。 - **鉱物**:鉱物名を入力すると、それが見つかる場所を星系ごとにまとめて表示し、場所を入力すると、そこで採れる鉱物を表示します。鉱物、またはリスト末尾の **サルベージ** にチェックを入れるとウォッチ対象になり、スキャンで見つかるとスキャンラベルが知らせます。デコーダーのオン/オフもここで切り替えられます。 - **クラフト**:鉱物名を入力すると、それを使うアイテムを表示し、アイテム名を入力すると、必要な鉱物を表示します。**Commodities** または **Journal** にチェックを入れて拡張を生成すると、内容が埋まります。 diff --git a/languages/japanese/LEGAL.md b/languages/japanese/LEGAL.md index 1dc41cb4..262fface 100644 --- a/languages/japanese/LEGAL.md +++ b/languages/japanese/LEGAL.md @@ -50,6 +50,17 @@ Smart Citizen が外部へのネットワークリクエストを行うのは、 - **ユーザーが設定したリモートソース** — Config タブで `http(s)://` URL を指すデータソースを設定している場合、Smart Citizen はソースファイルの更新時にその URL を取得します。標準状態では、これは `global` ソースの GitHub-raw URL 形式にのみ該当します。v1.0 以降の標準構成では、代わりにローカルの Data.p4k 抽出から `base.ini` を読み込みます。 - **SCO アイテム検索のショップリスト** — アイテム検索セクションをオンにしてオーバーレイを実行している間、Smart Citizen はショップとアイテム価格のリストを [UEX](https://uexcorp.space) の API(`api.uexcorp.uk`)から最大 12 時間ごとにダウンロードします。アプリ名とバージョンだけを含む 2 回の単純なリクエストで、お使いのマシンの情報は送信されません。リストはローカルにキャッシュされます。止めるには、オーバーレイタブでアイテム検索をオフにしてください。 +### Smart Citizen オーバーレイ + +オーバーレイは起動するまでオフのままです。動作中に読み取るものはすべてコンピューター内にとどまります。 + +- **画面** — 採掘スキャナーの表示周辺の小さな範囲をキャプチャして、シグナルの数値を読み取ります。キャプチャはメモリ上で読み取るだけで、保存しません。 +- **Game.log** — 受け取ったブループリントを見つけるために Star Citizen のログを読み取ります。 +- **Windows** — 最前面のウィンドウとマウスポインターが表示されているかを Windows に問い合わせ、照準中はドロワーがクリックをゲームに通すようにします。 +- **ドロワーのホットキー** — 設定した場合のみ。Star Citizen が最前面にあるとき、ホットキーのキーが押されているかを Windows に問い合わせ、押されているときだけ Ctrl、Alt、Shift、Win も問い合わせます。ほかのキーは問い合わせず、入力した内容を受け取ることもありません。 + +ゲームのメモリを読み取ることも、ゲームにフックやインジェクトすることも、ゲームに入力を送ることもありません。 + ### Smart Citizen が**しない**こと - いかなる種類のテレメトリー、分析、利用状況レポートも行いません。 diff --git a/languages/japanese/ui.json b/languages/japanese/ui.json index f73d39bc..8ed58f68 100644 --- a/languages/japanese/ui.json +++ b/languages/japanese/ui.json @@ -2992,6 +2992,14 @@ "ht": "", "at": "Smart Citizen が次の場所で作業フォルダーを使用できませんでした:\n{folder}\n\n{reason}\n\n抽出は開始されなかったため、何も変更されていません。" }, + "contract_scan_failed": { + "ht": "", + "at": "{total} 件の契約のうち {skipped} 件を読み取れなかったため、拡張の生成を停止しました。既存の拡張は変更されていません。通常は Smart Citizen の不具合ですので、報告してください。\n\n最初の契約:\n{first}" + }, + "contract_scan_stopped": { + "ht": "", + "at": "契約の読み取りがエラーで止まったため、拡張の生成を停止しました。既存の拡張は変更されていません。通常は Smart Citizen の不具合ですので、報告してください。\n\nエラー:\n{first}" + }, "cache_folder_refused": { "ht": "", "at": "Windows によって、次の場所に DataForge キャッシュを作成するアクセス許可が Smart Citizen に対して拒否されました:\n{folder}\n\n抽出は開始されなかったため、何も変更されていません。" @@ -3123,7 +3131,7 @@ }, "description": { "ht": "", - "at": "「生成」時にどの拡張カテゴリーを実行するかを切り替えます。艦船、コンポーネント、艦船武器、FPS 武器、ミッション、ミッション報酬、商品クラフト、医療消耗品を、それぞれ独立して有効にできます。" + "at": "「生成」時に実行する拡張カテゴリーを切り替えます:Ships, Ship Items, Gear, Missions, Commodities, Journal, Medical Consumables。Ship Items はコンポーネント、艦船武器、ミサイル、Gear は FPS 武器とアーマータグを含みます。各カテゴリーは個別に有効・無効にできます。" } }, "enh_favorites": { @@ -3156,24 +3164,24 @@ "at": "コンポーネント、ミサイル、艦船武器、商品、アーマーに追加される角括弧付きの名称タグを組み立てます。▲/▼ で要素を並べ替え、チェックを外して除外し、省略の長さを変更し、区切り文字と括弧を選び、あるいはタグを名前の前ではなく後ろに配置できます。" } }, - "overlay": { + "blueprint_tracker": { "title": { "ht": "", - "at": "8. Smart Citizen オーバーレイ" + "at": "7. ブループリントトラッカー" }, "description": { "ht": "", - "at": "ここかツールバーのオーバーレイボタンでオーバーレイを開始します。ゲームの上で採掘スキャンのシグネチャーを解読し、ブループリント・鉱物・クラフトを検索するドロワーを開き、入手したブループリントを所有済みにします。ゲームはメイン画面のボーダーレスウィンドウモードで実行してください。" + "at": "所有しているブループリントをマークします。左のリストを名前やミッションで検索するか、コンポーネントのタイプ、クラス、サイズ、グレードで絞り込み、矢印を使って所有リストにアイテムを移動します。所有済みのブループリントは、ミッションの潜在的な報酬に表示される場所すべてで [Owned] タグが付くため、追う価値のあるものが一目でわかります。" } }, - "blueprint_tracker": { + "overlay": { "title": { "ht": "", - "at": "7. ブループリントトラッカー" + "at": "8. Smart Citizen オーバーレイ" }, "description": { "ht": "", - "at": "所有しているブループリントをマークします。左のリストを名前やミッションで検索するか、コンポーネントのタイプ、クラス、サイズ、グレードで絞り込み、矢印を使って所有リストにアイテムを移動します。所有済みのブループリントは、ミッションの潜在的な報酬に表示される場所すべてで [Owned] タグが付くため、追う価値のあるものが一目でわかります。" + "at": "ここかツールバーのオーバーレイボタンでオーバーレイを開始します。ゲームの上で採掘スキャンのシグネチャーを解読し、ブループリント・鉱物・クラフトを検索するドロワーを開き、入手したブループリントを所有済みにします。ゲームはメイン画面のボーダーレスウィンドウモードで実行してください。" } }, "edit": { @@ -3233,7 +3241,7 @@ }, "description": { "ht": "", - "at": "アプリのテーマ(Default / Light / Dark / ODW)を選び、任意で新バージョン時の自動ツアーを無効にできます。" + "at": "アプリのテーマ(Default / Light / Dark / ODW)と文字サイズ(小 / 中 / 大、再起動後に反映)を選び、任意で新バージョン時の自動ツアーを無効にできます。" } }, "cfg_sc_install": { @@ -3273,13 +3281,33 @@ }, "description": { "ht": "", - "at": "競合解決ダイアログを介して外部 INI をオーバーライドにインポートするか、アクティブなチャンネルの user.ini をリセットできます(クリア前に自動的にバックアップされます)。" + "at": "競合解決ダイアログを使って外部の INI をオーバーライドに取り込めます。アクティブチャンネルの user.ini をリセット(事前にバックアップ)したり、「user.ini を復元」で以前のコピーに戻したりできます。プレビューは「適用」で書き込まれる内容を表示し、「アップデートを確認」は新しいバージョンを探します。" + } + }, + "cfg_backup": { + "title": { + "ht": "", + "at": "19. Config:設定バックアップ" + }, + "description": { + "ht": "", + "at": "「設定をエクスポート」は、設定、タグ構成、Star Citizen フォルダー、全チャンネルのカスタム文字列を 1 つのファイルに保存します。「設定をインポート」で、新しい PC やクリーンインストール後に元に戻せます。" + } + }, + "cfg_sc_tools": { + "title": { + "ht": "", + "at": "20. Config:Star Citizen ツール" + }, + "description": { + "ht": "", + "at": "「シェーダーキャッシュを削除」は、ゲームのシェーダーキャッシュフォルダーをビルドごとに一覧表示します。「クリーン」はシェーダーを削除してグラフィック設定を残し、「削除」はフォルダー全体を削除します。先に Star Citizen を終了してください。" } }, "help": { "title": { "ht": "", - "at": "19. ヘルプとフィードバック" + "at": "21. ヘルプとフィードバック" }, "description": { "ht": "", @@ -3590,7 +3618,7 @@ }, "desc": { "ht": "", - "at": "Star Citizen の上に表示するウィンドウです。採掘スキャンのデコーダーとブループリントドロワーを含みます。ゲームはボーダーレスウィンドウモードで起動してください。オーバーレイは画面と Game.log を読むだけで、ドロワーのホットキーを設定した場合は、その組み合わせのためだけにキー入力を確認します。ゲームのプロセスには一切触れません。" + "at": "Star Citizen の上に表示するウィンドウです。採掘スキャンのデコーダーとブループリントドロワーを含みます。ゲームはボーダーレスウィンドウモードで起動してください。オーバーレイは画面と Game.log を読み、最前面のウィンドウとポインターが表示されているかを Windows に問い合わせるだけで、ドロワーのホットキーを設定した場合は、そのキーと Ctrl、Alt、Shift、Win が押されているかどうかも問い合わせます。ゲームのプロセスには一切触れません。" }, "start_btn": { "ht": "", diff --git a/languages/korean/ABOUT.md b/languages/korean/ABOUT.md index 4f499811..aa307eb5 100644 --- a/languages/korean/ABOUT.md +++ b/languages/korean/ABOUT.md @@ -29,6 +29,7 @@ Smart Citizen에 코드로 기여해 주신 분들께 감사드립니다: - **scubamount** - **hkstrongside** - **odw-okano** +- **RWolfyo** ## 번역가 @@ -113,7 +114,7 @@ Smart Citizen은 다음의 업스트림 도구도 함께 번들로 제공합니 - **임무 제목**: 운송 제목을 경로로 시작하게 합니다(예: `Area18 > Lorville`). 배치, 화살표, 구분 기호, 위치 세부 정보를 사용자 지정할 수 있으며, 선택적인 기본 제목 축약과 실시간 미리보기도 제공됩니다 - **통계 위/아래**: 통계 블록이 설명의 위에 위치할지 아래에 위치할지 선택하세요 - **설계도 추적기**: 이미 보유한 제작 설계도를 표시하는 전용 탭입니다. 사용 가능/보유 사이에서 항목을 이동하고, 임무/유형/등급/크기/품급으로 필터링하며, 보유한 항목은 임무 설계도 목록에서 파란색 `[보유 중]` 태그를 받습니다. **보유 설계도를 위해 로그 스캔**은 Star Citizen 로그 파일에서 소유 여부를 자동으로 채우며, 마지막 스캔 이후 새로 발견된 것만 가져옵니다(**시작 시 로그 자동 스캔**이 켜져 있으면 시작 시 자동으로). **보유 설계도 내보내기/가져오기**는 보유 목록을 PC 간에 옮깁니다(JSON 또는 CSV; 가져오기는 항상 추가만 하며, scmdb.net 내보내기도 사용 가능) -- **Smart Citizen 오버레이**: 게임 위에 띄우는 선택적 창입니다(테두리 없는 창 모드). 채굴 스캔 해독기는 신호 뒤에 있는 매장물(`3 × Lindinium`)을 보여 주고 감시 중인 광물이나 인양물이 발견되면 빛나기, 깜박이기, 소리로 알릴 수 있습니다. 전용 단축키로 여닫는 서랍에서는 설계도, 광물이 발견되는 위치, 광물로 무엇을 제작하는지 검색할 수 있으며, 실행 중에는 획득한 설계도가 `Game.log`를 통해 보유로 표시됩니다. 화면 픽셀, `Game.log`, 선택적 단축키만 사용합니다: 코드 주입, 메모리 읽기, 입력 전송 없음 +- **Smart Citizen 오버레이**: 게임 위에 띄우는 선택적 창입니다(테두리 없는 창 모드). 채굴 스캔 해독기는 신호 뒤에 있는 매장물(`3 × Lindinium`)을 보여 주고 감시 중인 광물이나 인양물이 발견되면 빛나기, 깜박이기, 소리로 알릴 수 있습니다. 전용 단축키로 여닫는 서랍에서는 설계도, 광물이 발견되는 위치, 광물로 무엇을 제작하는지 검색할 수 있으며, 실행 중에는 획득한 설계도가 `Game.log`를 통해 보유로 표시됩니다. 화면 픽셀, `Game.log`, 맨 앞에 있는 창, 포인터 표시 여부, 선택적 단축키만 사용합니다: 코드 주입, 메모리 읽기, 입력 전송 없음 - **임무 레이블**: 섹션 제목(임무 세부 정보, 잠재적 설계도 등), 경험치 레이블, 제목에 사용되는 강조 태그의 이름을 바꾸세요 - **선언적 CIG 데이터 오류 패치**: 패치 시스템이 추출 시점에 알려진 DataForge 오류에 대한 수정을 적용하여, CIG를 기다리지 않고도 게임 내 텍스트가 올바르게 표시됩니다 - **선택적 카테고리**: 강화 탭에서 각 강화 카테고리를 독립적으로 활성화하거나 비활성화하세요 diff --git a/languages/korean/FAQ.md b/languages/korean/FAQ.md index 0c809604..a631d47f 100644 --- a/languages/korean/FAQ.md +++ b/languages/korean/FAQ.md @@ -15,7 +15,7 @@ Smart Citizen은 현지화 텍스트(게임이 보여주는 단어)만 편집할 뿐, 게임 로직에는 손대지 않고, 어떤 이점도 주지 않으며, CIG 서버와 통신하지 않습니다. 저희의 변경 사항은 **문제없어야** 합니다. -선택 기능인 **Smart Citizen 오버레이**(오버레이 탭)도 똑같이 게임에 손대지 않는 방식으로 작동합니다. 게임 위에 일반 창을 띄우고, 스크린샷 도구처럼 화면의 픽셀을 읽으며, 게임의 `Game.log` 파일을 읽습니다. 게임에 코드를 주입하거나 후킹하지 않고, 게임 프로세스를 열거나 메모리를 읽지 않으며, 키보드나 마우스 입력을 보내지도 않습니다. 서랍 단축키를 설정하면 프로그램이 단축키를 요청하는 표준 방식으로 그 키 조합 하나만 Windows에 등록합니다. Star Citizen은 포커스가 있는 동안 다른 프로그램이 등록한 단축키를 막기 때문에, 단축키가 설정되어 있는 동안 오버레이는 키보드의 원시 입력(Raw Input)도 받습니다. 이는 Windows가 백그라운드 프로그램에 키 입력을 알려 주는 읽기 전용 방식입니다. 키보드 후킹이 아니며, 어떤 키도 붙잡거나 바꾸거나 보내지 않고, 아무것도 기록하지 않으며, 설정한 조합에만 반응합니다. CIG는 이런 오버레이에 대해 아무런 입장도 밝힌 적이 없으므로, 아래의 본인 책임 안내가 똑같이 적용됩니다. +선택 기능인 **Smart Citizen 오버레이**(오버레이 탭)도 똑같이 게임에 손대지 않는 방식으로 작동합니다. 게임 위에 일반 창을 띄우고, 스크린샷 도구처럼 화면의 픽셀을 읽으며, 게임의 `Game.log` 파일을 읽습니다. 서랍이 표시되어 있는 동안에는 어떤 창이 맨 앞에 있는지와 마우스 포인터가 보이는지도 Windows에 물어, 조준하는 동안 사격이 서랍을 통과하게 합니다. 게임에 코드를 주입하거나 후킹하지 않고, 게임 프로세스를 열거나 메모리를 읽지 않으며, 키보드나 마우스 입력을 보내지도 않습니다. 서랍 단축키를 설정하면 프로그램이 단축키를 요청하는 표준 방식으로 그 키 조합 하나만 Windows에 등록합니다. Star Citizen은 포커스가 있는 동안 다른 프로그램이 등록한 단축키를 막기 때문에, 게임이 맨 앞에 있는 동안 오버레이는 그 조합의 키가 눌려 있는지도 Windows에 묻고, 그 키가 눌려 있는 동안에만 Ctrl, Alt, Shift, Win이 눌려 있는지 묻습니다. 다른 키에 대해서는 전혀 묻지 않고, 게임이나 다른 프로그램에서 입력하는 내용을 받지도 않으며, 어떤 키도 붙잡거나 바꾸거나 보내지 않습니다. CIG는 이런 오버레이에 대해 아무런 입장도 밝힌 적이 없으므로, 아래의 본인 책임 안내가 똑같이 적용됩니다. CIG는 커뮤니티 현지화를 공개적으로 지지해 왔습니다. [Community Localization Update](https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/star-citizen-community-localization-update) 게시물은 플레이어가 만든 번역에 대한 공식 지원을 명시하고 있으며, 저희는 이것이 Smart Citizen이 수행하는 방식의 현지화 편집을 명시적으로 허용하는 것으로 이해하고 있습니다. diff --git a/languages/korean/HELP.md b/languages/korean/HELP.md index 81225ca7..e3c7296f 100644 --- a/languages/korean/HELP.md +++ b/languages/korean/HELP.md @@ -80,6 +80,8 @@ Smart Citizen은 두 모드 중 하나로 열리며, 언제든지 전환할 수 Smart Citizen은 또한 런처 버전 문자열(`Frontend_PU_Version`)에 작은 워터마크를 남깁니다. 자체 줄에 `\nLocalizations Enhanced with Smart Citizen v{VERSION}`을 추가합니다. 이를 통해 현지화 패키지가 활성화되어 있는지 게임 내에서 확인할 수 있습니다. Star Citizen 메인 메뉴의 버전 레이블을 보세요. 이 워터마크는 적용할 때마다 다시 작성되므로 버전이 바뀌어도 계속 쌓이지 않습니다. +적용할 때 Smart Citizen은 메인 메뉴의 플레이 버튼(`Frontend_play_star_citizen`)에도 두 번째 줄로 `Run Smart Citizen after every patch`를 추가하고, 두 줄을 모두 가운데 정렬합니다. 게임 패치는 적용된 `global.ini`를 그대로 두지만, 패치로 추가된 키는 Smart Citizen을 실행해 다시 적용할 때까지 `@key` 이름 그대로 표시됩니다. 그래서 패치 후 게임을 처음 시작할 때도 이 알림이 메뉴에 표시됩니다. 워터마크와 마찬가지로 적용할 때마다 다시 작성되며, 어떤 언어를 선택해도 영어로 표시됩니다. + ## 8. 백업 복원하기 이전 버전으로 되돌리려면 도구 모음의 **더 보기** 메뉴를 열고 **백업 복원**을 선택하세요. Smart Citizen은 최대 **5개의 자동 백업**을 유지하며, 새 백업이 생성될 때마다 가장 오래된 것이 삭제됩니다. @@ -166,11 +168,11 @@ Smart Citizen은 시작할 때마다 새 버전이 있는지 확인합니다. ## 오버레이 탭 -**Smart Citizen 오버레이**는 Star Citizen 위에 작은 창 두 개를 띄웁니다: 채굴 스캔 해독기와 검색 서랍입니다. 이 탭의 **오버레이 시작** 또는 도구 모음의 **오버레이** 버튼으로 시작하고 중지합니다. 게임은 주 화면에서 테두리 없는 창 모드로 실행하세요. 그렇지 않으면 오버레이가 게임 위에 표시되지 않습니다. 오버레이는 화면과 `Game.log`만 읽고, 서랍 단축키를 설정하면 그 조합 하나만을 위해 키 입력을 살피며, 게임 자체에는 절대 손대지 않습니다. +**Smart Citizen 오버레이**는 Star Citizen 위에 작은 창 두 개를 띄웁니다: 채굴 스캔 해독기와 검색 서랍입니다. 이 탭의 **오버레이 시작** 또는 도구 모음의 **오버레이** 버튼으로 시작하고 중지합니다. 게임은 주 화면에서 테두리 없는 창 모드로 실행하세요. 그렇지 않으면 오버레이가 게임 위에 표시되지 않습니다. 오버레이는 화면과 `Game.log`만 읽고, 어떤 창이 맨 앞에 있는지와 마우스 포인터가 보이는지를 Windows에 묻고(조준하는 동안 사격이 서랍을 통과하도록), 서랍 단축키를 설정하면 그 키와 Ctrl, Alt, Shift, Win 키가 눌려 있는지도 물으며, 게임 자체에는 절대 손대지 않습니다. - **채굴 스캔 해독기**는 레이더 아래의 스캔 신호를 읽고, 그 바로 아래에 매장물 종류와 개수를 표시합니다(예: `3 × Lindinium`). 같은 숫자가 연속으로 두 번 읽힌 후에만 레이블이 바뀌므로, 한 프레임 동안 잘못 읽혀도 표시가 깜박이지 않습니다. **스캔 글자 크기**로 레이블을 작게 또는 크게 할 수 있습니다. 12,000 같은 딱 떨어지는 숫자는 인양물일 수도, 지표 매장물(ROC 또는 FPS 채굴)일 수도 있습니다. 인양물이 맨 앞에 나오고 나머지는 지표 전용으로 표시됩니다. 우주에서는 인양물만 가능하기 때문입니다. - **관심 광물이나 인양물이 스캔되면**: 레이블이 알려 주는 방식을 고릅니다. **빛나기**와 **깜박이기**가 기본으로 켜져 있고, **글자 색 바꾸기**(밝은 초록색), **글자 크게**, **소리 재생**을 더할 수 있습니다. 깜박임과 소리는 대상을 처음 읽을 때만 나오며, 화면에 계속 보이는 동안에는 반복되지 않습니다. **소리 재생**이 켜져 있으면 **알림 소리**에서 소리를 고릅니다: **Smart Citizen 기본값**(짧은 차임), 영어 음성(미국, 영국, 호주, 아일랜드, 나이지리아 억양) 또는 Windows 소리 중 하나이며, **미리 듣기**로 재생해 볼 수 있습니다. Windows 소리는 Windows 소리 구성표를 따르므로 그곳에서 (없음)으로 설정된 소리는 울리지 않습니다. -- **오버레이 서랍**은 화면 가장자리에 탭으로 나뉜 섹션을 배치합니다. 탭을 클릭하면 해당 섹션이 열리고, 다시 클릭하면 닫힙니다. **서랍 위치**에서 여덟 곳 중 하나를 선택합니다(기본값은 오른쪽 가운데). **서랍 단축키**는 게임 중에 서랍을 마지막으로 쓴 섹션으로 여는 키 조합을 정합니다. 다시 누르면 닫힙니다. Windows가 오버레이에 Star Citizen의 마우스를 넘겨주지 않으므로, 게임 중에 마우스로 쓰려면 지금처럼 F를 누르고 있으세요. Star Citizen도 이 키를 그대로 받으므로, 게임에서 쓰지 않는 조합을 고르세요. F 키와 Pause가 아니면 Ctrl, Alt 또는 Win이 들어가야 합니다. **지우기**를 누르면 단축키가 지워집니다. 다른 프로그램이 이미 쓰고 있으면 탭에 표시됩니다. +- **오버레이 서랍**은 화면 가장자리에 탭으로 나뉜 섹션을 배치합니다. 탭을 클릭하면 해당 섹션이 열리고, 다시 클릭하면 닫힙니다. **서랍 위치**에서 여덟 곳 중 하나를 선택합니다(기본값은 오른쪽 가운데). **서랍 단축키**는 게임 중에 서랍을 마지막으로 쓴 섹션으로 여는 키 조합을 정합니다. 다시 누르면 닫힙니다. Windows가 오버레이에 Star Citizen의 마우스를 넘겨주지 않으므로, 게임 중에 마우스로 쓰려면 지금처럼 F를 누르고 있으세요. Star Citizen도 이 키를 그대로 받으므로, 게임에서 쓰지 않는 조합을 고르세요. 게임에서는 키를 잠깐 누르고 계세요. 누르는 시간이 없는 Stream Deck 버튼처럼 아주 짧게 누르면 놓칠 수 있습니다. Star Citizen을 관리자로 실행한다면 Smart Citizen도 관리자로 실행해야 게임에서 단축키가 작동합니다. F 키와 Pause가 아니면 Ctrl, Alt 또는 Win이 들어가야 합니다. **지우기**를 누르면 단축키가 지워집니다. 다른 프로그램이 이미 쓰고 있으면 탭에 표시됩니다. - **설계도**: 설계도를 검색하고, 어떤 임무가 그 설계도를 보상으로 주는지 확인하고, 보유한 것을 체크합니다(설계도 추적기 탭과 같은 보유 목록). - **광물**: 광물을 입력하면 그 광물이 발견되는 곳을 항성계별로 묶어 보여 주고, 위치를 입력하면 그곳의 광물을 보여 줍니다. 광물이나 목록 맨 아래의 **인양**을 체크하면 감시 대상이 되어, 스캔에서 발견될 때 스캔 레이블이 알려 줍니다. 여기서 해독기를 켜고 끌 수도 있습니다. - **제작**: 광물을 입력하면 그 광물을 사용하는 아이템을, 아이템을 입력하면 그 아이템에 필요한 광물을 보여 줍니다. **Commodities** 또는 **Journal**을 체크하고 강화를 생성하면 채워집니다. diff --git a/languages/korean/LEGAL.md b/languages/korean/LEGAL.md index 2477b263..5e5dfa98 100644 --- a/languages/korean/LEGAL.md +++ b/languages/korean/LEGAL.md @@ -48,6 +48,17 @@ Smart Citizen은 다음 네 가지 상황에서만 외부로 나가는 네트워 - **사용자 구성 원격 소스** — 설정 탭에서 `http(s)://` URL을 가리키는 데이터 소스를 구성한 경우, Smart Citizen은 소스 파일을 새로 고칠 때 해당 URL을 가져옵니다. 기본 설정에서는 이는 `global` 소스의 GitHub-raw URL 형태에만 적용되며, v1.0부터 표준 구성은 대신 로컬 Data.p4k 추출에서 `base.ini`를 읽습니다. - **SCO 아이템 찾기 상점 목록** — 아이템 찾기 섹션을 켠 상태로 오버레이가 실행되는 동안 Smart Citizen은 [UEX](https://uexcorp.space) API(`api.uexcorp.uk`)에서 상점과 아이템 가격 목록을 최대 12시간마다 내려받습니다. 앱 이름과 버전만 담은 단순한 요청 두 개이며, 컴퓨터의 정보는 전송되지 않습니다. 목록은 로컬에 캐시됩니다. 중지하려면 오버레이 탭에서 아이템 찾기를 끄세요. +### Smart Citizen 오버레이 + +오버레이는 직접 시작하기 전까지 꺼져 있습니다. 실행 중에 읽는 모든 것은 컴퓨터에 남습니다. + +- **화면** — 채굴 스캐너 표시 주변의 작은 영역을 캡처해 신호 숫자를 읽습니다. 캡처는 메모리에서만 읽고 저장하지 않습니다. +- **Game.log** — 받은 설계도를 찾기 위해 Star Citizen의 로그를 읽습니다. +- **Windows** — 어떤 창이 맨 앞에 있는지와 마우스 포인터가 보이는지를 Windows에 물어, 조준하는 동안 서랍이 클릭을 게임으로 통과시키게 합니다. +- **서랍 단축키** — 설정한 경우에만. Star Citizen이 맨 앞에 있을 때 단축키의 키가 눌려 있는지 Windows에 묻고, 눌려 있을 때만 Ctrl, Alt, Shift, Win 키를 묻습니다. 다른 키는 묻지 않으며 입력한 내용을 받지 않습니다. + +게임 메모리를 읽거나, 게임에 후킹 또는 인젝션하거나, 게임에 입력을 보내는 일은 절대 없습니다. + ### Smart Citizen이 **하지 않는** 것 - 어떤 종류의 텔레메트리, 분석, 사용 보고도 하지 않습니다. diff --git a/languages/korean/ui.json b/languages/korean/ui.json index d0b924ee..53b37589 100644 --- a/languages/korean/ui.json +++ b/languages/korean/ui.json @@ -2992,6 +2992,14 @@ "ht": "", "at": "Smart Citizen이 다음 위치에서 작업 폴더를 사용할 수 없었습니다:\n{folder}\n\n{reason}\n\n추출이 시작되지 않았으므로 아무것도 변경되지 않았습니다." }, + "contract_scan_failed": { + "ht": "", + "at": "계약 {total}개 중 {skipped}개를 읽을 수 없어 강화 생성이 중지되었습니다. 기존 강화는 변경되지 않았습니다. 대개 Smart Citizen의 오류이므로 신고해 주세요.\n\n첫 번째 계약:\n{first}" + }, + "contract_scan_stopped": { + "ht": "", + "at": "계약을 읽는 중 오류가 발생해 강화 생성이 중지되었습니다. 기존 강화는 변경되지 않았습니다. 대개 Smart Citizen의 오류이므로 신고해 주세요.\n\n오류:\n{first}" + }, "cache_folder_refused": { "ht": "", "at": "Windows가 다음 위치에 DataForge 캐시를 만드는 권한을 Smart Citizen에 거부했습니다:\n{folder}\n\n추출이 시작되지 않았으므로 아무것도 변경되지 않았습니다." @@ -3237,7 +3245,7 @@ }, "description": { "ht": "", - "at": "생성 시 실행할 강화 카테고리를 선택하세요. 함선, 부품, 함선 무기, FPS 무기, 임무, 임무 보상, 상품 제작, 의료 소모품을 각각 독립적으로 활성화할 수 있습니다." + "at": "생성 시 실행할 강화 카테고리를 선택합니다: Ships, Ship Items, Gear, Missions, Commodities, Journal, Medical Consumables. Ship Items는 부품, 함선 무기, 미사일을, Gear는 FPS 무기와 방어구 태그를 포함합니다. 각 카테고리는 따로 켜고 끌 수 있습니다." } }, "enh_favorites": { @@ -3270,24 +3278,24 @@ "at": "부품, 미사일, 함선 무기, 상품, 방어구에 추가되는 괄호 이름 태그를 만드세요. ▲/▼로 요소 순서를 바꾸고, 선택을 해제해 제외하고, 약자 길이를 바꾸고, 구분 기호와 괄호를 선택하고, 태그를 이름 앞이 아니라 뒤에 배치할 수 있습니다." } }, - "overlay": { + "blueprint_tracker": { "title": { "ht": "", - "at": "8. Smart Citizen 오버레이" + "at": "7. 설계도 추적기" }, "description": { "ht": "", - "at": "여기서 또는 도구 모음의 오버레이 버튼으로 오버레이를 시작하세요. 게임 위에서 채굴 스캔 신호를 해독하고, 설계도·광물·제작을 검색하는 서랍을 열며, 획득한 설계도를 보유로 표시합니다. 게임은 주 화면에서 테두리 없는 창 모드로 실행하세요." + "at": "보유한 설계도를 표시하세요. 왼쪽 목록을 이름이나 임무로 검색하거나, 부품 유형, 등급, 크기, 품급으로 좁힌 다음, 화살표로 항목을 보유 목록으로 옮기세요. 보유한 설계도는 임무의 잠재적 보상에 나타날 때마다 [보유 중] 태그를 얻어, 무엇을 노려볼 가치가 있는지 한눈에 알 수 있습니다." } }, - "blueprint_tracker": { + "overlay": { "title": { "ht": "", - "at": "7. 설계도 추적기" + "at": "8. Smart Citizen 오버레이" }, "description": { "ht": "", - "at": "보유한 설계도를 표시하세요. 왼쪽 목록을 이름이나 임무로 검색하거나, 부품 유형, 등급, 크기, 품급으로 좁힌 다음, 화살표로 항목을 보유 목록으로 옮기세요. 보유한 설계도는 임무의 잠재적 보상에 나타날 때마다 [보유 중] 태그를 얻어, 무엇을 노려볼 가치가 있는지 한눈에 알 수 있습니다." + "at": "여기서 또는 도구 모음의 오버레이 버튼으로 오버레이를 시작하세요. 게임 위에서 채굴 스캔 신호를 해독하고, 설계도·광물·제작을 검색하는 서랍을 열며, 획득한 설계도를 보유로 표시합니다. 게임은 주 화면에서 테두리 없는 창 모드로 실행하세요." } }, "edit": { @@ -3347,7 +3355,7 @@ }, "description": { "ht": "", - "at": "앱 테마(기본값 / 밝게 / 어둡게 / ODW)를 선택하고, 필요하면 새 버전에서 자동 투어를 비활성화할 수 있습니다." + "at": "앱 테마(기본값 / 밝게 / 어둡게 / ODW)와 글꼴 크기(작게 / 보통 / 크게, 재시작 후 적용)를 고르고, 원하면 새 버전에서 자동 투어를 끌 수 있습니다." } }, "cfg_sc_install": { @@ -3387,13 +3395,33 @@ }, "description": { "ht": "", - "at": "충돌 해결 대화 상자를 통해 외부 INI를 재정의 항목으로 가져오거나, 활성 채널의 user.ini를 재설정하세요(지우기 전에 자동으로 백업됨)." + "at": "충돌 해결 대화상자로 외부 INI를 재정의 항목으로 가져옵니다. 활성 채널의 user.ini를 초기화하거나(먼저 백업됨) user.ini 복원으로 이전 사본을 되돌릴 수 있습니다. 미리 보기는 적용 시 기록될 내용을 보여 주고, 업데이트 확인은 새 버전을 찾습니다." + } + }, + "cfg_backup": { + "title": { + "ht": "", + "at": "19. 설정: 설정 백업" + }, + "description": { + "ht": "", + "at": "설정 내보내기는 환경설정, 태그 구성, Star Citizen 폴더, 모든 채널의 사용자 문자열을 파일 하나에 저장합니다. 설정 가져오기로 새 PC나 새로 설치한 뒤에 다시 불러올 수 있습니다." + } + }, + "cfg_sc_tools": { + "title": { + "ht": "", + "at": "20. 설정: Star Citizen 도구" + }, + "description": { + "ht": "", + "at": "셰이더 캐시 지우기는 게임의 셰이더 캐시 폴더를 빌드마다 하나씩 보여 줍니다. 정리는 셰이더를 지우고 그래픽 설정은 남기며, 제거는 폴더 전체를 지웁니다. 먼저 Star Citizen을 종료하세요." } }, "help": { "title": { "ht": "", - "at": "19. 도움말 및 피드백" + "at": "21. 도움말 및 피드백" }, "description": { "ht": "", @@ -3590,7 +3618,7 @@ }, "desc": { "ht": "", - "at": "Star Citizen 위에 표시되는 창입니다. 채굴 스캔 해독기와 설계도 서랍이 있습니다. 게임은 테두리 없는 창 모드로 실행하세요. 오버레이는 화면과 Game.log만 읽고, 서랍 단축키를 설정하면 그 조합 하나만을 위해 키 입력을 살핍니다. 게임 프로세스에는 절대 손대지 않습니다." + "at": "Star Citizen 위에 표시되는 창입니다. 채굴 스캔 해독기와 설계도 서랍이 있습니다. 게임은 테두리 없는 창 모드로 실행하세요. 오버레이는 화면과 Game.log만 읽고, 어떤 창이 맨 앞에 있는지와 포인터가 보이는지를 Windows에 묻고, 서랍 단축키를 설정하면 그 키와 Ctrl, Alt, Shift, Win 키가 눌려 있는지도 묻습니다. 게임 프로세스에는 절대 손대지 않습니다." }, "start_btn": { "ht": "", diff --git a/languages/portuguese_br/ABOUT.md b/languages/portuguese_br/ABOUT.md index b87b705f..b6f7239c 100644 --- a/languages/portuguese_br/ABOUT.md +++ b/languages/portuguese_br/ABOUT.md @@ -31,6 +31,7 @@ Obrigado a quem contribuiu com código para o Smart Citizen: - **scubamount** - **hkstrongside** - **odw-okano** +- **RWolfyo** ## Tradutores @@ -115,7 +116,7 @@ As strings do jogo em idiomas diferentes do inglês são traduções da comunida - **Títulos de Missão**: comece títulos de transporte pela rota (ex.: `Area18 > Lorville`) — posicionamento, seta, separador e nível de detalhe do local configuráveis, além do encurtamento opcional dos títulos originais, com pré-visualização ao vivo - **Estatísticas Acima ou Abaixo**: escolha se o bloco de estatísticas fica no topo ou no final da descrição - **Rastreador de Blueprints**: uma aba dedicada para marcar os blueprints de fabricação que você já possui. Mova itens entre Disponíveis e Adquiridos, filtre por Missão / Tipo / Classe / Tamanho / Grau, e itens adquiridos ganham uma tag azul `[Owned]` nas listas de blueprints das missões. **Escanear Logs por Blueprints Adquiridos** preenche a coleção automaticamente a partir dos seus arquivos de log do Star Citizen, importando só o que é novo desde o último escaneamento (ou automaticamente ao iniciar, quando **Escanear logs automaticamente ao iniciar** está ativado), e **Exportar / Importar Blueprints Adquiridos** move a lista de adquiridos entre PCs (JSON ou CSV; a importação só adiciona, e exportações do scmdb.net também funcionam) -- **Sobreposição do Smart Citizen**: janelas opcionais sobre o jogo (modo janela sem bordas). Um decodificador de escaneamento de mineração mostra o depósito por trás de uma assinatura (`3 × Lindinium`) e pode brilhar, piscar ou tocar um som para os minerais ou o salvamento que você acompanha; uma gaveta, com atalho próprio, pesquisa seus blueprints, onde os minerais são encontrados e o que se fabrica com eles; e os blueprints que você ganha são marcados como adquiridos a partir do `Game.log` enquanto ela roda. Só pixels da tela, o `Game.log` e um atalho opcional: sem injeção, leitura de memória nem envio de entradas +- **Sobreposição do Smart Citizen**: janelas opcionais sobre o jogo (modo janela sem bordas). Um decodificador de escaneamento de mineração mostra o depósito por trás de uma assinatura (`3 × Lindinium`) e pode brilhar, piscar ou tocar um som para os minerais ou o salvamento que você acompanha; uma gaveta, com atalho próprio, pesquisa seus blueprints, onde os minerais são encontrados e o que se fabrica com eles; e os blueprints que você ganha são marcados como adquiridos a partir do `Game.log` enquanto ela roda. Só pixels da tela, o `Game.log`, a janela em primeiro plano, a visibilidade do ponteiro e um atalho opcional: sem injeção, leitura de memória nem envio de entradas - **Rótulos de Missão**: renomeie os cabeçalhos de seção (MISSION DETAILS, POTENTIAL BLUEPRINTS etc.), o rótulo de XP e a tag de ênfase dos cabeçalhos - **Patches Declarativos para Bugs de Dados da CIG**: um sistema de patches aplica correções a bugs conhecidos do DataForge no momento da extração, para o texto no jogo sair certo sem esperar a CIG - **Categorias Seletivas**: ative ou desative cada categoria de aprimoramento de forma independente na aba Aprimoramentos diff --git a/languages/portuguese_br/FAQ.md b/languages/portuguese_br/FAQ.md index 21da9671..d81bbfb6 100644 --- a/languages/portuguese_br/FAQ.md +++ b/languages/portuguese_br/FAQ.md @@ -15,7 +15,7 @@ Suas edições pessoais ficam em `user.ini`, na sua pasta de dados do Smart Citi O Smart Citizen só edita o texto de localização (as palavras que o jogo mostra), ele não mexe na lógica do jogo, não te dá nenhuma vantagem, nem se comunica com os servidores da CIG. Nossas modificações **devem** estar tranquilas. -A **Sobreposição do Smart Citizen** opcional (aba Sobreposição) funciona do mesmo jeito, sem interferir no jogo. Ela desenha janelas comuns por cima do jogo, lê pixels da sua tela como faz uma ferramenta de captura de tela e lê o arquivo `Game.log` do jogo. Ela nunca se injeta no jogo nem se engancha nele, nunca abre o processo do jogo nem lê a memória dele, e nunca envia entradas de teclado ou mouse. Se você definir um atalho para a gaveta, ela registra no Windows só essa combinação de teclas, do jeito padrão que um programa usa para pedir um atalho. O Star Citizen bloqueia os atalhos registrados por outros programas enquanto está em foco, então, enquanto houver um atalho definido, a sobreposição também recebe a entrada bruta do teclado (raw input), a forma somente leitura com que o Windows avisa um programa em segundo plano sobre as teclas pressionadas. Isso não é um hook de teclado: ela não segura, não altera e não envia nenhuma tecla, não registra nada e só reage à sua combinação. A CIG não disse nada sobre sobreposições como esta, então vale o mesmo aviso de uso por sua conta e risco abaixo. +A **Sobreposição do Smart Citizen** opcional (aba Sobreposição) funciona do mesmo jeito, sem interferir no jogo. Ela desenha janelas comuns por cima do jogo, lê pixels da sua tela como faz uma ferramenta de captura de tela e lê o arquivo `Game.log` do jogo. Enquanto a gaveta está à vista, ela também pergunta ao Windows qual janela está em primeiro plano e se o ponteiro do mouse está visível, para que seus tiros atravessem a gaveta enquanto você mira. Ela nunca se injeta no jogo nem se engancha nele, nunca abre o processo do jogo nem lê a memória dele, e nunca envia entradas de teclado ou mouse. Se você definir um atalho para a gaveta, ela registra no Windows só essa combinação de teclas, do jeito padrão que um programa usa para pedir um atalho. O Star Citizen bloqueia os atalhos registrados por outros programas enquanto está em foco, então, enquanto o jogo estiver em primeiro plano, a sobreposição também pergunta ao Windows se a tecla dessa combinação está pressionada e, só enquanto estiver, se Ctrl, Alt, Shift ou Win está pressionada. Ela não pergunta sobre nenhuma outra tecla, nunca recebe o que você digita no jogo ou em outro programa e nunca segura, altera ou envia nenhuma tecla. A CIG não disse nada sobre sobreposições como esta, então vale o mesmo aviso de uso por sua conta e risco abaixo. A CIG apoiou publicamente a localização feita pela comunidade. O post deles [Community Localization Update](https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/star-citizen-community-localization-update) explica o suporte oficial a traduções feitas por jogadores, o que entendemos como uma permissão explícita para o tipo de edição de localização que o Smart Citizen faz. diff --git a/languages/portuguese_br/HELP.md b/languages/portuguese_br/HELP.md index 1ea08c5e..cc8ef93d 100644 --- a/languages/portuguese_br/HELP.md +++ b/languages/portuguese_br/HELP.md @@ -82,6 +82,8 @@ A cor do botão mostra a situação: **vermelho** significa que algo mudou desde O Smart Citizen também carimba uma pequena marca d'água na string de versão do launcher (`Frontend_PU_Version`), acrescentando `\nLocalizations Enhanced with Smart Citizen v{VERSION}` em sua própria linha. É assim que você confirma no jogo que seu loc-pack está ativo: olhe o rótulo de versão no menu principal do Star Citizen. A marca é reescrita a cada aplicação, então nunca se acumula entre versões. +Ao aplicar, o Smart Citizen também acrescenta uma segunda linha ao botão Jogar do menu principal (`Frontend_play_star_citizen`), `Run Smart Citizen after every patch`, com as duas linhas centralizadas. Um patch do jogo mantém o `global.ini` aplicado no lugar, mas as chaves que o patch acrescentou aparecem como nomes `@key` crus até você abrir o Smart Citizen e aplicar de novo, então o lembrete está no menu na primeira vez que o jogo abre depois de um patch. Como a marca, ele é reescrito a cada aplicação, e fica em inglês em qualquer idioma. + ## 8. Restaurar um Backup Abra o menu **Mais** na barra de ferramentas e escolha **Restaurar Backup** para voltar a uma versão anterior. O Smart Citizen mantém até **5 backups automáticos**; o mais antigo é removido conforme novos são criados. @@ -168,11 +170,11 @@ Acompanhe quais blueprints de fabricação você já possui, e veja isso refleti ## Aba Sobreposição -A **Sobreposição do Smart Citizen** desenha duas pequenas janelas sobre o Star Citizen: um decodificador de escaneamento de mineração e uma gaveta de buscas. Inicie e pare a sobreposição com **Iniciar sobreposição** nesta aba ou com o botão **Sobreposição** da barra de ferramentas. Rode o jogo em modo janela sem bordas na sua tela principal; caso contrário, a sobreposição não consegue aparecer por cima dele. A sobreposição só lê a sua tela e o `Game.log` e, se você definir um atalho para a gaveta, observa as teclas pressionadas só para essa combinação; ela nunca mexe no jogo em si. +A **Sobreposição do Smart Citizen** desenha duas pequenas janelas sobre o Star Citizen: um decodificador de escaneamento de mineração e uma gaveta de buscas. Inicie e pare a sobreposição com **Iniciar sobreposição** nesta aba ou com o botão **Sobreposição** da barra de ferramentas. Rode o jogo em modo janela sem bordas na sua tela principal; caso contrário, a sobreposição não consegue aparecer por cima dele. A sobreposição só lê a sua tela e o `Game.log`, pergunta ao Windows qual janela está em primeiro plano e se o ponteiro do mouse está visível (para que seus tiros atravessem a gaveta enquanto você mira) e, se você definir um atalho para a gaveta, se a tecla do atalho e as teclas Ctrl, Alt, Shift e Win estão pressionadas; ela nunca mexe no jogo em si. - **Decodificador de escaneamento de mineração** lê a assinatura de escaneamento abaixo do seu radar e mostra o tipo e a quantidade do depósito logo embaixo dela (por exemplo `3 × Lindinium`). O rótulo só muda depois que o mesmo número é lido duas vezes seguidas, para que uma leitura errada de um único quadro não pisque na tela. **Tamanho do texto do escaneamento** deixa o rótulo menor ou maior. Um número redondo como 12,000 pode ser salvamento ou um depósito de superfície (mineração ROC ou FPS); o salvamento aparece primeiro e os outros são marcados como só na superfície, porque no espaço só pode ser salvamento. - **Quando um mineral observado ou salvamento for escaneado**: escolha como o rótulo avisa você. **Brilho** e **Piscar** vêm ligados por padrão; dá para acrescentar **Mudar a cor do texto** (verde brilhante), **Texto maior** e **Tocar um som**. O piscar e o som vêm quando o alvo é lido pela primeira vez, não de novo enquanto ele continua na tela. Com **Tocar um som** ligado, **Som de alerta** escolhe o som: **Padrão do Smart Citizen** (um toque curto), uma voz em inglês (sotaque americano, britânico, australiano, irlandês ou nigeriano) ou um dos sons do Windows, e **Ouvir** o toca. Um som do Windows segue o seu esquema de sons do Windows; um definido como (Nenhum) fica em silêncio. -- **Gaveta da sobreposição** coloca seções com abas na borda da tela. Clique em uma aba para abrir a seção e clique de novo para fechá-la. **Posição da gaveta** escolhe um de oito lugares (meio à direita por padrão). **Atalho da gaveta** define uma combinação de teclas que abre a gaveta de dentro do jogo na última seção usada; apertar de novo a fecha. No jogo, continue segurando F para usar o mouse nela, porque o Windows não deixa a sobreposição tirar o mouse do Star Citizen. O Star Citizen continua recebendo essas teclas, então escolha uma combinação que você não usa no jogo. Ela precisa ter Ctrl, Alt ou Win, a menos que seja uma tecla F ou Pause. **Limpar** remove o atalho. Se outro programa já a usa, a aba avisa. +- **Gaveta da sobreposição** coloca seções com abas na borda da tela. Clique em uma aba para abrir a seção e clique de novo para fechá-la. **Posição da gaveta** escolhe um de oito lugares (meio à direita por padrão). **Atalho da gaveta** define uma combinação de teclas que abre a gaveta de dentro do jogo na última seção usada; apertar de novo a fecha. No jogo, continue segurando F para usar o mouse nela, porque o Windows não deixa a sobreposição tirar o mouse do Star Citizen. O Star Citizen continua recebendo essas teclas, então escolha uma combinação que você não usa no jogo. No jogo, segure as teclas por um instante: um toque muito rápido, como um botão do Stream Deck sem tempo de pressionamento, pode passar despercebido. Se o Star Citizen roda como administrador, o Smart Citizen também precisa rodar assim, senão o atalho não faz nada no jogo. Ela precisa ter Ctrl, Alt ou Win, a menos que seja uma tecla F ou Pause. **Limpar** remove o atalho. Se outro programa já a usa, a aba avisa. - **Blueprints**: pesquise blueprints, veja quais missões os concedem e marque os que você possui (a mesma lista de adquiridos da aba Rastreador de Blueprints). - **Minerais**: digite um mineral para ver onde ele é encontrado, agrupado por sistema estelar, ou um local para ver seus minerais. Marque um mineral, ou **Salvamento** no fim da lista, para ficar de olho nele: o rótulo do escaneamento avisa você quando um escaneamento o encontra. O decodificador também pode ser ligado e desligado aqui. - **Fabricação**: digite um mineral para ver quais itens o usam, ou um item para ver os minerais de que ele precisa. É preenchida quando você gera os aprimoramentos com **Commodities** ou **Journal** marcado. diff --git a/languages/portuguese_br/LEGAL.md b/languages/portuguese_br/LEGAL.md index 050d9038..dbbd50d7 100644 --- a/languages/portuguese_br/LEGAL.md +++ b/languages/portuguese_br/LEGAL.md @@ -50,6 +50,17 @@ O Smart Citizen faz requisições de rede de saída em apenas quatro circunstân - **Fontes remotas configuradas pelo usuário**: se você configurou uma fonte de dados apontando para uma URL `http(s)://` na aba Config, o Smart Citizen consulta essa URL ao atualizar os arquivos de fontes. De fábrica, isso só se aplica à forma de URL GitHub-raw da fonte `global`; a configuração padrão desde a v1.0 lê o `base.ini` da sua extração local do Data.p4k. - **Lista de lojas do Localizador de itens do SCO** — Enquanto o overlay roda com a seção Localizador de itens ligada, o Smart Citizen baixa a lista de lojas e preços da API do [UEX](https://uexcorp.space) (`api.uexcorp.uk`), no máximo a cada 12 horas. São duas requisições simples que enviam apenas o nome e a versão do app; nada da sua máquina é enviado. A lista fica em cache local. Desligue o Localizador de itens na aba Overlay para parar. +### A sobreposição do Smart Citizen + +A sobreposição fica desligada até você iniciá-la. Enquanto ela roda, tudo o que ela lê fica no seu computador: + +- **Tela** — ela captura uma pequena área ao redor do mostrador do scanner de mineração para ler o número do sinal. As capturas são lidas na memória e não são salvas. +- **Game.log** — ela lê o log do Star Citizen para encontrar os blueprints que você recebe. +- **Windows** — ela pergunta ao Windows qual janela está em primeiro plano e se o ponteiro do mouse está visível, para que a gaveta deixe seus cliques passarem para o jogo enquanto você mira. +- **Atalho da gaveta** — só se você definir um. Enquanto o Star Citizen está em primeiro plano, ela pergunta ao Windows se a tecla do atalho está pressionada, e as teclas Ctrl, Alt, Shift e Win só quando ela está. Ela não pergunta sobre nenhuma outra tecla e nunca recebe o que você digita. + +Ela nunca lê a memória do jogo, nunca se conecta nem se injeta no jogo e nunca envia entradas para ele. + ### O que o Smart Citizen **não** faz - Nenhuma telemetria, análise ou relatório de uso de qualquer tipo. diff --git a/languages/portuguese_br/ui.json b/languages/portuguese_br/ui.json index fef5fb9a..ce27305f 100644 --- a/languages/portuguese_br/ui.json +++ b/languages/portuguese_br/ui.json @@ -2992,6 +2992,14 @@ "ht": "", "at": "O Smart Citizen não conseguiu usar uma pasta de trabalho em:\n{folder}\n\n{reason}\n\nA extração não foi iniciada, então nada foi alterado." }, + "contract_scan_failed": { + "ht": "", + "at": "A geração de aprimoramentos foi interrompida porque {skipped} de {total} contratos não puderam ser lidos. Seus aprimoramentos atuais não foram alterados. Informe isso, pois costuma ser um erro do Smart Citizen.\n\nPrimeiro contrato:\n{first}" + }, + "contract_scan_stopped": { + "ht": "", + "at": "A geração de aprimoramentos foi interrompida porque a leitura dos contratos parou com um erro. Seus aprimoramentos atuais não foram alterados. Informe isso, pois costuma ser um erro do Smart Citizen.\n\nO erro:\n{first}" + }, "cache_folder_refused": { "ht": "", "at": "O Windows negou ao Smart Citizen a permissão para criar o cache do DataForge em:\n{folder}\n\nA extração não foi iniciada, então nada foi alterado." @@ -3123,7 +3131,7 @@ }, "description": { "ht": "", - "at": "Escolha quais categorias de aprimoramentos rodam ao Gerar. Naves, componentes, armas de nave, armas FPS, missões, recompensas de missão, fabricação de mercadorias e consumíveis médicos podem ser ativados de forma independente." + "at": "Escolha quais categorias de aprimoramentos rodam ao Gerar: Ships, Ship Items, Gear, Missions, Commodities, Journal, Medical Consumables. Ship Items inclui componentes, armas de nave e mísseis; Gear inclui armas FPS e tags de armadura. Cada categoria pode ser ligada ou desligada separadamente." } }, "enh_favorites": { @@ -3156,6 +3164,26 @@ "at": "Monte as tags entre colchetes adicionadas aos nomes de componentes, mísseis, armas de nave, commodities e armaduras. Reordene os elementos com ▲/▼, desmarque para excluir, mude o tamanho das abreviações, escolha o separador e os colchetes, ou coloque a tag depois do nome em vez de antes." } }, + "blueprint_tracker": { + "title": { + "ht": "", + "at": "7. Rastreador de Blueprints" + }, + "description": { + "ht": "", + "at": "Marque os blueprints que você possui. Busque na lista da esquerda por nome ou missão, ou refine por Tipo, Classe, Tamanho e Grau de componente, e então use as setas para mover itens para a sua lista de adquiridos. Blueprints adquiridos recebem uma tag [Owned] onde quer que apareçam nas recompensas potenciais de uma missão, para você ver de relance o que ainda vale caçar." + } + }, + "overlay": { + "title": { + "ht": "", + "at": "8. Sobreposição do Smart Citizen" + }, + "description": { + "ht": "", + "at": "Inicie a sobreposição aqui ou com o botão Sobreposição da barra de ferramentas. Sobre o jogo, ela decodifica assinaturas de escaneamento de mineração, abre uma gaveta para buscar seus blueprints, minerais e fabricação, e marca como possuídos os blueprints que você ganha. Rode o jogo em modo janela sem bordas na sua tela principal." + } + }, "edit": { "title": { "ht": "", @@ -3213,7 +3241,7 @@ }, "description": { "ht": "", - "at": "Escolha o tema do app (Padrão / Claro / Escuro / ODW) e, se quiser, desative o tour automático a cada nova versão." + "at": "Escolha o tema do app (Padrão / Claro / Escuro / ODW) e o tamanho da fonte (Pequeno / Médio / Grande, aplicado após reiniciar) e, se quiser, desative o tour automático em novas versões." } }, "cfg_sc_install": { @@ -3253,37 +3281,37 @@ }, "description": { "ht": "", - "at": "Importe um INI externo para suas personalizações pela caixa de resolução de conflitos, ou redefina seu user.ini do canal ativo (com backup automático antes de limpar)." + "at": "Importe um INI externo para suas personalizações pela janela de resolução de conflitos. Redefina o user.ini do canal ativo (com backup antes) ou recupere uma cópia anterior com Restaurar user.ini. A prévia mostra o que Aplicar escreveria, e Verificar atualizações procura uma nova versão." } }, - "help": { + "cfg_backup": { "title": { "ht": "", - "at": "19. Ajuda e feedback" + "at": "19. Config: Backup de Configurações" }, "description": { "ht": "", - "at": "O botão Ajuda abre um painel lateral com o guia completo, a lista de Problemas Conhecidos e um link para o canal do Smart Citizen no Discord. Isso é tudo o que você precisa para começar: boa sorte, cidadão." + "at": "Exportar Configurações salva suas preferências, ajustes de tags, pasta do Star Citizen e textos personalizados de todos os canais em um só arquivo. Importar Configurações os traz de volta, em um PC novo ou após uma instalação limpa." } }, - "overlay": { + "cfg_sc_tools": { "title": { "ht": "", - "at": "8. Sobreposição do Smart Citizen" + "at": "20. Config: Ferramentas do Star Citizen" }, "description": { "ht": "", - "at": "Inicie a sobreposição aqui ou com o botão Sobreposição da barra de ferramentas. Sobre o jogo, ela decodifica assinaturas de escaneamento de mineração, abre uma gaveta para buscar seus blueprints, minerais e fabricação, e marca como possuídos os blueprints que você ganha. Rode o jogo em modo janela sem bordas na sua tela principal." + "at": "Limpar cache de shaders lista as pastas de cache de shaders do jogo, uma por versão. Limpar apaga os shaders e mantém suas configurações gráficas; Remover apaga a pasta inteira. Feche o Star Citizen antes." } }, - "blueprint_tracker": { + "help": { "title": { "ht": "", - "at": "7. Rastreador de Blueprints" + "at": "21. Ajuda e feedback" }, "description": { "ht": "", - "at": "Marque os blueprints que você possui. Busque na lista da esquerda por nome ou missão, ou refine por Tipo, Classe, Tamanho e Grau de componente, e então use as setas para mover itens para a sua lista de adquiridos. Blueprints adquiridos recebem uma tag [Owned] onde quer que apareçam nas recompensas potenciais de uma missão, para você ver de relance o que ainda vale caçar." + "at": "O botão Ajuda abre um painel lateral com o guia completo, a lista de Problemas Conhecidos e um link para o canal do Smart Citizen no Discord. Isso é tudo o que você precisa para começar: boa sorte, cidadão." } } }, @@ -3590,7 +3618,7 @@ }, "desc": { "ht": "", - "at": "Janelas desenhadas sobre o Star Citizen: o decodificador de escaneamento de mineração e a gaveta de blueprints. Rode o jogo em modo janela sem bordas. A sobreposição só lê sua tela e o Game.log e, se você definir um atalho para a gaveta, observa as teclas pressionadas só para essa combinação; nunca toca no processo do jogo." + "at": "Janelas desenhadas sobre o Star Citizen: o decodificador de escaneamento de mineração e a gaveta de blueprints. Rode o jogo em modo janela sem bordas. A sobreposição só lê sua tela e o Game.log, pergunta ao Windows qual janela está em primeiro plano e se o ponteiro está visível e, se você definir um atalho para a gaveta, se a tecla do atalho e as teclas Ctrl, Alt, Shift e Win estão pressionadas; nunca toca no processo do jogo." }, "start_btn": { "ht": "", diff --git a/languages/russian/ABOUT.md b/languages/russian/ABOUT.md index 520ddd09..836035f4 100644 --- a/languages/russian/ABOUT.md +++ b/languages/russian/ABOUT.md @@ -29,6 +29,7 @@ - **scubamount** - **hkstrongside** - **odw-okano** +- **RWolfyo** ## Переводчики @@ -113,7 +114,7 @@ Smart Citizen также включает инструментарий из: - **Заголовки миссий**: добавляйте маршрут в заголовки перевозок (например, `Area18 > Lorville`) — настраиваемое размещение, стрелка, разделитель и детализация местоположения, плюс необязательное сокращение стандартных заголовков с живым предварительным просмотром - **Характеристики сверху или снизу**: выбирайте, располагается ли блок характеристик в верхней или нижней части описания - **Трекер чертежей**: выделенная вкладка для отметки уже имеющихся чертежей крафта. Перемещайте элементы между «Доступные чертежи» и «Имеющиеся чертежи», фильтруйте по «Миссия» / «Тип» / «Класс» / «Размер» / «Категория», а элементы в собственности получают синий тег `[Owned]` в списках чертежей миссий. **Сканировать журналы на наличие чертежей** автоматически заполняет собственность из файлов журналов Star Citizen, импортируя только новое с момента последнего сканирования (или автоматически при запуске, когда включено **Автосканирование журналов при запуске**), а **Экспорт / Импорт имеющихся чертежей** перемещает список между компьютерами (JSON или CSV; импорт только добавляет, и экспорты scmdb.net тоже работают) -- **Smart Citizen Overlay**: необязательные окна поверх игры (режим «окно без рамки»). Расшифровщик сканирования добычи показывает залежь за сигнатурой (`3 × Lindinium`) и может подсвечивать, мигать или подавать звук для отслеживаемых минералов и утилизации; панель со своей горячей клавишей ищет ваши чертежи, места, где встречаются минералы, и то, что из них создаётся; а полученные чертежи отмечаются как имеющиеся по `Game.log`, пока оверлей работает. Только пиксели экрана, `Game.log` и необязательная горячая клавиша: никаких внедрений, чтения памяти или ввода +- **Smart Citizen Overlay**: необязательные окна поверх игры (режим «окно без рамки»). Расшифровщик сканирования добычи показывает залежь за сигнатурой (`3 × Lindinium`) и может подсвечивать, мигать или подавать звук для отслеживаемых минералов и утилизации; панель со своей горячей клавишей ищет ваши чертежи, места, где встречаются минералы, и то, что из них создаётся; а полученные чертежи отмечаются как имеющиеся по `Game.log`, пока оверлей работает. Только пиксели экрана, `Game.log`, окно на переднем плане, видимость указателя и необязательная горячая клавиша: никаких внедрений, чтения памяти или ввода - **Метки миссий**: переименовывайте заголовки разделов (MISSION DETAILS, POTENTIAL BLUEPRINTS и т.д.), метку XP и тег акцента для заголовков - **Декларативные патчи багов данных CIG**: система патчей применяет исправления к известным багам DataForge при извлечении, чтобы текст в игре читался корректно без ожидания CIG - **Выборочные категории**: включайте или отключайте каждую категорию улучшений независимо на вкладке «Улучшения» diff --git a/languages/russian/FAQ.md b/languages/russian/FAQ.md index 5cfd6625..b0906aed 100644 --- a/languages/russian/FAQ.md +++ b/languages/russian/FAQ.md @@ -15,7 +15,7 @@ Smart Citizen редактирует только текст локализации (слова, которые игра вам показывает), он не затрагивает игровую логику, не даёт никаких преимуществ и не общается с серверами CIG. Наши модификации **должны** быть в порядке. -Необязательный **Smart Citizen Overlay** (вкладка «Оверлей») работает так же, не вмешиваясь в игру. Он рисует обычные окна поверх игры, читает пиксели с экрана, как программа для снимков экрана, и читает файл игры `Game.log`. Он никогда не внедряется в игру и не перехватывает её вызовы, никогда не открывает процесс игры и не читает её память, и никогда не отправляет ввод с клавиатуры или мыши. Если вы задали горячую клавишу панели, он регистрирует в Windows только это одно сочетание клавиш, стандартным способом, которым программа запрашивает горячую клавишу. Пока Star Citizen в фокусе, он не пропускает горячие клавиши, зарегистрированные другими программами, поэтому, пока горячая клавиша задана, оверлей также получает необработанный ввод клавиатуры (raw input): так Windows только сообщает фоновой программе о нажатиях клавиш. Это не перехват клавиатуры: он не задерживает, не меняет и не отправляет ни одной клавиши, ничего не записывает и реагирует только на ваше сочетание. CIG ничего не говорила о подобных оверлеях, поэтому к нему относится то же предупреждение «на свой страх и риск» ниже. +Необязательный **Smart Citizen Overlay** (вкладка «Оверлей») работает так же, не вмешиваясь в игру. Он рисует обычные окна поверх игры, читает пиксели с экрана, как программа для снимков экрана, и читает файл игры `Game.log`. Пока его панель видна, он также спрашивает у Windows, какое окно на переднем плане и виден ли указатель мыши, чтобы ваши выстрелы во время прицеливания проходили сквозь панель. Он никогда не внедряется в игру и не перехватывает её вызовы, никогда не открывает процесс игры и не читает её память, и никогда не отправляет ввод с клавиатуры или мыши. Если вы задали горячую клавишу панели, он регистрирует в Windows только это одно сочетание клавиш, стандартным способом, которым программа запрашивает горячую клавишу. Пока Star Citizen в фокусе, он не пропускает горячие клавиши, зарегистрированные другими программами, поэтому, пока игра на переднем плане, оверлей также спрашивает у Windows, нажата ли клавиша этого сочетания, и только пока она нажата, удерживаются ли Ctrl, Alt, Shift или Win. Ни о каких других клавишах он не спрашивает, то, что вы печатаете в игре или в другой программе, к нему никогда не попадает, и он никогда не задерживает, не меняет и не отправляет ни одной клавиши. CIG ничего не говорила о подобных оверлеях, поэтому к нему относится то же предупреждение «на свой страх и риск» ниже. CIG публично поддержал локализацию сообщества. Их пост [Community Localization Update](https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/star-citizen-community-localization-update) излагает официальную поддержку переводов, созданных игроками, что, по нашему пониманию, явно разрешает тот тип редактирования локализации, который делает Smart Citizen. diff --git a/languages/russian/HELP.md b/languages/russian/HELP.md index 5dbd898b..871caced 100644 --- a/languages/russian/HELP.md +++ b/languages/russian/HELP.md @@ -80,6 +80,8 @@ Smart Citizen открывается в одном из двух режимов, Smart Citizen также наносит небольшой водяной знак на строку версии лаунчера (`Frontend_PU_Version`), добавляя `\nLocalizations Enhanced with Smart Citizen v{VERSION}` на отдельной строке. Так вы можете подтвердить в игре, что ваш пакет локализации активен — посмотрите на метку версии в главном меню Star Citizen. Водяной знак перезаписывается при каждом применении, поэтому он не накапливается между версиями. +При применении Smart Citizen также добавляет вторую строку на кнопку «Играть» в главном меню (`Frontend_play_star_citizen`), `Run Smart Citizen after every patch`, и выравнивает обе строки по центру. Патч игры оставляет применённый `global.ini` на месте, но ключи, добавленные патчем, отображаются как необработанные имена `@key`, пока вы не запустите Smart Citizen и не примените изменения снова, поэтому напоминание видно в меню уже при первом запуске игры после патча. Как и водяной знак, оно перезаписывается при каждом применении и остаётся на английском, какой бы язык вы ни выбрали. + ## 8. Восстановление резервной копии Откройте меню **Ещё** на панели инструментов и выберите **Восстановить резервную копию**, чтобы вернуться к предыдущей версии. Smart Citizen хранит до **5 автоматических резервных копий** — самая старая удаляется при создании новых. @@ -166,11 +168,11 @@ Smart Citizen проверяет наличие новой версии при ## Вкладка «Оверлей» -**Smart Citizen Overlay** рисует два небольших окна поверх Star Citizen: расшифровщик сканирования добычи и панель с поиском. Запускайте и останавливайте его кнопкой **Запустить оверлей** на этой вкладке или кнопкой **Оверлей** на панели инструментов. Запускайте игру в режиме «окно без рамки» на основном экране, иначе оверлей не сможет отображаться поверх неё. Оверлей только читает ваш экран и `Game.log`, а если вы задали горячую клавишу панели, следит за нажатиями клавиш только ради этого сочетания; саму игру он никогда не затрагивает. +**Smart Citizen Overlay** рисует два небольших окна поверх Star Citizen: расшифровщик сканирования добычи и панель с поиском. Запускайте и останавливайте его кнопкой **Запустить оверлей** на этой вкладке или кнопкой **Оверлей** на панели инструментов. Запускайте игру в режиме «окно без рамки» на основном экране, иначе оверлей не сможет отображаться поверх неё. Оверлей только читает ваш экран и `Game.log`, спрашивает у Windows, какое окно на переднем плане и виден ли указатель мыши (чтобы ваши выстрелы во время прицеливания проходили сквозь панель), а если вы задали горячую клавишу панели, то и нажаты ли основная клавиша сочетания и клавиши Ctrl, Alt, Shift и Win; саму игру он никогда не затрагивает. - **Расшифровщик сканирования добычи** читает сигнатуру сканирования под радаром и показывает тип и количество залежей прямо под ней (например, `3 × Lindinium`). Метка меняется только после того, как одно и то же число прочитано дважды подряд, поэтому ошибка в одном кадре не мелькает. **Размер текста сканирования** делает метку мельче или крупнее. Круглое число вроде 12,000 может быть утилизацией или залежью на поверхности (добыча ROC или FPS); утилизация идёт первой, а остальные помечены как «только на поверхности», ведь в космосе это может быть только утилизация. - **Когда сканируется отслеживаемый минерал или утилизация**: выберите, как метка вас оповестит. **Свечение** и **Мигание** включены по умолчанию; можно добавить **Сменить цвет текста** (ярко-зелёный), **Крупнее текст** и **Звуковой сигнал**. Мигание и звук срабатывают, когда цель прочитана впервые, и не повторяются, пока она остаётся на экране. Когда включён **Звуковой сигнал**, в **Звук оповещения** выбирается звук: **Smart Citizen по умолчанию** (короткий сигнал), английский голос (американский, британский, австралийский, ирландский или нигерийский акцент) или один из звуков Windows, а **Прослушать** его воспроизводит. Звук Windows берётся из звуковой схемы Windows, поэтому звук со значением (Нет) не прозвучит. -- **Панель оверлея** размещает разделы с вкладками у края экрана. Нажмите на вкладку, чтобы открыть раздел, и ещё раз, чтобы закрыть. **Положение панели** выбирает одно из восьми мест (по умолчанию посередине справа). **Горячая клавиша панели** задаёт сочетание клавиш, которое открывает панель прямо из игры на последнем использованном разделе; повторное нажатие закрывает её. В игре, чтобы пользоваться в ней мышью, по-прежнему удерживайте F: Windows не даёт оверлею забрать мышь у Star Citizen. Star Citizen всё равно получает эти клавиши, поэтому выберите сочетание, которым вы не пользуетесь в игре. В нём должна быть Ctrl, Alt или Win, если это не клавиша F и не Pause. Кнопка **Очистить** удаляет горячую клавишу. Если его уже занимает другая программа, вкладка сообщит об этом. +- **Панель оверлея** размещает разделы с вкладками у края экрана. Нажмите на вкладку, чтобы открыть раздел, и ещё раз, чтобы закрыть. **Положение панели** выбирает одно из восьми мест (по умолчанию посередине справа). **Горячая клавиша панели** задаёт сочетание клавиш, которое открывает панель прямо из игры на последнем использованном разделе; повторное нажатие закрывает её. В игре, чтобы пользоваться в ней мышью, по-прежнему удерживайте F: Windows не даёт оверлею забрать мышь у Star Citizen. Star Citizen всё равно получает эти клавиши, поэтому выберите сочетание, которым вы не пользуетесь в игре. В игре удерживайте клавиши хотя бы мгновение: очень короткое нажатие, например кнопка Stream Deck без времени удержания, может быть пропущено. Если Star Citizen запущена от имени администратора, Smart Citizen тоже нужно запустить так, иначе горячая клавиша в игре не сработает. В нём должна быть Ctrl, Alt или Win, если это не клавиша F и не Pause. Кнопка **Очистить** удаляет горячую клавишу. Если его уже занимает другая программа, вкладка сообщит об этом. - **Чертежи**: ищите чертежи, смотрите, какие миссии дают их в награду, и отмечайте имеющиеся (тот же список, что и на вкладке «Трекер чертежей»). - **Минералы**: введите минерал, чтобы увидеть, где он встречается (по звёздным системам), или место, чтобы увидеть его минералы. Отметьте минерал или строку **Утилизация** внизу списка, чтобы отслеживать их: метка сканирования оповестит вас, когда сканирование их найдёт. Здесь же можно включить и выключить расшифровщик. - **Крафт**: введите минерал, чтобы увидеть, какие предметы его используют, или предмет, чтобы увидеть нужные ему минералы. Заполняется, когда вы генерируете улучшения с отмеченными **Commodities** или **Journal**. diff --git a/languages/russian/LEGAL.md b/languages/russian/LEGAL.md index 4e451199..af0ddd01 100644 --- a/languages/russian/LEGAL.md +++ b/languages/russian/LEGAL.md @@ -50,6 +50,17 @@ Smart Citizen делает исходящие сетевые запросы то - **Пользовательские удалённые источники** — если вы настроили источник данных, указывающий на URL `http(s)://` на вкладке Config, Smart Citizen запрашивает этот URL при обновлении файлов источников. Из коробки это применяется только к URL-форме GitHub-raw источника `global`; стандартная конфигурация с v1.0 читает `base.ini` из вашей локальной экстракции Data.p4k. - **Список магазинов для поиска предметов SCO** — Пока оверлей работает с включённым разделом «Поиск предметов», Smart Citizen загружает список магазинов и цен через API [UEX](https://uexcorp.space) (`api.uexcorp.uk`) не чаще раза в 12 часов. Это два простых запроса, в которых передаются только название и версия приложения; ничего с вашего компьютера не отправляется. Список кэшируется локально. Чтобы это прекратить, выключите «Поиск предметов» на вкладке «Оверлей». +### Оверлей Smart Citizen + +Оверлей выключен, пока вы его не запустите. Пока он работает, всё, что он читает, остаётся на вашем компьютере: + +- **Экран** — он захватывает небольшую область вокруг показаний сканера добычи, чтобы прочитать число сигнала. Снимки читаются в памяти и не сохраняются. +- **Game.log** — он читает журнал Star Citizen, чтобы найти полученные вами чертежи. +- **Windows** — он спрашивает у Windows, какое окно на переднем плане и виден ли указатель мыши, чтобы панель пропускала ваши щелчки в игру, пока вы целитесь. +- **Горячая клавиша панели** — только если вы её задали. Пока Star Citizen на переднем плане, он спрашивает у Windows, нажата ли основная клавиша сочетания, и клавиши Ctrl, Alt, Shift и Win — только когда она нажата. Ни о каких других клавишах он не спрашивает и никогда не получает то, что вы вводите. + +Он никогда не читает память игры, не перехватывает её и не внедряется в неё и никогда не отправляет ей ввод. + ### Чего Smart Citizen **не делает** - Никакой телеметрии, аналитики или отчётности об использовании. diff --git a/languages/russian/ui.json b/languages/russian/ui.json index bb73349f..cac524ed 100644 --- a/languages/russian/ui.json +++ b/languages/russian/ui.json @@ -2992,6 +2992,14 @@ "ht": "", "at": "Smart Citizen не удалось использовать рабочую папку в:\n{folder}\n\n{reason}\n\nИзвлечение не началось, поэтому ничего не изменено." }, + "contract_scan_failed": { + "ht": "", + "at": "Генерация улучшений остановлена: не удалось прочитать контракты ({skipped} из {total}). Ваши текущие улучшения не изменены. Сообщите об этом, так как обычно это ошибка Smart Citizen.\n\nПервый контракт:\n{first}" + }, + "contract_scan_stopped": { + "ht": "", + "at": "Генерация улучшений остановлена: чтение контрактов прервалось с ошибкой. Ваши текущие улучшения не изменены. Сообщите об этом, так как обычно это ошибка Smart Citizen.\n\nОшибка:\n{first}" + }, "cache_folder_refused": { "ht": "", "at": "Windows не разрешила Smart Citizen создать кэш DataForge в:\n{folder}\n\nИзвлечение не началось, поэтому ничего не изменено." @@ -3388,7 +3396,7 @@ }, "desc": { "ht": "", - "at": "Окна поверх Star Citizen: расшифровщик сканирования добычи и панель чертежей. Запускайте игру в режиме «окно без рамки». Оверлей только читает ваш экран и Game.log, а если вы задали горячую клавишу панели, следит за нажатиями клавиш только ради этого сочетания; к процессу игры он никогда не обращается." + "at": "Окна поверх Star Citizen: расшифровщик сканирования добычи и панель чертежей. Запускайте игру в режиме «окно без рамки». Оверлей только читает ваш экран и Game.log, спрашивает у Windows, какое окно на переднем плане и виден ли указатель, а если вы задали горячую клавишу панели, то и нажаты ли основная клавиша сочетания и клавиши Ctrl, Alt, Shift и Win; к процессу игры он никогда не обращается." }, "start_btn": { "ht": "", @@ -3701,7 +3709,7 @@ }, "description": { "ht": "", - "at": "Выберите, какие категории улучшений обрабатываются при генерации. Корабли, компоненты, корабельное оружие, FPS-оружие, миссии, награды миссий, крафт товаров и медицинские расходники включаются независимо друг от друга." + "at": "Выберите, какие категории улучшений запускаются при генерации: Ships, Ship Items, Gear, Missions, Commodities, Journal, Medical Consumables. Ship Items включает компоненты, корабельное оружие и ракеты; Gear включает оружие FPS и метки брони. Каждую категорию можно включить или выключить отдельно." } }, "enh_favorites": { @@ -3811,7 +3819,7 @@ }, "description": { "ht": "", - "at": "Выберите тему приложения (По умолчанию / Светлая / Тёмная / ODW) и при желании отключите автоматический запуск обзора при выходе новых версий." + "at": "Выберите тему приложения (По умолчанию / Светлая / Тёмная / ODW) и размер шрифта (Мелкий / Средний / Крупный, применяется после перезапуска) и при желании отключите автоматический тур при новых версиях." } }, "cfg_sc_install": { @@ -3851,13 +3859,33 @@ }, "description": { "ht": "", - "at": "Импортируйте внешний INI в свои переопределения через диалог разрешения конфликтов или сбросьте user.ini для активного канала (перед очисткой автоматически создаётся резервная копия)." + "at": "Импортируйте внешний INI в свои переопределения через окно разрешения конфликтов. Сбросьте user.ini активного канала (с резервной копией) или верните прежнюю копию кнопкой «Восстановить user.ini». Предпросмотр показывает, что запишет «Применить», а «Проверить обновления» ищет новую версию." + } + }, + "cfg_backup": { + "title": { + "ht": "", + "at": "19. Настройки: резервное копирование настроек" + }, + "description": { + "ht": "", + "at": "«Экспорт настроек» сохраняет ваши настройки, конфигурации меток, папку Star Citizen и свои строки для всех каналов в один файл. «Импорт настроек» возвращает их, на новом ПК или после чистой установки." + } + }, + "cfg_sc_tools": { + "title": { + "ht": "", + "at": "20. Настройки: инструменты Star Citizen" + }, + "description": { + "ht": "", + "at": "«Очистить кэш шейдеров» показывает папки кэша шейдеров игры, по одной на каждую версию. «Очистить» удаляет шейдеры и сохраняет настройки графики; «Удалить» удаляет всю папку. Сначала закройте Star Citizen." } }, "help": { "title": { "ht": "", - "at": "19. Справка и обратная связь" + "at": "21. Справка и обратная связь" }, "description": { "ht": "", diff --git a/languages/spanish/ABOUT.md b/languages/spanish/ABOUT.md index 4b3292c7..d6022d2f 100644 --- a/languages/spanish/ABOUT.md +++ b/languages/spanish/ABOUT.md @@ -31,6 +31,7 @@ Gracias a quienes han contribuido con código a Smart Citizen: - **scubamount** - **hkstrongside** - **odw-okano** +- **RWolfyo** ## Traductores @@ -115,7 +116,7 @@ Los textos del juego en idiomas distintos del inglés son traducciones comunitar - **Títulos de misión**: antepón a los títulos de transporte su ruta (p. ej. `Area18 > Lorville`) — posición, flecha, separador y detalle de la ubicación configurables, más un acortado opcional de los títulos originales, con vista previa en vivo - **Estadísticas arriba o abajo**: elige si el bloque de estadísticas va al principio o al final de la descripción - **Rastreador de blueprints**: una pestaña dedicada para marcar los blueprints de fabricación que ya posees. Mueve elementos entre Disponibles y Adquiridos, filtra por Misión / Tipo / Clase / Tamaño / Grado, y los objetos adquiridos reciben una etiqueta azul `[Owned]` en las listas de blueprints de las misiones. **Escanear registros en busca de blueprints adquiridos** rellena la colección automáticamente desde tus archivos de registro de Star Citizen, importando solo lo nuevo desde el último escaneo (o automáticamente al iniciar, cuando **Escanear registros automáticamente al iniciar** está activado), y **Exportar / Importar blueprints adquiridos** mueve la colección entre PC (JSON o CSV; la importación solo añade, y las exportaciones de scmdb.net también funcionan) -- **Superposición de Smart Citizen**: ventanas opcionales sobre el juego (modo ventana sin bordes). Un decodificador de escaneo minero muestra el depósito que hay detrás de una firma (`3 × Lindinium`) y puede brillar, parpadear o sonar con los minerales o la recuperación que vigilas; un cajón, con su propio atajo, busca en tus blueprints, dónde se encuentran los minerales y qué se fabrica con ellos; y los blueprints que obtienes se marcan como adquiridos a partir de `Game.log` mientras está en marcha. Solo píxeles de pantalla, `Game.log` y un atajo opcional: sin inyección, lectura de memoria ni envío de entradas +- **Superposición de Smart Citizen**: ventanas opcionales sobre el juego (modo ventana sin bordes). Un decodificador de escaneo minero muestra el depósito que hay detrás de una firma (`3 × Lindinium`) y puede brillar, parpadear o sonar con los minerales o la recuperación que vigilas; un cajón, con su propio atajo, busca en tus blueprints, dónde se encuentran los minerales y qué se fabrica con ellos; y los blueprints que obtienes se marcan como adquiridos a partir de `Game.log` mientras está en marcha. Solo píxeles de pantalla, `Game.log`, la ventana en primer plano, la visibilidad del puntero y un atajo opcional: sin inyección, lectura de memoria ni envío de entradas - **Rótulos de misión**: renombra los encabezados de sección (MISSION DETAILS, POTENTIAL BLUEPRINTS, etc.), el rótulo de XP y la etiqueta de énfasis de los encabezados - **Parches declarativos para errores de datos de CIG**: un sistema de parches aplica correcciones a los errores conocidos de DataForge en el momento de la extracción, para que el texto del juego se lea correctamente sin esperar a CIG - **Categorías selectivas**: activa o desactiva cada categoría de mejoras de forma independiente desde la pestaña Mejoras diff --git a/languages/spanish/FAQ.md b/languages/spanish/FAQ.md index 13e3ef0c..2553b8c5 100644 --- a/languages/spanish/FAQ.md +++ b/languages/spanish/FAQ.md @@ -15,7 +15,7 @@ Tus ediciones personales viven en `user.ini`, en tu carpeta de datos de Smart Ci Smart Citizen solo edita el texto de localización (las palabras que muestra el juego); no toca la lógica del juego, no te da ninguna ventaja ni se comunica con los servidores de CIG. Nuestras modificaciones **deberían** estar bien. -La **Superposición de Smart Citizen** opcional (pestaña Superposición) funciona con el mismo enfoque de no intervenir en el juego. Dibuja ventanas normales encima del juego, lee píxeles de tu pantalla como lo hace una herramienta de capturas de pantalla, y lee el archivo `Game.log` del juego. Nunca se inyecta ni se engancha al juego, nunca abre el proceso del juego ni lee su memoria, y nunca envía entradas de teclado ni de ratón. Si defines un atajo para el cajón, registra en Windows solo esa combinación de teclas, de la forma estándar en que un programa pide un atajo. Star Citizen bloquea los atajos registrados por otros programas mientras tiene el foco, así que, mientras haya un atajo definido, la superposición también recibe la entrada sin procesar del teclado (raw input), la forma de solo lectura con la que Windows avisa a un programa en segundo plano de las teclas pulsadas. No es un hook de teclado: no retiene, no cambia ni envía ninguna tecla, no registra nada y solo reacciona a tu combinación. CIG no se ha pronunciado sobre superposiciones como esta, así que se aplica el mismo aviso de uso bajo tu propia responsabilidad que encontrarás más abajo. +La **Superposición de Smart Citizen** opcional (pestaña Superposición) funciona con el mismo enfoque de no intervenir en el juego. Dibuja ventanas normales encima del juego, lee píxeles de tu pantalla como lo hace una herramienta de capturas de pantalla, y lee el archivo `Game.log` del juego. Mientras su cajón está visible, también pregunta a Windows qué ventana está en primer plano y si el puntero del ratón está visible, para que tus disparos atraviesen el cajón mientras apuntas. Nunca se inyecta ni se engancha al juego, nunca abre el proceso del juego ni lee su memoria, y nunca envía entradas de teclado ni de ratón. Si defines un atajo para el cajón, registra en Windows solo esa combinación de teclas, de la forma estándar en que un programa pide un atajo. Star Citizen bloquea los atajos registrados por otros programas mientras tiene el foco, así que, mientras el juego está en primer plano, la superposición también pregunta a Windows si la tecla de esa combinación está pulsada y, solo mientras lo está, si Ctrl, Alt, Mayús o Win están pulsadas. No pregunta por ninguna otra tecla, nunca recibe lo que escribes en el juego o en otro programa y nunca retiene, cambia ni envía ninguna tecla. CIG no se ha pronunciado sobre superposiciones como esta, así que se aplica el mismo aviso de uso bajo tu propia responsabilidad que encontrarás más abajo. CIG ha respaldado públicamente la localización comunitaria. Su publicación [Community Localization Update](https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/star-citizen-community-localization-update) expone el apoyo oficial a las traducciones hechas por jugadores, lo cual entendemos que permite explícitamente el tipo de edición de localización que hace Smart Citizen. diff --git a/languages/spanish/HELP.md b/languages/spanish/HELP.md index 2065e1e2..68a6789d 100644 --- a/languages/spanish/HELP.md +++ b/languages/spanish/HELP.md @@ -82,6 +82,8 @@ El color del botón te dice en qué punto estás: **rojo** significa que algo ha Smart Citizen también estampa una pequeña marca de agua en el texto de versión del lanzador (`Frontend_PU_Version`), añadiendo `\nLocalizations Enhanced with Smart Citizen v{VERSION}` en su propia línea. Así confirmas en el juego que tu loc-pack está activo: mira la etiqueta de versión en el menú principal de Star Citizen. La marca se reescribe con cada aplicación, así que nunca se acumula entre versiones. +Al aplicar también se añade una segunda línea al botón Jugar del menú principal (`Frontend_play_star_citizen`), `Run Smart Citizen after every patch`, con las dos líneas centradas. Un parche del juego deja en su sitio el `global.ini` aplicado, pero las claves que añadió el parche se muestran como nombres `@key` en bruto hasta que ejecutes Smart Citizen y vuelvas a aplicar, así que el recordatorio está en el menú la primera vez que el juego arranca tras un parche. Como la marca, se reescribe con cada aplicación, y queda en inglés sea cual sea tu idioma. + ## 8. Restaurar una copia de seguridad Abre el menú **Más** de la barra de herramientas y elige **Restaurar copia** para volver a una versión anterior. Smart Citizen conserva hasta **5 copias de seguridad automáticas**; la más antigua se elimina a medida que se crean nuevas. @@ -168,11 +170,11 @@ Lleva el control de qué blueprints de fabricación ya posees, y míralo refleja ## Pestaña Superposición -La **Superposición de Smart Citizen** dibuja dos pequeñas ventanas sobre Star Citizen: un decodificador de escaneo minero y un cajón de búsquedas. Iníciala y detenla con **Iniciar superposición** en esta pestaña o con el botón **Superposición** de la barra de herramientas. Ejecuta el juego en modo ventana sin bordes en tu pantalla principal; si no, la superposición no puede mostrarse encima. La superposición solo lee tu pantalla y `Game.log` y, si defines un atajo para el cajón, observa las teclas pulsadas solo para esa combinación; nunca toca el juego en sí. +La **Superposición de Smart Citizen** dibuja dos pequeñas ventanas sobre Star Citizen: un decodificador de escaneo minero y un cajón de búsquedas. Iníciala y detenla con **Iniciar superposición** en esta pestaña o con el botón **Superposición** de la barra de herramientas. Ejecuta el juego en modo ventana sin bordes en tu pantalla principal; si no, la superposición no puede mostrarse encima. La superposición solo lee tu pantalla y `Game.log`, pregunta a Windows qué ventana está en primer plano y si el puntero del ratón está visible (para que tus disparos atraviesen el cajón mientras apuntas) y, si defines un atajo para el cajón, si su tecla y las teclas Ctrl, Alt, Mayús y Win están pulsadas; nunca toca el juego en sí. - **Decodificador de escaneo minero** lee la firma de escaneo bajo tu radar y muestra justo debajo el tipo y la cantidad del depósito (por ejemplo `3 × Lindinium`). La etiqueta solo cambia después de leer el mismo número dos veces seguidas, así que una lectura errónea de un solo fotograma no parpadea. **Tamaño del texto del escaneo** hace la etiqueta más pequeña o más grande. Un número redondo como 12,000 puede ser recuperación o un depósito de superficie (minería ROC o FPS); la recuperación aparece primero y los demás se marcan como solo en superficie, porque en el espacio solo puede ser recuperación. - **Cuando se escanea un mineral vigilado o recuperación**: elige cómo te avisa la etiqueta. **Brillo** y **Parpadeo** vienen activados por defecto; puedes añadir **Cambiar el color del texto** (verde brillante), **Texto más grande** y **Reproducir un sonido**. El parpadeo y el sonido llegan cuando el objetivo se lee por primera vez, no otra vez mientras sigue en pantalla. Con **Reproducir un sonido** activado, **Sonido de alerta** elige el sonido: **Smart Citizen predeterminado** (un breve tono), una voz en inglés (acento estadounidense, británico, australiano, irlandés o nigeriano) o uno de los sonidos de Windows, y **Escuchar** lo reproduce. Un sonido de Windows sigue tu combinación de sonidos de Windows; uno configurado como (Ninguno) no suena. -- **Cajón de la superposición** coloca secciones con pestañas en el borde de la pantalla. Haz clic en una pestaña para abrir su sección y vuelve a hacer clic para cerrarla. **Posición del cajón** elige uno de ocho lugares (en el centro a la derecha por defecto). **Atajo del cajón** fija una combinación de teclas que abre el cajón desde el juego en la última sección usada; pulsarla otra vez lo cierra. En el juego sigue manteniendo pulsada la F para usar el ratón en él, porque Windows no deja que la superposición le quite el ratón a Star Citizen. Star Citizen sigue recibiendo esas teclas, así que elige una combinación que no uses en el juego. Debe llevar Ctrl, Alt o Win, salvo que sea una tecla F o Pausa. **Borrar** quita el atajo. Si otro programa ya la usa, la pestaña te lo dice. +- **Cajón de la superposición** coloca secciones con pestañas en el borde de la pantalla. Haz clic en una pestaña para abrir su sección y vuelve a hacer clic para cerrarla. **Posición del cajón** elige uno de ocho lugares (en el centro a la derecha por defecto). **Atajo del cajón** fija una combinación de teclas que abre el cajón desde el juego en la última sección usada; pulsarla otra vez lo cierra. En el juego sigue manteniendo pulsada la F para usar el ratón en él, porque Windows no deja que la superposición le quite el ratón a Star Citizen. Star Citizen sigue recibiendo esas teclas, así que elige una combinación que no uses en el juego. En el juego, mantén pulsadas las teclas un momento: una pulsación muy breve, como un botón de Stream Deck sin tiempo de pulsación, puede pasarse por alto. Si Star Citizen se ejecuta como administrador, Smart Citizen también debe hacerlo, o el atajo no hará nada en el juego. Debe llevar Ctrl, Alt o Win, salvo que sea una tecla F o Pausa. **Borrar** quita el atajo. Si otro programa ya la usa, la pestaña te lo dice. - **Blueprints**: busca blueprints, mira qué misiones los otorgan y marca los que posees (la misma colección que la pestaña Rastreador de blueprints). - **Minerales**: escribe un mineral para ver dónde se encuentra, agrupado por sistema estelar, o una ubicación para ver sus minerales. Marca un mineral, o **Recuperación** al final de la lista, para vigilarlo: la etiqueta del escaneo te avisa cuando un escaneo lo encuentra. El decodificador también puede activarse y desactivarse aquí. - **Fabricación**: escribe un mineral para ver qué objetos lo usan, o un objeto para ver los minerales que necesita. Se rellena al generar las mejoras con **Commodities** o **Journal** marcados. diff --git a/languages/spanish/LEGAL.md b/languages/spanish/LEGAL.md index f6efc2be..bca7cff0 100644 --- a/languages/spanish/LEGAL.md +++ b/languages/spanish/LEGAL.md @@ -50,6 +50,17 @@ Smart Citizen realiza peticiones de red salientes solo en cuatro circunstancias: - **Fuentes remotas configuradas por el usuario**: si has configurado una fuente de datos apuntando a una URL `http(s)://` en la pestaña Configuración, Smart Citizen consulta esa URL al refrescar los archivos de origen. De fábrica esto solo aplica a la forma de URL «GitHub raw» de la fuente `global`; la configuración estándar desde la v1.0 lee `base.ini` de tu extracción local de Data.p4k. - **Lista de tiendas del buscador de objetos de SCO** — Mientras el overlay funciona con la sección Buscador de objetos activada, Smart Citizen descarga la lista de tiendas y precios desde la API de [UEX](https://uexcorp.space) (`api.uexcorp.uk`), como mucho cada 12 horas. Son dos peticiones simples que solo envían el nombre y la versión de la app; no se envía nada de tu equipo. La lista se guarda en caché localmente. Desactiva el Buscador de objetos en la pestaña Overlay para detenerlo. +### La superposición de Smart Citizen + +La superposición está apagada hasta que la inicias. Mientras funciona, todo lo que lee se queda en tu equipo: + +- **Pantalla** — captura una pequeña zona alrededor del indicador del escáner minero para leer el número de la señal. Las capturas se leen en memoria y no se guardan. +- **Game.log** — lee el registro de Star Citizen para encontrar los blueprints que recibes. +- **Windows** — pregunta a Windows qué ventana está en primer plano y si el puntero del ratón está visible, para que el cajón deje pasar tus clics al juego mientras apuntas. +- **Atajo del cajón** — solo si defines uno. Mientras Star Citizen está en primer plano, pregunta a Windows si la tecla del atajo está pulsada, y las teclas Ctrl, Alt, Mayús y Win solo cuando lo está. No pregunta por ninguna otra tecla y nunca recibe lo que escribes. + +Nunca lee la memoria del juego, nunca se engancha ni se inyecta en el juego y nunca le envía entradas. + ### Lo que Smart Citizen **no** hace - Nada de telemetría, analítica ni informes de uso de ningún tipo. diff --git a/languages/spanish/ui.json b/languages/spanish/ui.json index f3b04fc1..59718e52 100644 --- a/languages/spanish/ui.json +++ b/languages/spanish/ui.json @@ -2992,6 +2992,14 @@ "ht": "", "at": "Smart Citizen no pudo usar una carpeta de trabajo en:\n{folder}\n\n{reason}\n\nLa extracción no se inició, así que no se cambió nada." }, + "contract_scan_failed": { + "ht": "", + "at": "La generación de mejoras se detuvo porque no se pudieron leer {skipped} de {total} contratos. Tus mejoras actuales no han cambiado. Infórmalo, ya que suele ser un error de Smart Citizen.\n\nPrimer contrato:\n{first}" + }, + "contract_scan_stopped": { + "ht": "", + "at": "La generación de mejoras se detuvo porque la lectura de contratos falló. Tus mejoras actuales no han cambiado. Infórmalo, ya que suele ser un error de Smart Citizen.\n\nEl error:\n{first}" + }, "cache_folder_refused": { "ht": "", "at": "Windows le denegó a Smart Citizen el permiso para crear la caché de DataForge en:\n{folder}\n\nLa extracción no se inició, así que no se cambió nada." @@ -3123,7 +3131,7 @@ }, "description": { "ht": "", - "at": "Elige qué categorías de mejoras se ejecutan al Generar. Naves, componentes, armas de nave, armas FPS, misiones, recompensas de misión, fabricación de mercancías y consumibles médicos pueden activarse de forma independiente." + "at": "Elige qué categorías de mejoras se ejecutan al Generar: Ships, Ship Items, Gear, Missions, Commodities, Journal, Medical Consumables. Ship Items incluye componentes, armas de nave y misiles; Gear incluye armas FPS y etiquetas de armadura. Cada categoría se activa o desactiva por separado." } }, "enh_favorites": { @@ -3156,24 +3164,24 @@ "at": "Construye las etiquetas entre corchetes añadidas a componentes, misiles, armas de nave, mercancías y armaduras. Reordena elementos con ▲/▼, desmarca para excluir, cambia la longitud de abreviatura, elige separador y corchetes, o coloca la etiqueta después del nombre en lugar de antes." } }, - "overlay": { + "blueprint_tracker": { "title": { "ht": "", - "at": "8. Superposición de Smart Citizen" + "at": "7. Rastreador de blueprints" }, "description": { "ht": "", - "at": "Inicia la superposición aquí o con el botón Superposición de la barra de herramientas. Sobre el juego decodifica las firmas de escaneo minero, abre un cajón para buscar tus blueprints, minerales y fabricación, y marca como poseídos los blueprints que consigues. Ejecuta el juego en modo ventana sin bordes en tu pantalla principal." + "at": "Marca los blueprints que posees. Busca en la lista izquierda por nombre o misión, o acótala por Tipo, Clase, Tamaño y Grado de componente, y usa las flechas para mover objetos a tu lista de adquiridos. Los blueprints adquiridos reciben una etiqueta [Owned] allí donde aparezcan entre las recompensas potenciales de una misión, para ver de un vistazo qué merece la pena perseguir." } }, - "blueprint_tracker": { + "overlay": { "title": { "ht": "", - "at": "7. Rastreador de blueprints" + "at": "8. Superposición de Smart Citizen" }, "description": { "ht": "", - "at": "Marca los blueprints que posees. Busca en la lista izquierda por nombre o misión, o acótala por Tipo, Clase, Tamaño y Grado de componente, y usa las flechas para mover objetos a tu lista de adquiridos. Los blueprints adquiridos reciben una etiqueta [Owned] allí donde aparezcan entre las recompensas potenciales de una misión, para ver de un vistazo qué merece la pena perseguir." + "at": "Inicia la superposición aquí o con el botón Superposición de la barra de herramientas. Sobre el juego decodifica las firmas de escaneo minero, abre un cajón para buscar tus blueprints, minerales y fabricación, y marca como poseídos los blueprints que consigues. Ejecuta el juego en modo ventana sin bordes en tu pantalla principal." } }, "edit": { @@ -3233,7 +3241,7 @@ }, "description": { "ht": "", - "at": "Elige el tema de la app (Default / Light / Dark / ODW) y desactiva, si quieres, el recorrido automático en versiones nuevas." + "at": "Elige el tema de la app (Default / Light / Dark / ODW) y el tamaño de letra (Pequeño / Mediano / Grande, se aplica tras reiniciar), y desactiva, si quieres, el recorrido automático en versiones nuevas." } }, "cfg_sc_install": { @@ -3273,13 +3281,33 @@ }, "description": { "ht": "", - "at": "Importa un INI externo a tus modificaciones mediante el diálogo de resolución de conflictos, o restablece tu user.ini del canal activo (con copia de seguridad automática antes de borrarlo)." + "at": "Importa un INI externo a tus modificaciones mediante el diálogo de resolución de conflictos. Restablece tu user.ini del canal activo (con copia de seguridad previa) o recupera una copia anterior con Restaurar user.ini. Vista previa muestra lo que escribiría Aplicar, y Buscar actualizaciones comprueba si hay una versión nueva." + } + }, + "cfg_backup": { + "title": { + "ht": "", + "at": "19. Config: Copia de seguridad de ajustes" + }, + "description": { + "ht": "", + "at": "Exportar ajustes guarda tus preferencias, configuraciones de etiquetas, carpeta de Star Citizen y textos personalizados de todos los canales en un solo archivo. Importar ajustes los recupera, en un PC nuevo o tras una instalación limpia." + } + }, + "cfg_sc_tools": { + "title": { + "ht": "", + "at": "20. Config: Herramientas de Star Citizen" + }, + "description": { + "ht": "", + "at": "Borrar caché de shaders muestra las carpetas de caché de shaders del juego, una por versión. Limpiar borra los shaders y conserva tus ajustes gráficos; Eliminar borra la carpeta entera. Cierra Star Citizen antes." } }, "help": { "title": { "ht": "", - "at": "19. Ayuda y comentarios" + "at": "21. Ayuda y comentarios" }, "description": { "ht": "", @@ -3590,7 +3618,7 @@ }, "desc": { "ht": "", - "at": "Ventanas dibujadas sobre Star Citizen: el decodificador de escaneo minero y el cajón de blueprints. Ejecuta el juego en modo ventana sin bordes. La superposición solo lee tu pantalla y Game.log y, si defines un atajo para el cajón, observa las teclas pulsadas solo para esa combinación; nunca toca el proceso del juego." + "at": "Ventanas dibujadas sobre Star Citizen: el decodificador de escaneo minero y el cajón de blueprints. Ejecuta el juego en modo ventana sin bordes. La superposición solo lee tu pantalla y Game.log, pregunta a Windows qué ventana está en primer plano y si el puntero está visible y, si defines un atajo para el cajón, si su tecla y las teclas Ctrl, Alt, Mayús y Win están pulsadas; nunca toca el proceso del juego." }, "start_btn": { "ht": "", diff --git a/languages/turkish/ABOUT.md b/languages/turkish/ABOUT.md index 772f94f3..870bec7e 100644 --- a/languages/turkish/ABOUT.md +++ b/languages/turkish/ABOUT.md @@ -29,6 +29,7 @@ Smart Citizen'a kod katkısında bulunanlara teşekkürler: - **scubamount** - **hkstrongside** - **odw-okano** +- **RWolfyo** ## Çevirmenler @@ -113,7 +114,7 @@ Smart Citizen ayrıca şu kaynaklardan gelen üst akış araçlarını da paketl - **Görev Başlıkları**: Nakliye başlıklarını rotalarıyla başlatın (ör. `Area18 > Lorville`) — yapılandırılabilir yerleşim, ok, ayırıcı ve konum ayrıntısı, ayrıca isteğe bağlı orijinal başlık kısaltma, canlı önizleme ile - **İstatistikler Üstte veya Altta**: İstatistik bloğunun açıklamanın üstünde mi altında mı yer alacağını seçin - **Plan Takipçisi**: Zaten sahip olduğunuz üretim planlarını işaretlemek için özel bir sekme. Öğeleri Mevcut ve Sahip Olunan listeleri arasında taşıyın, Görev / Tür / Sınıf / Boyut / Derece'ye göre filtreleyin; sahip olunan öğeler görev plan listelerinde mavi bir `[Owned]` etiketi alır. **Sahip Olunan Planlar için Günlükleri Tara**, Star Citizen günlük dosyalarınızdan sahiplik bilgisini otomatik olarak doldurur ve yalnızca son taramadan bu yana yeni olanları içe aktarır (veya **Başlangıçta günlükleri otomatik tara** açıksa başlangıçta otomatik olarak); **Sahip Olunan Planları Dışa Aktar / İçe Aktar** ise sahip olunan listesini bilgisayarlar arasında taşır (JSON veya CSV; içe aktarma yalnızca ekleme yapar ve scmdb.net dışa aktarımları da çalışır) -- **Smart Citizen Katmanı**: Oyunun üzerinde isteğe bağlı pencereler (kenarlıksız pencere modu). Bir maden tarama çözücüsü bir imzanın ardındaki yatağı gösterir (`3 × Lindinium`) ve izlediğiniz mineraller veya hurda için parlayabilir, yanıp sönebilir ya da ses çalabilir; kendi kısayolu olan bir çekmece planlarınızı, minerallerin nerede bulunduğunu ve neyin üretiminde kullanıldıklarını arar; katman çalışırken kazandığınız planlar da `Game.log` üzerinden sahip olunan olarak işaretlenir. Yalnızca ekran pikselleri, `Game.log` ve isteğe bağlı bir kısayol: kod enjeksiyonu, bellek okuma veya girdi yok +- **Smart Citizen Katmanı**: Oyunun üzerinde isteğe bağlı pencereler (kenarlıksız pencere modu). Bir maden tarama çözücüsü bir imzanın ardındaki yatağı gösterir (`3 × Lindinium`) ve izlediğiniz mineraller veya hurda için parlayabilir, yanıp sönebilir ya da ses çalabilir; kendi kısayolu olan bir çekmece planlarınızı, minerallerin nerede bulunduğunu ve neyin üretiminde kullanıldıklarını arar; katman çalışırken kazandığınız planlar da `Game.log` üzerinden sahip olunan olarak işaretlenir. Yalnızca ekran pikselleri, `Game.log`, öndeki pencere, işaretçinin görünürlüğü ve isteğe bağlı bir kısayol: kod enjeksiyonu, bellek okuma veya girdi yok - **Görev Etiketleri**: Bölüm başlıklarını (MISSION DETAILS, POTENTIAL BLUEPRINTS vb.), XP etiketini ve başlıklar için kullanılan vurgu etiketini yeniden adlandırın - **Bildirimsel CIG Veri Hatası Yamaları**: Bir yama sistemi, bilinen DataForge hatalarına yönelik düzeltmeleri çıkarma sırasında uygular; böylece oyun içi metin CIG'i beklemeden doğru okunur - **Seçmeli Kategoriler**: Her geliştirme kategorisini Geliştirmeler sekmesinden bağımsız olarak etkinleştirin veya devre dışı bırakın diff --git a/languages/turkish/FAQ.md b/languages/turkish/FAQ.md index 4c55bb98..a55c2809 100644 --- a/languages/turkish/FAQ.md +++ b/languages/turkish/FAQ.md @@ -15,7 +15,7 @@ Kişisel düzenlemeleriniz, oyundan ayrı olarak Smart Citizen veri klasörünü Smart Citizen yalnızca yerelleştirme metnini (oyunun size gösterdiği sözcükleri) düzenler; oyun mantığına dokunmaz, size herhangi bir avantaj sağlamaz ve CIG'in sunucularıyla iletişim kurmaz. Değişikliklerimiz sorun yaratmamalıdır **diye düşünüyoruz**. -İsteğe bağlı **Smart Citizen Katmanı** (Katman sekmesi) de aynı şekilde oyuna dokunmadan çalışır. Oyunun üzerine sıradan pencereler çizer, ekranınızdaki pikselleri bir ekran görüntüsü aracının yaptığı gibi okur ve oyunun `Game.log` dosyasını okur. Oyuna asla kod enjekte etmez veya kanca atmaz, oyunun işlemini asla açmaz veya belleğini okumaz ve asla klavye ya da fare girdisi göndermez. Bir çekmece kısayolu ayarlarsanız, bir programın kısayol istediği standart yolla yalnızca o tuş birleşimini Windows'a kaydeder. Star Citizen odaktayken diğer programların kaydettiği kısayolları engeller, bu yüzden bir kısayol ayarlı olduğu sürece katman klavyenin ham girdisini (raw input) de alır; bu, Windows'un arka plandaki bir programa tuş basışlarını bildirdiği salt okunur yoldur. Bu bir klavye kancası değildir: hiçbir tuşu tutmaz, değiştirmez veya göndermez, hiçbir kayıt tutmaz ve yalnızca sizin birleşiminize tepki verir. CIG bu tür katmanlar hakkında herhangi bir açıklama yapmadı; bu nedenle aşağıdaki, kullanımın kendi sorumluluğunuzda olduğuna dair not burada da geçerlidir. +İsteğe bağlı **Smart Citizen Katmanı** (Katman sekmesi) de aynı şekilde oyuna dokunmadan çalışır. Oyunun üzerine sıradan pencereler çizer, ekranınızdaki pikselleri bir ekran görüntüsü aracının yaptığı gibi okur ve oyunun `Game.log` dosyasını okur. Çekmecesi görünürken Windows'a hangi pencerenin önde olduğunu ve fare işaretçisinin görünüp görünmediğini de sorar, böylece nişan alırken atışlarınız çekmeceden geçer. Oyuna asla kod enjekte etmez veya kanca atmaz, oyunun işlemini asla açmaz veya belleğini okumaz ve asla klavye ya da fare girdisi göndermez. Bir çekmece kısayolu ayarlarsanız, bir programın kısayol istediği standart yolla yalnızca o tuş birleşimini Windows'a kaydeder. Star Citizen odaktayken diğer programların kaydettiği kısayolları engeller, bu yüzden oyun öndeyken katman Windows'a o birleşimin tuşunun basılı olup olmadığını da sorar ve yalnızca o tuş basılıyken Ctrl, Alt, Shift veya Win tuşunun basılı tutulup tutulmadığını sorar. Başka hiçbir tuşu sormaz, oyunda veya başka bir programda yazdıklarınız ona asla gönderilmez ve hiçbir tuşu asla tutmaz, değiştirmez veya göndermez. CIG bu tür katmanlar hakkında herhangi bir açıklama yapmadı; bu nedenle aşağıdaki, kullanımın kendi sorumluluğunuzda olduğuna dair not burada da geçerlidir. CIG, topluluk yerelleştirmesini açıkça desteklemiştir. [Community Localization Update](https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/star-citizen-community-localization-update) gönderisi, oyuncular tarafından yapılan çevirilere yönelik resmi desteği ortaya koyar; bizim anladığımız kadarıyla bu, Smart Citizen'ın yaptığı türden yerelleştirme düzenlemelerine açıkça izin vermektedir. diff --git a/languages/turkish/HELP.md b/languages/turkish/HELP.md index 55249b80..e18eb57e 100644 --- a/languages/turkish/HELP.md +++ b/languages/turkish/HELP.md @@ -80,6 +80,8 @@ Düğmenin rengi nerede olduğunuzu söyler: **kırmızı**, son uygulamanızdan Smart Citizen ayrıca başlatıcı sürüm metnine (`Frontend_PU_Version`) küçük bir filigran ekler ve kendi satırında `\nLocalizations Enhanced with Smart Citizen v{VERSION}` yazar. Yerelleştirme paketinizin etkin olduğunu oyun içinde böyle doğrulayabilirsiniz — Star Citizen ana menüsündeki sürüm etiketine bakın. Damga her uygulamada yeniden yazılır; bu nedenle sürümler arasında birikmez. +Uygulama sırasında Smart Citizen, ana menüdeki Oyna düğmesine (`Frontend_play_star_citizen`) ikinci satır olarak `Run Smart Citizen after every patch` ekler ve iki satırı da ortalar. Bir oyun yaması uygulanmış `global.ini` dosyasını yerinde bırakır, ancak yamanın eklediği anahtarlar siz Smart Citizen'ı çalıştırıp yeniden uygulayana kadar ham `@key` adları olarak görünür. Bu yüzden hatırlatma, yamadan sonra oyun ilk açıldığında menüde durur. Damga gibi her uygulamada yeniden yazılır ve hangi dili seçerseniz seçin İngilizce kalır. + ## 8. Bir Yedeği Geri Yükleyin Önceki bir sürüme dönmek için araç çubuğundaki **Daha Fazla** menüsünü açın ve **Yedeği Geri Yükle** seçeneğini seçin. Smart Citizen en fazla **5 otomatik yedek** saklar — yenileri oluşturuldukça en eskisi silinir. @@ -166,11 +168,11 @@ Hangi üretim planlarına zaten sahip olduğunuzu takip edin ve bunun oyun için ## Katman Sekmesi -**Smart Citizen Katmanı**, Star Citizen'ın üzerine iki küçük pencere çizer: bir maden tarama çözücüsü ve bir arama çekmecesi. Katmanı bu sekmedeki **Katmanı Başlat** düğmesiyle veya araç çubuğundaki **Katman** düğmesiyle başlatıp durdurun. Oyunu ana ekranınızda kenarlıksız pencere modunda çalıştırın; aksi halde katman oyunun üzerinde görünemez. Katman yalnızca ekranınızı ve `Game.log` dosyasını okur, bir çekmece kısayolu ayarlarsanız yalnızca o birleşim için tuş basışlarını izler; oyunun kendisine asla dokunmaz. +**Smart Citizen Katmanı**, Star Citizen'ın üzerine iki küçük pencere çizer: bir maden tarama çözücüsü ve bir arama çekmecesi. Katmanı bu sekmedeki **Katmanı Başlat** düğmesiyle veya araç çubuğundaki **Katman** düğmesiyle başlatıp durdurun. Oyunu ana ekranınızda kenarlıksız pencere modunda çalıştırın; aksi halde katman oyunun üzerinde görünemez. Katman yalnızca ekranınızı ve `Game.log` dosyasını okur, Windows'a hangi pencerenin önde olduğunu ve fare işaretçisinin görünüp görünmediğini sorar (böylece nişan alırken atışlarınız çekmeceden geçer), bir çekmece kısayolu ayarlarsanız kısayolun tuşunun ve Ctrl, Alt, Shift ve Win tuşlarının basılı olup olmadığını da sorar; oyunun kendisine asla dokunmaz. - **Maden tarama çözücüsü** radarınızın altındaki tarama imzasını okur ve yatak türünü ve sayısını hemen altında gösterir (örneğin `3 × Lindinium`). Etiket yalnızca aynı sayı art arda iki kez okunduktan sonra değişir; böylece tek karelik bir yanlış okuma ekranda yanıp sönmez. **Tarama metni boyutu** etiketi küçültür veya büyütür. 12,000 gibi yuvarlak bir sayı hurda da olabilir, yüzeydeki bir yatak da (ROC veya FPS madenciliği); hurda ilk sırada gösterilir, diğerleri yalnızca yüzeyde olarak işaretlenir, çünkü uzayda yalnızca hurda olabilir. - **İzlenen bir mineral veya hurda tarandığında**: etiketin sizi nasıl uyaracağını seçin. **Parlama** ve **Yanıp sönme** varsayılan olarak açıktır; **Metin rengini değiştir** (parlak yeşil), **Daha büyük metin** ve **Ses çal** eklenebilir. Yanıp sönme ve ses, hedef ilk okunduğunda gelir; hedef ekranda kaldığı sürece tekrarlanmaz. **Ses çal** açıkken **Uyarı sesi** sesi seçer: **Smart Citizen Varsayılan** (kısa bir çan sesi), İngilizce bir ses (ABD, Birleşik Krallık, Avustralya, İrlanda veya Nijerya aksanı) ya da Windows seslerinden biri; **Dinle** onu çalar. Windows sesleri Windows ses düzeninizi izler; orada (Yok) olarak ayarlanan ses çalmaz. -- **Katman çekmecesi** ekranın kenarına sekmeli bölümler yerleştirir. Bir bölümü açmak için sekmesine tıklayın, kapatmak için yeniden tıklayın. **Çekmece konumu** sekiz noktadan birini seçer (varsayılan olarak sağ orta). **Çekmece kısayolu**, çekmeceyi oyunun içinden en son kullanılan bölümde açan bir tuş birleşimi ayarlar; yeniden basmak onu kapatır. Windows katmanın fareyi Star Citizen'dan almasına izin vermediği için oyunda fareyi içinde kullanmak için yine F tuşunu basılı tutun. Star Citizen bu tuşları yine de alır, bu yüzden oyunda kullanmadığınız bir birleşim seçin. F tuşu veya Pause değilse içinde Ctrl, Alt veya Win olmalıdır. **Temizle** kısayolu kaldırır. Başka bir program onu zaten kullanıyorsa sekme bunu söyler. +- **Katman çekmecesi** ekranın kenarına sekmeli bölümler yerleştirir. Bir bölümü açmak için sekmesine tıklayın, kapatmak için yeniden tıklayın. **Çekmece konumu** sekiz noktadan birini seçer (varsayılan olarak sağ orta). **Çekmece kısayolu**, çekmeceyi oyunun içinden en son kullanılan bölümde açan bir tuş birleşimi ayarlar; yeniden basmak onu kapatır. Windows katmanın fareyi Star Citizen'dan almasına izin vermediği için oyunda fareyi içinde kullanmak için yine F tuşunu basılı tutun. Star Citizen bu tuşları yine de alır, bu yüzden oyunda kullanmadığınız bir birleşim seçin. Oyunda tuşları bir an basılı tutun: çok kısa bir basış, örneğin basılı tutma süresi olmayan bir Stream Deck düğmesi, kaçırılabilir. Star Citizen yönetici olarak çalışıyorsa Smart Citizen da öyle çalışmalıdır, yoksa kısayol oyunda hiçbir şey yapmaz. F tuşu veya Pause değilse içinde Ctrl, Alt veya Win olmalıdır. **Temizle** kısayolu kaldırır. Başka bir program onu zaten kullanıyorsa sekme bunu söyler. - **Planlar**: Plan arayın, hangi görevlerin onları ödül olarak verdiğini görün ve sahip olduklarınızı işaretleyin (Plan Takipçisi sekmesiyle aynı sahip olunan listesi). - **Mineraller**: Yıldız sistemine göre gruplanmış olarak nerede bulunduğunu görmek için bir mineral, minerallerini görmek için de bir konum yazın. Bir minerali veya listenin en altındaki **Hurda** satırını izlemek için işaretleyin: bir tarama onu bulduğunda tarama etiketi sizi uyarır. Çözücü burada da açılıp kapatılabilir. - **Üretim**: Onu hangi eşyaların kullandığını görmek için bir mineral, gerektirdiği mineralleri görmek için de bir eşya yazın. **Emtialar** veya **Günce** işaretliyken geliştirmeleri oluşturduğunuzda doldurulur. diff --git a/languages/turkish/LEGAL.md b/languages/turkish/LEGAL.md index 76eb470d..dab0fa0a 100644 --- a/languages/turkish/LEGAL.md +++ b/languages/turkish/LEGAL.md @@ -50,6 +50,17 @@ Smart Citizen yalnızca dört durumda giden ağ isteği yapar: - **Kullanıcı tarafından yapılandırılan uzak kaynaklar** — Yapılandırma sekmesinde bir `http(s)://` URL'sine işaret eden bir veri kaynağı yapılandırdıysanız Smart Citizen, kaynak dosyalarını yenilerken bu URL'yi alır. Kurulum sonrası varsayılan durumda bu yalnızca `global` kaynağının GitHub-raw URL biçimi için geçerlidir; v1.0'dan bu yana standart yapılandırma `base.ini` dosyasını bunun yerine yerel Data.p4k çıkarımınızdan okur. - **SCO Eşya Bulucu mağaza listesi** — Overlay, Eşya Bulucu bölümü açıkken çalıştığı sürece Smart Citizen mağaza ve eşya fiyatı listesini [UEX](https://uexcorp.space) API'sinden (`api.uexcorp.uk`) en fazla 12 saatte bir indirir. Bunlar yalnızca uygulamanın adını ve sürümünü taşıyan iki basit istektir; bilgisayarınızdan hiçbir şey gönderilmez. Liste yerel olarak önbelleğe alınır. Durdurmak için Overlay sekmesinde Eşya Bulucu'yu kapatın. +### Smart Citizen Katmanı + +Katman siz başlatana kadar kapalıdır. Çalışırken okuduğu her şey bilgisayarınızda kalır: + +- **Ekran** — sinyal sayısını okumak için maden tarayıcısının göstergesinin çevresindeki küçük bir alanı yakalar. Yakalamalar bellekte okunur ve kaydedilmez. +- **Game.log** — aldığınız planları bulmak için Star Citizen'ın günlüğünü okur. +- **Windows** — nişan alırken çekmecenin tıklamalarınızı oyuna geçirmesi için Windows'a hangi pencerenin önde olduğunu ve fare işaretçisinin görünüp görünmediğini sorar. +- **Çekmece kısayolu** — yalnızca bir kısayol ayarlarsanız. Star Citizen öndeyken Windows'a kısayolun tuşunun basılı olup olmadığını sorar; Ctrl, Alt, Shift ve Win tuşlarını yalnızca o tuş basılıyken sorar. Başka hiçbir tuşu sormaz ve yazdıklarınızı asla almaz. + +Oyunun belleğini asla okumaz, oyuna asla kanca atmaz veya enjekte olmaz ve oyuna asla girdi göndermez. + ### Smart Citizen'ın **yapmadığı** şeyler - Hiçbir türde telemetri, analiz veya kullanım raporlaması yoktur. diff --git a/languages/turkish/ui.json b/languages/turkish/ui.json index 19661574..a68033c7 100644 --- a/languages/turkish/ui.json +++ b/languages/turkish/ui.json @@ -2992,6 +2992,14 @@ "ht": "", "at": "Smart Citizen şu konumda bir çalışma klasörü kullanamadı:\n{folder}\n\n{reason}\n\nÇıkarma işlemi başlamadı, bu yüzden hiçbir şey değiştirilmedi." }, + "contract_scan_failed": { + "ht": "", + "at": "{total} sözleşmeden {skipped} tanesi okunamadığı için geliştirme oluşturma durduruldu. Mevcut geliştirmeleriniz değişmedi. Genellikle Smart Citizen hatası olduğundan lütfen bildirin.\n\nİlk sözleşme:\n{first}" + }, + "contract_scan_stopped": { + "ht": "", + "at": "Sözleşmeler okunurken bir hata oluştuğu için geliştirme oluşturma durduruldu. Mevcut geliştirmeleriniz değişmedi. Genellikle Smart Citizen hatası olduğundan lütfen bildirin.\n\nHata:\n{first}" + }, "cache_folder_refused": { "ht": "", "at": "Windows, Smart Citizen'ın şu konumda DataForge önbelleğini oluşturma iznini reddetti:\n{folder}\n\nÇıkarma işlemi başlamadı, bu yüzden hiçbir şey değiştirilmedi." @@ -3237,7 +3245,7 @@ }, "description": { "ht": "", - "at": "Oluştur dediğinizde hangi geliştirme kategorilerinin çalışacağını seçin. Gemiler, bileşenler, gemi silahları, FPS silahları, görevler, görev ödülleri, emtia üretimi ve tıbbi sarf malzemelerinin her biri bağımsız olarak etkinleştirilebilir." + "at": "Oluştur'a basınca hangi geliştirme kategorilerinin çalışacağını seçin: Ships, Ship Items, Gear, Missions, Commodities, Journal, Medical Consumables. Ship Items bileşenleri, gemi silahlarını ve füzeleri; Gear FPS silahlarını ve zırh etiketlerini kapsar. Her kategori ayrı ayrı açılıp kapatılabilir." } }, "enh_favorites": { @@ -3270,24 +3278,24 @@ "at": "Bileşenlere, füzelere, gemi silahlarına, emtialara ve zırhlara eklenen köşeli parantezli ad etiketlerini oluşturun. Öğeleri ▲/▼ ile yeniden sıralayın, hariç tutmak için işaretini kaldırın, kısaltma uzunluğunu değiştirin, ayırıcı ve parantez seçin veya etiketi adın önüne değil arkasına yerleştirin." } }, - "overlay": { + "blueprint_tracker": { "title": { "ht": "", - "at": "8. Smart Citizen Katmanı" + "at": "7. Plan Takipçisi" }, "description": { "ht": "", - "at": "Katmanı buradan veya araç çubuğundaki Katman düğmesiyle başlatın. Oyunun üzerinde maden tarama imzalarını çözer, planlarınızı, minerallerinizi ve üretimi aramak için bir çekmece açar ve kazandığınız planları sahip olunan olarak işaretler. Oyunu ana ekranınızda kenarlıksız pencere modunda çalıştırın." + "at": "Sahip olduğunuz planları işaretleyin. Soldaki listede ada veya göreve göre arama yapın ya da bileşen Türü, Sınıfı, Boyutu ve Derecesine göre daraltın, ardından öğeleri sahip olunanlar listenize taşımak için okları kullanın. Sahip olunan planlar, bir görevin olası ödüllerinde göründükleri her yerde [Owned] etiketi alır; böylece neyin peşine düşmeye değer olduğunu bir bakışta görebilirsiniz." } }, - "blueprint_tracker": { + "overlay": { "title": { "ht": "", - "at": "7. Plan Takipçisi" + "at": "8. Smart Citizen Katmanı" }, "description": { "ht": "", - "at": "Sahip olduğunuz planları işaretleyin. Soldaki listede ada veya göreve göre arama yapın ya da bileşen Türü, Sınıfı, Boyutu ve Derecesine göre daraltın, ardından öğeleri sahip olunanlar listenize taşımak için okları kullanın. Sahip olunan planlar, bir görevin olası ödüllerinde göründükleri her yerde [Owned] etiketi alır; böylece neyin peşine düşmeye değer olduğunu bir bakışta görebilirsiniz." + "at": "Katmanı buradan veya araç çubuğundaki Katman düğmesiyle başlatın. Oyunun üzerinde maden tarama imzalarını çözer, planlarınızı, minerallerinizi ve üretimi aramak için bir çekmece açar ve kazandığınız planları sahip olunan olarak işaretler. Oyunu ana ekranınızda kenarlıksız pencere modunda çalıştırın." } }, "edit": { @@ -3347,7 +3355,7 @@ }, "description": { "ht": "", - "at": "Uygulama temasını seçin (Varsayılan / Açık / Koyu / ODW) ve isterseniz yeni sürümlerde otomatik turu devre dışı bırakın." + "at": "Uygulama temasını (Varsayılan / Açık / Koyu / ODW) ve yazı boyutunu (Küçük / Orta / Büyük, yeniden başlatınca uygulanır) seçin; isterseniz yeni sürümlerde otomatik turu kapatın." } }, "cfg_sc_install": { @@ -3387,13 +3395,33 @@ }, "description": { "ht": "", - "at": "Çakışma çözme iletişim kutusu aracılığıyla harici bir INI dosyasını geçersiz kılmalarınıza aktarın veya etkin kanal için user.ini dosyanızı sıfırlayın (temizlenmeden önce otomatik olarak yedeklenir)." + "at": "Harici bir INI dosyasını çakışma çözme penceresiyle geçersiz kılmalarınıza aktarın. Etkin kanalın user.ini dosyasını sıfırlayın (önce yedeklenir) ya da user.ini Dosyasını Geri Yükle ile önceki bir kopyayı geri getirin. Önizleme Uygula'nın ne yazacağını gösterir, Güncellemeleri Denetle yeni sürüm arar." + } + }, + "cfg_backup": { + "title": { + "ht": "", + "at": "19. Yapılandırma: Ayar Yedeği" + }, + "description": { + "ht": "", + "at": "Ayarları Dışa Aktar tercihlerinizi, etiket ayarlarınızı, Star Citizen klasörünüzü ve tüm kanallardaki özel metinlerinizi tek bir dosyaya kaydeder. Ayarları İçe Aktar bunları yeni bir bilgisayarda ya da temiz kurulumdan sonra geri getirir." + } + }, + "cfg_sc_tools": { + "title": { + "ht": "", + "at": "20. Yapılandırma: Star Citizen Araçları" + }, + "description": { + "ht": "", + "at": "Gölgelendirici Önbelleğini Temizle, oyunun gölgelendirici önbellek klasörlerini her oyun sürümü için bir tane olacak şekilde listeler. Temizle gölgelendiricileri siler ve grafik ayarlarınızı korur; Kaldır tüm klasörü siler. Önce Star Citizen'ı kapatın." } }, "help": { "title": { "ht": "", - "at": "19. Yardım ve geri bildirim" + "at": "21. Yardım ve geri bildirim" }, "description": { "ht": "", @@ -3590,7 +3618,7 @@ }, "desc": { "ht": "", - "at": "Star Citizen'ın üzerine çizilen pencereler: maden tarama çözücüsü ve plan çekmecesi. Oyunu kenarlıksız pencere modunda çalıştırın. Katman yalnızca ekranınızı ve Game.log dosyasını okur, bir çekmece kısayolu ayarlarsanız yalnızca o birleşim için tuş basışlarını izler; oyun işlemine asla dokunmaz." + "at": "Star Citizen'ın üzerine çizilen pencereler: maden tarama çözücüsü ve plan çekmecesi. Oyunu kenarlıksız pencere modunda çalıştırın. Katman yalnızca ekranınızı ve Game.log dosyasını okur, Windows'a hangi pencerenin önde olduğunu ve işaretçinin görünüp görünmediğini sorar, bir çekmece kısayolu ayarlarsanız kısayolun tuşunun ve Ctrl, Alt, Shift ve Win tuşlarının basılı olup olmadığını da sorar; oyun işlemine asla dokunmaz." }, "start_btn": { "ht": "", diff --git a/scripts/CLAUDE.md b/scripts/CLAUDE.md index 143ded1e..5b21aba8 100644 --- a/scripts/CLAUDE.md +++ b/scripts/CLAUDE.md @@ -35,8 +35,11 @@ Closing Smart Citizen stops a running generation. `main()` takes `should_cancel` ### Recco Battaglia's Scan/Mining contracts — "[RS ####]" mission-title tag (4.9+) `Battaglia_RPT_Scan_*` / `Battaglia_RPT_ScanMine_*` contracts each target 1-3 mineable ores via sibling `MissionProperty` overrides with `extendedTextToken="ResourceType"`/`"ResourceType2"`/`"ResourceType3"` pointing at a `mineabletype_primary_` loc key. CIG doesn't expose a per-ore "RS" (resonance-signature) number anywhere in DataForge — checked the full PTU 4.9 cache for both the literal values and any per-mineable stat registry, found neither — so `MINEABLE_RS_VALUES` is a curated table sourced from community reference data (MrKraken/StarStrings, `ptu/4.9` branch `mining.ini`, cross-checked against starminersdepot.com's Alpha 4.8 scanner table). `_battaglia_mineable_rs_in()` scans one contractgen XML for matching titles and formats e.g. `[RS 3600/4300/3900]` (multiple ores slash-joined, in ResourceType/2/3 order) — every contract variant sharing a title targets the same ore set, so first-variant-wins. A generation runs it on each file of the contractgen parse it shares with `scan_contract_generators` (see the single-pass entry below), so there is no separate pre-pass. The tag itself is a hardcoded title-loop append gated by the `"rs"` key in `AppSettings.MISSION_TITLE_TAG_KEYS`/`_MISSION_TITLE_TAG_SETTING` (the "General Tags" checkbox pattern — same shape as `[BP]`/`[ACE]`/`[…Rep]`, not the `TagConfig`/`render_tag()` element system). Locked by `tests/test_battaglia_mineable_rs.py`, which reads the tags off a `_run_gen_missions` run. +### A contract the scan cannot read is skipped with a WARNING, and a scan that skips most fails +`scan_contract_generators` reads each contract in its own `try`: one that raises leaves nothing behind, since its blueprints and items are recorded only once its variant is built, and the scan goes on. The line names the contract and the error type at WARNING, as the ship and component generators log a bad file, and not at ERROR, which would open the error box over one odd contract. It used to be at DEBUG, which a normal run does not show (the app logs at INFO unless it starts with `--debug` or `LOG_LEVEL=DEBUG`), so a bug in that block lost everything quietly: one wrong `ContractVariant(...)` call, tried on LIVE, skipped all 1,809 contracts it reached and 787 entries of `mission_rewards_enhancements.ini`, and the run still finished as a success. So more contracts skipped than giving a variant raise `ContractScanFailed` once the walk ends, as does a walk that stops on an error before any contract gave one (a walk that stops later keeps what it read, with its WARNING, as before), which is meant to take a bug here: failing every category of the run is the deliberate trade. `main()` has written no INI yet, so the old set stays whole, the worker leaves `.dataforge_stamp` empty and the next start offers to generate again. The script stays free of `tr()`: the worker matches the class by name, as it does `GenerationStopped`, and words its box with `extract.contract_scan_failed`, or `extract.contract_scan_stopped` for a walk that stopped (a total of 0), so keep the name and its fields. A listing that fails part-way stops the walk too, and `_run_gen_missions` still ends the run with that error itself. Game data should not be able to do it. A spawn count that is not a whole number does not raise (`_spawn_count`): one written as `4.0` reads as 4, and anything else counts as 0 with a WARNING, so the mission loses that spawn line and keeps its variant, because 52% of LIVE's released contracts read a count, and one change to how counts are written would otherwise stop every generation. A failure in a handler's own spawns skips those spawns with a WARNING of its own and keeps its contracts: it used to end the whole scan, with the later files lost and the variants unsorted. A variant is built by keyword, and a sub-contract's comes from its contract's with `_replace(desc_key=...)`, so two values cannot swap and the two cannot drift apart. `tests/test_contract_scan.py` and `tests/test_mission_variant_tuple.py` lock this. + ### Mining Compendium journal — per-ore Base Resource Signature line (2.2.0) `MINEABLE_RS_VALUES` (see the Battaglia entry above for sourcing) has a second consumer: the "Mining Fundamentals #2: Where to Mine" journal entry (`Journal_General_Mining_Compendium_Content`), reformatted by `scan_crafting_blueprints`'s per-mineral block builder into `Name` / `Locations:` / `Used To Craft:` blocks. Each ore's block now gets a `Base Resource Signature: {value}` line (inserted right after the name header, before Locations) whenever `MINEABLE_RS_VALUES` has a confirmed value for it; ores without one (the journal lists 35, the table covers 26) are left unchanged, no placeholder. `_MINING_COMPENDIUM_ORE_ALIASES` bridges the one known spelling mismatch between the journal's own prose and the DataForge loc-key convention (`"Savrilium"` in-journal vs `mineabletype_primary_savrillium`). Locked by `TestMiningCompendiumRSTagging` in `tests/test_commodity_journal.py`. -### DataForge XMLs read as few times as possible, and only XML facts in the lookup pickles (perf proposal) -`generate_enhancements_ini.py` parses each XML as few times as it can, and the `.lookups` pickles it reshapes hold facts read from the XML, never text made from base.ini or the Tag Builder config, so each is keyed on the DataForge build alone (`_LOOKUP_VERSIONS` records the shapes). `scitem_lookups` (`_scitem_facts`, the ~24k scitem files) and `blueprint_pools` (`_blueprint_pool_facts`) are turned into names and `[CLASS-Sx-grade]` tags on every run (`_render_scitem_lookups`, and the name loop in `build_blueprint_pool_lookup`), so a Tag Builder change or the annotate toggle re-renders them instead of parsing every scitem XML again. Because those two hold no loc text, the English-loc fallback mark (`en_loc_cache_mark`, for a translated run whose English base.ini is missing) keys only `standings`, the one pickle still built from the loc: a fallback run and the next English run share the facts pickles, and each renders its own names from them. `_component_name_tag` and `_mining_laser_component_tag` read their XML facts through `_component_tag_facts` / `_mining_laser_name_attr` and share the rendering (`_component_name_tag_from_facts`, `_mining_laser_tag_from_name`) with the cached path. The flight controller and armour lookups (`build_controller_lookup`, `build_armor_lookup`) hold the attribute values the ship block shows (`_controller_flight_stats`, `_armor_stats`) instead of lxml trees, still formatted in `enhancements_ship_dataforge`, so an armour value `_fmt` cannot format fails only its ship, as before. Those two are built on every run (about 0.2 s on LIVE) and never pickled: DataForge patches are applied again before every generation without a re-extraction, so a pickle keyed on the DataForge build would keep a patched controller or armour XML's old values until the next extraction. A pickle must hold builtins only: the app loads this script under a module name of its own, so a pickled class of the script would not load. The scitem walk finds the magazine with lxml's own tag filter when a file is ASCII-compatible and holds no `__polymorphicType` (`_holds_no_poly_type_attr`), which is every file on LIVE today, and keeps the per-element `_poly_type` loop otherwise. `_run_gen_missions` reads each pu_missions XML once (`_scan_pu_missions`: the #165 choice between a body with and without hostiles waits until every file is read) and each contractgen XML and contract template once (`scan_contract_generators` takes `roots` and `template_lookup`; the Battaglia RS tags and the calculated-reward diagnostic run on each root just before it, their errors held and raised where their own calls raised them, and the walk is finished for them if it stops early; a failure listing the files still ends the run). `scan_crafting_blueprints` parses each blueprint once, reads a carryable only when its filename names a commodity, and lowercases the loc keys once (`_commodity_loc_keys`), for the commodity entries, the Mining Compendium and the SCO crafting index (#474) alike. The hot loops parse through `_parse_xml_file` (the bytes read in one call, then `ET.fromstring`: the same parser and errors as `ET.parse`, and faster on Windows). On a LIVE cache (`main()` with `max_workers=1`, medians of three interleaved runs of the 3.0.0 code with #474 and #477 and of the perf proposal's final code, each with its own `src/`) a regeneration went from 11.9 s to 6.3 s, a components Tag Builder change from 31.0 s to 6.2 s, and the first generation after an extraction from 33.8 s to 24.0 s, which stays bound by parsing the ~1 GB of scitem XML once; the peak working set fell from about 320 MB to 190 MB. None of this changes a byte of output: every file the generator writes (the nine INIs and `crafting_index.json`) matched the unchanged code on a real LIVE cache, cold, warm, after a components change, with non-default components, commodities and armor configs with the annotate toggle on and off, and on a run whose English base.ini is missing. Run that comparison again for any change here. Two outputs used to depend on the string hash seed, because each took the order of a set: three courier titles in `mission_rewards_enhancements.ini` (`_derive_route_fragment` took the first of a set of bodies) and the order of the materials in `crafting_index.json` (`scan_crafting_blueprints` met each blueprint's materials in set order, #474's code). Both now sort (perf proposal), so two runs of this code match whatever the seed. An endpoint some of a title's agreeing bodies write bare and others with `|Address` also takes the `|Address` form (`_agreed_endpoint_tokens`), so a route follows the tokens rather than which body's greeting sorts first; on a LIVE cache that changed one title against the sorting alone, `Covalex_courier_dc_small_title_001`, whose `Dropoff1` was bare. Against code from before those fixes, set `PYTHONHASHSEED=0` on both sides, and expect those two to differ: the titles give an endpoint their bodies write both bare and with `|Address` its `|Address` form, where the old code gave one form or the other at random, and the index holds the same JSON with its materials in a fixed order. Locked by `tests/test_generator_single_pass.py` and `tests/test_mission_route_title.py` (the route for every order of the bodies, and the `|Address` form), and by `tests/test_battaglia_mineable_rs.py`, `tests/test_calculated_reward_titles.py` and `tests/test_commodity_journal.py`, which read the RS tags, the calculated-reward titles and the blueprint material UUIDs off the code a generation runs: the separate scans they used to call were removed. +### DataForge XMLs read as few times as possible, and only XML facts in the lookup pickles (#522) +`generate_enhancements_ini.py` parses each XML as few times as it can, and the `.lookups` pickles it reshapes hold facts read from the XML, never text made from base.ini or the Tag Builder config, so each is keyed on the DataForge build alone (`_LOOKUP_VERSIONS` records the shapes). `scitem_lookups` (`_scitem_facts`, the ~24k scitem files) and `blueprint_pools` (`_blueprint_pool_facts`) are turned into names and `[CLASS-Sx-grade]` tags on every run (`_render_scitem_lookups`, and the name loop in `build_blueprint_pool_lookup`), so a Tag Builder change or the annotate toggle re-renders them instead of parsing every scitem XML again. Because those two hold no loc text, the English-loc fallback mark (`en_loc_cache_mark`, for a translated run whose English base.ini is missing) keys only `standings`, the one pickle still built from the loc: a fallback run and the next English run share the facts pickles, and each renders its own names from them. `_component_name_tag` and `_mining_laser_component_tag` read their XML facts through `_component_tag_facts` / `_mining_laser_name_attr` and share the rendering (`_component_name_tag_from_facts`, `_mining_laser_tag_from_name`) with the cached path. The flight controller and armour lookups (`build_controller_lookup`, `build_armor_lookup`) hold the attribute values the ship block shows (`_controller_flight_stats`, `_armor_stats`) instead of lxml trees, still formatted in `enhancements_ship_dataforge`, so an armour value `_fmt` cannot format fails only its ship, as before. Those two are built on every run (about 0.2 s on LIVE) and never pickled: DataForge patches are applied again before every generation without a re-extraction, so a pickle keyed on the DataForge build would keep a patched controller or armour XML's old values until the next extraction. A pickle must hold builtins only: the app loads this script under a module name of its own, so a pickled class of the script would not load. The scitem walk finds the magazine with lxml's own tag filter when a file is ASCII-compatible and holds no `__polymorphicType` (`_holds_no_poly_type_attr`), which is every file on LIVE today, and keeps the per-element `_poly_type` loop otherwise. `_run_gen_missions` reads each pu_missions XML once (`_scan_pu_missions`: the #165 choice between a body with and without hostiles waits until every file is read) and each contractgen XML and contract template once (`scan_contract_generators` takes `roots` and `template_lookup`; the Battaglia RS tags and the calculated-reward diagnostic run on each root just before it, their errors held and raised where their own calls raised them, and the walk is finished for them if it stops early; a failure listing the files still ends the run). `scan_crafting_blueprints` parses each blueprint once, reads a carryable only when its filename names a commodity, and lowercases the loc keys once (`_commodity_loc_keys`), for the commodity entries, the Mining Compendium and the SCO crafting index (#474) alike. The hot loops parse through `_parse_xml_file` (the bytes read in one call, then `ET.fromstring`: the same parser and errors as `ET.parse`, and faster on Windows). On a LIVE cache (`main()` with `max_workers=1`, medians of three interleaved runs of the 3.0.0 code with #474 and #477 and of #522's final code, each with its own `src/`) a regeneration went from 11.9 s to 6.3 s, a components Tag Builder change from 31.0 s to 6.2 s, and the first generation after an extraction from 33.8 s to 24.0 s, which stays bound by parsing the ~1 GB of scitem XML once; the peak working set fell from about 320 MB to 190 MB. None of this changes a byte of output: every file the generator writes (the nine INIs and `crafting_index.json`) matched the unchanged code on a real LIVE cache, cold, warm, after a components change, with non-default components, commodities and armor configs with the annotate toggle on and off, and on a run whose English base.ini is missing. Run that comparison again for any change here. Two outputs used to depend on the string hash seed, because each took the order of a set: three courier titles in `mission_rewards_enhancements.ini` (`_derive_route_fragment` took the first of a set of bodies) and the order of the materials in `crafting_index.json` (`scan_crafting_blueprints` met each blueprint's materials in set order, #474's code). Both now sort (#522), so two runs of this code match whatever the seed. An endpoint some of a title's agreeing bodies write bare and others with `|Address` also takes the `|Address` form (`_agreed_endpoint_tokens`), so a route follows the tokens rather than which body's greeting sorts first; on a LIVE cache that changed one title against the sorting alone, `Covalex_courier_dc_small_title_001`, whose `Dropoff1` was bare. Against code from before those fixes, set `PYTHONHASHSEED=0` on both sides, and expect those two to differ: the titles give an endpoint their bodies write both bare and with `|Address` its `|Address` form, where the old code gave one form or the other at random, and the index holds the same JSON with its materials in a fixed order. Locked by `tests/test_generator_single_pass.py` and `tests/test_mission_route_title.py` (the route for every order of the bodies, and the `|Address` form), and by `tests/test_battaglia_mineable_rs.py`, `tests/test_calculated_reward_titles.py` and `tests/test_commodity_journal.py`, which read the RS tags, the calculated-reward titles and the blueprint material UUIDs off the code a generation runs: the separate scans they used to call were removed. diff --git a/scripts/generate_enhancements_ini.py b/scripts/generate_enhancements_ini.py index 472569c6..f3a2ff60 100644 --- a/scripts/generate_enhancements_ini.py +++ b/scripts/generate_enhancements_ini.py @@ -426,7 +426,7 @@ def write_ini(path: Path, entries: dict[str, str]) -> None: # prefixed bp_dir/entity_dir callers compare them against and crashing # scan_crafting_blueprints's xml_file.relative_to(bp_dir) with "not in # the subpath of". Bump flushes any pre-#231 pickle. -# scitem_lookups v11 / blueprint_pools v16 (perf proposal) — both pickles +# scitem_lookups v11 / blueprint_pools v16 (#522) — both pickles # now hold only XML facts, keyed on the DataForge build alone: no loc # text, no Tag Builder config, no annotate toggle and no English-loc # fallback mark (the extra_key is gone). The names and the @@ -443,7 +443,7 @@ def write_ini(path: Path, entries: dict[str, str]) -> None: # bump, a regen against an unchanged DataForge reuses pools baked # before those fixes and the mission text stays untagged/garbled. # v15: name_fallback_tags read the English loc (see the history above). - # v16: XML facts only (perf proposal, see the history above). + # v16: XML facts only (#522, see the history above). "blueprint_pools": "v16", "scitem_lookups": "v11", "standings": "v3", @@ -482,7 +482,7 @@ def _cached_lookup(forge_dir: Path, name: str, builder, extra_key: str = ""): the version in _LOOKUP_VERSIONS; passing a different *extra_key* (used by standings for the English-loc fallback mark; scitem_lookups and blueprint_pools used it for the components Tag Builder config until - they came to hold XML facts only, perf proposal) bumps the third + they came to hold XML facts only, #522) bumps the third segment. An unreadable pickle (a truncated one from a run cut off before these writes became atomic, say) is rebuilt, with an INFO line, since a rebuild re-reads its whole subtree. The pickle is @@ -530,7 +530,7 @@ def _build_xml_path_index(records_dir: Path) -> dict[str, list[str]]: The walk stays rglob's, so the folders keep rglob's order, which every reader's file order follows. Only the relative folder key is worked out once per folder (keyed on the path text up to the last separator) rather - than with Path.relative_to for each of the ~31k files (perf proposal). + than with Path.relative_to for each of the ~31k files (#522). """ idx: dict[str, list[str]] = defaultdict(list) # type: ignore[assignment] key_by_folder: dict[str, str] = {} @@ -590,7 +590,7 @@ def _parse_xml_file(xml_file: Path) -> ET.Element: and handing them to lxml is faster on Windows than letting lxml read the file itself: on a LIVE cache the ~2.6k pu_missions XMLs parse in 0.53 s instead of 0.73 s, the ~8.5k ships scitem XMLs in 2.1 s instead of - 2.8 s (perf proposal).""" + 2.8 s (#522).""" return ET.fromstring(xml_file.read_bytes()) @@ -971,7 +971,7 @@ def _component_name_tag(desc_value: str, root: ET.Element | None = None, The XML half is read by :func:`_component_tag_facts`, so the scitem lookup can cache those facts once per DataForge build and render the tags from them with :func:`_component_name_tag_from_facts`, the one - implementation both paths share (perf proposal). + implementation both paths share (#522). """ return _component_name_tag_from_facts( desc_value, _component_tag_facts(root), config=config, component_type=component_type @@ -1238,7 +1238,7 @@ def _mining_laser_tag_from_name(desc_value: str, name_attr: str, mining_tag_cfg: "TagConfig | None") -> str | None: """:func:`_mining_laser_component_tag` for a known mining laser, from its entity class name, so the scitem lookup can render the tag from - cached facts with the same code (perf proposal).""" + cached facts with the same code (#522).""" if mining_tag_cfg is None or render_tag is None: return None size = None @@ -1561,7 +1561,7 @@ def _agreed_endpoint_tokens(per_body: list[dict]) -> dict: endpoints, invisible to a static scan; treating them as vetoes would strip routes that demonstrably resolve in-game. First body's order/tokens win, except that a var some agreeing bodies write bare and others with - ``|Address`` takes the ``|Address`` form (perf proposal): the bodies are + ``|Address`` takes the ``|Address`` form (#522): the bodies are sorted, and pooled bodies differ in their greetings, so the first one's form was down to which greeting sorts first. """ @@ -1612,7 +1612,7 @@ def _derive_route_fragment(desc_bodies: list[str], cfg=None, loc=None, expand_ca # _agreed_endpoint_tokens) and callers build the list from a set, whose # order changes with every run's string hashing. Unsorted, three courier # titles flipped between the bare and |Address forms of Pickup1 and - # Dropoff1 from one generation to the next (perf proposal); a var some + # Dropoff1 from one generation to the next (#522); a var some # bodies write bare and others with |Address now takes |Address whatever # the order. for body in sorted(b for b in desc_bodies if b): @@ -2881,6 +2881,27 @@ def _within_excluded_subtree(node: ET.Element, scope: ET.Element, return False +def _spawn_count(value: str, group: str, attribute: str) -> int: + """*value* as a whole number, also when it is written as "4.0". Anything else + counts as 0 with a WARNING, so a mission loses that spawn line and keeps its + variant: over half of LIVE's contracts read a count, and one change to how counts + are written would otherwise fail every generation (see ContractScanFailed). + """ + try: + return int(value) + except ValueError: + pass + try: + if float(value).is_integer(): + return int(float(value)) + except ValueError: + pass + logger.warning( + f"Spawn count is not a whole number, counted as 0: {group} {attribute}={value!r}" + ) + return 0 + + def _extract_spawn_counts(element: ET.Element, exclude_within: str | tuple[str, ...] | None = None) -> SpawnBreakdown: """Extract a per-bucket per-label breakdown of spawn descriptions. @@ -2916,7 +2937,10 @@ def _extract_spawn_counts(element: ET.Element, continue name = sg.get("Name", "") ships = sg.findall(".//SpawnDescription_Ship") - total = sum(int(s.get("concurrentAmount", "0")) for s in ships) + total = sum( + _spawn_count(s.get("concurrentAmount", "0"), name, "concurrentAmount") + for s in ships + ) if total <= 0: continue # Turret ship-groups are reported separately by _extract_turret_info; @@ -2941,11 +2965,13 @@ def _extract_spawn_counts(element: ET.Element, for auto in auto_settings: max_spawns = auto.get("maxSpawns", "0") if max_spawns != "-1": - total_npcs += max(int(max_spawns), 0) + total_npcs += max(_spawn_count(max_spawns, name, "maxSpawns"), 0) else: max_concurrent = auto.get("maxConcurrentSpawns", "0") if max_concurrent != "-1": - total_npcs += max(int(max_concurrent), 0) + total_npcs += max( + _spawn_count(max_concurrent, name, "maxConcurrentSpawns"), 0 + ) if total_npcs <= 0: m = re.search(r"x\s*(\d+)", name) @@ -3673,7 +3699,7 @@ def build_blueprint_pool_lookup( config) is cached there per DataForge build as the ``blueprint_pools`` pickle, and only the names below are worked out per run, so a Tag Builder change or the annotate toggle no - longer re-parses the pool and blueprint XMLs (perf proposal). + longer re-parses the pool and blueprint XMLs (#522). Returns: Tuple of: @@ -3755,7 +3781,7 @@ def _builder() -> list: def _blueprint_pool_facts(pool_dir: Path, bp_dir: Path) -> list: """The XML half of :func:`build_blueprint_pool_lookup`, with no names, - tags or config, so it can be cached per DataForge build (perf proposal). + tags or config, so it can be cached per DataForge build (#522). Returns ``[(pool __ref UUID, pool filename stem, rewards), ...]`` in file order, one entry per pool record with a __ref, where *rewards* is @@ -4027,7 +4053,7 @@ def _battaglia_mineable_rs_in( *template_lookup* is :func:`_build_template_lookup` of the sibling contracttemplates folder. _run_gen_missions runs this on each root of the contractgen parse it shares with scan_contract_generators, in file - order (perf proposal: it used to be a separate walk of its own). + order (#522: it used to be a separate walk of its own). """ for contract in root.findall(".//CareerContract") + root.findall(".//Contract"): title_param = contract.find(".//ContractStringParam[@param='Title']") @@ -4103,12 +4129,12 @@ class ContractVariant(NamedTuple): Was a bare positional tuple that grew to 12 fields (10 -> 11 for rank_name in 1.4.2, 11 -> 12 for rep_track in 2.2.0's reputation-track - change, #161); every growth risked an off-by-one at one of the many - ``v[N]`` reads and destructures below. A NamedTuple is still a plain - tuple — positional unpacking, indexing, and ``len()`` all still work - exactly as before (see tests/test_mission_variant_tuple.py, which locks - that contract) — so this is purely a self-documenting rename at the call - sites that read fields by name instead of by position. + change, #161); every growth risked an off-by-one at one of the ``v[N]`` + reads and destructures it had then. Now scan_contract_generators builds + it by keyword and _run_gen_missions reads it by field name, so a field + that moves or a new one cannot put a value in the wrong field. A + NamedTuple is still a plain tuple, and tests/test_mission_variant_tuple.py + locks its fields and their order. """ system_name: str success_xp: int @@ -4142,7 +4168,7 @@ def scan_contract_generators( *template_lookup* (:func:`_build_template_lookup` of the sibling contracttemplates folder) and *roots* (the parsed contractgen XML roots, in file order) let _run_gen_missions hand over the parse it shares with - the Battaglia RS-tag and calculated-reward scans (perf proposal); each + the Battaglia RS-tag and calculated-reward scans (#522); each is worked out here when omitted, as it always was, so a call with the folder alone still works. A generation always hands both over: only the tests that call this directly (test_blueprint_pools.py, @@ -4171,6 +4197,13 @@ def scan_contract_generators( reward pools sharing the same title/system. - mission_items: dict mapping title_key → list of reward item display names Sorted by system name for consistent output. + + A contract that raises is skipped with a WARNING and leaves nothing behind. + Raises ContractScanFailed when more contracts were skipped than gave a variant, + or when the walk stopped on an error before any gave one. Each is meant to take + a bug here, and game data should not be able to do it (see _spawn_count). Failing + every category of the run is the deliberate trade: a set without most of its + contracts must not be certified. """ if not contractgen_dir.exists(): return {}, {}, {}, {} @@ -4196,6 +4229,10 @@ def scan_contract_generators( mission_blueprints: dict[str, dict[str, dict]] = {} mission_bp_chance: dict[str, float] = {} mission_items: dict[str, list[str]] = {} + walk_error = "" + skipped_contracts = 0 + built_contracts = 0 + first_skip = "" # Build template lookup for contracts that inherit title/desc from templates if template_lookup is None: @@ -4275,9 +4312,18 @@ def _extract_system(name: str, fallback: str) -> str: # not a union of every sibling contract's roster (#186) — # including the one-time intro mission's own roster, which # uses the plain tag, not . - handler_spawns = _extract_spawn_counts( - handler, exclude_within=("CareerContract", "Contract") - ) + try: + handler_spawns = _extract_spawn_counts( + handler, exclude_within=("CareerContract", "Contract") + ) + except Exception as e: + # Outside the per-contract try, so a failure here used to end + # the whole scan. The contracts' own spawns still count. + logger.warning( + f"Skipped the shared spawns of handler {debug_name or '?'}: " + f"{type(e).__name__}: {e}" + ) + handler_spawns = _empty_spawn_breakdown() contracts = handler.findall(contract_xpath) @@ -4372,6 +4418,7 @@ def _extract_system(name: str, fallback: str) -> str: # the identical pool set. contract_has_bp = False contract_bp_chance = 0.0 + first_bp_chance = None contract_bp_variant = contract.get("debugName", "") # Accumulate this contract's own BlueprintRewards # locally, grouped by pool_label, before merging @@ -4417,18 +4464,13 @@ def _extract_system(name: str, fallback: str) -> str: contract_bp_chance = float(bp_elem.get("chance", "1")) except (ValueError, TypeError): contract_bp_chance = 1.0 - if title_key not in mission_bp_chance: - mission_bp_chance[title_key] = contract_bp_chance - for pool_label, (label_uuids, label_items) in contract_pools_by_label.items(): - _merge_blueprint_pool( - mission_blueprints, title_key, system_name, - tuple(sorted(label_uuids)), label_items, pool_label, - ) + if first_bp_chance is None: + first_bp_chance = contract_bp_chance # Extract item rewards null_uuid = "00000000-0000-0000-0000-000000000000" + item_names = [] if entity_names: - item_names = [] for item_elem in contract.findall(".//ContractResult_Item"): ec = item_elem.get("entityClass", "") if ec and ec != null_uuid and ec in entity_names: @@ -4441,8 +4483,6 @@ def _extract_system(name: str, fallback: str) -> str: name = entity_names[ec] if name not in item_names: item_names.append(name) - if item_names and title_key not in mission_items: - mission_items[title_key] = item_names # Extract XP from ContractResult_LegacyReputation blocks # First block with positive XP = success, first with negative = failure @@ -4476,7 +4516,7 @@ def _extract_system(name: str, fallback: str) -> str: continue try: val = int(float(points)) - except (ValueError, TypeError): + except (ValueError, TypeError, OverflowError): continue if val > 0: success_xp = val @@ -4515,9 +4555,40 @@ def _extract_system(name: str, fallback: str) -> str: rep_track = standing_track_lookup.get(min_standing, "") if min_standing else "" # Add all missions (not just those with XP/blueprint data) + variant = ContractVariant( + system_name=system_name, + success_xp=success_xp, + failure_xp=failure_xp, + desc_key=desc_key, + flags=contract_flags, + spawns=spawns, + difficulty=contract_difficulty, + has_bp=contract_has_bp, + bp_chance=contract_bp_chance, + bp_variant=contract_bp_variant, + rank_name=rank_name, + rep_track=rep_track, + ) + # After the call: a title with no variants would read + # as every variant having a blueprint (all([]) is True). if title_key not in missions: missions[title_key] = [] - missions[title_key].append(ContractVariant(system_name, success_xp, failure_xp, desc_key, contract_flags, spawns, contract_difficulty, contract_has_bp, contract_bp_chance, contract_bp_variant, rank_name, rep_track)) + missions[title_key].append(variant) + built_contracts += 1 + + # Only now, so a contract that raised above leaves no + # blueprints or items under its title. + for pool_label, (label_uuids, label_items) in ( + contract_pools_by_label.items() + ): + _merge_blueprint_pool( + mission_blueprints, title_key, system_name, + tuple(sorted(label_uuids)), label_items, pool_label, + ) + if first_bp_chance is not None and title_key not in mission_bp_chance: + mission_bp_chance[title_key] = first_bp_chance + if item_names and title_key not in mission_items: + mission_items[title_key] = item_names # Sub-contracts override title/desc but inherit # everything else from the parent contract. @@ -4532,7 +4603,9 @@ def _extract_system(name: str, fallback: str) -> str: sub_desc = "" if sub_title not in missions: missions[sub_title] = [] - missions[sub_title].append(ContractVariant(system_name, success_xp, failure_xp, sub_desc or desc_key, contract_flags, spawns, contract_difficulty, contract_has_bp, contract_bp_chance, contract_bp_variant, rank_name, rep_track)) + missions[sub_title].append( + variant._replace(desc_key=sub_desc or desc_key) + ) if contract_has_bp and sub_title != title_key: # Reuse contract_pools_by_label (already # scanned above) instead of re-iterating @@ -4549,7 +4622,13 @@ def _extract_system(name: str, fallback: str) -> str: mission_bp_chance[sub_title] = contract_bp_chance except Exception as e: - logger.debug(f"Skipped contract {contract.get('debugName', '?')}: {e}") + # WARNING, as the ship and component generators log a bad + # file. A normal run does not show DEBUG, and a bug in this + # block loses every contract's variants, not just one's. + skip = f"{contract.get('debugName', '?')}: {type(e).__name__}: {e}" + logger.warning(f"Skipped contract {skip}") + skipped_contracts += 1 + first_skip = first_skip or skip # Sort variants by system name for consistent output (Stanton first, then others alphabetically) for title_key in missions: @@ -4557,6 +4636,16 @@ def _extract_system(name: str, fallback: str) -> str: except Exception as e: logger.warning(f"Error scanning contract generators: {e}") + walk_error = f"{type(e).__name__}: {e}" + + # Outside the try above, which would only log it. main() has written no INI yet, + # so the old set stays whole and the worker leaves its stamp empty. + if skipped_contracts > built_contracts: + raise ContractScanFailed( + skipped_contracts, skipped_contracts + built_contracts, first_skip + ) + if walk_error and not built_contracts: + raise ContractScanFailed(0, 0, walk_error) logger.info(f"Contract generators: {len(missions)} missions, {len(mission_blueprints)} with blueprints, {len(mission_items)} with items") return missions, mission_blueprints, mission_bp_chance, mission_items @@ -4572,13 +4661,11 @@ def _calculated_reward_titles_in(root: ET.Element, titles: set[str]) -> None: (blueprint-only or item-only rewards), which is a separate, equally correct "nothing to show" case. - A separate scan rather than widening ContractVariant (its 12-field - width is locked by tests/test_mission_variant_tuple.py, and several - ``for ... in variants:`` sites destructure it positionally) for a value + A separate scan rather than a 13th ContractVariant field for a value only the end-of-run diagnostic needs. _run_gen_missions runs it on each root of the contractgen parse scan_contract_generators already makes, rather than walking the files again once a zero-XP title turns up - (perf proposal). + (#522). """ for contract in root.findall(".//CareerContract") + root.findall(".//Contract"): if contract.find(".//ContractResult_CalculatedReward") is None: @@ -4692,7 +4779,7 @@ def _build_uuid_to_commodity( fname, ) # A carryable whose filename names no commodity can add nothing, - # so only the others are read (perf proposal: 658 of the 2,570 + # so only the others are read (#522: 658 of the 2,570 # carryables on a LIVE cache). if not m: continue @@ -4715,8 +4802,7 @@ def _commodity_loc_keys(loc: dict[str, str]) -> list[tuple[str, str]]: """``(key, key.lower())`` for every ``items_commodities_*`` key in *loc* (case-insensitive), in loc order: what every :func:`_discover_commodity_loc_pairs` call scans, worked out once - instead of lowercasing all ~91k loc keys for each commodity (perf - proposal).""" + instead of lowercasing all ~91k loc keys for each commodity (#522).""" keys = [] for key in loc: klow = key.lower() @@ -5048,6 +5134,29 @@ def _place_commodity_tag(base_name: str, tag: str, cfg) -> str: return join_tag(base_name, tag, placement) +_FPS_ROCK_NAME_PREFIX = "hud_mining_fps_rock_name_" + + +def _tag_fps_rock_names(out: dict[str, str], loc: dict[str, str], + tag_by_name: dict[str, str], cfg) -> None: + """Tag each ``hud_mining_fps_rock_name_*`` key in *loc* whose text is a + tagged commodity's name, ignoring case, with that commodity's tag. + + These keys are the names the HUD shows for a hand-mineable gem rock + before it is fractured (``_1`` Aphorite, ``_2`` Dolivine, ``_3`` + Hadanite). They name no commodity, so the crafting loop never reaches + them, and a gem rock showed no tag until it broke into commodities. + *tag_by_name* maps a lowercased commodity name to the tag its name key + got in the crafting loop. + """ + for key, base in loc.items(): + if not key.lower().startswith(_FPS_ROCK_NAME_PREFIX) or key in out: + continue + tag = tag_by_name.get(base.strip().lower()) + if tag: + out[key] = _place_commodity_tag(base, tag, cfg) + + def _parse_compendium_locations(base_content: str) -> dict: """Map a Mining Compendium mineral name (lowercased) to its sorted mining locations, parsed from the stock ``Name - loc, loc, ...`` paragraphs. @@ -5123,7 +5232,7 @@ def scan_crafting_blueprints( logger.info("No crafting blueprints directory found") return {}, {} - # Step 1: Read every blueprint once (perf proposal: steps 1 and 3 each + # Step 1: Read every blueprint once (#522: steps 1 and 3 each # used to parse them all): its category, its display name and the # material UUIDs it names, collecting those UUIDs as it goes. resource_uuids: set[str] = set() @@ -5169,7 +5278,7 @@ def scan_crafting_blueprints( materials.add(uuid_names[uid]) # Sorted, so each material is first met in the same place on every # run: crafting_index.json keeps that order, and a set's order changes - # with each run's string hashing (perf proposal review). + # with each run's string hashing (#522 review). for mat in sorted(materials): commodity_items[mat].append((category, item_name)) @@ -5178,7 +5287,7 @@ def scan_crafting_blueprints( # commodity strings) — surfacing that in the log beats silently writing an # empty enhancements file. # The items_commodities_* keys every loc lookup below scans, lowercased - # once (perf proposal). + # once (#522). commodity_keys = _commodity_loc_keys(loc) if crafting_index is not None: for commodity, pairs_ in commodity_items.items(): @@ -5209,6 +5318,7 @@ def scan_crafting_blueprints( ) out: dict[str, str] = {} + tag_by_name: dict[str, str] = {} # lowercased commodity name -> its tag skipped_no_loc: list[str] = [] for commodity in sorted(commodity_items.keys()): pairs = _discover_commodity_loc_pairs(commodity, loc, commodity_keys) @@ -5234,6 +5344,8 @@ def scan_crafting_blueprints( usage_keys=usage_keys, ) out[name_key] = _place_commodity_tag(base_name, tag, cfg) if tag else base_name + if tag: + tag_by_name.setdefault(base_name.strip().lower(), tag) base_desc = loc.get(desc_key, "") if base_desc and desc_key not in out: @@ -5249,6 +5361,10 @@ def scan_crafting_blueprints( sections.append(enhancements_block) out[desc_key] = f"{base_desc}\\n\\n" + "\\n\\n".join(sections) + # A gem rock not yet fractured shows its HUD name, not its commodity + # name, so give those names the commodity's tag too. + _tag_fps_rock_names(out, loc, tag_by_name, tag_config or DEFAULT_TAG_CONFIGS.get("commodities")) + if skipped_no_loc: logger.warning( f"Crafting: {len(skipped_no_loc)} commodities had no matching loc keys " @@ -5690,7 +5806,7 @@ def build_controller_lookup(controller_dir: Path) -> dict[str, tuple]: included so each spaceship entity can find its exact match. The values are the few attributes the ship stats read, not the XML - root (perf proposal). The lookup is built on every run, not pickled per + root (#522). The lookup is built on every run, not pickled per DataForge build: DataForge patches are applied again before every generation without a re-extraction, and a pickle would keep a patched controller's old values until the next extraction. @@ -5744,7 +5860,7 @@ def build_armor_lookup(armor_dir: Path) -> dict[str, tuple]: lowercased for case-insensitive matching. The values are the attributes _armor_stats_block formats, not the XML - root (perf proposal). The formatting stays in enhancements_ship_dataforge, + root (#522). The formatting stays in enhancements_ship_dataforge, so a value it cannot format still fails that one ship, as before. Built on every run, not pickled, for the same reason as build_controller_lookup: DataForge patches are applied again before every generation without a @@ -5997,6 +6113,12 @@ def scan_spaceships( loc_key = desc_attr.lstrip("@") base_value = loc.get(loc_key) + # #561: a key base.ini has but leaves blank is not this ship's own + # description. The game shows such keys elsewhere (the Carrack's + # interior map labels), so stats written there show up on the map. + if base_value is not None and not base_value.strip(): + skipped += 1 + continue is_discovered = base_value is None if is_discovered: base_value = _synthesize_description(root, xml_file, loc_key) @@ -6136,7 +6258,7 @@ def build_scitem_lookups( ``scitem_lookups`` pickle, and the names and tags are rendered from those facts, *loc* and *tag_config* on every run (:func:`_render_scitem_lookups`). A Tag Builder change used to key the - whole pickle and re-parse all ~24k scitem files (perf proposal). + whole pickle and re-parse all ~24k scitem files (#522). """ if not scitem_dir.exists(): return {}, {}, {}, {} @@ -6178,7 +6300,7 @@ def _scitem_facts( records_dir: Path | None = None, ) -> tuple: """The XML half of :func:`build_scitem_lookups`, with no loc or Tag - Builder input, so it can be cached per DataForge build (perf proposal). + Builder input, so it can be cached per DataForge build (#522). Returns ``(mag_lookup, names, tag_candidates)``, all builtins so the pickle loads under any module name: @@ -7246,7 +7368,7 @@ def _scan_pu_missions( separator: str, ) -> _PuMissionScan: """Read every pu_missions XML once for all of _run_gen_missions' uses - (perf proposal: they were five separate passes, each parsing every + (#522: they were five separate passes, each parsing every file). Each step keeps its own error handling and its file order. *mission_enhancement(root, ambiguous_keys)* is enhancements_mission @@ -7423,7 +7545,7 @@ def _show_title_tag(_field: str) -> bool: # matched against are both English. Reading the run's own language left a # translated run's pools untagged, and a later English run reused them # from the blueprint_pools pickle, which held the tagged names until it - # came to hold XML facts only (perf proposal). + # came to hold XML facts only (#522). name_fallback_tags = ( bare_type_name_tag_lookup(ctx.get("tag_loc") or loc, _comp_cfg) if annotate_descs else {} @@ -7453,7 +7575,7 @@ def _mission_enhancement(root: ET.Element, ambiguous_keys) -> str: show_fields=_mdf, spawn_ambiguous_keys=ambiguous_keys) - # One pass over the pu_missions XMLs (perf proposal; see + # One pass over the pu_missions XMLs (#522; see # _scan_pu_missions) gives their description entries plus everything the # title passes below read from them. #165: a single mission description # is often shared by many pu_missions XMLs with DIFFERENT hostile spawns @@ -7506,7 +7628,7 @@ def _mission_enhancement(root: ET.Element, ambiguous_keys) -> str: bp_dir = records / "crafting" / "blueprints" / "crafting" # Only the XML walk is cached (per DataForge build): the pool names bake # in the English names, the components tags, placement and the annotate - # toggle, so they are worked out from it on every run (perf proposal). + # toggle, so they are worked out from it on every run (#522). # Armor tags (#492) are added later still, when the bullets are written. blueprint_pools, pool_names = build_blueprint_pool_lookup( pool_dir, bp_dir, entity_names, @@ -7520,7 +7642,7 @@ def _mission_enhancement(root: ET.Element, ambiguous_keys) -> str: # One parse of each contractgen XML (and one template lookup) feeds # scan_contract_generators, the Battaglia RS-tag scan and the # calculated-reward diagnostic, which used to walk the files three times - # (perf proposal). The other two run on each root just before + # (#522). The other two run on each root just before # scan_contract_generators sees it. Each keeps its own error handling: # a failure in either is held and raised where that scan's own call # used to raise it, and the walk is finished for them if @@ -7575,15 +7697,23 @@ def _contractgen_roots(xml_files): _contractgen_roots(_indexed_xml_files(contractgen_dir, xml_path_index, records)) if contractgen_dir.exists() else iter(()) ) - contractgen_missions, mission_blueprints, mission_bp_chance, mission_items = scan_contract_generators( - contractgen_dir, reputation_lookup, blueprint_pools, entity_names, - xml_path_index=xml_path_index, records_dir=records, - pool_names=pool_names, - standings_lookup=standings_lookup, - standing_track_lookup=standing_track_lookup, - template_lookup=_template_lookup, - roots=_roots, - ) + try: + contractgen_missions, mission_blueprints, mission_bp_chance, mission_items = ( + scan_contract_generators( + contractgen_dir, reputation_lookup, blueprint_pools, entity_names, + xml_path_index=xml_path_index, records_dir=records, + pool_names=pool_names, + standings_lookup=standings_lookup, + standing_track_lookup=standing_track_lookup, + template_lookup=_template_lookup, + roots=_roots, + ) + ) + except ContractScanFailed: + # A listing that failed part-way stops the scan too, and ends the run as itself. + if battaglia_error is not None: + raise battaglia_error + raise for _root in _roots: pass logger.info(f"Processed {len(contractgen_missions)} contract generator mission variants") @@ -8131,6 +8261,25 @@ class GenerationStopped(Exception): never checks for a stop once its write phase has begun.""" +class ContractScanFailed(Exception): + """More contracts were skipped than gave a variant, or the walk stopped on an + error before any gave one (a total of 0), so the run fails. + + EnhancementsGeneratorWorker matches it by class name, as it does + GenerationStopped, and words its own box from these fields in the selected + language, so keep the name and the fields. + """ + + def __init__(self, skipped: int, total: int, first: str): + super().__init__( + f"{skipped} of {total} contracts could not be read. The first: {first}" + if total else f"The contract scan stopped: {first}" + ) + self.skipped = skipped + self.total = total + self.first = first + + def main(base_ini_path: Path, forge_dir: Path | None = None, categories: set[str] | None = None, progress_callback: Optional[Callable[[int, int, str], None]] = None, @@ -8236,7 +8385,7 @@ def _stop_if_asked(where: str) -> None: # next English run to reuse: that run sees a different key and rebuilds. # Only standings is built from en_loc now: scitem_lookups and # blueprint_pools hold XML facts alone, and their names are resolved - # through en_loc on every run (perf proposal). + # through en_loc on every run (#522). en_loc_cache_mark = "" if english_base_ini_path is not None: english_base_ini_path = Path(english_base_ini_path) @@ -8337,7 +8486,7 @@ def _stop_if_asked(where: str) -> None: # build_scitem_lookups renders into entity_name_tags (and so into the # POTENTIAL BLUEPRINTS list entries). Only the XML facts behind them are # pickled, per DataForge build, so a config change re-renders the tags - # instead of re-parsing every scitem XML (perf proposal). + # instead of re-parsing every scitem XML (#522). _components_cfg = (tag_configs or {}).get("components") or DEFAULT_TAG_CONFIGS.get("components") def _build_scitem_pair(): diff --git a/src/gui/CLAUDE.md b/src/gui/CLAUDE.md index 1081eec4..8126c8b8 100644 --- a/src/gui/CLAUDE.md +++ b/src/gui/CLAUDE.md @@ -4,14 +4,14 @@ GUI layer (PyQt6). See the root `CLAUDE.md` for project context and cross-cuttin ## Files -- `main_window.py` — main window with table, toolbar, filters, backup/restore, DataForge extraction trigger, worker orchestration. The largest file in the repo; runs the core workflow load→merge→edit→apply. Workers live in `workers.py`; pure-Python helpers (`validate_applied_file`, `filter_entry_indices`, `markdown_to_html`) live in their own modules and are wrapped by thin `MainWindow` methods. Owns `_stamp_frontend_version` — see *Frontend version stamp on apply* below. Less-frequent toolbar actions (restore backup, clear localization/cache, import/export INI, open loc dir) live under a **More** overflow `QMenu` (2.0). `_on_language_changed(language)` runs the language-switch pipeline (2.0, #30): cancel any in-flight loader, `i18n.set_language()` + `retranslate_ui()`, then `_apply_language_base_source()` repoints the `global` source at that language's base.ini (downloading it via `LanguageBaseDownloadWorker` when a URL is mapped; falling back to a cached copy, then to English), and `_reload_with_language_enhancements()` regenerates that language's enhancements first when the `.dataforge_stamp` is stale (skipped if no DataForge cache: prose loads without stat overlays). `retranslate_ui()` also re-renders the About, FAQ and Legal tabs (#314) and the Help panel (#540) from the new language's docs (`AppSettings.get_localized_doc_path`), which are otherwise rendered only when each is built and on a theme swap. Both go through `_render_document_browsers`, so a theme swap (`refresh_action_buttons`) and a switch cannot render different documents: each used to keep its own list, and the switch's had no Help panel. It also retitles the Help, String Editor and Test Plan panels, whose titles are set only when each is built, and each tab's `retranslate_ui` also sets again the texts its refreshes and loads write, which a switch used to leave in the old language: the Config tab reruns `_populate_channel_combo` (the channel list's not-installed tooltips and hint) and `_refresh_p4k_status`, the Blueprint Tracker renames each filter's first row (`enhancements.blueprints_facet_any`), and the Log tab rewrites its line count (#540). English goes through it too whenever its base.ini exists, because a re-extraction made while another language was selected regenerated only that language. That regeneration is the switch's launch: it clears the Generate button first, as `_run_enhancements_pipeline` does (#292), and leaves the switch's reload to the run. A run that fails still loads the language picked, with the stats it has: `_run_enhancements_generation` keeps its `if_unfinished` in `_after_unfinished_generation`, and the finished slot runs it once the run's error dialog has closed (parked in `_after_error_dialog`, which `_show_error_dialog` runs as it closes). `_run_enhancements_generation` returns whether it started, like `_run_p4k_extraction`, and a start refused because a generation is already running loads the language at once. user.cfg's `g_language` is NOT set here; that happens at window init and apply-to-game time. Its DataForge cache status and freshness checks read the cache folder without creating it, and `_run_dataforge_extraction` reports a cache folder it cannot create in one box before any worker starts (see *Status checks never create the DataForge cache folder* below, #494), as it does a cache folder that is a link (#491). More > Clear Cache (`clear_cache`, #479) deletes the active channel's cached `*.ini` and `*.txt` and, when the user agrees, the DataForge cache in use: the folder `get_dataforge_cache_leaf()` names (the default, the portable build's or a cache folder override), offered only when it holds a cache (its `.p4k_mtime` stamp or its records). It used to look in the data folder's `cache\dataforge`, where the cache lived before 1.x, so the real one was never offered; a leftover there is the queued old-cache cleanup's. A cache folder on a drive or share that is not there is named in the summary and the rest still clears, the file question is skipped when there are no files (a No to the DataForge question then changes nothing, just as a No to the file question), nothing is cleared while an extraction or a generation runs (`clear_cache_busy` in the status bar; the background delete of a finished extraction's working folder, or a sweep of the ones a crash left, does not count, perf proposal, since neither touches the other's folder), the Enhancements tab is refreshed afterwards, a failure is listed in the summary and logged once at WARNING (an ERROR record opened a second box), and every text goes through `tr()`. A channel switch and a data-folder change (`_sync_canonical_source_paths`, through `AppSettings.sync_global_source_path`) and a successful global.ini extraction (`_on_p4k_extract_finished`) keep the `global` source on the selected language's base.ini (`AppSettings.get_global_source_base_ini()`, English when this channel has none yet); they used to point every language at the English one (#502). -- `workers.py` — every `QThread` background worker plus the shared `AnimatedProgressDialog` (its `set_close_guard(guard)` asks before Esc or the title-bar X dismisses it, never on a programmatic `close()`, and only for a dialog without a cancel button, #471; its `set_progress` shows the moving busy bar for a total of 0 and for nothing counted yet, 0 of N, until the first count, #507: a bar standing at 0% looked hung, as the generator's first lookups did for seconds, and the string loader and the update download start at 0 too) and `SelectAllDelegate`. Workers: `FileLoaderWorker` (sources → `StringEntry` list + sort keys), `AppliedStateWorker` (#398 review: runs the already-applied comparison off the GUI thread; takes an injected `compute(snapshot, should_stop)` instead of importing it, because the merge it shares with Apply to Game lives in `main_window.py` and importing that here would be a gui-to-gui cycle; always emits `finished(bool)` once, False being the safe "not applied" answer), `StartupSyncWorker` (refresh URL-backed sources at startup), `EnhancementsGeneratorWorker` (run `scripts/generate_enhancements_ini.py` in-process via `importlib.util`; takes a `language` param so output lands in that language's enhancements dir while annotation paths still parse the English base.ini; captures that folder, the DataForge build key and the tag fingerprint when its run starts, empties `.dataforge_stamp` just before the generator's `main()` and writes the tag stamp and then the DataForge stamp after it returns, see *A cut-off generation is offered again at the next start* below; `requestInterruption()`, which only closing the window sends, stops it before its patches, its module load or `main()`, and inside `main()` at the next job boundary, never during the writes, records it in `stopped` and ends with `finished(False)`, no `error` and nothing at ERROR), `P4kExtractWorker` (unp4k extract of `global.ini`, working beside the DataForge cache it is handed as `scratch_near`), `DataForgeExtractWorker` (unp4k + unforge + post-extract patches; both stop on `requestInterruption()`, record it in `stopped` and then end with `finished(False)`, no `error` and nothing at ERROR, #471; a successful DataForge run keeps its working folder for `take_working_folder()`, any other outcome deletes it before `finished`, and a DataForge run first waits for the background deletes it is handed as `wait_for`, perf proposal), `WorkingFolderDeleteWorker` (deletes that folder in the background, perf proposal, see *Closing stops a running extraction*), `StaleWorkingFolderSweepWorker` (sweeps the working folders a crash or a kill left, perf proposal, same section), `LanguageBaseDownloadWorker` (2.0: fetch a non-English language's global.ini from its mapped URL into `cache\lang\{language}\base.ini`), `UexShopDataWorker` (3.1.0, #606: `uex_shops.load_shop_data` for the SCO Item Finder, always emits `finished(ShopData or None, error)` once; `closeEvent` waits for it, its requests time out after `REQUEST_TIMEOUT_S`), `LiveBlueprintLogWorker` (SCO, 3.0.0: polls `blueprint_log_scanner.GameLogTail` on the active channel's `Game.log` every `POLL_MS` while the overlay runs, LIVE and HOTFIX only, and emits `blueprints_found(raw names, newest)`; read-only like the Scan, the main thread updates the owned set; stopped with `requestInterruption()` + `_reap_worker`; a lasting poll fault logs one traceback, then debug), `BlueprintLogScanWorker` (#222: scan a channel dir for "Received Blueprint" notifications via `blueprint_log_scanner.scan_channel`, watermark-aware — takes `(channel_dir, since)`, emits a `ScanResult`; stays read-only, all owned-set/watermark mutation happens on the main thread in `MainWindow._on_blueprint_log_scan_finished`). Each emits `progress` (str) and `progress_pct` (completed, total, message); `AnimatedProgressDialog.set_progress` consumes the latter. Exception: `AppUpdateCheckWorker` and `AppUpdateDownloadWorker` live in `src/utils/app_updater.py` because the workers, version comparison, and installer-asset picking belong together (#211). +- `main_window.py` — main window with table, toolbar, filters, backup/restore, DataForge extraction trigger, worker orchestration. The largest file in the repo; runs the core workflow load→merge→edit→apply. Workers live in `workers.py`; pure-Python helpers (`validate_applied_file`, `filter_entry_indices`, `markdown_to_html`) live in their own modules and are wrapped by thin `MainWindow` methods. Owns `_stamp_frontend_version` and `_add_play_button_reminder` — see *Frontend version stamp on apply* and *Play button reminder on apply* below. Less-frequent toolbar actions (restore backup, clear localization/cache, import/export INI, open loc dir) live under a **More** overflow `QMenu` (2.0). `_on_language_changed(language)` runs the language-switch pipeline (2.0, #30): cancel any in-flight loader, `i18n.set_language()` + `retranslate_ui()`, then `_apply_language_base_source()` repoints the `global` source at that language's base.ini (downloading it via `LanguageBaseDownloadWorker` when a URL is mapped; falling back to a cached copy, then to English), and `_reload_with_language_enhancements()` regenerates that language's enhancements first when the `.dataforge_stamp` is stale (skipped if no DataForge cache: prose loads without stat overlays). `retranslate_ui()` also re-renders the About, FAQ and Legal tabs (#314) and the Help panel (#540) from the new language's docs (`AppSettings.get_localized_doc_path`), which are otherwise rendered only when each is built and on a theme swap. Both go through `_render_document_browsers`, so a theme swap (`refresh_action_buttons`) and a switch cannot render different documents: each used to keep its own list, and the switch's had no Help panel. It also retitles the Help, String Editor and Test Plan panels, whose titles are set only when each is built, and each tab's `retranslate_ui` also sets again the texts its refreshes and loads write, which a switch used to leave in the old language: the Config tab reruns `_populate_channel_combo` (the channel list's not-installed tooltips and hint) and `_refresh_p4k_status`, the Blueprint Tracker renames each filter's first row (`enhancements.blueprints_facet_any`), and the Log tab rewrites its line count (#540). English goes through it too whenever its base.ini exists, because a re-extraction made while another language was selected regenerated only that language. That regeneration is the switch's launch: it clears the Generate button first, as `_run_enhancements_pipeline` does (#292), and leaves the switch's reload to the run. A run that fails still loads the language picked, with the stats it has: `_run_enhancements_generation` keeps its `if_unfinished` in `_after_unfinished_generation`, and the finished slot runs it once the run's error dialog has closed (parked in `_after_error_dialog`, which `_show_error_dialog` runs as it closes). `_run_enhancements_generation` returns whether it started, like `_run_p4k_extraction`, and a start refused because a generation is already running loads the language at once. user.cfg's `g_language` is NOT set here; that happens at window init and apply-to-game time. Its DataForge cache status and freshness checks read the cache folder without creating it, and `_run_dataforge_extraction` reports a cache folder it cannot create in one box before any worker starts (see *Status checks never create the DataForge cache folder* below, #494), as it does a cache folder that is a link (#491). More > Clear Cache (`clear_cache`, #479) deletes the active channel's cached `*.ini` and `*.txt` and, when the user agrees, the DataForge cache in use: the folder `get_dataforge_cache_leaf()` names (the default, the portable build's or a cache folder override), offered only when it holds a cache (its `.p4k_mtime` stamp or its records). It used to look in the data folder's `cache\dataforge`, where the cache lived before 1.x, so the real one was never offered; a leftover there is the queued old-cache cleanup's. A cache folder on a drive or share that is not there is named in the summary and the rest still clears, the file question is skipped when there are no files (a No to the DataForge question then changes nothing, just as a No to the file question), nothing is cleared while an extraction or a generation runs (`clear_cache_busy` in the status bar; the background delete of a finished extraction's working folder, or a sweep of the ones a crash left, does not count, #522, since neither touches the other's folder), the Enhancements tab is refreshed afterwards, a failure is listed in the summary and logged once at WARNING (an ERROR record opened a second box), and every text goes through `tr()`. A channel switch and a data-folder change (`_sync_canonical_source_paths`, through `AppSettings.sync_global_source_path`) and a successful global.ini extraction (`_on_p4k_extract_finished`) keep the `global` source on the selected language's base.ini (`AppSettings.get_global_source_base_ini()`, English when this channel has none yet); they used to point every language at the English one (#502). +- `workers.py` — every `QThread` background worker plus the shared `AnimatedProgressDialog` (its `set_close_guard(guard)` asks before Esc or the title-bar X dismisses it, never on a programmatic `close()`, and only for a dialog without a cancel button, #471; its `set_progress` shows the moving busy bar for a total of 0 and for nothing counted yet, 0 of N, until the first count, #507: a bar standing at 0% looked hung, as the generator's first lookups did for seconds, and the string loader and the update download start at 0 too) and `SelectAllDelegate`. Workers: `FileLoaderWorker` (sources → `StringEntry` list + sort keys), `AppliedStateWorker` (#398 review: runs the already-applied comparison off the GUI thread; takes an injected `compute(snapshot, should_stop)` instead of importing it, because the merge it shares with Apply to Game lives in `main_window.py` and importing that here would be a gui-to-gui cycle; always emits `finished(bool)` once, False being the safe "not applied" answer), `StartupSyncWorker` (refresh URL-backed sources at startup), `EnhancementsGeneratorWorker` (run `scripts/generate_enhancements_ini.py` in-process via `importlib.util`; takes a `language` param so output lands in that language's enhancements dir while annotation paths still parse the English base.ini; captures that folder, the DataForge build key and the tag fingerprint when its run starts, empties `.dataforge_stamp` just before the generator's `main()` and writes the tag stamp and then the DataForge stamp after it returns, see *A cut-off generation is offered again at the next start* below; `requestInterruption()`, which only closing the window sends, stops it before its patches, its module load or `main()`, and inside `main()` at the next job boundary, never during the writes, records it in `stopped` and ends with `finished(False)`, no `error` and nothing at ERROR), `P4kExtractWorker` (unp4k extract of `global.ini`, working beside the DataForge cache it is handed as `scratch_near`), `DataForgeExtractWorker` (unp4k + unforge + post-extract patches; both stop on `requestInterruption()`, record it in `stopped` and then end with `finished(False)`, no `error` and nothing at ERROR, #471; a successful DataForge run keeps its working folder for `take_working_folder()`, any other outcome deletes it before `finished`, and a DataForge run first waits for the background deletes it is handed as `wait_for`, #522), `WorkingFolderDeleteWorker` (deletes that folder in the background, #522, see *Closing stops a running extraction*), `StaleWorkingFolderSweepWorker` (sweeps the working folders a crash or a kill left, #522, same section), `LanguageBaseDownloadWorker` (2.0: fetch a non-English language's global.ini from its mapped URL into `cache\lang\{language}\base.ini`), `UexShopDataWorker` (3.1.0, #606: `uex_shops.load_shop_data` for the SCO Item Finder, always emits `finished(ShopData or None, error)` once; `closeEvent` waits for it, its requests time out after `REQUEST_TIMEOUT_S`), `LiveBlueprintLogWorker` (SCO, 3.0.0: polls `blueprint_log_scanner.GameLogTail` on the active channel's `Game.log` every `POLL_MS` while the overlay runs, LIVE and HOTFIX only, and emits `blueprints_found(raw names, newest)`; read-only like the Scan, the main thread updates the owned set; stopped with `requestInterruption()` + `_reap_worker`; a lasting poll fault logs one traceback, then debug; takes `(log_path, since, loc_files)` and reads the notification's texts from the loc files once, when it starts, #564; a failure there is guarded as a poll is, logged once at WARNING with its traceback, since an ERROR would open the error box over the game, while the watch goes on with English alone), `BlueprintLogScanWorker` (#222: scan a channel dir for "Received Blueprint" notifications via `blueprint_log_scanner.scan_channel`, watermark-aware — takes `(channel_dir, since, loc_files)`, emits a `ScanResult`; stays read-only, all owned-set/watermark mutation happens on the main thread in `MainWindow._on_blueprint_log_scan_finished`). Both read the notification's text in the language the game shows from the loc files they are handed (#564, `blueprint_log_scanner.notification_templates`, English always) on their own thread, because each can be about 11 MB, and log the texts at INFO. Each emits `progress` (str) and `progress_pct` (completed, total, message); `AnimatedProgressDialog.set_progress` consumes the latter. Exception: `AppUpdateCheckWorker` and `AppUpdateDownloadWorker` live in `src/utils/app_updater.py` because the workers, version comparison, and installer-asset picking belong together (#211). - `markdown_renderer.py` — `markdown_to_html(text, text_color, base_color, link_color)` for About/Help. Pure-Python; the Qt caller passes palette colours so the converter has no Qt dep. Stash-and-restore code-span handling keeps `**` and `_` inside backticks literal (loc keys like `vehicle_Name*` shouldn't sprout `` tags). - `config_tab.py` — **Config Tab**: source management, drag-drop merge hierarchy, SC install path, DataForge extraction trigger. Also the language selector (2.0): emits `language_changed(str)` for `MainWindow._on_language_changed`, and hosts `LanguageSourceDialog` (the *Map Language File* button) for per-language base.ini URL overrides. Changing the data folder migrates existing data via `migrate_user_data_dir(move=True)`. A DataForge cache folder change whose cache folder cannot be made (Windows refuses it, cannot reach it or rejects it) is undone as Cancel undoes it, with one box (`_report_cache_folder_error`, #494, see below). The cache folder field saves only a folder the user typed (`_cache_dir_edited`), so a click into it and out again, or Enter with nothing typed, tries nothing. While an extraction or a generation runs, `set_data_locations_locked` locks the folders, the channel, the language, Extract, Import Settings and Check for Updates, with the reason shown (#483, see *Run in Background and the job lock* below). - `shader_cache_dialog.py` — `ShaderCacheDialog`: what the Config tab's **Clear Shader Cache** button opens. One row per build from `shader_cache.find_shader_cache_dirs()`, each with **Clean** (subfolders only; disabled and the name greyed out when `is_clean`) and **Remove** (hard-deletes the whole folder at once, no prompt), plus a single **Close** button. Each click runs `ShaderCacheWorker` (`workers.py`), which first refuses to touch anything while `StarCitizen.exe` runs, then always emits `finished(str)` once (`STATUS_DONE` / `STATUS_FAILED` / `STATUS_GAME_RUNNING`, exceptions logged at WARNING so `ErrorDialogHandler` doesn't add a second box), under an `AnimatedProgressDialog` whose close guard keeps Esc and the X from hiding it mid-delete; then the rows are re-scanned. Keyboard safety, since Remove has no prompt: row buttons have `autoDefault` off, Close is the default button and gets focus on open and after every refresh, so Enter never lands on Remove. Close is ignored while a worker runs. `ConfigTab._clear_shader_cache` just opens the dialog; the dialog's own empty state covers "no folders". - `enhancements_tab.py` — **Enhancements Tab**: stats-overlay toggles, ship favorites prefix, DataForge extraction trigger, per-field mission-detail show/hide toggles (#121, persisted via `AppSettings._MISSION_FIELD_SETTING`). Emits `merge_requested`, `enhancements_pipeline_requested`, `favorite_prefix_changed` and `category_ticks_changed`. Apply Category Changes, Save Tag Changes and Generate Enhancements are locked while an extraction or a generation runs (`set_changes_locked`, #483). Its DataForge status (`refresh_forge_status`, run while the tab is built) reads the cache folder without creating it, so a folder Windows refuses or a drive that is gone reads as not extracted instead of stopping Smart Citizen opening (#494, see below). The whole tab sits in a `QScrollArea` so a small window squishes nothing (#145). Its dropdowns are `combo_box.NoScrollComboBox`. A category tick is pending until the category Apply button under the checkboxes saves it (`_apply_category_changes`: the settings, the `.disabled` renames and a reload), and pending ticks count (#532): generation (`MainWindow._run_enhancements_generation` when no categories are passed, which none of its callers do), Apply Enhancements (once it has saved `user.ini`, so the reload reads the table's own overrides back), Export Settings (once a file is picked, so a cancelled export saves no tick) and the Config tab's Preview Apply (its button sends `ConfigTab.preview_starting` before `preview_merge` runs) call `apply_pending_category_changes` first, the same rule #215 gave Generate for the Tag Builder, so they build, write, back up and preview what the checkboxes show. Generation passes `reload=False`: a successful run reloads, and a failed one that saved ticks reloads through its `if_unfinished` unless its caller gave one (a language switch's reload). A launch that saved ticks also marks Apply Enhancements dirty, so an already-applied check that read the old set cannot turn it green during the run. Apply Enhancements' reload is synchronous, so its merge and the table both use the saved ticks. While a tick is pending, Apply Enhancements is red and enabled (`category_ticks_changed` to `MainWindow._on_category_ticks_changed`, which marks it dirty, so closing offers Apply Now unless a revert of the game file has cleared that reminder since), and an already-applied verdict cannot turn it green (`_apply_applied_state_verdict`), because the check merges the saved set. Ticks put back re-run the check, except while closing, with nothing loaded or with a load running, as after a blueprint scan. While a job runs (#483) the category Apply button is locked, and so is every other way to save a tick: `apply_pending_category_changes` saves nothing then, so Apply Enhancements, Export Settings and Preview Apply leave the tick pending (the renames would land in the folder a generation writes), and `_mark_applied` keeps Apply Enhancements red for it. A generation's own launch is not a job yet, so it always saves. Locking and unlocking refresh the button through `_refresh_category_apply_btn`, not the tick handler, so they tell MainWindow nothing and leave Generate's record alone. A tick lights Generate too, and ticks put back put Generate back as it was before the first one, unless another change lit it meanwhile (`_generate_dirty_without_ticks`, which `_mark_enhancements_dirty`, `mark_enhancements_clean`, `set_operation_idle` and `refresh_enhancements_dirty_state` keep up to date): it used to stay lit as if something had changed. Saving the ticks (`_save_category_state`) does the same when they only turned categories off, whose files are just set aside, and keeps Generate lit when one was turned on, whose files may be missing or set aside from an older run. A generation that saves the ticks builds them, so its launch leaves Generate clean. A tick counts once Generate or Apply Enhancements has used it, so closing without either drops pending ticks and the next start shows the saved set. Leaving the tab keeps pending ticks and the category Apply button stays lit. `revert_category_checkboxes` resets every box after Import Settings, and only the offered ones after the enhancement category question, which can also come after a channel switch or a global.ini extraction, so a tick pending on another category stays. The question (`_check_enhancements_freshness`) leaves out of its offer a category the tab has unticked and not saved (`pending_unticked_file_keys`): it ticks what it offers, so its Generate built a category the user had just unticked, and left out, the run's own save turns it off with its files. - `combo_box.py` — `NoScrollComboBox` (#197: a `QComboBox` that lets the mouse wheel scroll the page instead of changing the selection when not focused, and opens its list below the box where it fits) and `reposition_combo_popup_below_if_it_fits` (#388). Used by the Enhancements, Blueprint Tracker (`_NoWheelComboBox` subclasses it) and Overlay tabs; it moved out of `enhancements_tab.py` when the third tab needed it. -- `blueprint_tracker_tab.py` — **Blueprint Tracker Tab** (#157; split out of the Enhancements tab into its own tab in 2.2.x, #222): the Available/Owned shuttle for blueprints that appear in missions' POTENTIAL BLUEPRINTS rewards, with search + Mission/Type/Class/Size/Grade filters. Owned items get an `[Owned]` tag woven into blueprint bullets wherever they appear (`src/utils/owned_items.py`). `set_blueprint_items(meta)` receives `{name: BlueprintItem}` from `MainWindow._recompute_owned` (computed by `src/utils/blueprint_meta.py::build_blueprint_metadata` from the loaded strings, which this tab can't see directly). Emits `owned_items_changed`, consumed by `MainWindow._recompute_owned`. The "Show tags on blueprint names" checkbox (#221, `AppSettings.get_/set_blueprint_show_tags`) toggles between `BlueprintItem.name` (bare, the stable matching identity) and `BlueprintItem.tagged_name` (the item's live item_Name value, tag and all) for display only — matching/filtering/Owned-tracking always use the bare name. Most of its i18n strings still live under the `enhancements.blueprints_*` namespace in `languages/*/ui.json` (unchanged on purpose — only the tab housing moved, not the strings' meaning); the tab's own title is `tabs.blueprint_tracker` / `blueprint_tracker.title`. The "Scan Logs for Owned Blueprints" button (#223 tab move; scanning itself is #222) emits `scan_logs_requested`; `MainWindow._run_blueprint_log_scan` validates the install root (`AppSettings.get_sc_install_root()`), queues the channels from `_scan_queue_for_root` (LIVE, plus HOTFIX when its folder is present; there is no checkbox, the Config channel makes no difference, and PTU/EPTU/TECH-PREVIEW are never scanned, enforced by the `_SCANNED_CHANNELS` allow-list in `_channels_to_scan` and again where `_start_next_blueprint_scan` starts each worker, #446) and reads each channel's own watermark (`AppSettings.get_blueprint_log_watermark()`), runs `BlueprintLogScanWorker` (`workers.py`, wrapping `src/utils/blueprint_log_scanner.py`'s `scan_channel`) with a progress dialog, and `_on_blueprint_log_scan_finished` normalizes the returned raw names (running the #372 foreign-name recovery only when the Config channel is LIVE or HOTFIX, because the item list it matches against is the Config channel's, #446), merges new ones into `AppSettings.set_owned_items()`, and advances the watermark (monotonically, even when nothing new was found) so a re-scan only re-reads log growth since the last run. `_finish_blueprint_scan_queue` also calls `_seed_default_owned_blueprints` (#416), which adds each starter blueprint every player owns (`blueprint_meta.DEFAULT_OWNED_BLUEPRINTS`, never logged and never a mission reward) to the Owned set once, recorded by loc key in `AppSettings.get_/set_default_blueprints_seed()`, and lists them in that scan's summary. A scan that adds blueprints then hands Apply's verdict to the background already-applied check (`_refresh_apply_dirty_after_reload`), because a starter is in no mission list and changes nothing in the game file, except while closing, with nothing loaded or with a load running (that load checks after its own re-weave). `closeEvent` settles the check again after its unapplied-changes prompt, whose event loop can deliver a scan finish. The names come from the loaded strings, so a scan that finishes before any have loaded (the startup auto-scan can) marks the seed pending and `_rebuild_blueprint_metadata` finishes it after the next load, then reports what it added the way a silent auto-scan does (`_report_blueprints_added`, shared with the scan finish). The load keeps the names and queues the report as its last step but one (`_queue_deferred_starter_report`, followed only by `_queue_asks_after_the_job`, #483, whose flush waits while any modal box is open), because an earlier modal step such as the enhancement categories prompt would run a sooner queued call inside its own event loop, and `_flush_deferred_starter_report` waits while an extraction, generation, Simple-mode run or load is going (each normally ends in a reload that queues it again, and after a failed or stopped one the report waits for the next load) and never runs while closing. It is one-shot per item: a starter moved back to Available stays there, one declared in a later release reaches Owned on the next scan, and it never raises (a failure is logged and retried on the next scan). The "Auto-scan logs on startup" checkbox (#386, `AppSettings.get_/set_auto_scan_blueprints_enabled`, off by default) drives `MainWindow._maybe_auto_scan_blueprints`, called from `_continue_startup_after_update_gate`: reuses the same channel-queue/worker pipeline as a manual click (the same LIVE-plus-HOTFIX coverage, #446), but sets `_bp_scan_silent = True` so `_finish_blueprint_scan_queue` reports through the status bar instead of the manual scan's modal summary dialogs, and shows no progress dialog either — a launch isn't the place for a popup, especially once most runs find nothing new. Silently skips (no warning dialog, unlike the manual scan) when no LIVE or HOTFIX folder is found under the install path yet. The sibling "Show popup for new blueprints found by auto-scan" checkbox (#386 follow-up, `AppSettings.get_/set_auto_scan_show_popup_enabled`, also off by default) opts a silent run's "found something new" case back into the manual scan's own modal summary dialog instead of the status bar message — checked in `_finish_blueprint_scan_queue` only on that branch; a quiet run (nothing new) ignores it and stays silent either way. +- `blueprint_tracker_tab.py` — **Blueprint Tracker Tab** (#157; split out of the Enhancements tab into its own tab in 2.2.x, #222): the Available/Owned shuttle for blueprints that appear in missions' POTENTIAL BLUEPRINTS rewards, with search + Mission/Type/Class/Size/Grade filters. Owned items get an `[Owned]` tag woven into blueprint bullets wherever they appear (`src/utils/owned_items.py`). `set_blueprint_items(meta)` receives `{name: BlueprintItem}` from `MainWindow._recompute_owned` (computed by `src/utils/blueprint_meta.py::build_blueprint_metadata` from the loaded strings, which this tab can't see directly). Emits `owned_items_changed`, consumed by `MainWindow._recompute_owned`. The "Show tags on blueprint names" checkbox (#221, `AppSettings.get_/set_blueprint_show_tags`) toggles between `BlueprintItem.name` (bare, the stable matching identity) and `BlueprintItem.tagged_name` (the item's live item_Name value, tag and all) for display only — matching/filtering/Owned-tracking always use the bare name. Most of its i18n strings still live under the `enhancements.blueprints_*` namespace in `languages/*/ui.json` (unchanged on purpose — only the tab housing moved, not the strings' meaning); the tab's own title is `tabs.blueprint_tracker` / `blueprint_tracker.title`. The "Scan Logs for Owned Blueprints" button (#223 tab move; scanning itself is #222) emits `scan_logs_requested`; `MainWindow._run_blueprint_log_scan` validates the install root (`AppSettings.get_sc_install_root()`), queues the channels from `_scan_queue_for_root` (LIVE, plus HOTFIX when its folder is present; there is no checkbox, the Config channel makes no difference, and PTU/EPTU/TECH-PREVIEW are never scanned, enforced by the `_SCANNED_CHANNELS` allow-list in `_channels_to_scan` and again where `_start_next_blueprint_scan` starts each worker, #446) and reads each channel's own watermark (`AppSettings.get_blueprint_log_watermark()`), runs `BlueprintLogScanWorker` (`workers.py`, wrapping `src/utils/blueprint_log_scanner.py`'s `scan_channel`) with a progress dialog, handing it `_blueprint_notification_files(channel, channel folder)` (#564: the game logs the notification in the language it shows, a Spanish player `Plano recibido: `, so the worker also looks for that text in the scanned channel's own files, never the Config channel's: its base.ini for the selected language as the table reads it, the English one until the language's own is fetched (`AppSettings.get_base_ini_leaf`), and the global.ini applied to that channel's game (`get_applied_global_ini`), which holds what the game shows, an override once applied or another tool's file; English is always looked for, for older logs. They are named without making a folder, and a data folder that cannot be reached leaves the applied file alone, since the scan reads the install's logs, with one WARNING for as long as the same failure lasts (`_data_folder_warning`: repeats go to DEBUG)), and `_on_blueprint_log_scan_finished` normalizes the returned raw names (running the #372 foreign-name recovery only when the Config channel is LIVE or HOTFIX, because the item list it matches against is the Config channel's, #446), merges new ones into `AppSettings.set_owned_items()`, and advances the watermark (monotonically, even when nothing new was found) so a re-scan only re-reads log growth since the last run. The recovery's item list (`blueprint_meta.known_item_names`, kept in `_known_item_names`) leaves out items' short labels (keys ending `_short`, #570), which name no item anyone owns: with them in, an old logged name that ends in an armour set's name was saved as the set's label, which matches no blueprint. On every load `_repair_foreign_owned_names` drops a label saved that way (`_short_label_names`: the labels `blueprint_meta.item_name_sets` gives in the same pass as `_known_item_names`, less the names the tracker offers, which the user can mark owned, dropped through `owned_items.drop_short_labels`) before the #372 repair runs. Between the two it renames an owned name saved in another language (#569): the Owned set holds display names, so after a language switch an item owned under its old name stayed in Owned and showed again in Available under its new one. `owned_items.rename_across_languages` traces a name the loaded strings do not know through its loc key in the other languages' item name tables to its loaded name (`_item_names_by_key`, from the same `item_name_sets` pass). The tables come from one cached base.ini per language but the loaded one (`blueprint_meta.other_language_files` over `AppSettings.get_cached_base_ini_paths`, every channel's, since the Owned set is shared by all channels: the active channel's copy when it has one, otherwise the first channel's; the loaded language is the one whose file the `global` source loads, found by file identity), through `blueprint_meta.read_item_keys_by_name`, which reads only a file that is new or changed since the last load. A name only one channel's build of a language uses is not traced through another channel's copy: one table per language, not per channel and language. No file is read on the GUI thread: the async load reads them on `FileLoaderWorker`'s thread (`workers.read_language_name_tables`, handed the window's tables and handing back the new ones with the entries, stored in `_language_name_tables` before the rebuild), and a synchronous reload (a channel switch, a data folder change, a backup restore, a favourite prefix change) starts `workers.LanguageNameTablesRead`, a daemon thread, before it reads the sources and takes its result before the rebuild, so the rename itself (`_other_language_item_keys`) only looks the names up. A file that cannot be read (its stat fails, or it holds something and no line could be read from it) gets an entry with no stamp (`(None, {})`), while an empty one counts as read, since a cut-off download that left one would otherwise hold the drop back for as long as it is there, and a failure that leaves unknown which files to read hands back the window's tables with one more such entry (`workers._NOT_LISTED`), each at WARNING: the rename still uses what was read, and `_language_tables_complete` holds the #570 label drop back until a load reads every file, since an unread language might use a label's text as an item's name (a Spanish load would otherwise drop the English-seeded "S-38 Pistol" whenever the English file was held at the session's first load). It renames only when the keys lead to one name, merges the name into that one when it is already owned, and leaves a name two items share or one no language knows as it is. The load after a switch runs it, which is the rename on switch, and the first load of a version with it fixes the names already saved. It runs before the #372 repair, which would read an old language's name as decorated and could fold it into a shorter item whose name it ends with. The #570 label drop before it keeps a label's text that another cached language uses as an item's own name (`drop_short_labels`' `other_languages`), for the rename: community translations leave some short labels untranslated, so the Spanish file's S-38 short label is "S-38 Pistol", the pistol's English name, and a Spanish load dropped it from an Owned set seeded in English (the user's portable test; Demeco LMG, Liberator and S71 Rifle make the same trap). `_rename_from_other_languages` does it with an INFO line per name, for the load, for `_owned_names_from_log` (a scan's log names and the overlay's live watch, before its #372 recovery and for any Config channel, since it matches loc keys exactly) and for Import Owned Blueprints, which the tab runs through the renamer the window hands it (`set_name_renamer`, `_rename_imported_names`) before `match_import_names`, listing a name it still cannot match as the file spells it. `_finish_blueprint_scan_queue` also calls `_seed_default_owned_blueprints` (#416), which adds each starter blueprint every player owns (`blueprint_meta.DEFAULT_OWNED_BLUEPRINTS`, never logged and never a mission reward) to the Owned set once, recorded by loc key in `AppSettings.get_/set_default_blueprints_seed()`, and lists them in that scan's summary. A scan that adds blueprints then hands Apply's verdict to the background already-applied check (`_refresh_apply_dirty_after_reload`), because a starter is in no mission list and changes nothing in the game file, except while closing, with nothing loaded or with a load running (that load checks after its own re-weave). `closeEvent` settles the check again after its unapplied-changes prompt, whose event loop can deliver a scan finish. The names come from the loaded strings, so a scan that finishes before any have loaded (the startup auto-scan can) marks the seed pending and `_rebuild_blueprint_metadata` finishes it after the next load, then reports what it added the way a silent auto-scan does (`_report_blueprints_added`, shared with the scan finish). The load keeps the names and queues the report as its last step but one (`_queue_deferred_starter_report`, followed only by `_queue_asks_after_the_job`, #483, whose flush waits while any modal box is open), because an earlier modal step such as the enhancement categories prompt would run a sooner queued call inside its own event loop, and `_flush_deferred_starter_report` waits while an extraction, generation, Simple-mode run or load is going (each normally ends in a reload that queues it again, and after a failed or stopped one the report waits for the next load) and never runs while closing. It is one-shot per item: a starter moved back to Available stays there, one declared in a later release reaches Owned on the next scan, and it never raises (a failure is logged and retried on the next scan). The "Auto-scan logs on startup" checkbox (#386, `AppSettings.get_/set_auto_scan_blueprints_enabled`, off by default) drives `MainWindow._maybe_auto_scan_blueprints`, called from `_continue_startup_after_update_gate`: reuses the same channel-queue/worker pipeline as a manual click (the same LIVE-plus-HOTFIX coverage, #446), but sets `_bp_scan_silent = True` so `_finish_blueprint_scan_queue` reports through the status bar instead of the manual scan's modal summary dialogs, and shows no progress dialog either — a launch isn't the place for a popup, especially once most runs find nothing new. Silently skips (no warning dialog, unlike the manual scan) when no LIVE or HOTFIX folder is found under the install path yet. The sibling "Show popup for new blueprints found by auto-scan" checkbox (#386 follow-up, `AppSettings.get_/set_auto_scan_show_popup_enabled`, also off by default) opts a silent run's "found something new" case back into the manual scan's own modal summary dialog instead of the status bar message — checked in `_finish_blueprint_scan_queue` only on that branch; a quiet run (nothing new) ignores it and stays silent either way. - `log_tab.py` — **Log Tab**: in-app log viewer. Bridges Python `logging` to Qt via `_LogEmitter` (thread-safe). Level filtering, auto-scroll, export. - `error_dialog.py` — `ErrorDialogHandler` + `_ErrorDialogEmitter` bridge `logger.error(...)` / `logger.critical(...)` to a Qt modal so users see failures without opening the Log tab. Same shape as `log_tab.py`: the handler is `setLevel(logging.ERROR)` so INFO/WARNING records skip it at the logger gate; the emitted record is marshalled to the main thread via `error_emitted = pyqtSignal(str, str)`. Cooldown + "N suppressed" coalescing live in `MainWindow._show_error_dialog` (not the handler), so the handler stays a stateless transport. - `filter_header.py` — `FilterHeaderView`: `QHeaderView` subclass with a per-column `QLineEdit` filter row below header labels, debounced. @@ -22,8 +22,8 @@ GUI layer (PyQt6). See the root `CLAUDE.md` for project context and cross-cuttin - `test_plan_panel.py` — **Test Plan dock** (#144): `TestPlanPanel`, the right-side `QDockWidget` checklist testers use to verify a release. Checkboxes grouped by section, a live progress bar, a persisted tester name, and Copy Report / Submit to Discord / Reset. Modelled on the Help dock (`_ensure_help_dock` → `_ensure_test_plan_dock` / `show_test_plan`, opened from the **More** menu). Check-state, tester name, and webhook URL persist via `AppSettings`; the plan content and report formatting are Qt-free in `src/utils/test_plan.py`; the Discord POST runs off-thread in `TestPlanSubmitWorker` (`workers.py`). Submit is disabled with no webhook configured (`AppSettings.get_test_webhook_url()` → stored override, then `SMART_CITIZEN_TEST_WEBHOOK_URL` env); Copy Report always works. - `coach_mark.py` — `CoachMarkOverlay` plus `TutorialTour` for the in-app guided tour. Self-contained: the main window builds `CoachMarkStep` records (target widget, title, description, optional pre-action) and calls `tour.start()`. The overlay dims the window, spotlights the target, floats a callout with Back/Next/Skip; emits `finished(completed: bool)`. - `overlay_tab.py` — **Overlay Tab** (3.0.0): Start/Stop Overlay button plus one checkbox per `AppSettings.SCO_OPTION_SETTING` switch (names are `AppSettings.SCO_*` constants; a drawer section's switch is `SCO_DRAWER_SECTION_PREFIX` plus its `sco_overlay.SECTION_ICONS` name) (scan decoder, drawer, its Blueprints / Minerals / Crafting sections indented under it and greyed out while the drawer is off (names starting `drawer_`), mark new blueprints owned from Game.log) and a drawer position picker under the drawer switch (`AppSettings.SCO_DRAWER_POSITIONS`, default middle right, greyed out with the drawer). The scan-sample capture has no switch here (tuning only, see `sco_overlay.py`). #523 added, under the scan decoder switch and greyed out with it, a **Scan text size** picker (`AppSettings.SCO_LABEL_SIZES`, `get_/set_sco_label_size`, default medium) and, under an `overlay.alerts_title` line, one switch per watched-target alert (names `SCO_ALERT_PREFIX` plus a `sco_overlay.ALERTS` name: glow and flash on by default, color, bigger and sound off), and under the drawer's position picker, greyed out with the drawer, a **Drawer hotkey** box (`HotkeyEdit`, saved through `get_/set_sco_drawer_hotkey` as portable text; its hint's example is Alt+8 because Star Citizen's default bindings, `Data/Libs/Config/defaultProfile.xml` in Data.p4k, use every letter, F1 to F12, Home, End, Page Up and Down, Pause, Tab, Space, the arrows and `/`, and Left Ctrl and both Shifts on their own, but never 8, Insert, Delete or Alt on its own, read on LIVE 2026-10-23). Since #523 the tab is in titled boxes like the Config and Enhancements tabs (`_group`, titles `overlay.scan_group`, `drawer_group`, `blueprint_watch_group`): each part's switch first with its hint under it (`_add_switch`), what hangs under it set in (`_indented`), and the alerts and the drawer's sections side by side (`_switch_row`) with their hints as tooltips. `HotkeyEdit` (a `QLineEdit` nothing can be typed or pasted into, with a **Clear** button to its right, `clear_hotkey`, lit only while a hotkey is saved, since every key pressed in the box is taken as the hotkey) records one key combination from the Windows virtual key each press reports (`nativeVirtualKey`, through `global_hotkey.hotkey_text`), not from the character the keyboard layout makes of it: where Ctrl+Alt is AltGr, Ctrl+Alt+O makes a character such as "ó", which a `QKeySequenceEdit` takes for the key (so the combination could not be registered; found in testing), and Shift+1 makes "!". A press with no virtual key (another platform, a press sent by code) falls back to Qt's key. While only modifiers are held it shows them ("Ctrl+Alt+"; Qt leaves a modifier key's own modifier out of its press, so `_MODIFIER_KEYS` adds it back), it takes Tab and every key an app shortcut would (it accepts `ShortcutOverride`), and a combination `windows_hotkey` does not take (a key Windows has no code for, a dead key, a symbol another key also types, or a letter, digit, symbol, Space, Tab or navigation key without Ctrl, Alt or Win) is not saved: the box goes back to the saved one and says why (`refused`). `set_hotkey_problem()` shows why the hotkey is not in use (`global_hotkey.HOTKEY_TAKEN` or `HOTKEY_UNSUPPORTED`, worded by `hotkey_problem_text()` as `overlay.hotkey_taken` or `overlay.hotkey_unsupported`), which `MainWindow._on_sco_hotkey_problem` passes on from `ScoOverlay.hotkey_problem` along with the same text in the status bar. The text size and position pickers are both built by `_picker_row`, and their settings read and saved through `AppSettings._get_choice` / `_set_choice` (a value outside the choices reads, and saves, as the default). Checkboxes save straight to settings and emit `options_changed` → `MainWindow._apply_sco_options` (pushes them to `ScoOverlay.set_options` and starts/stops the live log watcher); the start button emits `overlay_toggled`, which drives the toolbar Overlay button so both go through `_toggle_sco_overlay`, and `set_running()` mirrors the overlay back without re-emitting; `set_option()` likewise mirrors a switch the SCO drawer changed. `refresh_styles()` re-applies the start button's theme colour; `MainWindow.refresh_action_buttons()` calls it on a live theme swap, with the toolbar's Overlay and Tutorial buttons. -- `sco_overlay.py` — **Smart Citizen Overlay (SCO)** (3.0.0): always-on-top windows over the game, toggled by the toolbar's **Overlay** button (`MainWindow._toggle_sco_overlay`). `ScanLabelWindow` is click-through and shows the decoded mining signature centred under the scanner readout, always in the ODW colours (`ODW_OVERLAY_COLORS`, see-through at `DRAWER_ALPHA`) whatever the app theme; `BlueprintDrawer` is a stack of three tapered icon tabs (`SectionTabBar`, one per section, icons from `SECTION_ICONS` painted as `QPainterPath`s and kept upright on every edge) docked at one of eight positions (`set_position()`; `drawer_edge()` maps a corner or middle position to its side edge and top/bottom centre to the top or bottom edge, and `SectionTabBar.set_edge()` turns the stack to match). Neighbouring tabs overlap by their taper (`DRAWER_HANDLE_OVERLAP`), like browser tabs; the open section's tab is painted last and near-solid so it sits in front, and `tab_at()` hit-tests front to back so a click in an overlap goes to the tab you see. A tab click (`open_section()`) opens the see-through (`DRAWER_ALPHA`) panel, a `QStackedWidget`, straight to that section, another tab switches section, and the open section's own tab closes it. A section switched off on the Overlay tab hides its tab (closing the drawer if it was open), and with all three off the drawer is hidden (`has_sections()`). The panel takes clicks and focus, but only a search box (`DrawerSearch`, focus on a click only) ever takes the keyboard: every other widget in the panel is `NoFocus`, and a search box ignores a held key's printable repeats. In game F is held to move the mouse, and a tab click gave the Blueprints or Crafting search focus, which then filled with "ffff" (#523). Its sections: a searchable blueprint list with owned checkboxes, a Minerals search (mineral → star system → location; a location finds its minerals) topped by a scan decoder checkbox (the same `scan_decoder` setting as the Overlay tab's: `scan_decoder_toggled` → `MainWindow._on_sco_scan_decoder_toggled` saves it and mirrors the tab via `OverlayTab.set_option`, while `set_options` mirrors the tab back with `set_scan_decoder`) and a **Clear all** button, with a watch checkbox right-aligned in column 1 of each ore's row (only ores `mining_catalog.ore_key` knows, since only those can decode) and of a **Salvage** row that ends the list whatever the catalog holds (`SALVAGE`, the `OTHER_SIGNATURES` key it watches, #523; `_add_watch_box` makes both kinds of box). Ticked ores and salvage go out through `watched_changed` and are saved by MainWindow (`AppSettings.get_/set_sco_watched_minerals`, fed back with `ScoOverlay.set_watched_minerals` on start); when a decode includes one, the label sets off the alerts switched on (`ScanLabelWindow.set_alerts`, from the Overlay tab's `alert_` switches; `set_watched` while it shows). The lasting ones: the glow (a pulsing `QGraphicsDropShadowEffect` in the theme accent, `GLOW_PULSE_MS`, with room for it from `GLOW_MARGIN`, less above (`GLOW_TOP_MARGIN`) so the masked label window never covers the readout), the text in `ALERT_COLOR` (a bright green, not the theme accent, which is dark blue in the Light theme) and the text `ALERT_TEXT_SCALE` times bigger, the label re-sized and re-centred under its anchor (`_place`). When a watched target is first read (`_on_reading`'s `fresh`: a value that was not showing), the label flashes, `FLASH_TOGGLES` swaps of its text and background colours `FLASH_MS` apart that change no size, and `play_alert_sound` starts the sound picked on the Overlay tab (`AppSettings.get_sco_alert_sound`, pushed with `ScoOverlay.set_alert_sound`; the tab's **Preview** calls it too) with winmm's `PlaySoundW`: "Smart Citizen Default" is a two-note chime made in memory (`alert_chime_wav`, `SND_MEMORY | SND_ASYNC`, so nothing waits and no sound file ships), the `voice_` choices are recorded WAVs shipped in `assets/sounds/` (`VOICE_ALERT_SOUNDS`, `voice_sound_path`, `SND_FILENAME`; bundled with the rest of `assets/`), and the others are Windows sound aliases (`WINDOWS_ALERT_SOUNDS`, `SND_ALIAS`, which follow the user's sound scheme); keep both in step with `AppSettings.SCO_ALERT_SOUNDS`; a steady repeat does neither. `set_text_size` (the Overlay tab's **Scan text size**) scales the label's font against the app font (`LABEL_SIZE_SCALE`). The third section is a Crafting search (a mineral lists the items it goes into, an item lists the materials it needs). The fourth, the Item Finder (#606, magnifying glass `_finder_icon`, switch `drawer_finder`), searches the shop list `set_shop_data()` hands it (`src/utils/uex_shops.py`): each matching item is a collapsed row with its shop count (opened by itself when it is the only match), its children the shops, place, system and price, cheapest first, with `MATCH_LIMIT` items at most and a row saying how many matched; a line under the tree says where the data is from and when it was fetched, or that it is loading, or that UEX could not be reached. `MainWindow._refresh_sco_shops` (from `_apply_sco_options` once the overlay runs) starts `UexShopDataWorker` when the finder is shown and the data is missing or over 12 hours old, not again within `UEX_RETRY_S` of the last try. Crafting rows lead back to their compendium mineral through `_mineral_by_material`, built in `set_catalog()` with `CraftingIndex.material_key_for`, the same link the mineral tooltips use, so CIG's spelling differences (Pressurized Ice / Ice, Aluminum / Aluminium, ...) resolve both ways. Minerals, locations and items carry tooltips (`mineral_tooltip`, `location_tooltip`, `_item_tooltip`). `BlueprintDrawer.retranslate_ui()` sets every fixed text and redraws the list and trees; it runs at construction and from `MainWindow.retranslate_ui()` after a language switch. The guided tour's `overlay` step (`assets/tutorial.json`, after `blueprint_tracker`) points at the Overlay tab's start button. `MainWindow._refresh_sco_catalog` feeds `set_catalog()` from the English base.ini's Mining Compendium and the `crafting_index.json` the generator writes (see `src/utils/mining_catalog.py`), re-reading only when either file changed. The drawer is coloured from the active theme via `OverlayColors.from_theme()` (window colour + title/tagline accents), re-read on every start. `ScoOverlay.set_options(dict)` applies the Overlay tab switches, a missing name taking its `SCO_OPTION_SETTING` default. `format_matches` lists a reading that fits salvage too (12,000 is 3 ROC, 4 FPS or 6 Salvage) with salvage first and the `SURFACE_ONLY` kinds marked `sco.surface_only`: the overlay cannot tell space from a planet, and in space salvage is the only answer (#523). A selected row in the drawer keeps the panel's text colour (`::item:selected { color }`): left to the palette it took `HighlightedText`, near black in the SCLE and ODW themes, on the dark see-through panel. **Drawer hotkey (#523).** `ScoOverlay` owns a `global_hotkey.GlobalHotkey`, given the Overlay tab's combination by `set_drawer_hotkey` and held only while the overlay runs with the drawer showing (`_sync_hotkey`, from `_sync_windows` and `stop`), since Windows keeps a held combination from the game. Each try ends in `hotkey_problem` ("" or why), and a refused combination is not tried again until it changes or the overlay stops (`_hotkey_refused`), so one start reports it once. The hotkey runs `toggle_drawer`: closed, it remembers the window that has focus (`foreground_window`, the game), opens the drawer on the section used last (`BlueprintDrawer.open_last_section`, the first shown one before any) and activates it. That takes focus only when the press came as `WM_HOTKEY` (Windows lets a process that just got its hotkey take the foreground), which frees the mouse over another program. In Star Citizen the press arrives through raw input alone, Windows keeps focus on the game, and the player still holds F to use the mouse in the drawer (found in testing; `_report_focus` logs it at INFO `FOCUS_CHECK_MS` after the open). Taking focus anyway would need `AttachThreadInput` with the game's thread, sent input or a changed Windows setting, which the anti-cheat rule below keeps out. Open, it closes it. Whenever the drawer closes (the hotkey or its own tab, `expanded_changed`) while it still has focus, the remembered window gets focus back (`give_focus_back`), so the mouse returns to the game; a drawer the player has clicked away from leaves focus alone, and a drawer hidden by its switch (`_sync_windows`) forgets the window, since it closed nothing the hotkey opened. `ScoOverlay` owns both plus the capture timer over `SCAN_REGION` (fractions of the primary screen); the reader is pluggable (`SignatureReader`); the default `hud_signature_reader` hands the capture's red, green and blue channels to `src/utils/sco_digit_reader.py` and maps the box back from device to logical pixels. A new reading only replaces the label after `READINGS_TO_CHANGE` identical captures in a row (`_on_reading`; any accepted or steady reading clears the pending candidate, so a misread that comes back later still has to repeat back to back), so a one-frame misread can't flash "Unidentified" over a steady signature. The confirming capture runs at once (`QTimer.singleShot(0, _capture_once)` on a first sighting) instead of waiting for the next tick, so a new signal shows up to a tick sooner; `_capture_once` drops a queued one once the timer has stopped. The label sits `LABEL_GAP` px below the readout, centred under the scanner's pin icon and the number together (the reader's box covers the digits only, so `_handle_found` widens it left by `READOUT_PIN_WIDTH` digit heights, #523), and `_mask_own_label` blacks it out of each capture so its own text is never read. The box comes to logical pixels with each edge rounded outward, so with display scaling the label never sits over the digits' bottom row (it did, and its blackout then made the next reads fail, 1080 px at 125%), and while the label shows, `_steady_anchor` keeps it where it is unless the readout has moved more than `ANCHOR_DEAD_ZONE` digit heights: captures of a still readout put its box a few pixels apart, which made the label twitch on every capture (#523). Each distinct reading's crop is saved once per session to `{logs_dir}/sco_samples/