v0.2.0-rc4: the launcher's fourth candidate, the first with a wizard and two changelogs
\nThe Phaethon launcher installed from a wizard around Velopack's Setup.exe, updated in place\nthrough Velopack, signed with an Azure Artifact Signing identity, reading the game's session\njournal while it runs, and now aware of what a runtime update reaches.
\nSince v0.2.0-rc3: the install wizard with its license, its read-only location, its progress\nand its launch box, which says whether it installs, updates, reinstalls or replaces and\nrefuses while the launcher runs, and one Apps and Features entry whose uninstaller asks what\nelse to remove; the two changelogs, the launcher's and the runtime's, read as markdown from\nthe store in two tabs; a runtime update that rebuilds only the games and stages whose build\ninputs changed, from the keys the runtime's manifest carries, with Play running the rebuild\nfirst; the Discord presence under the Phaethon application's id; a download the store answers\nwith 429 or 503 waiting and asking again; the extractor's exit 4003 worded and 4001 corrected.
\nThis candidate reads the rebuild keys and the runtime changelog from a runtime at v0.1.0-rc4 or\nlater; against an older runtime it rebuilds every imported game once per runtime version, as\nupstream's launcher does, and the Runtime tab says no changelog is published.
\nsigned: true
"},{"PackageId":"PhaethonLauncher","Version":"0.2.0-rc4","Type":"Delta","FileName":"PhaethonLauncher-0.2.0-rc4-delta.nupkg","SHA1":"010C28C2C91C2E8FA6BDA9D4E9BC2F731CD1A37E","SHA256":"A32E96E8AA8F991141747B3F3A2103AB36D67080381C4EBEC8B997BE3A169F7A","Size":545065,"NotesMarkdown":"v0.2.0-rc4: the launcher's fourth candidate, the first with a wizard and two changelogs\n\nThe Phaethon launcher installed from a wizard around Velopack's Setup.exe, updated in place\nthrough Velopack, signed with an Azure Artifact Signing identity, reading the game's session\njournal while it runs, and now aware of what a runtime update reaches.\n\nSince v0.2.0-rc3: the install wizard with its license, its read-only location, its progress\nand its launch box, which says whether it installs, updates, reinstalls or replaces and\nrefuses while the launcher runs, and one Apps and Features entry whose uninstaller asks what\nelse to remove; the two changelogs, the launcher's and the runtime's, read as markdown from\nthe store in two tabs; a runtime update that rebuilds only the games and stages whose build\ninputs changed, from the keys the runtime's manifest carries, with Play running the rebuild\nfirst; the Discord presence under the Phaethon application's id; a download the store answers\nwith 429 or 503 waiting and asking again; the extractor's exit 4003 worded and 4001 corrected.\n\nThis candidate reads the rebuild keys and the runtime changelog from a runtime at v0.1.0-rc4 or\nlater; against an older runtime it rebuilds every imported game once per runtime version, as\nupstream's launcher does, and the Runtime tab says no changelog is published.\n\nsigned: true","NotesHTML":"v0.2.0-rc4: the launcher's fourth candidate, the first with a wizard and two changelogs
\nThe Phaethon launcher installed from a wizard around Velopack's Setup.exe, updated in place\nthrough Velopack, signed with an Azure Artifact Signing identity, reading the game's session\njournal while it runs, and now aware of what a runtime update reaches.
\nSince v0.2.0-rc3: the install wizard with its license, its read-only location, its progress\nand its launch box, which says whether it installs, updates, reinstalls or replaces and\nrefuses while the launcher runs, and one Apps and Features entry whose uninstaller asks what\nelse to remove; the two changelogs, the launcher's and the runtime's, read as markdown from\nthe store in two tabs; a runtime update that rebuilds only the games and stages whose build\ninputs changed, from the keys the runtime's manifest carries, with Play running the rebuild\nfirst; the Discord presence under the Phaethon application's id; a download the store answers\nwith 429 or 503 waiting and asking again; the extractor's exit 4003 worded and 4001 corrected.
\nThis candidate reads the rebuild keys and the runtime changelog from a runtime at v0.1.0-rc4 or\nlater; against an older runtime it rebuilds every imported game once per runtime version, as\nupstream's launcher does, and the Runtime tab says no changelog is published.
\nsigned: true
"},{"PackageId":"PhaethonLauncher","Version":"0.2.0-rc3","Type":"Full","FileName":"PhaethonLauncher-0.2.0-rc3-full.nupkg","SHA1":"7350FAA5126781FFC28E636374524D18623C262D","SHA256":"62A6EB8CC479131078826D5D77544AA03B94A02FBDEDA8D3C0A48C18428C213A","Size":65948689,"NotesMarkdown":"v0.2.0-rc3: the launcher's third candidate, the first signed and the first that reads the game\n\nThe Phaethon launcher installed from Setup.exe and updated in place through Velopack, now\nsigned with an Azure Artifact Signing identity, so Windows names the publisher and SmartScreen\ncan build reputation on it. While a game the launcher started runs, the Game page and the\nDiscord presence say what the player is doing, read from the runtime's session journal (at the\ntitle, in the menus, racing on a named track, in a cutscene), play time is credited from it, each\ngame keeps its last session, and the exit toast says how the session went.\n\nSince v0.2.0-rc2: the session reader, the status, the play time and the last session on the\nGame page; the Discord presence and the exit toast reading the session; the download's presence\nkeeping the same floor; settings schema four; the tree naming alex/phaethon-launcher and\nalex/phaethon; the release job signing through the identity's six values.\n\nThis candidate needs the runtime at v0.1.0-rc3 or later for the journal; against an older\nruntime it shows what rc2 showed.\n\nsigned: true","NotesHTML":"v0.2.0-rc3: the launcher's third candidate, the first signed and the first that reads the game
\nThe Phaethon launcher installed from Setup.exe and updated in place through Velopack, now\nsigned with an Azure Artifact Signing identity, so Windows names the publisher and SmartScreen\ncan build reputation on it. While a game the launcher started runs, the Game page and the\nDiscord presence say what the player is doing, read from the runtime's session journal (at the\ntitle, in the menus, racing on a named track, in a cutscene), play time is credited from it, each\ngame keeps its last session, and the exit toast says how the session went.
\nSince v0.2.0-rc2: the session reader, the status, the play time and the last session on the\nGame page; the Discord presence and the exit toast reading the session; the download's presence\nkeeping the same floor; settings schema four; the tree naming alex/phaethon-launcher and\nalex/phaethon; the release job signing through the identity's six values.
\nThis candidate needs the runtime at v0.1.0-rc3 or later for the journal; against an older\nruntime it shows what rc2 showed.
\nsigned: true
"}]}