Homer_400 Posted June 4, 2020 Posted June 4, 2020 (edited) When i play in my favorite modpack, it doesn't work. There's just a white screen and it never opens. I tried to downgrade java as people from other forums told to do. But doesn't work either. I'm sure that isn't a problem with low space in disk because i have 800Gb free in my 1tb disk. So i Opened the console and it says that version.json file is missing. I've already seen others posts about this problems, but there was no answer to this problem, actually. https://paste.ubuntu.com/p/xJkd7chXGN/ Edited June 4, 2020 by Homer_400 Forgot ubuntu paste file
Forum Administrators Lord Ptolemy Posted June 5, 2020 Forum Administrators Posted June 5, 2020 Not a launcher issue. Moved to Platform Pagoda.
Homer_400 Posted June 6, 2020 Author Posted June 6, 2020 On 6/4/2020 at 9:39 PM, Lord Ptolemy said: Not a launcher issue. Moved to Platform Pagoda. ok, now how do i solve it?
TerdyTheTerd Posted June 6, 2020 Posted June 6, 2020 Well, what does the modpack.jar file look like in ~.technic\modpacks\a-era-do-futuro-1-fg\bin\ (you can get here more by pressing the modpack options gear from the launcher -> open folder). You will need something like winrar to open the file. If the file is missing or is no longer valid, either try re-installing the pack or manually replacing it I should have looked at that log file first, at com.mrcrayfish.furniture.Donators.<init>(Donators.java:19) that furniture mod is attempting to connect to something for what appears to be donor cape related, and its bombing out. Try looking for the config for that mod as there's usually options to disable those sorts of things.
Homer_400 Posted June 10, 2020 Author Posted June 10, 2020 @TerdyTheTerd yo man, removed the mod, but it is still with the problem of this line: [B#546] File version.json not found in C:\Users\mbc-j\AppData\Roaming\.technic\modpacks\a-era-do-futuro-1-fg\bin\modpack.jar -snip- Ptolemy
TerdyTheTerd Posted June 10, 2020 Posted June 10, 2020 Ahh I just assumed it was that mod as the log made it appear that the launcher was bombing out after failing to connect. I'll have to look at this again in a little bit.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now