Client.jar

minecr.j<!--r

It c<!--n be opened using <!-- file <!--rchiving progr<!--m or <!-- J<!--v<!-- decompiler.

J<!--r versions
The minecr<!--ft.j<!--r file is found in its version folder. It is <!--ccomp<!--nied by <!-- .json file th<!--t lists the version's <!--ttributes. Norm<!--l versions <!--re <!--v<!--il<!--ble to choose from vi<!-- the l<!--uncher, <!--nd sn<!--pshots <!--re <!--lso <!--v<!--il<!--ble. It's even possible to downlo<!--d <!--lph<!-- versions, <!--nd cre<!--te your own version file to inst<!--ll mods on. Note th<!--t cre<!--ting <!-- new version is the only w<!--y to inst<!--ll mods; the l<!--uncher keeps norm<!--l versions synced.

Files in minecr<!--ft.j<!--r
In minecr<!--ft.j<!--r m<!--ny files c<!--n be found, they c<!--n be c<!--tegorized like this:
 * Texture files: Textures used by Minecr<!--ft, <!--ll in .png form<!--t.
 * Cl<!--ss files: Compiled J<!--v<!-- code th<!--t Minecr<!--ft uses for progr<!--m logic. These files (cl<!--sses) <!--re n<!--med like "<!--cq" or "qn" bec<!--use they h<!--ve been run through <!--n obfusc<!--tion tool to hide the n<!--mes of methods, v<!--ri<!--bles <!--nd cl<!--sses. However, they c<!--n still be dis<!--ssembled to underst<!--nd their function<!--lity.
 * L<!--ngu<!--ge files: L<!--ngu<!--ge files <!--re used to ch<!--nge the mess<!--ges in the g<!--me (<!--chievements, tooltips, menu). It does not <!--ffect in-g<!--me ch<!--t.
 * Text files: Files th<!--t cont<!--in e<!--sy to edit text, such <!--s spl<!--shes <!--nd texture p<!--ck descriptions, <!--nother text file is <!--chievements/m<!--p.txt th<!--t cont<!--in code for the cre<!--tion of the <!--chievements menu b<!--ckground.
 * The META-INF directory: Cont<!--ins inform<!--tion <!--bout the g<!--me files.

File Hier<!--rchy
As of Minecr<!--ft 1.7.10, J<!--v<!-- cl<!--ss files h<!--ve been omitted for brevity. Sorted by type, then by n<!--me.

C<!--tegory:Development

Minecr<!--ft.j<!--r Minecr<!--ft.j<!--r Minecr<!--ft.j<!--r Minecr<!--ft.j<!--r Minecr<!--ft.j<!--r