Need help with modpack

[Trevman822]

I was attempting to make a private modpack for my friends and I to play on, when I came across an error that I am having trouble with.

 

When the pack launches, it stays on the Mojang screen for a bit and then sends me back to the Technic launcher screen.

 

I honestly have no clue on how to fix it, and am looking for anyone that could help me solve this problem. 

 

Here is the log : http://pastebin.com/dR8BvMYh

 

And here is my pack : http://www.technicpack.net/modpack/details/trevs-test-pack.362177

 

Thank you to anyone that is able to help me!

 

 

Edited May 19, 2014 by Trevman822

[plowmanplow]

• You have included REIMinimap for Forge/MC 1.6.2. Get the 1.6.4 version.
• You have included an old version of IC2 with known problems. If you are going to include IC2 I recommend looking at this post:
• You have included MutantCreatures mod but not the AnimationAPI mod it requires. Make sure you only get your mods from the author's preferred distribution channels so that you can also get the proper installation instructions.
• Your Iguana Tweaks mod for TConstruct is not compatible with the version of TConstruct you have. You need to use the experimental version.
• You have NEI but none of the addons/plugins additions. You probably want these.
• You have NEI but it is a RAR format archive. 1) All archive files intended for use by the platform must be in ZIP format. 2) The author does not distribute RAR files. See the third bullet point.
• Your CodeChickenCore is a RAR format archive. See previous bullet point.
• You need to manually update ForgeMultipart to Build #250.
• I don't use the OreSpawn mod but I find it hard to believe that it just doesn't work at all. However, I have had a number of packs lately that it just doesn't work in. It will crash the game with an exception in entity packets (Packet24). I'm not going to go through the entire pack to find out what the conflict is. I'll leave that up to you. If you want to use OreSpawn you'll likely need to ask some questions in the MCF thread.
• The IDFix mod often does "bad things". Use IDFixMinus instead. With IDFix in place Forge was throwing a very ambiguous exception. With IDFixMinus it was able to resolve most (all?) of the conflicts properly.

[Trevman822]

Thank you, your solutions fixed the modpack and it is able to launch successfully without any problems.

 

However I am attempting to set up a server and am having trouble, I placed the server side mods and configs in the right place (at least I think I did) but it fails to launch the server. I most likely didn't put something in the right place or didn't set something up properly.

 

I'm trying to launch it with MCPC+ and am completely clueless like I was with the regular modpack as to what I am doing wrong.

 

Here is my most recent crash (I'm going to stop trying to 'fix' things as it seems to keep messing things up) : https://dl.dropboxusercontent.com/u/244726417/ForgeModLoader-server-1.log

I did it through Dropbox because I reached the limit on pastebin and it wouldn't let me save it.

 

It looks like there are some of the same errors, but some new ones have formed on top of the old ones I was encountering before.

 

Here's the list of mods in my modpack : http://gyazo.com/ddf2523ae925f3e7034c448c15a38bc9

 

Config in modpack : http://gyazo.com/288951419987164cc3e34d7567a0b703

 

List of mods in the server : http://gyazo.com/980c24f9f1481c03797b5d4f72e4a350

 

Config for the server : http://gyazo.com/9dd2e073f6f3f068b3a8adc5a0731e5f

 

Thank you again for helping me with the launching issues, I'm glad that part is working smoothly. If you could help me once more, I would be even more grateful for your assistance. If you need any more details I would be more than willing to give them to you.

Edited May 20, 2014 by Trevman822

[plowmanplow]

Based on your current client pack:

• Forge Multipart should be in the mods1.6.4 folder.
• You have updated IC2 but have not included the recipe fix mod from the link I gave you.
• Even with IDFixMinus you still have some ID conflicts you need to resolve. Specifically with Mystcraft. Check your FML client log.
• Current dev versions of MMMPS are fundamentally broken. If you place a Tinker's Table it will crash the client. I think you can use up to Build #100 or #99, but just use the recommended one from Machine Muse's website.
• You have included MMMPS but not the Addons mod. MMMPS is pretty gimpy without the addons (autofeed module, etc.)
• You have an outdated version of Optifine and should update.
• When intending to use your pack with a server you MUST remove IDFixMinus and include the full working config folder in your modpack archive and in your server.

Mod removed for the server:

• REIMinimap
• Damage Indicators
• Optifine

Removing the listed mods (and IDFixMinus) and using the client config folder allowed me to start a MCPC+ B262 server and connect from the client.

[Trevman822]

I made all the changes you suggested, but I'm getting another error. I'm not sure what is causing it.

 

This is the error (It wasn't showing up in the crash log) : http://gyazo.com/ce12a2ccef397ae8b1923f8da2e392a7

Sorry about the picture, I tried to screenshot it as it was happening.

 

My new mods folder : http://gyazo.com/71bc954a9beaefdfb0f1796fc6a8b31e

 

Modpack config : http://gyazo.com/b2e687acb34ef8539fc9d23b4eb64efa

 

New server mods : http://gyazo.com/186aa4cc0e8b275c33a2b18f233bc102

 

New server config : http://gyazo.com/eb5f4bf757af248d515027535f97936d

 

The new crash log : https://dl.dropboxusercontent.com/u/244726417/ForgeModLoader-server-0.log

 

I apoligize if it's something that is extremely easy to fix, I have little experience with making modpacks/servers for the modpack. I wouldn't have been able to make this server/modpack if you hadn't of helped me. Thank you again.

Edited May 21, 2014 by Trevman822

[plowmanplow]

The tiny screenshot has your error:

entityLandmine Exception: java.lan.OutOfMemoryError: PermGen space

You need to increase the PermSize setting of your server command line arguments.

[Trevman822]

Thank you, I was able to fix that error. There is 1 last error that is occurring though.

 

The error is : 

2014-05-20 22:36:32 [sEVERE] [ForgeModLoader] Found anonymous item of class mods.XW.item.ItemIngot with ID 31971 owned by mod XW, this item will NOT survive a 1.7 upgrade!

and this goes on for a couple other mods.

 

http://pastebin.com/LnkujUUv

 

Should I also be worried about any warnings, or are the [sEVERE] problems the only ones I should be worried about.

Edited May 21, 2014 by Trevman822

[plowmanplow]

That error has no impact on the server. It is more a warning to mod authors and to let you know that unless the author fixes the mod that the item/block won't survive an upgrade.

[Trevman822]

Turns out that there is another error that is stopping me from playing on the server. Whenever I try and launch it, the server stops when it reaches the Buildcraft version check. It gives me the error "[iNFO] [buildcraft] Version check failed". When it reaches that point it doesn't continue and stays like that until it do /stop.

 

End part of server log : http://pastebin.com/PYfrPvHL

 

Entire log : https://dl.dropboxusercontent.com/u/244726417/ForgeModLoader-server-0.log

 

I'm using BC version 4.2.2, and tried downgrading to version 4.2.1 but encountered the same problem.

Edited May 21, 2014 by Trevman822

[plowmanplow]

The version check failing just means that the mod isn't able to retrieve the file to compare versions against. The end of that log file looks "normal".

[Trevman822]

Thanks again, but I have another issue (I know, I'm really sorry). You've practically put this pack together for me and I feel bad, but I got a couple missing IDs and mismatched IDs. How do I fix these? Hopefully this will be the last error that I will need help fixing, I'm sorry about the constant problems.

 

I get this when I try and connect to my server : http://gyazo.com/d91d21fe9903c3e55d8fcab233c24dc6

[plowmanplow]

This is what happens with you dont:

1. Include a full working set of config files in your published modpack.
2. Use the working config files from the client pack in your server configuration.

[Trevman822]

I remade the server folder, re adding all the config files from the modpack. It turns out that I was replacing the config files when I tried to fix something, once I deleted all the config files and replaced them with the new config files in the modpack it worked. It seems like the server is running smoothly and has no problems. Thank you for your help with the modpack and server, I know I said this before but I seriously wouldn't of been able to create this modpack/server without your help. 

[plowmanplow]

Glad to help. It's something I enjoy. And no need to apologize for asking questions. I only get discouraged when someone keeps making the same mistakes over and over again.