Repository navigation
feat(runtime): add initial Silky Engine startup support - #458
Closed
akitaSummer wants to merge 1 commit into
Closed
akitaSummer wants to merge 1 commit into
akitaSummer wants to merge 1 commit into
Conversation
Probe Silky archive directories before falling back to KiriKiri. Preserve the directory root for remembered EXE launchers and map pointer input to the provider frame. Pin the initial Internal runtime and add launch/input routing regressions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Silky Engine packages were falling back to KiriKiri, so selecting a remembered Windows launcher failed at startup. Route recognized packages through the optional private provider, keep their game directory as the launch root, and map pointer input to the native frame.
The public diff contains only runtime selection, launch/input routing, regression tests, and the Internal gitlink. Private source and reverse-engineering details remain in Internal.
Validation on the complete macOS arm64 Debug application:
Silky coverage is currently limited to startup and the opening. Save/load, native settings, galleries, backlog, character/E-mote playback, and movie playback are not implemented.
Companion: https://github.com/AetherKiri/AetherInternal/pull/88. It is stacked on Internal #87, whose head is already pinned by public main. Merge the Internal dependency chain first, then merge this PR; update the gitlink if Internal is squash-merged or rebased. Keep the private feature branch available until the pinned commit is permanently reachable.
The existing same-repository CI builds include Internal. Public build logs and binary artifacts retain their existing exposure; no workflow or artifact policy is changed.