StoneBlock 3 broken?

[SGlyph]

Modpack

FTB StoneBlock 3

Modpack version

1.5

Has the pack been modified

No

Log Files

No response

Describe the bug

The pack refuses to launch? It began a few days ago after it crashed out of the blue.

The modpack exists in a sort of limbo where it's in my library until I try to launch it. then it disappears.
I've not modified any files so I really can't tell where its gone wrong

I've uninstalled the pack, deleted instance files, but I've no clue what has caused this or how to fix it.
I've even reinstalled FTB from Overwolf but to no avail

Steps to reproduce

Unless other people have experienced this, I don't know how

Expected behaviour

.

Screenshots

This is what I experienced the day before yesterday.

This is what happens when I try to launch or install it from FTB

Additional information

No response

[Gaz492]

We are not aware of any issues with Stoneblock 3, would you be able to go to the settings in the app then click on the app tab and then click on the upload logs button then reply with the url it gives you?

[ftb-helper]

Hay, thanks for the issue! Unfortunately it looks like you've not provided a Debug code... We require this as it helps us find your issue as quickly as possible.

Please do the following

Please use the link below to download and run the FTB Debug tool. This is a tool built by our App Developers and will provide you a code that you need to attach to this issue. Please either edit your original issue or add a comment with this code. If you need more help running this tool, you can follow our guide on how to use the FTB Debug tool.

Windows // MacOS // Linux // Windows (Arm) // MacOS (Arm) // Linux (Arm)

[SGlyph]

We are not aware of any issues with Stoneblock 3, would you be able to go to the settings in the app then click on the app tab and then click on the upload logs button then reply with the url it gives you?

This is probably very irresponsible, but I'm not super tech savvy. So I'll post the latest log and hope you can figure it out from there.
latest.log
I also installed the debug tool like the bot suggested and got the following code: FTB-DBGUJIPIKEPOJ

I'm sure this whole thing is from my own incompetence somewhere down the line, but its really out of the blue from my perspective.

[Gaz492]

Could you try clicking on the settings button in the app, then if you click on App in the sidebar you will be taken to a page where there are 3 blue buttons in a row.

Click on the Home button, this should open windows explorer to where the app stores its data.
Now close the app and then in the explorer window right click on the bin folder and rename it to bin_broken.
Start the app up again then try starting the modpack up again, you might need to right click the modpack in the app, click on settings and then click the repair button if it still doesnt start up for you.

[SGlyph]

Could you try clicking on the settings button in the app, then if you click on App in the sidebar you will be taken to a page where there are 3 blue buttons in a row.

Click on the Home button, this should open windows explorer to where the app stores its data. Now close the app and then in the explorer window right click on the bin folder and rename it to bin_broken. Start the app up again then try starting the modpack up again, you might need to right click the modpack in the app, click on settings and then click the repair button if it still doesnt start up for you.

I think this has worked??
It let me install the modpack properly, but as it was validating assets, it seemed to have found something it didn't like

But then a minute after showing this pop-up the game launched and seems to be working fine.
I closed and relaunched to test and it seems to all be good!
Sadly all my previous worlds didn't get saved but that's not such a big deal.

Hopefully I won't need to add to this reply chain any longer

[Gaz492]

If this issue returns feel free to either reopen this issue or create a new one.