docs(wiki): the device code can be copied
Follows krt-profit/basetool-sc-extractor#78.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>
bf667c3
docs(wiki): the "not switched on yet" message of the go-live
Follows krt-profit/basetool-sc-extractor#76.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>
072317f
docs(wiki): the wait after a failed send
Follows krt-profit/basetool-sc-extractor#75: after a failure the app waits
5 seconds, doubling to at most 5 minutes and never shorter than the
Basetool asks, before it sends again.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>
bd01068
docs(wiki): the new error messages, the reference and the account question
Follows krt-profit/basetool-sc-extractor#74: an account the profile does not
name is confirmed before the sync, every refusal ends with a reference to
quote, and the new messages for pauses, quota, outages, terms, approval,
refused accounts, the 2000-item cap and format refusals.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>
c2dfdcc
docs(wiki): type the device code on the bare verification page
For krt-profit/basetool-sc-extractor#73: the app opens the page without a
pre-filled code, so the member sees the phishing warning every time.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>
4dea806
docs(wiki): the migration release is 2.10.0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>
3619d21
docs(wiki): the exchange migration - own account, envelope, sync, one re-login
For the extractor release that moves onto the Basetool's exchange API
(krt-profit/basetool-sc-extractor #68, #69, #70; krt-profit/basetool#2088).
Held back until those PRs are merged and the release is out.
An Basetool senden: the new interface and the switch-off hint an old build
shows, the installation name on the consent step, the one re-login and why,
the direct sync (opt-in, account check, add-only, removed-elsewhere only on
request, undo in "Verbundene Anwendungen"), disconnecting in the Basetool,
and the new failure messages.
Datenformat: the basetool.blueprints 1.0 envelope and what it leaves out;
old files still import; the refinery draft omits unread fields.
Workflow Blueprints: the account list and the third action.
Datenschutz: no handle, account, folder or file name is sent; the account
check is the one place the handle goes; the installation name.
Fehlerbehebung: the new messages.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>
a84943c
docs(wiki): LIVE and HOTFIX both ways, folder detection, clipboard watch, glyph veto
Follows the extractor change from the VerseKit comparison: the channel
folder is pre-filled from the RSI Launcher and the install, a picked
HOTFIX also reads LIVE, untranslated @key names are resolved
(localizationKey), pack class tags are explained, the images step can
watch the clipboard, and the new GLYPH_VETOED finding is listed. German
refinery labels are named for German installs, still unmeasured.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>
e935330
docs(wiki): the non-exportable login key and the fail-closed updater
- Updates: an update is offered only for an .msi from this project's releases
with a published SHA-256; it downloads into a fresh temp folder and the digest
is checked again right before the Windows Installer opens the file, including
the administrator retry (#58, #59).
- An Basetool senden, Datenschutz: the stored login holds the token and only the
name of a non-exportable key kept in the Windows key store (TPM where present),
so a copied entry is useless elsewhere; members of 2.9.1 and older sign in once
after updating (#58).
- Deinstallation: disconnecting also deletes the key from the Windows key store.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>
90b39af
docs(wiki): align every page with v2.9.1 and the web tool as it ships
- Sending to the Basetool needs version 2.9.1: since the identity move of
2026-09-14 older builds fail with "unrecognized_name".
- The release file is Basetool.SC.Extractor-<version>.msi; size and the
VirusTotal result are re-measured.
- The app does store settings: config.json in %APPDATA% holds the last
channel folder and the send consent, written by the first successful
Blueprint run.
- The three messages that block sending, the REFINERY SYSTEM C47.02 terminal
look, and the real manual-import paths in the web tool (Raffinerieverwaltung
-> Neuer Auftrag, and Meine Blueprints -> JSON importieren).
- The owner's handle in the data-format example is a placeholder now.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>
22d3c3e
docs(wiki): the Defender false positive, and how to verify a download
Members meet Microsoft Defender before they ever open the app, and the handbook
had nothing to say about it - the answer lived only in the English README. New
page `Virenwarnung-und-Echtheit`: why an unsigned MSI with no reputation and a
self-updating installer reads as `Trojan:Script/Wacatac.H!ml` to an ML
classifier, and the three ways to check the file instead of trusting the claim -
the VirusTotal report linked from every release, the SHA-256 via Get-FileHash,
and the signed SLSA provenance attestation via `gh attestation verify`. Linked
from Home, the sidebar, Installation, Updates and Fehlerbehebung.
Also documented the three send failures that were missing, all of which a retry
cannot fix, so the page has to say what would:
- The system clock outside the narrow window a signed request is accepted in,
with the way to synchronise it. This is the live failure mode of the DPoP
binding and it presents as "sign-in is broken".
- "Nur von freigegebenen Programmen" - a fork with a changed client id, refused
permanently by the server-side allowlist.
- The DPoP nonce handshake this build deliberately does not implement, which
needs a new release rather than a second attempt.
Datenschutz now explains why the remembered sign-in sits in one record with a
private key: the token is bound to it, so a copy of the token alone is worthless.
Corrected sizes that had not moved since the OCR models and the ONNX runtime
were bundled: the MSI is ~110 MB, not ~60 MB, and the installed program is
~185 MB across ~220 files, not ~515 files.
Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>
1a8bc93
docs(wiki): Spielsprache wird aus der Installation gelesen
Die Erkennung rät die Übersetzung nicht mehr, sondern liest den Meldungstext aus
`data\Localization\…\global.ini` des gewählten Ordners — also genau den Text, den
das Spiel schreiben wird, in jeder Sprache und auch dann, wenn sich die
Formulierung mit einem Update ändert.
Der Abschnitt "Was genau ausgelesen wird" beschreibt das jetzt so, statt von einer
festen Liste aus Englisch und Deutsch zu sprechen.
Beide Fehlertabellen sind entsprechend umgestellt: "0 Blueprints, obwohl ich
welche habe" nannte bisher die Spielsprache als Hauptverdacht. Das ist sie nicht —
in aller Regel sind die Logs der betreffenden Sitzungen schlicht weggeräumt. Die
Zusammenfassung nennt im Leerfall ausserdem die erkannte Spielsprache, das steht
jetzt auch in der Anleitung.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
cd7ab56
docs(wiki): Archivordner, Spielsprache, gemerkter Ordner, Log-Aufräumung
Zieht das Handbuch auf den Stand der Blueprint-Änderungen:
- **Archivordner.** Ein Ordner mit losen `*.log`-Dateien (ohne `Game.log`, ohne
`logbackups`) wird jetzt gelesen. Neu beschrieben in Workflow-Blueprints inkl.
der bewussten Grenze: nicht rekursiv. Die beiden Fehlertabellen und die
geänderte Hinweiszeile ziehen nach.
- **Spielsprache.** Star Citizen übersetzt das Etikett `Received Blueprint`; mit
Sprachpaket steht dort `Bauplan erhalten`. Beides wird erkannt, Groß- und
Kleinschreibung egal. Andere Sprachen finden vorerst nichts — deshalb ein
eigener Eintrag "0 Blueprints, obwohl ich welche habe" mit der Bitte um eine
Beispielzeile, statt Nutzer im Dunkeln zu lassen.
- **Gemerkter Channel-Ordner.** Das Feld ist ab jetzt mit dem Ordner des letzten
erfolgreichen Laufs vorausgefüllt. Das ist eine echte Korrektur am
Datenschutz-Kapitel: dort stand, die App speichere "keine Einstellungen". Der
Pfad kann den Windows-Benutzernamen enthalten, also steht jetzt da, was
gespeichert wird, wo, und wie man es loswird. Deinstallation und
An-Basetool-senden führen dieselbe Datei konsistent auf.
- **Reichweite eines Laufs.** Gelesen wird nur, was noch auf der Platte liegt —
SC räumt alte logbackups weg. Das erklärt die häufigste Rückfrage
("zu wenig Blueprints") und steht jetzt bei der Zusammenfassung.
- **gameBuild** kommt für die laufende Game.log aus dem Log-Kopf, weil deren
Dateiname keine Build-Nummer trägt.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ca79b4e
docs(wiki): App startet nach dem Update automatisch neu
Updates-Seite an das neue Verhalten angepasst: Der Installer-Helfer startet die
installierte App nach dem Einspielen (bzw. Rollback) selbst wieder; manueller
Start nur noch als Fallback.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
09d9e0a
docs(wiki): Error 1926 (Config.Msi / non-system-drive) beim Update dokumentieren
Neuer Fehler-Eintrag zu "Could not set file security for file …\Config.Msi\
….rbf. Error: 5" (endlose Schleife auf D:/E:), Beschreibung des neuen Dialogs
"Als Administrator erneut versuchen?" in Updates, und C:-Empfehlung bei der
Ordnerauswahl in Installation.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
12b52aa
docs(wiki): deutsches Benutzerhandbuch
Vollständiges deutschsprachiges Wiki als Handbuch: Installation, Updates,
Deinstallation, Bedienungsgrundlagen, beide Workflows (Blueprints, Refinery),
Ollama-/Hardware-Einrichtung, Screenshot-Leitfaden, Review & Auffälligkeiten,
"An Basetool senden", Datenschutz, JSON-Datenformat und Fehlerbehebung/FAQ.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2a41036