LexManos

Whatever method you are using to launch Minecraft is not adding the 16.0 guava files which Forge uses. What launcher are you using.

Run the installer manually as described in my signature and post the logs.

Or better yet, we do not support 1.6.4 anymore -.- 9 Months is long enough to update. If you do not, please read your log yourself and find your answers.

Yes, having Forge on the client is required to connect to a Forge server. It's something we are working on. But for the most part as mods add new content this will be a requirement.

No, you could just you know.. edit the run config yourself. We provide the default location that works for the bulk of people. This is nothing that stops you from completely customizing things yourself. We've even made it easier by introducing GradleStart which takes no arguments and builds all the correct arguments for you!

You had to be a dick in your message, protip DONT BE A FUCKING DICK WHEN ASKING FOR HELP. Especially when you don't follow the damn rule of ALWAYS provide your log. You're probably missing a mod or have a mod for the wrong version of minecraft your log file has full details. However, since you were rude in your messed I'm just gunna lock this.

One or more of your mods is not compatible with the dedicated server, you will have to find out which one.

That is indeed odd, from looking it up it looks like a issue with cisco routers and java.. So do you have a cisco router? You could always try manually grabbing the erroring library from maven central.

Well the issue is that one or more of your mods is sending a invalid packet, there isn't much we can do to diagnose except try to kill off mods till it stops happeneing. You should also update to 1.7.10, and encourage any of the mod authors that haven't already to do the same.

Update Forge/MC.

Provide the log from running the installer manually as described in my signature.

This is caused by your 1.7.10 jar being invalid, you should delete your versions folders and re-install 1.7.10 and Forge.

If one of you can provide me with your mod pack I can try and test things out tonight. This is interesting tho in your log: [10:53:11] [Client thread/TRACE] [FML/]: Recursing into package JavaVirtualMachines.1.6.0.jdk.Contents.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home. bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle. Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle.Home.bundle. Home.bundle.Resources.zh_TW.lproj Any idea where that is coming from and why it has 'Home.bundle' so many times?

This MIGHT be caused by a combination of your computer just being slow and the new Asynchronous chunk System. There should not be a noticeable 'lag' on modern computers, however, it's possible. To try it out, go install version 1122 and 1123 and try it out. As 1123 is the version that introduced this new system. If this is the case I may move to a system where it forces the chunks to pre-generate to a certain extent out before even showing you the world at all.. Beyond that we would need some actual Profiling information from your clients to try and track down this issue. Please look into a program called visualvm, it's part of the JDK. If you have it provide us with some data.

You have a tools mod installed of some kind that seems to be throwin a NPE on block break. You should find the author of that mod and ask them.

That is interesting.. I could understand if it threw a memory issue or timeout. But a connection reset would make me think you have some anti-virus or firewall that is killing the connection. What types of those programs do you have?

Your report is super helpful I will get on this RIGHT AWAY. Umm no, Skins work fine in all my testing and you've provided no logs to help diagnose the issue so I'm just gunna consider it fixed and move on.

Just as a note, we do not officiall support ANY base editing mod used in conjunction with Forge for these exact reasons we have no clue what they edit and have no way of telling what is going on in your environment because of it. However, the error states net.minecraft.client.renderer.StitcherException: Unable to fit: quartz_ore - size: 144x144 - Maybe try a lowerresolution resourcepack? The 144x144 is odd considering it's a 128x texture pack. Perhaps optifine is making the file not read correctly. Confirm that it is that size, and that its being read correctly. Also be careful, using high resolution texture packs combined with mods can easily blow away your max texture size which your gfx card supports. Which would result in an error such as this. The more items you stitch together the more space it takes up, and space is limited, get me?

Try running the installer from the command line as specified int he video in my wsignature. Also add a the -Xmx2G argument to the command line.

This has been fixed in 1180, try again.

Its not a file, its part of your launcher, edit profile.

Forge Version: 1.7.10-10.13.0.1180 Minecraft Version: 1.7.10 Downloads: Changelog (Direct) Windows Installer (Adfly) (Direct) Other Installer (Adfly) (Direct) Javadoc (Adfly) (Direct) Source (Adfly) (Direct) Universal (Adfly) (Direct) Alright time for another Recomended build/release. This time for Minecraft 1.7.10, we've had these builds out for quite some time and people have been testing it reigourusly. There is good news, MOST 1.7.2 mods should work JUST fine on 1.7.10 due to the inner workings of minecraft changing little in areas modders use, and our runtime deobfusction providing a stable target. However this does not GUARANTEE your mods will work, so give it a try if they do not, then you need to wait for the mod author to update. Modders, it appears that 1.7.2 mods will work with 1.7.10 {barring any Mojang derps} with a few caveots that you should take into accout now! AABBPool is gone, use static function in AxisAlignedBB Vec3Pool is gone, use normal Vec3s. And a few others. Minecraft Forge 10.13.0 Changelog: ============================================================================ Updated to Minecraft 1.7.10. New: FML now sets a security manager (FINALLY!). It's primary purpose at this point is to catch rogue calls to System.exit so that they can cause a proper crash report, rather than silently abandoning the game. New event for when players are loaded/saved to disk, allowing modders to add and manage extra player information. Add support for mod access transformers without a coremod requirement. Use the "FMLAT" manifest attribute, with a space separate list of files that live in the 'META-INF' directory. They should conform to standard AT formatting. New GUI system for modders, allowing them to create in-game config screen. Thanks bspkrs, http://minalien.com/minecraft-forge-feature-spotlight-config-guis/ for more info. API is now able to "provide" and "own" itself. Useful for libraries without a Mod in them. To go along with this, you can now require an API, with a version, in your mod dependency string Add config option to specify the default spawn fuzz factor for the overworld. New RenderItemInFrameEvent fired when, well, a ItemFrame renders an Item. Added FluidStack sensitive version for Fluid's localised name Updated scala libraries to 2.11 New AchivementEvent fired when a player receives an achivement. Added World to ChunkProviderEvent.ReplaceBiomeBlocks, and exposed metadata to End and Nether generation events. Enhanced the Biome Dictionary with tags based on temperature, vegetation, moisture, trees and others Added ability for modders to create there own BiomeDictionary Types. New RenderBlockOverlay event fired when the client renders any 'overlay' on the HUD, such as Fire, In Water, or Suffocating in a solid block. Added new system flag to disable Forge's Stincil bits in the display, -Dforge.forceNoStencil=true, Use this if you have graphics issues on the main menu. Caused by lwjgl issues and old graphics cards. Update realms library to 1.3.1, and implement network latch when connecting to Realms. Tested and working. New GradleStart and GradleStartServer classes for developers, takes no required arguments and will find everything for you. can also specify a --username and --password to be logged in to your account at dev time for remote server testing. Bug Fix: Added missing onLivingJump calls Fixed vines generation for hanging off of trees. Added sanity check to prevent ArrayIndexOutOfBoundsException in getOreName for negative ids. Added missing 1.7 biomes to BiomeDictionary Fixed a server crash caused by a player joining that is in a non existent dimension Fixed NPE caused by modders passing around an invalid ItemStack. Fixed flower pots not droping the items that are inside them. Added Configuration.load() exception handling and logging Fixed compounding quotes issue with category names that require quotes when save is called more than once Fixed creative inventory tabs not blending base don items rendered. Fixed issue where Fire's 'fizz' would not play for the person who extinguished the fire. Fixed more issues where certian Items would messup the GL context and cause other things to render oddly after them. Fixed EmeraldOre not respecting isReplaceableOreGen Fixed Enchantment.addToBookList Force preferIPv4Stack to true early in the load chain to combat netty loopback issues. Major New Feature: Asynchronous Chunk Loading:[/n] Bspkr's GUI System: A new GUI system created by bspkrs and cpw to allow modders to create in-game configuration guis. http://minalien.com/minecraft-forge-feature-spotlight-config-guis/ Note on Realms: Forge DOES connect and play on Realms servers just fine. However, Mojang likes to push out many new versions of there Realms library, they have the ability to update there json files remotely, we do not. As such if they update the required realms library version, you either have to wait until Forge updates, or manually edit your json file. We are working on a simple method to automate this process, however, for the time being this is what we have. Updating your json is really simple, go to your .minecraft/versions/1.7.10.json Look for com.mojang:realms: There will be a version number after that. Go to .minecraft/versions/1.7.19-Forge{ForgeVersion}.json Find the same com.mojang:realms line, and update the version number to match the one in 1.7.10. ONLY do this is you are having issues connecting to Realms! As stated we are trying to find a more generic automatic solution. But mojang's launcher does not support the features we need in order for it to be possible.

Yes, it's a command line argument, you just need to pass in a correctly formatted uuid and it'll use it.

There is a 'Developer Console' in the mojang launcher, that is the log, give it to us.

You need to specify a uuid, or login for it to grab yours for you. You CAN NOT connect to remote servers without it.