plowmanplow

Then that is a server owner not properly controlling access to items that bypass protections. Permitting access by players to items that bypass protections defeats the whole purpose of putting the mechanisms in place to begin with. Raiding is working within the mechanisms/plugins provided to overcome someone's defenses. Griefing is exploiting some game mechanic or using an item which bypasses a protections mechanism to harass other players and should never be permitted or condoned.

Mekanism, directly from the author's site, recommended version for 1.6.4: http://aidancbrady.com/mekanism/download/ Galacticraft, directly from the author's build service, built for 1.6.4: http://ci.micdoodle8.com/job/Galacticraft/ TConstruct, directly from the MinecraftForum thread created by the author for 1.6.4: http://www.minecraftforum.net/topic/1659892-164tinkers-construct/ And no, you are going to need to go through your pack to make sure you have the correct/updated/compatible/stable versions. If I went through the whole thing and gave you links directly to every mod after auditing every mod you have in the pack I might as well build it myself. You are doing fine, just keep going and you'll get there.

So, when you say that "I can't find any ID conflicts", how are you actually checking that? If you open up your most recent ForgeModLoader client log and search for the word "CONFLICT" (without quotes) you get no matches? Because I find quite a few.

All the versions I quoted are specifically for Forge/MC 1.6.4.

Alright. I'll need to pack/link to continue.

Your Mekanism = 5.5.7.291, Current Mekanism = 6.0.4.43 Your Galacticraft = 2.0.2.814, Current Galacticraft = 2.0.12.1050 Your TConstruct = 1.5.4d4, Current TConstruct = 1.5.5.7 The list goes on.

It might be good to make a note that the pack is FREAKING ENORMOUS and that the majority of people will either have a poor play experience or not be able to play at all. A PC with only 4G of ram is really going to struggle with the pack.

There is a SUB-forum to this one which Manus was referring to called Platform Potluck. You have a number of old mods included with known problems which should be updated. Additionally, there are a number of ID conflicts (specifically with Mystcraft) which will cause major problems if not resolved.

Your modpack.jar is named "modpack.jar.jar". Turn on the Explorer option to always show file extensions to prevent this mistake (Google is your friend). You need to updated a number of mods (see my previous post on this).

Your public IP can be found here: http://www.whatsmyip.org/ You will need to open and redirect a port in your router/firewall (typically 25565) in order to allow remote people to connect. The specifics of this are far beyond the scope of these forums. Google is your friend.

Re-read my first sentence. It specifically says to find the current key binding tied to the "H" key and change it to "Y". If you don't see the ID conflicts then you aren't looking in the ForgeModLoader client log. It is riddled with them.

Have you downloaded the OpenMods versions specifically for CC 1.63?

Your most recently posted crash report shows that you are using some absolutely ancient versions of mods with known serious problems (such as Galacticraft and Mekanism). Without updating your mods to working/compatible versions it will be difficult to help you. Without a link to your modpack page or download it will be even more difficult to help.

You "bin" folder should contain one file and that being "modpack.jar" which is simply the correct version of Forge renamed to modpack.jar.

Actually, the first post originally contained a lot of misinformation and anecdotal testaments concerning the awesomeness of Windows and how bad Linux was for hosting. The OP has since removed the content of the post and replaced it with the current "contact me on Skype" message... which no one in their right mind would ever do.

I assume you have changed/fixed something because I am able to add your pack to my launcher and it starts. Also, you have a large number of item ID conflicts.

You are supposed to leave that setting blank. If you are running the server on the same machine as the client then you need to connect to "localhost" (without quotes).

Your problem with Hats is just a control/key definition conflict. Open your control settings and change the current binding for "H" (team settings I think) to "Y" and Hats will work just fine on the "H" key. That being said, you have a MASSIVE number of ID conflicts which will render many aspects of gameplay and development unusable. In addition to that you have many outdated mods and mods with known fatal conflicts (Mekanism 5.6 and IC2).

Ubuntu one seems to be having trouble at the moment. You might try dropping it on another host so we can look at it.

“That which can be asserted without evidence, can be dismissed without evidence.” ― Christopher Hitchens

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.

After making a very large tech modpack for Forge/MC 1.6.4 I decided to trim things down and essentially "upgrade" the mod collection that makes up Tekkit Lite to 1.6.4. This is my attempt at doing so. The full mod list is available on the mod list tab, but almost all the mods either had direct updates or spiritual successors which have been included in this pack. The only notable changes: Added Natura: because vanilla nether is a stack of suck at this point. Added Extra Cells: because TekkitLite has always lacked good liquid storage and management and this integrates smoothly. Added Chisel & Carpenter's: For some fancy buildings. Very light on resources. Technic Pack: http://www.technicpack.net/modpack/details/jclite.349189 Server files: https://copy.com/AzRK28osVaHs?download=1

Precisely. If you would be so kind as to provide Technic pack page links we might be able to get somewhere.

This is what happens with you dont: Include a full working set of config files in your published modpack. Use the working config files from the client pack in your server configuration.

You have included an incompatible version of IndustrialCraft in your pack. If you intend to include IC2 I would highly recommend checking out this post: You have included Immibis Microblocks but not the required dependency Immibis Core. You have a number of fatal block ID conflicts between a few mods. You have many item ID conflicts, some of which are with Flan's packs which require you to edit files inside the respective zip files. You have not included any config files in your modpack. Without config files your pack will be unusable since there are fatal ID conflicts in the config files which are generated by default. Always include a full working set of config files in the config folder for your modpack.