Releases: jonigirl/open-strings
v1.3.9
Added
- Installer now reads the RSI Launcher's settings file to auto-detect the Star Citizen
install path during setup — most users no longer need to browse for it manually - App settings also fall back to the RSI Launcher path on first launch if no path
has been configured - Uninstaller now offers to remove the DataForge game data cache (~1.4 GB) as an
optional cleanup step
Fixed
- App settings are now stored as a plain JSON file in
%APPDATA%instead of the
Windows registry — settings survive reinstalls and are portable between machines - Star Citizen install path chosen during installation is now correctly applied on
the app's first launch — previously it was silently ignored when asettings.json
already existed from a prior install - Workers module failed to load on startup due to a stale import reference introduced
when the string-loading service was moved — corrected - Status bar text was clipped on narrower windows; body font size increased to 11 pt
- Variant string resolution now prefers the richer (longer) value when an
_SCItem
mirror key and its canonical form conflict — prevents short or empty values winning
Changed
- Activity spinner in the status bar now alternates between light blue and light
pink while operations are in progress
Open Strings 1.3.1
What's fixed
Enhancements generation crashed immediately after DataForge extraction with \No module named 'xml.etree'.
Root cause: \generate_enhancements_ini.py\ is bundled as a data file so PyInstaller does not analyse its imports. \xml.etree.ElementTree\ lost its only analysed reference when \dataforge_patcher.py\ switched to lxml in 1.3.0, so it was silently dropped from the bundle.
All other 1.3.0 features are intact. If you installed 1.3.0, upgrade to this release to restore enhancements generation.
Assets
- \OpenStrings-1.3.1-Setup.exe\ — installer (recommended)
- \OpenStrings.exe\ — standalone portable executable
v1.3.0
Warning
This release has a critical bug. Enhancements generation crashes with \No module named 'xml.etree'. Please upgrade to v1.3.1.
Added - Frontend_PU_Version watermark written into global.ini on every Apply — marks which Open Strings version produced the file and stamps the SC build version alongside it - DataForge cache directory relocated to %LOCALAPPDATA%\Open Strings\<channel>\cache\dataforge to keep the ~1.4 GB XML tree outside OneDrive sync scope; one-shot startup migration from the old Documents path - Apply dialog per-category enhancement breakdown (Ships, Components, etc.) with category counts - Blueprint scanner widened to include the full blueprintrewards/ subtree for SC 4.8 compatibility - Versioned lookup cache keyed by "<version>:<fingerprint>" to invalidate stale generator caches across SC releases ## Fixed - Enhancement generators now correctly detect DataForge changes — a path prefix bug caused dirty_categories() to always return empty, so generators never re-ran after a DataForge update - Enhancement generation now skips unchanged categories instead of always regenerating all — reduces unnecessary DataForge re-processing after clean extractions - DataForge extraction progress dialog now stays open across the extraction→enhancement handoff and closes correctly on failure - g_language key detection is now case-insensitive (g_Language, G_LANGUAGE, etc. all matched) - Double-separator paths on Windows fixed at all path-setting call sites - "Copy Filtered" clipboard export now shows the true stock base.ini value in the "Original Value" column - Misleading "retrying…" log message on download timeout corrected ## Changed - Preview pane and Help/About panels now render with Atkinson Hyperlegible font - Log export filename changed from sc_loc_editor_{timestamp}.log to open_strings_{timestamp}.log - "Preview Merge" renamed to "Preview Apply" in the Config tab - "Smart Citizen Enhancements" label updated to "Open Strings Enhancements" in Apply dialog - Apply success dialog shows per-category enhancement counts - lxml >= 6.1.1 added as a dependency
v1.2.0
What's changed
Added
- Export Loc-Pack button — packages the applied
global.inias a shareable zip from the toolbar - Enhanced status badge — Status column now shows
Enhanced(blue) for auto-generated enhancements entries andModified(green) only for user edits - Mission Engagement Type — enhancements generator derives
FPS,Ship, orFPS & Shipfrom mission loc-key naming and includes it in the mission stats block - Mission Turret counts — enhancements generator extracts turret counts and hostility from DataForge spawn XML and includes them in the mission stats block
Fixed
- Tutorial Skip preference now persists correctly across app version updates
- mypy attr-defined error:
QCoreApplicationnarrowed toQApplicationbeforesetFontcall - Import INI download: replaced deprecated
urlretrievewith size-capped HTTPS-enforced downloader (50 MB cap) - Tools download:
urlopennow usestimeout=60to prevent worker thread hanging on stalled server
Changed
- Preview pane height cap raised to 120 px
_COMPONENT_CODESnow defined in one canonical place (string_model.py)- Ruff bugbear (
B) rules added to linting - Removed dead
source_category_filtersblock fromini_parser.py - Build signing simplified: always self-signs, no interactive prompts
v1.1.2
Open Strings 1.1.1
Open Strings 1.1.1 — Attribution and legal patch
Changes
- Add MIT attribution for bundled unp4k / unforge tools to NOTICE.md
- Add RSI / Data.p4k disclaimer to README
- Install LICENSE and NOTICE.md alongside app via installer
Install
Download and run \OpenStrings-1.1.1-Setup.exe. Requires Windows 10/11 x64 and a Star Citizen installation.
Licence
GPL-3.0-only. See NOTICE.md for upstream and third-party attribution.
Open Strings v1.1.0
Initial fork release of Open Strings, based on Smart Citizen 1.0.0 by Osiris DevWorks.
Changes from upstream
- Rebranded to Open Strings
- Removed Smart Citizen / Osiris DevWorks branding, donation links, and ODW Discord references
- Data directory changed from \Documents\Smart Citizen\ to \Documents\Open Strings\
- Added Check for Updates (checks jonigirl/open-strings GitHub releases on startup and via toolbar)
- Journal annotation tag changed from [SmC]\ to [OS]\
Installation
Run \OpenStrings-1.1.0-Setup.exe. Requires Windows 10/11 x64. No other dependencies needed.