LexManos

Screen shots would be nice. You're not really describing it well. You could also try downloading the installer.jar and running it instead of the exe.

Forge logs everything to the logs file. Everything that you're describing just makes me think you simply didnt install the mod on the server. Just stick the jar in the mods folder and you should be good. if not, post your log file.

Stable are just version++s they dont coorolate to MCP versions. http://export.mcpbot.bspk.rs/

You should just be registerering your dusts as is... no reason to not have them.

You have a non-1.7.10 mod installed.

What EXACTLY did you download, show the exact url, screenshots help. Only download the installer from our download page: http://files.minecraftforge.net

THey arnt, as stated above you need to do so in the AttachCapabilityEvent.

The entire point of the capability system is that it is a soft reference. Unless you do some dirty reflection hacks specifically on that field to resolve the generic type. Then it wont crash. As for you faking the cap with your own code. Yes its possible, the JVM doesn't care who wrote the class as long as its structurally the same. However it is better to talk to the mod author to see if they WANT to allow others to access that cap/feature of their mod.

http://minecraft.gamepedia.com/Minecraft_launcher#Command_Line_usage

So you want to change a gui when its opened, we already have an event for that...

Actually flesh out your ideas beyond 'I think thing should go here!' Give reasons, examples of what you're trying to accomplish, let others try and help you achieve it in the way that we already have. In most cases you can do everything you want without any extra hooks anywhere. And if you CANT then people can discuss how best to go about the hooks. So, Moved to Modder Support NOT suggestions, you need to flesh things out.

It's not going to hapopen, there is literally no reason to have a 1.11.1 version. 1.11.2 is out and stable.

When you run the installer it creates a text file in the same directory as the installer. We need that text file. As for checking whats blocking your etwork, thats all based on your computer/firewalls/whatever... There really isn't a generic way to do it.

Then post your installer logs and make sure nothing is blocking your internet connections to our servers

Why are you installing .1? use .2

Post the log, its 99% the mods fault not Forge's.

If the two worlds have the same mapping, which the vanilla objects should all be the same no matter of the server. Then a scematic file without a mapping will work fine. As it sits tho, unless the file has a mappings table then you're gunna have issues if things change.

The fundamental flaw of schematic files is they hardcode IDs outside of the file itself so it relies on things simply being the same between setups. I advise moving to Mojang's official format here: http://minecraft.gamepedia.com/Structure_block_file_format

There ARE mods that do this, none of which will be supported or endorsed by Forge. Touching the Realms button moves to close to 'Lets remove Mojang's ability to make money!' Which is something we will never touch.

It has been reviewed and will not be adopted for the issues that it may cause. Stop being a twat, it is the official stance of this forum that ALL 'performance' enchancement mods such as FoamFix, Optifine, and the like are not supported as they tend to cause more issues then they fix.

Its practiced anywhere that a product is expected to run on more then windows. As almost every other system besides windows is case sensitive. It may not be forced in code, such as this case. But it is usually in the 'best practices' guide for naming things. Mojang has decided to enforce it because they previously had no defined standard for themselves and people on windows were getting pissed off that their resource packs worked fine on disc and not when zipped. It's the exact same thing that causes all other products to define the standard to use for file names. They get annoyed with people having issues because they don't follow what others would consider common sense. The choice between WHAT the standard was {lower case, upper case, camel case, snake case} was arbitrary. {Tho lower case is disproportionately used by the rest of the programming world, so it's no surprise they chose it}

If you put "CamelCase.txt" into a jar and unzip it it will be "CamelCase.txt" unless whatever tool you are using is screwing with the file name. As for who is trying to look for "fileone.png" That would be Minecraft:

https://en.wikipedia.org/wiki/Filename#Letter_case_preservation Yes if a developer intentionally makes the same file name in a different casing and expects users to know the difference then they are doing it wrong. All archive formats that I know {notably they are mostly based off zip and rar formats} are case sensitive. As they simple store a map of "file path" to address in the file. The point is jars CAN handle CamelCase. But "camelcase.txt" and "CamelCase.txt" are two distinct files and unless you specifically write a handler for it then there is no automatic translation of the names.

Note, it is a industry standard due in part to exactly what Matry said. And it was not FORGE who forced it in 1.11, Mojang did. We have always advised you follow the standard programming practice, its now just enforced by Mojang.