LexManos

Post the launcher log, it's in the 'Launcher Log' tab in the Launcher.

Don't bring me into stuff like this, Don't use ant unless you know exactly what you're doing. FG was built for a reason and it's dead simple to use. USE IT!.

The 1.9 update should be nothing like the 1.8 update. It should be a lot simpler of a jump. We're getting close to doing a 1.8.8 release, we've fixed 99.99% of all fernflower issues and it now decompiles the new minecraft code like a champ {There is still one known variance that I need to fix but that'll be done soon} As for people updating to 1.8, its slow going mainly because of the inital nay-sayers who went on evangelical rampages about how bad 1.8 was without actually looking at it or applying some logical thought. Sadly, what influential people say on the internet has a large impact on things. But now people are moving forward, and hopefully when people see the new sexy code that 1.8.8 produces with all our fixes to fernflower and changes mojang has done to help us. They will be enticed to go for it. So, what I would say to you about starting a new mod. Start on 1.8, the 1.8.8 bump will be a big shift but not a BAD shift. The fundamental things will stay the same, but you may need to change a few function names and add generic arguments to your code. For any competent programmer this should be a breeze. As for 1.9, yes there are changes, however most of them are isolated to one feature here and there. And from a modders point of view rather small. So I don't see it being a issue.

Don't be a dick wolf.

When in doubt post everything. The launcher has a console log which shows everything. The logs folder has many logs that show different details of everything. If that is your latest log then it means you either have a mod installed that is breaking the GL stack, or your graphics card cant handle the loading screen, so try disabling that. And before you ask the steps to disable it are in the EAQs -.-

THERE ARE ALWAYS LOGS The launcher displays them int eh console and they are logged to file in the logs folder. NEVER assume that shit happens to other people ALWAYS include a log and FULL details of what you're doing. And I don't care if you're a guy or a girl, we have the rule requiring logs for a reason. -.-

Thread locked cuz this is just dumb -.- Go to the eaq, Linked at the top of the support forums. READ IT, or search for 'loading screen' READ WHAT IT SAYS! The EAQ is designed to make these dumb questions simple. Not to have them go around in circles.

Something is preventing you from connecting to our downloads servers. If you can't figure it out then go download the required libraries manually and put them into the proper folders in your .minecraft/libraries directory. You can search for all the libraries at http://search.maven.org/

And this kids, is how NOT to ask for support -.- Just tested on 1.8.0_65 {The 'oct 20 java update', seriuously be fucking specific} Everything works just fine, and this guy comes in with no logs so we have no freakin idea what he's talking about...

Start off in a fresh world to see if it happens without any mod machines. I'd also say start trying to reproduce it without some of the mods. First mods i would chuck is optifine and any that are listed as coremods in the logs.

No we do not have a system to automatically remap between two mapping versions for forge dev. So no you'd have to do it manually, However the MDK has nothing to do with Forge-Dev itself. Unless you are going to make a PR for Forge, you shouldn't use the Forge-Dev workspace. And a side note, for Forge-Dev you never use 'stable' you MUST use 'nodoc' as we need to NOT have the javadoc comments.

What the hell did you even say? If I deciphered that correctly you're saying that you want to update the Forge-Dev version of MCP snapshots. Why, Who fucking knows.... But no, updating is not that simple you'd have to go in to the MC code and fix all the references to changed mappings. The MDK is special because it ships SRG named Forge classes/patches. Which will apply against any MCP mapping you want. If you want to update your mappings in your MDK instance you can thats what it's designed for.

Feel free to make the tutorials yourself and submit them to our repo. https://github.com/MinecraftForge/Documentation http://mcforge.readthedocs.org/en/latest/ There is already quite a bit of documentation there about 1.8. Beyond that I've stated MANY MANY MANY TIMES That I suck at writing documentation and it's up to other people to do it. MY Time is better spent actually working on the code and related projects to continue moving Forge forward. And what you described is basic debugging, its part of being a programmer, deal with it. How about quit bitching, and help the community yourself by sharing what YOU learn.

Delete the scala compiler jar from your libraries folder, it's corrupt, the installer will re-dowload and install it again.

'Is it something added by Forge.. I wonder where I could figure that out, maybe the public repository where it lists all the patches at Forge applies...' Make a PR.

Post a screenshot of what you mean by 'Session lost' there is no 'Session lost' in your logs. Also, you ARE using DIFFERENT accounts on both computers correct...

There is a mod out there called Cubic chunks, which tries to add more height to the world. However, this is not supported by forge and causes major issues with mods and saves because its a fundamental change to the world format/game format. This is not 'simple' and not something that we'd support.

That would be whenever Mojang releases 1.9.

We don't typically fix bugs in vanilla minecraft that arnt actually real bugs. And ya.. I should make a RB here soon. Haven't been caring to as we've been working on getting ready for 1.8.9

Nothing stands out, except for the fact that you have a crapload of mods/worlds installed. Your best bet is to find a way to constantly reproduce and then start nuking mods until it stops.

Logs, also try removing fastcraft if its in.

9 times out of 10 the issue is that you renamed the texture file, To fix a casing issue. You may of first created it with the name "Steelingot.png" and 1/2 a second later changed it to "SteelIngot.png" What you need to do is do a full clean in your project. It should wipe out the mis-capitolized name in your bin directory.

The ENTIRE freakin point is that mods don't manage their own tickets and that allows for a standard way of REQUESTING chunks be loaded. They key point is REQUESTING they be loaded, as the end user {usually the server admin} can determine to allow things or not. This is a major feature for server admins and trying to work around it is bad and will not be supported here.

Mods have to opt-in for this feature its up to the mods. Most of them dont. So you have to remove the mods.

In the launcher -> Edit Profile -> Version -> Forge {Whatever version you installed} If you're running and not seeing the Forge branding on the main menu, then you didn't run forge.