Removed email address.

.gitattributes

@@ -0,0 +1,26 @@
+# default
+* text eol=auto
+
+# git
+.gitattributes text eol=lf
+.gitignore text eol=lf
+
+# sources
+*.java text eol=lf
+
+# resources
+*.lang text eol=lf
+*.cfg text eol=lf
+*.info text eol=lf
+*.mcmeta text eol=lf
+*.md text eol=lf
+*.xml text eol=lf
+
+# scripts
+*.bat text eol=crlf
+*.gradle text eol=lf
+*.properties text eol=lf
+
+# binaries
+*.png binary
+*.jar binary

.gitignore

@@ -11,8 +11,11 @@
 /.classpath
 /.project
 /bin
+*.launch
 
 ## intellij
 /out
 /.idea
 /*.iml
+/*.ipr
+/*.iws

CONTRIBUTING.md

@@ -0,0 +1,44 @@
+## Contributing
+### Submitting a Pull Request (PR)
+So you found a bug in the code? Think you can make it more efficient? Want to help in general? Great!
+
+1. If you haven't already, create a [GitHub account](https://github.com/signup/free).
+2. Click the `Fork` icon located at the top-right of this page (below your username).
+3. Make the changes that you want to and commit them.
+    * If you're making changes locally, you'll have to do `git add -A`, `git commit` and `git push` in your command line.
+4. Click `Pull Request` at the right-hand side of the gray bar directly below your fork's name.
+5. Click `Click to create a pull request for this comparison`, enter your pull request title, and create a detailed description explaining what you changed.
+6. Click `Send pull request`, and wait for feedback!
+
+#### Instructions/Advice when submitting a Pull Request (PR)
+I use [this](https://gist.github.com/460be5119b93d73c24ab) IDEA formatting. To be short:
+
+* spaces for indentation
+* braces on same lines
+
+When you finish up your PR you'll want to [squash](http://davidwalsh.name/squash-commits-git) them into a single commit (unless it makes sense to have them split).
+
+1. Make sure your working directory is clean by executing `git status`.
+2. Execute `git rebase -i HEAD~X` where `X` is the amount of your commits. This will make sure you squash only your own commits.
+3. You should now see a list of all your commits, prefixed with `pick`. Change all instances of `pick` (excluding the first!) into `squash` or simply `s`. Then save/quit the editor once.
+4. A second screen should show up, displaying all the commit messages (you may edit them, delete or add some). After your done save/quit the editor again.
+5. If git successfully rebased things simply push your cleaned up commits by executing `git push -f`.
+
+#### Localization
+You should always use `en_US.lang` as the base for localization to other languages. To modify the files you have two options:
+
+* Create or modify the file directly with your favorite text editor (make sure encoding is set to `UTF-8`!).
+* Use [this](http://mc.lunatri.us/translate) website to load the base file (and optionally the target language if you're updating localizations).
+_Note: you **must** use the link to the `Raw` file._
+
+### Creating an Issue
+Crashing? Have a suggestion? Found a bug? Create an issue now!
+
+1. Make sure your issue hasn't already been answered or fixed. Also think about whether your issue is a valid one before submitting it.
+2. Click `New Issue` right below `Star` and `Fork`.
+3. Enter your issue title (something that summarizes your issue), and then add a detailed description ("Hey, could you add/change stuff?" or "Hey, found an exploit: stuff").
+    * If you are reporting a bug, make sure you include the following:
+        * The log file `fml-client-latest.log` (or `fml-server-latest.log`) uploaded to [gist](https://gist.github.com/).
+        * Detailed description of the bug.
+            * Include steps on how to reproduce the bug (if possible).
+4. Click `Submit new issue`, and wait for feedback!

LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2014-2016 Jadran "Lunatrius" Kotnik
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

LICENSE-EXCLUSIONS

@@ -0,0 +1,9 @@
+##############################################################################
+
+logo.png (commit: 8867629) (c) by razarosu (MCF)
+
+logo.png (commit: 8867629) is licensed under a
+Creative Commons Attribution-NoDerivatives 4.0 International License.
+
+You should have received a copy of the license along with this
+work. If not, see <http://creativecommons.org/licenses/by-nd/4.0/>.

README.md

@@ -1,13 +1,7 @@
 ## Welcome to Schematica!
-[Compiling Schematica](#compile-schematica) - for those that want the latest unreleased features
-
-[Contributing](#contributing) - for those that want to help out
-
 ### Compiling
 [Setup Java](#setup-java)
 
-[Setup Gradle](#setup-gradle)
-
 [Setup Git](#setup-git)
 
 [Setup Schematica](#setup-schematica)
@@ -37,28 +31,6 @@ The Java JDK is used to compile Schematica.
         7. Append `;%JAVA_HOME%\bin` EXACTLY AS SHOWN and click `Ok`. Make sure the location is correct; double-check just to make sure.
 3. Open up your command line and run `javac`. If it spews out a bunch of possible options and the usage, then you're good to go. If not try the steps again.
 
-#### Setup Gradle
-***
-You may skip this entire section and use the provided Gradle wrapper instead (use `gradlew` instead of `gradle`).
-***
-Gradle is used to execute the various build tasks when compiling Schematica.
-
-1. Download and install Gradle.
-    * [Windows/Mac download link](http://www.gradle.org/downloads). You only need the binaries, but choose whatever flavor you want.
-        * Unzip the package and put it wherever you want, eg `C:\Gradle`.
-    * Linux: Installation methods for certain popular flavors of Linux are listed below. If your distribution is not listed, follow the instructions specific to your package manager or install it manually [here](http://www.gradle.org/downloads).
-        * Gentoo: `emerge dev-java/gradle-bin`
-        * Archlinux: You'll have to install it from the [AUR](https://aur.archlinux.org/packages/gradle).
-        * Ubuntu/Debian: `apt-get install gradle`
-        * Fedora: Install Gradle manually from its website (see above), as Fedora ships a "broken" version of Gradle. Use `yum install gradle` only if you know what you're doing.
-2. Set up the environment.
-    * Windows: Set environment variables for Gradle.
-        1. Go back to `Environment Variables` and then create a new system variable.
-        2. For `Variable Name`, input `GRADLE_HOME`.
-        3. For `Variable Value`, input something similar to `C:\Gradle-1.10` exactly as shown (or wherever your Gradle installation is), and click `Ok`.
-        4. Scroll down to `Path` again, and append `;%GRADLE_HOME%\bin` EXACTLY AS SHOWN and click `Ok`. Once again, double-check the location.
-3. Open up your command line and run `gradle`. If it says "Welcome to Gradle [version].", then you're good to go. If not try the steps again.
-
 #### Setup Git
 Git is used to clone Schematica and update your local copy.
 
@@ -80,9 +52,9 @@ This section assumes that you're using the command-line version of Git.
 ***
 
 #### Compile Schematica
-1. Execute `gradle setupDevWorkspace`. This sets up Forge and downloads the necessary libraries to build Schematica. This might take some time, be patient.
-    * You will generally only have to do this once until the Forge version in `build.properties` changes.
-2. Execute `gradle build`. If you did everything right, `BUILD SUCCESSFUL` will be displayed after it finishes. This should be relatively quick.
+1. Execute `gradlew setupDevWorkspace`. This sets up Forge and downloads the necessary libraries to build Schematica. This might take some time, be patient.
+    * You will generally only have to do this once until the Forge version in `gradle.properties` changes.
+2. Execute `gradlew build`. If you did everything right, `BUILD SUCCESSFUL` will be displayed after it finishes. This should be relatively quick.
     * If you see `BUILD FAILED`, check the error output (it should be right around `BUILD FAILED`), fix everything (if possible), and try again.
 3. Go to `mcdev\Schematica\build\libs`.
     * You should see a `.jar` file named `Schematica-#.#.#-#.#.#.#-universal.jar`.
@@ -97,43 +69,4 @@ In order to get the most up-to-date builds, you'll have to periodically update y
     * If you have, try reverting them to the status that they were when you last updated your repository.
 4. Execute `git pull master`. This pulls all commits from the official repository that do not yet exist on your local repository and updates it.
 
-### Contributing
-#### Submitting a Pull Request (PR)
-So you found a bug in the code? Think you can make it more efficient? Want to help in general? Great!
-
-1. If you haven't already, create a [GitHub account](https://github.com/signup/free).
-2. Click the `Fork` icon located at the top-right of this page (below your username).
-3. Make the changes that you want to and commit them.
-    * If you're making changes locally, you'll have to do `git add -A`, `git commit` and `git push` in your command line.
-4. Click `Pull Request` at the right-hand side of the gray bar directly below your fork's name.
-5. Click `Click to create a pull request for this comparison`, enter your pull request title, and create a detailed description explaining what you changed.
-6. Click `Send pull request`, and wait for feedback!
-
-##### Instructions/Advice when submitting a Pull Request (PR)
-I use [this](https://gist.github.com/460be5119b93d73c24ab) IDEA formatting. To be short:
-
-* tabs for indentation
-* braces on same lines
-
-When you finish up your PR you'll want to [squash](http://davidwalsh.name/squash-commits-git) them into a single commit (unless it makes sense to have them split).
-
-1. Make sure your working directory is clean by executing `git status`.
-2. Execute `git rebase -i HEAD~X` where `X` is the amount of your commits. This will make sure you squash only your own commits.
-3. You should now see a list of all your commits, prefixed with `pick`. Change all instances of `pick` (excluding the first!) into `squash` or simply `s`. Then save/quit the editor once.
-4. A second screen should show up, displaying all the commit messages (you may edit them, delete or add some). After your done save/quit the editor again.
-5. If git successfuly rebased things simply push your cleaned up commits by executing `git push -f`.
-
-#### Creating an Issue
-Crashing? Have a suggestion? Found a bug? Create an issue now!
-
-1. Make sure your issue hasn't already been answered or fixed. Also think about whether your issue is a valid one before submitting it.
-2. Go to the issues page.
-3. Click `New Issue` right below `Star` and `Fork`.
-4. Enter your issue title (something that summarizes your issue), and then add a detailed description ("Hey, could you add/change xxx?" or "Hey, found an exploit: stuff").
-    * If you are reporting a bug, make sure you include the following:
-        * Version (can be found in the mcmod.info file or in the mod list)
-        * ForgeModLoader log (please use [gists](https://gist.github.com/) for large amounts of text!)
-        * Detailed description of the bug
-5. Click `Submit new issue`, and wait for feedback!
-
 Shamelessly based this README off [pahimar's version](https://github.com/pahimar/Equivalent-Exchange-3).