As it stands, people need to download MCP first, and then install Forge inside the MCP directory. I propose letting Forge install MCP for you, for the following reasons:

• It brings us in line with the "new" way of Forge installation
• There is one less step/place for human error
• Forge doesn't end up destroying your directory structure and install MCP twice (mcp\forge\mcp)

If you support the change, pahimar, I'll submit the PR I have ready already 😉
If not, I understand.

Time to ask for another change:
MinecraftForge/FML#263 (comment) (I'm thinking that this should be middle-term integration, not short-term)

It DOES. Forge automatically installs mcp. There's no need for it to be like buildcraft and one click compile it.

Take a close look at the build.xml or the README please. We need to "install" MCP first, then plop Forge inside it, then install Forge.

It DOES. Forge automatically installs mcp. There's no need for it to be like buildcraft and one click compile it.

^Correct.

how about just moving over to GMCP it would make it a lot simpler :P

• gradle wrapper FTW

... That was supposed to be a +

See #400 (comment) :>

? it is this issue ...

nop you can just install forge it Will install MCP for you .... I guess the README needs to be updated with that

nop you can just install forge it Will install MCP for you .... I guess the README needs to be updated with that

Look at the build.xml. The directory path is mcp\forge. Which either means that you install MCP first, or you give Forge some arguments, which is pretty "advanced".

ok so the build.xml also needs to get changed

Click it. Github doesn't parse comments correctly.