Ajuda a testar modpack

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Junior Alves

New Member
Jul 29, 2019
10
0
0
Estava testando um modpack que eu fiz, ai apareceu isso
"Forge Mod Loader has found a problem with your minecraft installation
The mods and versions listed below could not be found"
"bdlib: minimum version required is 1.9.1.97"
"The flie 'logs/fml-client-latest.log' contains more information"
Me ajudem se possivel, obrigado
 

Attachments

  • minecraft error.png
    minecraft error.png
    56 KB · Views: 85

Someone Else 37

Forum Addict
Feb 10, 2013
1,876
1,440
168
Looks like one of your mods needs bdlib version 1.9.1.97 or higher, which either means you're missing bdlib or you've got an outdated version of it. Try updating your version of that mod to the latest Alpha or Release version found here; see if that fixes it.

...or, in Portugese...

Parece que um de seus mods precisa bdlib versão 1.9.1.97 ou superior, o que quer significa que você está perdendo bdlib ou você tem uma versão desatualizada do mesmo. Tente atualizar sua versão do que mod para a mais recente versão Alpha ou Release encontrada aqui; ver se isso resolve o problema.
 
  • Like
Reactions: Junior Alves

Junior Alves

New Member
Jul 29, 2019
10
0
0
Eu resolvi o problema do lib, mas quando fui abrir o pack apareceu outra mensagem
 

Attachments

  • error.png
    error.png
    77.8 KB · Views: 79

Someone Else 37

Forum Addict
Feb 10, 2013
1,876
1,440
168
Eu nunca vi esse erro antes. Meu palpite é que ou você tem duas versões diferentes do "manequim Container" mod instalado de uma só vez, ou uma instância que está sob escuta alguma forma. Tente remover isso; se isso não corrigi-lo, meu próximo palpite seria tentar remover autopackager (ou desativando ele- se você alterar a extensão do arquivo de .jar para .jar.disabled, FML não irá carregá-lo) como essa é a única modificação listada lá que eu não estou familiarizado com excepção do manequim Container.

Se isso não funcionar, vá para a pasta onde sua instância Minecraft está instalado, localize o arquivo chamado "ForgeModLoader-client-0.log", enviá-lo para Pastebin, Gist, ou algum site semelhante, e postar um link aqui. Esse arquivo contém um monte mais informações sobre a instalação do Minecraft eo que deu errado, o que vamos precisar, a fim de entender corretamente a forma de corrigi-lo.

Além disso, a propósito, este é um fórum em língua Inglês; no entanto, se você não estiver familiarizado com o suficiente Inglês para fornecer uma tradução melhor do que o Google Translate pode fazer, você pode muito bem usar o Google Translate ou postar em seu idioma nativo. Eu não sou tão exigente.
 

Junior Alves

New Member
Jul 29, 2019
10
0
0
I can't find the folder "ForgeModLoader-client-0.log", I can't find the dummy container too. After delete the auto packager, this window dont open more, but the minecraft stop in this screen
 

Attachments

  • another erro.png
    another erro.png
    26.1 KB · Views: 76

Someone Else 37

Forum Addict
Feb 10, 2013
1,876
1,440
168
Huh. If you're running Minecraft through the Mojang launcher, the FTB launcher, MultiMC, or probably any other launcher out there, there should be a screen somewhere that fills up with a bunch of text as the game starts. This might be called a log, console, or development console depending on the launcher, and it should contain most of the same information as ForgeModLoader-client-0.log. Try uploading that to Pastebin (or Gist if it's too big).

Do note that the console window might be configured to disappear when the game starts; if it does that, you'll need to go into your launchers options or settings and change that.
 

Junior Alves

New Member
Jul 29, 2019
10
0
0
I know it, but, the launcher stop when enough this exact part of the launching, in the time of the cofh core run
 

Someone Else 37

Forum Addict
Feb 10, 2013
1,876
1,440
168
So... tell me if I'm understanding this correctly:
- After updating bdlib, your pack would load to a certain point, then crash with a message about a "mod sorting cycle".
- After removing autopackager, the pack hangs while post-initializing CoFH Core.
- You can't find the FML logfile or a way to upload the log directly from the launcher in the second case because it's frozen.

If you put autopackager back in, does the pack crash with the mod sorting cycle as it did before? If so, can you get to the logfile from that crash?
 

Junior Alves

New Member
Jul 29, 2019
10
0
0
when I put the auto packager, the modpack mopacks runs until this screen, but dont open, I think is probrably because the cofh core
 

Attachments

  • one other error awww.png
    one other error awww.png
    24.3 KB · Views: 119

Someone Else 37

Forum Addict
Feb 10, 2013
1,876
1,440
168
That's almost exactly the same information as the second one you posted here, so it doesn't really tell me much. I guess it's possible that CoFH Core or any of your other mods got corrupted somehow, although without any kind of logfile, I have no way to tell. Do note that the directory in which ForgeModLoader-client-0.log would appear is where the pack itself is installed, not your launcher- if you know how to find your Mods folder, look in that folder's parent folder. If the logfile isn't there, look for a folder called "logs" or "crash-reports".

If you still can't find the log file, try disabling half of the mods and see if the pack loads. If it doesn't, there's a good chance you disabled a dependency of a mod you didn't disable (for example, if you disabled CoFH Core or Thermal Foundation, but not Thermal Expansion), in which case FML will tell you what mods have missing dependencies, so you can disable them, too. If it still doesn't load, keep disabling things until it does. Once it does load, add mods back a few at a time until it breaks again; this way, you'll be able to narrow down which mod or mods are causing the problem.

Also, what pack, exactly, are you trying to play? What mods are in it?