Texturepacker
You can use texture packs to change the appearance of the terrain and items in Minecraft. Using this program you can make your own pack (you will still need a graphics editor to create the PNG files). You can also write recipes to remix existing texture packs.
Recipes can saved on disk as text files in YAML or JSON format for use with the
maketexture command, or can be created in Python code as objects to feed in to
an instance of texturepacker.Mixer in your own programs.
Texturepacker also powers Texturejam, a web application that one day allow users to remix texture packs, but for now allows you to download the results of some canned recipes.
Installation
Requires Python 2.7
and several Python modules (the complete list is in
the file REQUIREMENTS).
You should be able to install it using Pip with the following command:
pip install texturepackerIf all goes well it will automatically download the required modules and install them as well as Texturepacker itself.
If you like you can download the source code from the Texturepacker page on the Python Package Index and do:
python setup.py install
If all goes well, this will download and install
any missing dependencies, as well as installing the
texturepacker module and maketexture command.
The source package is larger (1 MB rather than 42K) because it includes example texture files and recipes. So you can build the groovyStipple package like so:
maketexture -v examples/groovystipple.tprx
This will create a file groovystipple.zip
that you can drop in to Minecraft’s texturepacks folder.
Development
Visit the Texturepacker project on GitHub to browse the source. There is a Texturepacker wiki, which may eventually have useful developer documentation on it. If you want to modify the code, you can also clone the project with Git by running:
git clone git://github.com/pdc/texturepacker
Then (preferably in a virtual environment created with virtualenv), install the dependencies:
pip install -r REQUIREMENTSYou can then run unit tests using Nose:
nosetests testsThe task backlog is in the wiki for now.
