Ricky1280 Posted February 22, 2016 Posted February 22, 2016 (edited) Hello, this is my first custom modpack that i'm trying to get working, I got all the mods to load properly but the problem starts when I try to connect to a server or load a world (generation goes well but the problem seems to be world loading or when I try to render something). The error that I keep getting is caused by: java.lang.ClassNotFoundException: net.minecraft.src.FMLRenderAccessLibrary here is the crash log please help!! http://pastebin.com/gQVquwSK Edited February 22, 2016 by Ricky1280 Formatting, weird highlights, I decided to use pastebin instead of pasting the whole crash log Quote
Discord Moderator plowmanplow Posted February 22, 2016 Discord Moderator Posted February 22, 2016 (edited) Always provide the API URL or a link to your platform pack page when requesting custom modpack assistance. Does the client work as expected in SSP? Is that crash report from the client or from the server? (If it's a server log I see many client only mods in that list) Once we have the API URL or a link to the pack page we can continue. Edited February 22, 2016 by plowmanplow Quote
Ricky1280 Posted February 22, 2016 Author Posted February 22, 2016 https://drive.google.com/file/d/0Bz5OO97rrC-dQ3UxYzFjbUpKcFU/view?usp=sharing like this? The client does the same thing in SSP It's a crash report from the client, I successfully hosted a server with the client sided mods removed, it seems to be a client bug and nothing seems to be wrong with it serverside. Quote
Ricky1280 Posted February 22, 2016 Author Posted February 22, 2016 (edited) http://api.technicpack.net/modpack/ricky1280s-modpack1 <- IT DOESN'T WORK That link doesn't work, I had to change config files so IDs wouldn't conflict, please use the first one even though it isn't a technicpack link it should work right? Edited February 22, 2016 by Ricky1280 Info, use the first link. Quote
Discord Moderator plowmanplow Posted February 22, 2016 Discord Moderator Posted February 22, 2016 As I stated, we need the API URL or a link to your pack page in order to assess the pack metadata. I'll assume that whatever download URL your pack references is current and will evaluate that. Always ensure you increment the pack version number any time you change the pack metadata or the contents or URL of the modpack archive download location. Your modpack archive is in RAR format. All archive files intended for use in the platform must be in ZIP format only. Your modpack archive is missing the /bin/ folder and the "modpack.jar" file which should be inside that folder. MDK-1.7.10-8.1.8.258.zip is the development kit for Mekanism and does not belong in a client modpack. Be aware that your pack is enormous and also contains Reika's mods. They are notorious for having compatibility issues in very large packs. Quote
Ricky1280 Posted February 22, 2016 Author Posted February 22, 2016 Thank you, so you only need the bin folder and modpack.jar or can you solve the problem from there? Quote
Discord Moderator plowmanplow Posted February 22, 2016 Discord Moderator Posted February 22, 2016 (edited) Well, you can solve the problem by creating a /bin/ folder and putting the correct modpack.jar inside. You will also need to address the other bullet points. Edited February 22, 2016 by plowmanplow Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.