-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Advanced options #15
Comments
note: there is demand |
im curious what the sudden need for this is? |
Multiple people have tried to patch LBP1 to lighthouse with Refresher, that wouldn't work though as beacon uses the original digest key, but refresher will set the key to "LbpPrivateServer" or something (i dont remember what the default was) |
the default is "CustomDigestKey" (imaginative, i know) |
another usecase is making some prototypes work with server aswell, since they dont always share the same digest key as the final game |
refresher will not patch the digest key unless autodiscover is used.
we dont really support prototypes anyway, so thats not a concern |
Patching the digest key to |
As Beyley says, this will only happen after a successful AutoDiscover negotiation where the server specifies What's likely happening is you're attempting to use Refresher after already having patched your game to Refresh. In this scenario, the digest key has already been modified to This can be solved by reverting to the original backup of the EBOOT taken when you first patch LBP by simply clicking the button to do so in the patcher's UI. I recognize that this is bad UX so I'll open an issue about using the backup for patches by default. |
Just as a note, another solution would technically be for Lighthouse to start accepting the |
Created #49 to track that issue. |
Ability to manually set if digest key should be patched, and other options if we implement any.
Low priority unless there is demand.
The text was updated successfully, but these errors were encountered: