ForgePatch

History

LexManos e79b5d1937 The install scripts will now only patch the client/server if they are there. This allows for people to only worry about getting one side setup correctly if they don't care about the other.		2011-12-11 07:37:54 +00:00
..
install.cmd	The install scripts will now only patch the client/server if they are there.	2011-12-11 07:37:54 +00:00
install.sh	The install scripts will now only patch the client/server if they are there.	2011-12-11 07:37:54 +00:00
README.txt	Fixed a infinite recursion loop in spacetoad's commit to Block.java.patch	2011-12-11 07:04:21 +00:00

README.txt

*** HOW TO INSTALL ***

Extract the download archive directly into your MCP-directiory.
It should create a folder "forge" within that directory, containing all 
extracted files.

You should use freshly downloaded jars, solely including ModLoader & 
ModLoaderMP. Anything else can eventually cause conflicts.

Now just start the install.cmd/.sh, MCForge will install itself into the proper
locations and copy all needed files, as well as modifying the needed baseclasses.

Forge also includes a snapshot of the MCP mapings, this may not be the current 
version of the mapings. But you must use the provided mapings in order for the 
patch files to work together.

The install scripts should take care of everything for you, so you should not need
to run ANY MCP script before installing forge.