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

[Bug]: 1,06 -> GBFRelinkFix.ini not found (easily?) #32

Closed
tomvoelske opened this issue Feb 25, 2024 · 4 comments
Closed

[Bug]: 1,06 -> GBFRelinkFix.ini not found (easily?) #32

tomvoelske opened this issue Feb 25, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@tomvoelske
Copy link

tomvoelske commented Feb 25, 2024

Issue Summary:

When the game loads, it is unable to find the .ini file. I've had it work once and once only, and not been able to replicate it since.

GBFRelinkFix & Game Version Numbers:

GBFRelinkFix 1,06 | Game version whatever it is as of 25/02/2024

Log Files:

GBFRelinkFix.log

Reproduction:

image

image

The folder "./scripts/scripts" is created upon log generation

image

My system volume for GBR is J: in case some default of C: is being used in the code

Please note that all files are exactly as from the 1.06 download - I haven't made any changes

@tomvoelske tomvoelske added the bug Something isn't working label Feb 25, 2024
Lyall added a commit that referenced this issue Feb 26, 2024
@Lyall
Copy link
Owner

Lyall commented Feb 26, 2024

That second scripts folder is just a bug with log generation that'll be fixed in the next version. It shouldn't affect functionality of the fix though. Can you post the log file from the scripts/scripts folder in your last screenshot? If it can't find the config file, it will say as much in the log file.

@tomvoelske
Copy link
Author

Hey, I did post it above but I know it kind of blends with the rest of the text. I'll post it again here:

GBFRelinkFix(1).log

I didn't try putting the missing files into the new /scripts folder to test, but I do remember it working once and then not after, so perhaps the base path was messed up when the new /scripts folder was made? Not sure.

@Lyall
Copy link
Owner

Lyall commented Feb 26, 2024

Hey, I did post it above but I know it kind of blends with the rest of the text. I'll post it again here:

My mistake, time to get my eyes checked!

I didn't try putting the missing files into the new /scripts folder to test, but I do remember it working once and then not after, so perhaps the base path was messed up when the new /scripts folder was made? Not sure.

Can you try this test build? I've set log generation to use an absolute path which should fix that erroneous scripts folder appearing. Also added more logging for file paths so you can see where the fix thinks your log file and config file are.

@tomvoelske
Copy link
Author

Cheers, seems to work beautifully! The logs indicate no problems, but I'll upload them nonetheless just to aid in future releases etc.

GBFRelinkFix - First run all default.log

GBFRelinkFix - Second run all default.log

GBFRelinkFix - Third run with changes.log

And I didn't try beyond that, since I'm sure it's working happily now. Appreciate the work and amazing mod!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants