Minecraft Forums

Hello everybody,

the Magic Launcher is a new Minecraft launcher which can load mods dynamically without changing or patching the minecraft.jar.

No more mod installation problems, just select your mods and enjoy.

Screenshots

Features

• Minecraft
- selectable minecraft.jar
- selectable environment
- automatic version detection
- automatic library download
- configurable window size, also maximized
- selectable minecraft folder
- selectable java executable
- java memory limit
- java custom parameters
- show error log
- multiple user profiles
- remember password
- configuration profiles

• Mods
- load mods dynamically without changing minecraft.jar
- META-INF does not have to be deleted
- automatic mod compatibility checking
- external mods detection and compatibility checking
- shortcut to external mods folder
- configurable external mods
- automatic mod requirements checking (ModLoader, ModLoaderMP, Forge, GuiAPI)

• Design (screenshots)
- Minecraft style

• News
- Minecraft
- Reddit
- Twitter
- Blogspot ...

Download

Get all MagicLauncher versions here: magiclauncher.com

Download MagicLauncher 1.3.4 (fixed Reddit RSS feed, fixed server status check, increased account limit to 100, fixed handling of derived profiles (Forge + LiteLoader), fixed "${version_type}" in main menu): for Windows, for Mac, for Windows/Mac/Linux
Mirrors: for Windows, for Mac, for Windows/Mac/Linux

Note for Minecraft 1.6.2+

Starting

Double click the downloaded file and the MagicLauncher should start.

Older versions

Changelog

Fixing common problems

TODO

Quote from xaero96»

Ok, I know what's wrong. Having Optifine deobfuscates func_187508_a() to getSprite(). Likely accidental, so it should probably be fixed on their end.

The real problem is that Forge adds the SRG named method func_187508_a() in BakedQuad:

https://github.com/MinecraftForge/MinecraftForge/blob/1.15.x/patches/minecraft/net/minecraft/client/renderer/model/BakedQuad.java.patch#L40

SRG names should only be used for deobfuscated methods.

The func_187508_a() was existing in 1.14.4 mappings, but it doesn't exist in 1.15.2 and is only added by Forge.

I will add it for now with comment to clean it up when the Forge patch is fixed.

OptiFine History

Minecraft 1.8.9

Minecraft 1.8.8

Minecraft 1.8.7

Minecraft 1.8.4

Minecraft 1.8.3

Minecraft 1.8.1

Minecraft 1.8.0

Minecraft 1.7.10

Minecraft 1.7.9

Minecraft 1.7.5

Minecraft 1.7.4

Minecraft 1.7.2

Minecraft 1.6.4

Minecraft 1.6.2

Minecraft 1.5.2

Minecraft 1.5.1

Minecraft 1.5.0

Minecraft 1.4.6

Minecraft 1.4.5

Minecraft 1.4.4

Minecraft 1.4.3

Minecraft 1.4.2

Minecraft 1.4.1

Minecraft 1.4.0

Minecraft 1.3.2

Minecraft 1.2.5

Minecraft 1.2.3

Minecraft 1.1

Minecraft 1.0.0

Minecraft Beta 1.9

Minecraft Beta 1.8.1

Minecraft Beta 1.7.3

Minecraft Beta 1.7.2

Minecraft Beta 1.6.6

Minecraft Beta 1.5

Minecraft Beta 1.4

Hello everybody,

This mod adds support for HD textures and a lot of options for better looks and performance.

Doubling the FPS is common.

You can follow the OptiFine development here: reddit.com/r/OptiFine, sp614x@twitter or http://optifog.blogspot.com.

Resources: translations, documentation, issue tracker.

Get the Magic Launcher for easy mod installation, compatibility checking and more.

Donate to OptiFine and receive the OptiFine cape as a sign of your awesomeness.

The cape is visible to everyone using OptiFine. Thank you for being awsome.

Download OptiFine

Get all OptiFine versions here: optifine.net

Features

Editions

Even Older Versions

If you have previously used MCPatcher for HD Textures, HD Fonts or Better Grass (important)

Compatibility with other mods

Installation

For Minecraft 1.6.2 and newer

For Minecraft up to 1.5.2

Please test and report back, include CPU, GPU and FPS before/after. Feedback is always welcome.

Copyright

Quote from ccar795»

@sp614x So since in 1.14 the lighting engine is being redone, will a lot of features have to be re-done?

The 1.14 render engine hasn't been deobfusctated yet so it is hard to say how it works.

Looking at the 1.14 performance and looks it is probably the same as 1.13, but packed in a different way.

I have registered the website on yandex webmaster and I have reported that the site is clean
it will probably take some time until the warning is removed
This is the Virus Total report for optifine.net:
https://www.virustotal.com/#/url/18bf8c18f49875d4a41a5170f7748f9bef6056c2d582a2b282c8b469147cc887/detection

Quote from JOHNB007»

Hello.

May I ask if it could be possible to use the id="depthsuspend" parameter in an Optifine shaderpack? The reason is to bring back the Void Fog. Also is it possible to convert a Forge shaderpack into an Optifine shaderpack? The brilliant Tamaized has released a Void Fog mod but it only works with Forge which just lags out constantly.

Thankyou for your time and hope to speak soon.

Quote from XDGrangerDX»

Hello! Im having a problem with creating a texturepack with CIT support: I cant get the custom textures to apply to my items.

Neither will "lame d'argent.properties" apply to swords named "Lame d'Argent" (via anvil?)

type=item
items=minecraft:diamond_sword
texture=mcpatcher\cit\sword\special\lame d'argent.png
nbt.display.Name=Lame d'Argent
weight=9001

nor does the "diamond_swordsh1.properties" apply to swords with one level of sharpness.

type=item
items=minecraft:diamond_sword
texture=mcpatcher\cit\sword\diamond_swordsh1.png
enchantmentIDs=16
enchantmentLevels=1

And finally, is there a way to match exact for enchantments? From what i read, the enchantmentIDs list looks for any of the listed enchantments being present instead of requiring them all and enchantmentLevels counts the levels of all enchantments together, rather than specifying levels for a cerain enchantment.

I played around some with nbt.tag.ench.id=[id] but i could get nowhere with that either.

Any help welcome!

Backslashes "\" will probably not work, resource packs use forward slashes only "/".

OptiFine usually complains in the log file (game output) when there is a problem and shows exactly what is incorrect.

Quote from VikingNation»

Optifine is a great mod. We donated to support the project and received a cape. Our Mojang account was locked after changing our cape. Mojang stated the following after restoring the account

- Do not enter your account credentials on any third party websites
- Do not use VPN/proxy when accessing our services
- Do not share your account with anyone else
- Do not use the same password on multiple account

This is not an isolated event any many have experienced the same issue.

Why does Optifine require a Mojang username and password?

When will Optifine be updating the service to not require a Mojang username and password?

Usually the accounts are not really compromized.

It is just that the Mojang authentication service is very, very, VERY
sensitive when it comes to login from another IP, failed logins and so
on. In any case when it thinks there may be something suspicious it just
locks the minecraft account and sends the user a warning message.

The login from the optifine.net comes from another IP than the user
usually uses and it is also very easy to enter the wrong password 2
times on the web site. Both of these may lead to Mojang locking the user
account "just in case" there may be something suspicious.

These same problems also happen with the normal minecraft launcher,

but not so often as it can cache the authentication token and so it
doesn't have to send the username/password on every login.

The main problem is that Mojang does not offer an easy way for third

parties to validate minecraft accounts, for example like OpenID, OAuth
and so on. Instead Mojang relies on the ancient username/password
mechanism and it has locked it down so much that it is almost unusable.

What Mojang should do is implement a modern way to authenticate

users, where the user does not have to enter username/password on
another website.

The security of optifine.net is up to date and no sensitive user

details are EVER saved or sent over non-secured connections. We take
security very seriously.

Quote from Mi4erahka»

there is a small problem with emissive textures, in the dark they do not have enchanting,[video]. this of course can be corrected with the enchantment of using mcpather but it is not very convenient due to pixel textures, and I have a subject which enchantment is not necessary visible, but it is put visible through enchantment....and just

[video]

A quick guide to help get started with entity modelling in optifine.

I hope to update this guide as time goes on, but currently this won't go too in depth with what you can do.

Intro

Optifine's entity modelling allows you to replace or add to different parts of an entity, ie head, body, arm1, arm2, leg1, leg2.

The parts that each entity has is different and the full list of parts can be found in optifine's jem documentation.

Optifine also has jpm documentation.

To help there is some existing entity modelling test resourcepacks which you can use to help see how the files can be made: my tests, sp614x's tests, sp614x's tests #2, and a remodeled creeper I made.

Working directory: all custom entity files will be placed into assets/minecraft/optifine/cem in your resourcepack.

jem Files:

A jem file is required when entity modelling, it is the main file which specifies how to re-model an entity.

You simply need to create a jem file named as the entity that you want to have a custom model, ie zombie.jem.

A full list of entities and the names of the files can be found in the optifine's jem documentation along with a list of parts which can be replaced in each entity.

jem stands for JSON Entity Model, meaning that the file must be written in valid JSON.

Firstly "models" is a required parameter which is an array, it will contain objects which then contain models and which parts they replace.

"models": [
    {
        "part": #part,
        #model
    }
]

#part must be replaced with one of the parts specified in the optifine's jem documentation. ie "head", "body", "leg1".
#model can be replaced one of two things, you can use a jpm file, or you can specify the model in-line by creating the elements within the jem file itself.

You can replace #model with elements (explained further down), or with "model": "file_name.jpm".

There is some other values that will come in handy which are: "attach": < true | false >, "translate": [x, y, z], "rotate": [x, y, z].

"attach" will default to false if left out, but if set to true will add the model to the part specified rather than replacing it.

"translate" will move the element the number of pixels on the specified axes.

"rotate" will rotate the element on the axes the amount of degrees.

jpm Files:

jpm stands for JSON Part Model, which means that the file must be valid JSON. jpm files must be located within the optifine/cem folder.

A jpm file is purely a part which can consist of multiple elements which can then be used by jem files when replacing parts.

These files do not need to have specific names. But you need to create at least one element.

Instead of writing jpm files by hand, Cubik Studio (~ €20), a modelling program which supports Minecraft json block models, also has the ability to export jpms from the program itself.

You can also use blockbench a free block modelling program, which can be downloaded or used online, which can also export optifine jpms.

This means you won't have to write a jpm by hand but can just create and export models from Cubik Studio or blockbench.

Creating Elements:

"texture": "path/to/texture.png",
"textureSize": ['width', 'height'],
"boxes": [
    {
        #texturing
        "coordinates": [0, 0, 0, 2, 2, 2]
    },
    {
        #texturing
        "coordinates": [3, 4, 0, 2, 2, 2]
    }
]

"texture": "path/to/texture.png", "textureSize": ['width', 'height'], "boxes": [ { #texturing "coordinates": [0, 0, 0, 2, 2, 2] }, { #texturing "coordinates": [3, 4, 0, 2, 2, 2] } ]

This is a basic method of creating elements, note that "coordinates" works quite differently from that when block modelling. The first three values are the location of the element, the next three are actually the width, height and depth.

"coordinates": [0, 0, 0, 2, 2, 2]

"coordinates": [3, 4, 0, 2, 2, 2]

Both of these elements will be the same size but will be in different places.

Texturing Elements:

There is two ways to texture elements but first you need to specify the texture that will be used by the element by specifying the path following assets/minecraft ie, "texture": "textures/entity/pig/pig.png". You also need to put the size of the texture in pixels ie, "textureSize": [64, 32].

When texturing an element you can specify the uv mapping of individual faces with: "uvUp", "uvDown", "uvNorth", "uvEast", "uvSouth", "uvWest".

ie "uvUp": [0, 0, 4, 6]. The first two numbers are the most top left coordiante of the area you want to have the texture then the next two will be the opposite most right down corner.

The second method is to use "textureOffset" which works with a unwrapped box texture layed out in this specific format. You specify one set of coordinates which is the most top left coordinates of the rectangle drawn around the unwrapped box. From this example the coordinates would be [0, 0], ie "textureOffset": [0, 0].

Animations:

Custom animations can be applied to each part of the entity, they are created by mathematical equations located within the jem file for mobs. You can read the optifine documentation on animations for more information.

The animation equations used for custom animations are located within an object, within an array called "animations" which will be inside the object within the "models" array in the jem file.

"models": [
    {
        "animations": [
            {
                #equations
            }
        ]
    }
]

Each equation will start with a key for the model the animations will affect. This is done through use of a model variable in the format <model>.<variable>:

The main two model properties are:

part - part refers to the part that the custom model has been attached to or replaced, this will animate the existing part and the model that has replaced/added to the part.

this - this refers to the part that has been added, this will not affect the original part, this can be seen clearly if the new model has been attached instead of replacing.

The variable has 12 possible values and this will define the type of animation and the axis that will be affected.

The type can any one of 4 possible values:

rotation (r), offset (o), translation (t), scale (s)

Followed by one of the three axis (x, y, z)

Note the difference between translate and offset. Offset refers to an absolute value for the model whereas translate will refer to a relative value, which will be relative to the existing location of the part model.

eg "part.ty", "this.ox", "part.rz"

Following the model variable will be a string which contains a mathematical equation.

There's several variables and functions which can be used within equations.

variables:

model variables - Already stated, these can be used to get values from other parts on the entity.

time - This is the world time in ticks and can be used on all entities.

limb_swing, limb_speed - Can only be used with 'living' entities, the swing and speed of entity limbs, these will change when the entity is moving.

operators:

+ addition, - subtraction, / division, * multiplication, % modulo (gives the remainder after division)

functions:

sin(), cos(), tan(), abs(), round(), sqrt() and many more, listed in the optifine documentation.

e.g.

"part.ty": "abs(2 * sin(time / 10)) + 12"
"part.tx": "abs(sin(time / 10))"
"part.rz": "0.2 * abs(sin(time/10))"

These animations are used on pigs in my model tests

Animating Existing Parts:

Custom animations can be applied to existing parts of an entity, this is done by not specifying any models but setting "attach": true for the part and setting the animations.

"part": #part,
"attach": true,
"animations": [
    {
        #equations
    }
]

Moving the Origin of a Part

This is a small problem which seemed impossible to acheive, the idea was to be able to change the origin for limbs as the point from where limbs were swinging couldn't be changed with translate. This would allow legs to be bigger or smaller, further apart or closer together than the original entity.

The way this can be done is using animations to simply translate the limb a fixed amount, and it will move the origin of the part itself.

"part": #part,
"animations": [
    {
        "part.ty": 2
    }
]

Finally, after several months of development, here is the official release of the 6th version of my shaders! This version is a huge code re-writting and re-organisation, which probably make this shaderpack the one with highest performance/quality ratio at the moment.

Lowest versions have been optimized for integrated gpus and minimize memory bandwith usage. For example, V6-Lite is the fastest shaderpack with shadows on an Intel HD 4600 with a 10-20% lead on the second one while maintaining a superior level of quality.

NB : Macs are not supported at the moment but will supported be in a short future.

Download it on my shaderpack thread : http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/1293898-chocapic13s-shaders

Short list of improvements over V5:

- Massive increase of the performance/quality ratio

- Totally new and improved lighting

- First shaderpack to support transparencies and particles correctly

- New lens flares

- Improved godrays

- Greatly increased shadow draw distance

- New SSAO for ultra and extreme versions

- Improved variable penumbra shadows (Ultra and extreme versions)

- POM support for High/Ultra/Extreme

Screenshots :

Quote from Kwitcherbelyakin

meh, at some point it becomes obvious that they aren't really putting much effort at all into the job & are dragging their feet. That time came and went a little while ago, IMO. This coming from someone who has been involved with similar projects. (major coding for no pay)

Quote from stoptake2244

I've been waiting for optifine but it hasn't been out since 1.7 came out. Can you put it out really soon?