-
Posts
4594 -
Joined
-
Last visited
-
Days Won
74
Everything posted by plowmanplow
-
Always provide an API URL link or the link to your pack page when requesting assistance. Depending on the version of Forge you have, the log files may be in the logs folder inside your modpack folder. Always post a crash report (in a spoiler tag or pastebin) when possible.
-
A well crafted post. My only suggestion would be to include the API URL (the URL you add to the launcher) in your post. Your modpack.jar file is a RAR format archive. All archive files intended for use in the platform must be in ZIP format only. That being said, the modpack.jar file is simply the Forge universal binary JAR file renamed to modpack.jar. Don't extract it or alter it in any way (unless you REALLY know what you are doing). Fix that and come back if you are still having troubles.
-
This is your current download URL: https://www.dropbox.com/sh/wd7zt48a7qc541p/AAD-Z0hpYL45G5SbnSEfJp4fa?dl=0 It should be this: https://www.dropbox.com/sh/wd7zt48a7qc541p/AADk9t27aUNh_QzKcJbUq2Z7a/Zomrvival.zip?dl=1 Your bin folder does not have a modpack.jar file. The modpack.jar file is simply the correct version of the Forge universal binary JAR renamed to modpack.jar. Flans-Mod-1.7.2.jar belongs in the mods folder, not in the Flan folder. Correct these issues and come back if you are still having difficulties.
-
Update your Java to the latest Java 7 64bit. It is critical when adding mods to your pack to be aware of the mod dependencies, both for which mod and which versions. Specifically with Calclavia's mods, one must be careful to download mods which are all using the same APIs and dependencies. For instance, you seem to have the most recent versions of ICBM, andUE, but an older version of ResonantEngine. I would recommend updating that and see where it gets you.
-
It is unhelpful to start multiple threads for the same issue. I've responded in your original thread: '?do=embed' frameborder='0' data-embedContent>>
-
@Neko_TheHood: Riiiight. Thread jacking is accomplished by making a "I'm having the same issue" post in an ancient thread with no supporting evidence. In all my support here I have never seen a single instance where a post like this actually was the EXACT same issue as the OP. Neither of these type posts in this thread provided any context and there are about a dozen different ways a pack can start as "vanilla". One of the posters actually threadjacked two threads and sent me a PM within a fairly short period of time. Since you obviously know what you are doing and have the experience to offer assistance to folks when folks haven't provided any relevant or contextual information I'll let you handle this thread. Best of luck.
- 19 replies
-
- custom modpack
- Minecraft
-
(and 1 more)
Tagged with:
-
Update your Java version. That error commonly occurs when a mod version does not match the version of Forge/MC for the pack or when mods have conflicting APIs. Without more detailed logs and without the API URL it is impossible to say for sure where the issue is originating. You should be building your pack methodically so that when you add a mod and things start crashing you know right where to look.
-
In the Forge/MC 1.6.4+ versions of OptiFine you simply drop the JAR file in your mods folder.
-
The crash report is indicating that you have a client only mod in your mods folder, or one of your mods is poorly coded and won't work in SMP (even though it should).
-
You probably shouldn't be using Java 8 with a 1.6.4 pack. Try removing your existing Java and installing the latest Java 7 64bit JRE. See what happens after that.
-
If you open the version.json file from the modpack.jar in a code based text editor (i.e. Notepad++, Vim, etc.) you can see some existing parameters listed. Just add yours.
-
Try OptiFine and fiddle with the settings. Sometimes it helps, sometimes it doesn't. You can add startup parameters by editing the version.json file in your modpack.jar.
-
help me please with mcpc+ and voltz3.1.1
plowmanplow replied to jacky3362's topic in Server Op Swap Shop
Maps/minimaps are only used on the client. They are not intended for use on a server and would provide no functionality there. They are what are known as client only mods. Client only mods are things that don't change the world data, just how you see it. Things like Damage Indicators, Dynamic Lights, OptiFine, minimaps, player animations, blood, etc. -
I know I remember seeing discussion about how to get pages in loot tables before. However, the best place to get help with this would be in the Mystcraft forums or their IRC channel.
- 1 reply
-
- Mystcraft
- BetterDungeons
-
(and 2 more)
Tagged with:
-
@Fireles: Dude! Stop hijacking threads RIGHT below someone saying "don't hijack threads". Your problem is different. Start a new thread. Provide relevant information: logs, crash reports, pack links, etc.
- 19 replies
-
- custom modpack
- Minecraft
-
(and 1 more)
Tagged with:
-
help me please with mcpc+ and voltz3.1.1
plowmanplow replied to jacky3362's topic in Server Op Swap Shop
Dude, I thought you were talking about the client. JourneyMap is a client-ony mod. It doesn't belong on the server. -
Running: MCPC+ version git-MCPC-Plus-jenkins-MCPC-Plus-164-250 This version of MCPC+ is ancient and has a know issue. The project has a new name: Cauldron. Download the latest installer and install it to your server folder. http://files.minecraftforge.net/Cauldron/ Use the new JAR for your server.
-
Technic Launcher All Packs said "offline"
plowmanplow replied to King_Chromester's topic in Platform Pagoda
Don't start multiple threads for the same problem. Use the official support channels (the Tracker at the top of this page) for products maintained by Technic. -
This is what you are looking for: http://forums.technicpack.net/tracker/project-1-technic-launcher/
-
You need to post in the Tracker for the Launcher. There is a link at the top of the page.
-
Without a link to your pack page or API URL we would just be guessing. Guess is bad. The modpack.jar file is JUST the Forge universal binary JAR file renamed to modpack.jar. Don't mess with it, just rename it.
-
You haven't provided enough information to know for sure, so I'll guess. Are you running MCPC+? The MCPC+ project has a new name: Cauldron. Get the latest installer and install it to your server folder: http://files.minecraftforge.net/Cauldron/ . Switch to starting the cauldron JAR in your startup script and come back if you are still having troubles.
-
Error linking technicpack to solder installation
plowmanplow replied to ThisIsSparta's topic in Platform Pagoda
I wouldn't think that would matter -
You are using an ancient version of MCPC+. The project has a new name: Cauldron. Get the latest Cauldron installer and install it to your server folder. http://files.minecraftforge.net/Cauldron/