Skip to content
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

Custom URL field #14

Open
turecross321 opened this issue Feb 21, 2022 · 3 comments
Open

Custom URL field #14

turecross321 opened this issue Feb 21, 2022 · 3 comments

Comments

@turecross321
Copy link

There should be a way to patch an already patched eboot if you enter the ip address the eboot's patched to.

@logantgt
Copy link
Contributor

Good idea - would make things easier but it kind of conflicts with #9 - we would need to actually store the locations of each URL in each version of the EBOOT unless we could come up with a better way of detecting that 'something' is a URL.

Right now the preferred method is to ensure that you ALWAYS have a backup of your original EBOOT.bin in the event that you want to connect to a different server - then it's as simple as copying that file and patching it multiple times with different URLs, and copying them to access different servers.

UnionEBOOTManager maybe? Lol.

@jvyden
Copy link
Contributor

jvyden commented Feb 21, 2022

Right now the preferred method is to ensure that you ALWAYS have a backup of your original EBOOT.bin in the event that you want to connect to a different server

Agreed. It's already a step in our guides to make a backup of the EBOOT.

@FridiNaTor1
Copy link

What if there was a config file created, that saved previously used URLs, or that you can put URLs in. First time starting the program would create the config with the official URLs, and you could add your old ones or different ones just into the config file. And UnionPatcher would also write the replacement URL into the config automatically, so you can still use the same eboot for repatching.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants