Minecraft Forums

Quote from 500 Internal Server Error

Items support is still OK: see https://raw.github.c...eebl_newitem.js

        ModPE.setItem(392, "stick", 0, "Wand");

Quote from srmalloy

From a casual examination of the .meta files, it appears that there are two routes you can go with creating new texture sets. Each "uv" property in the file has a data set with six parameters: [A, B, C, D, E, F]. The last two, E and F, are always the dimensions of the referenced file, so for a 16x terrain set, this would be '512, 256' if you were replicating the standard layout. A and B are the horizontal and vertical offsets from the upper-left corner of the image for the upper-left corner of the texture, expressed as a decimal fraction of the image, and C and D are the horizontal and vertical offsets from the upper-left corner of the image for the lower-right corner of the texture. Some block labels have multiple blocks under the one general category -- 'sandstone', for example, has five different individual textures -- and these have the 'additonal_textures' property populated with the coordinate set for each additional block in the group; 'sandstone', for example, has the initial texture, and the 'additonal_textures' property has the other four, separated by commas.

The first is to keep the layout of the items and terrain files the same as in the default files; in this case, you only need to fiddle with the .meta files if you're making a larger texture set (i.e., 32x textures would require a 1024x512 'terrain-atlas.tga' file, and you would change the string '512,256' everywhere it occurs in the terrain.meta file to '1024,512'.

I did it and it didn't work: 2048,1024 for 64x and used the same .meta files for a 16x TP and it didn't work either...

The second -- and without testing my theory, I don't know whether this will work -- is to convert the terrain.png file from a pre-0.8.0 texture pack to a Targa .tga file, and then go through the terrain.meta file and change all of the 'uv' coordinates to map where that particular texture appears in the file. So, for example, using a 1024x1024 terrain.png file as the source, the 'uv' coordinates for the diamond ore texture would be changed from '[0.125,0.125,0.1562,0.1875,512,256]' to '[0.1563,0.1875,0.1875,0.2188,1024,1024]' to point at the position of the diamond ore texture in its position as the third texture in the fourth row of the terrain.tga file. This is very tedious; whether it's more tedious than copying textures, one by one, into their correct places in the new layout will have to be up to the individual texture pack creator. However, once this mapping to the old terrain.png layout is done, the resulting terrain.meta file could be used for any terrain file using the old format.

The problem is that in the old TPs there are no more space for new blocks i.e. quartz blocks were placed over jungle wood and redstone lamps and so...

One of the things that I won't know until I part my own texture pack to the new format -- but which appears to fall out of the use of the .meta files is that it appears to allow for one texture to overlap, and possibly to have different sizes -- with a 16x texture pack, to have one or more textures defined in the .meta file as being, say, double the standard width and height. One of the cautions with either route is that, for textures with multiple textures -- the different sandstones, for example -- the order of the textures is inherent; for example, in the items image file, all of the tool/weapon items appear in the same order -- wood, stone, iron, gold, and diamond for each implement. If you get the 'additonal_textures' sets out of order, you'll get the wrong appearance for a tool. The advantage of the new system is that a new texture can simply be dropped into the appropriate file and the .meta filed edited to set the values that MCPE will use to locate the texture on the image.

Quote from Reddigirl

For all people which want to make a texture pack for 0.8.0 for android:
It's really difficult to make texture packs now. The 0.8.0 uses absoluetly new files, so that no 0.7.x Texture Pack is compatible.
For all those people:
There are 5 new folders in the assets:

First, the app folder.
In this folder you can only find icons and pictures for iOS, I don't know why this is there, but this folder isn't nesassary for porting a texture pack.

Then, the fonts folder. This only contains the minecraft.ttf, so it isn't nesassary until you don't want to change the fonts

And now, the most nesassary folder: The images-folder.
If you look in this, you can see this:

First, we beginn here with the armor-/art-folder. In this folder, there is no change, you can copy the data from 0.7.x

Second, there is the entity-folder. In this folder, you can find the "skin" of the minecart (minecart.png). You could change it, but I myself like the official minecart.

Third, there is the environment-folder. This contains the sun, the clouds and the moon texture.

Fourth, there is the font-folder. There is also no change, you can copy the data from 0.7.x.

Fifth, there is the gui-folder. There are some new files:
~cursor.png (Don't know what this file does :D)
~pititle.png (Isn't nesassary until you don't want to make the texture also for mcpi)
~the logo-folder, contains something with raknet (Why is this in a game like minecraft pe?)
With exception of these new files, there aren't any changes, coping from 0.7.x is easy.

Sixth, there is the item folder, you can copy this from 0.7.x

Seventh, the mob folder with all skins. Here is are new skins added, but the other skins you could add from 0.7.x. The new skins are:


This are only new skins for colored sheeps. But you need to port it.

Eighth, the first really important new files: compass.png and fireatlas.png
compass.png: The name says everything. This is the texture for compass.
fireatlas.png: This file is the texture of fire and the texture when a mob burns.

Ninth, the items.meta: Really important file, as there is all about how the item has to look like and other stuff. This is not a picture, this is a text. Open it with any text editor.

The tenth: The new items.png. Now this is named "items-opaque.png". You need to made it from the ground up new. There is a new order (I thing the old order is really better :D), you can see it at the end of the page, where I will post the /assets-folder (THIS IS LEGAL BECAUSE FROM THIS YOU COULDN'T MADE THE APK AS YOU NEED TO HAVE ALL THE OTHER FILES FROM THE APK :P).

The eleventh: participes.png. This file is not changed, you could copy it from your old (0.7.x) texture pack.

The twelfth: terrain.meta. The same as item.meta, but now for all blocks.

The thirteenth, the most important file(s) of the texture pack: The new terrain.png. I think that Mojang wants to make the porting of texture packs as difficult as possible. Now, there are 5 (!) new new files that are responable for the texture in 5 resolutions. Also, the game now uses .tga-files, a very exotic file format, don't understand why they don't use .png any longer. And, if you could open the file, you will see that all blocks are in new order. It is really difficult now to add a new block texture, which is the main part of every texture pack.

The fourteenth and last file in the folder: The "watch-atlas.png". This is the texture of the clock or watch.

You see, the folder images is the most important.

But now, let's look for the last two folders.

lang-folder: You will find in it the en_US.lang, also a text file. In this you find ALL texts which have to been shown by the game.

sound-folder: Yes! Now its possible to change all the sounds with a texture pack. YEY!
You have only to replace the old sounds.

Finally, after i have written 1h on this, I only want to say: SORRY FOR MY BAD ENGLISH, BECAUSE I'M GERMAN

And here the /assets-folder for porting your texture pack!
http://www.workupload.com/file/kUOWhDDR

Quote from QyMineAsap

Where can I find the textures?
What file?

Quote from 500 Internal Server Error

Items support is still OK: see https://raw.github.com/zhuowei/ModPEScripts/master/treebl_newitem.js

        ModPE.setItem(392, "stick", 0, "Wand");

Quote from 500 Internal Server Error

Each texture in the new 0.8.0 system has a name: check items.meta for the built-in texture names.

Quote from 500 Internal Server Error

Mojang decided to rotate textures to make graphics look better. I've made a patch to disable this - check my other thread.


Not touching Minecraft built-in text, sorry.

Quote from 500 Internal Server Error

Each texture in the new 0.8.0 system has a name: check items.meta for the built-in texture names.