Minecraft Forums

Description
This mod will automatically reel in and recast your fishing rod when you catch a fish. Just cast the fishing rod one time into the water and let the mod do the rest.

Usage

• Configurable key (V by default) to open a GUI for changing individual settings.
• Very simple to use, just cast the fishing rod into the water once, and it will automatically reel in at the correct time and recast after a couple second wait.
• Enable Autofish - Toggles the entire mod on or off.
• Enable MultiRod - After using up a rod, it will try to auto switch to the next one in your hotbar if it exists, so you can fish for extended periods of time with multiple rods. (Switches to the first rod in your hotbar after each reel)
• Enable Break Protection - Ignores fishing rods once they are almost broken. This is useful if you have an enchanted fishing rod and you don't want it to break.

Videos and Images:

Installation

For 1.14 and later:
1. Install the Fabric Mod Loader (Click "Vanilla" if you use the standard launcher).

2. Download the Fabric API and place the .jar file in the /.minecraft/mods/ folder.
3. Download Autofish and place the .jar file in the /.minecraft/mods/ folder.
4. Launch Minecraft using the Fabric profile.
For 1.13.2:

1. Install Rift Mod Loader for 1.13.2. (See under "Using the Minecraft Launcher"). Run the downloaded jar to install it.
2. Download Autofish and place the .jar file in the /.minecraft/mods/ folder.
3. Launch Minecraft using the Rift profile.

For 1.12.2 and earlier:
1. Install LiteLoader.
Click here for LiteLoader downloads
2. Download Autofish and place the .litemod file in the /.minecraft/mods/ folder. Do not change the extension from .litemod or it will not load.
3. Launch Minecraft using the LiteLoader profile.
　
Download:

Click here to download on CurseForge

Older Versions:

FAQ

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

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, [email protected] 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

---

Table of Contents:

Overview
Changes in how things work
Frequently Asked Questions
[WIP] The Cubic Chunks Mod!
Gallery
Supporting this suggestion
Special thanks

[spoiler=Tl:dr]Q: Won't this increase lag?
A: Absolutely not. The title of this suggestion and big red letters at the top of this post aren't lying. If you want to know how, then I suggest you actually read this post.

Q: Will this change terrain? Will this break existing worlds?
A: No. Terrain change is not necessary. Existing worlds can be converted fairly easily with a process described later in this post.

Q: How can sunlight or rain work with infinite vertical space?
A: I suggest you read Coping with sunlight, because it's too complex for a tl;dr.

Q: I have a different question but still don't feel like reading this post. What do I do?
A: Too bad, read the FAQ. I put way too much work into this for the entirety of it to be ignored.[/spoiler]

---

Overview:

In Minecraft, the sky is the limit - literally. It doesn't matter how many thousands of blocks a player has traveled, or what dimension they're in, or even if they're playing in creative or survival, the highest they can ever build is up to a height of 256. Why is that? If Minecraft can have a world that's infinite in the north, in the south, in the east, and in the west, why can't that world be infinite up and down too?

In Minecraft's earliest days, in Classic and Indev, the world was not infinite in any direction. This was because the entire world needed to be generated at the same time, and the entire world needed to be simulated at the same time as well. This led to a conundrum - the bigger the world, the more it lagged.
Notch didn't like this. He knew his players liked to explore and build large creations, so he found a way to make the world truly infinite. When the Minecraft '' class='bbc'>Infdev came out, it brought with it truly infinite worlds. Suddenly, players could travel hundreds of thousands of blocks in any direction, and never encounter a barrier, or become too laggy.
The Infdev update brought about a very large change to Minecraft worlds to accomplish this feat. For the first time, instead every world being just a single huge piece, they were broken up into a two-dimensional grid of pieces, called chunks. Through breaking the world up into pieces, this 'chunk system' enabled infinite worlds by letting Minecraft create new pieces and simulate them only when it needs to.

Why does that not apply to the vertical axis? Because the type of 'chunk system' Minecraft uses right now is a linear one, which, by using only a two-dimensional grid to map out chunks, means that it is impossible for chunks to stack on top of one another, and by extension, meaning that a single chunk must cover the entire vertical space. This brings back the problem that the Infdev update was supposed to eradicate, now only with chunks, instead of an entire world; the bigger a chunk is, the more laggy it is. You can't just increase the height limit and make chunks taller, because it will become laggier, and laggier, and laggier to do it.
That's why, to fix this, Minecraft must change over to a cubic chunk system. Under this system, 16³ block chunks are aligned on a three-dimensional grid, completely eliminating maximum height as an aspect of lag.

The immediate benefits:
•Minecraft worlds become as virtually infinite vertically as they are horizontally: The absolute limit being Y = ±30,000,000.
•A large FPS increase: Alpha testers report an FPS increase of 100~200%.
•Increase in running capability: Computers running Minecraft on Tiny render distance will handle only 30% the blocks they do now.

The possible features:
•Spherical render/load distance: Reduce handled blocks by up to 30% by cutting corners made of unneeded chunks.
•Server chunk occlusion/exclusion: Reduce bandwidth usage and defeat hackers by only sending data for visible chunks.
•Three-dimensional biomes: Save biome data per chunk rather than per block column, create volcanoes with magma chambers, underground rivers, tropical skylands floating over icy taigas, and more.

The disadvantages:
•Unloaded gravity-pause: Falling non-player entities and fluids will be forced to pause their fall if they reach unloaded chunks, but will resume falling when those chunks are loaded.
•Slow falling-pause: Players with slower computers and smaller render distances will have falling occasionally paused as they fall into unloaded chunks, until new chunks can be loaded.

The problems:
•Current sunlight and rain calculation methods cannot work with infinite vertical space: The solution to this is described here.
•Current BiomeDecorator cannot work with multiple vertical chunks simultaneously: The BiomeDecorator code must be altered to function correctly with this, or removed.
•Current cave generation method is executed an extra time for each vertical chunk created simultaneously, leading to lag spikes on world generation: Cave generation's method must be altered to suit this system more.
•Current grass/dirt generation algorithm forces additional chunk requests when chunks are loaded, causing chunks to load slower than they should: This algorithm must be replaced with something else.

---

Changes in how things work:

Obviously, the implementation of this new chunk system will change quite a few things. These changes are mostly either necessary or in the interest of increased efficiency. Such changes are categorized and explained below.

How worlds will be stored:
[spoiler]How the current storage works, and what changes:
Interestingly enough, the current method of storage, the Anvil format, is derived from the storage method that the original Cubic Chunks mod used. The Anvil format stores individual chunk as a series of 16³ quasi-cubic chunks. These 'fake' cubic chunks allow for easier reference of specific data, but they still can't be separated from each other, meaning that it fails to reap the full benefits of this system. Even so, the change allowed Mojang to double the maximum height with no performance hit. Chunks are stored in groups of 32², inside 'MCRegion' files, for a total of 1024 chunks.
By nature, cubic chunks does away with the 'quasi-cubic' nonsense. In terms of chunk grouping, instead of using groups of 32³ chunks, new "3DRegion" files would contain groups of 16³. This means each 3DRegion file contains 4096 chunks, four times as many as MCRegion files. However, each 3DRegion contains only one fourth the amount of blocks. For per-chunk positional metadata, 3DRegion files would use the same number of bits as MCRegion files, after compression. Calculations show that the same area encompassed by a single MCRegion file would consume 64 kilobytes of extra space with 4 3DRegion files, which is nothing.

Converting existing worlds:
Most people are probably wondering something like "But won't this totally destroy all existing worlds?". Absolutely not; conversion could not be simpler. When a non-cubic world is loaded after the implementation of this system, a conversion process will begin and convert the entire world at once(To avoid making chunk loading take longer during play). First, all existing MCRegion files will be divided into quarters to create 3DRegion files. Then, all existing chunks are divided into sixteenths using the quasi-cubic properties to identify boundaries. After that, conversion is done.

The "isEmpty" flag optimization:
A 1-bit flag is added to each chunk, named "isEmpty". If the chunk consists of 100% air blocks, this bit is 1, any other case makes it 0. When the bit is 1, all data for the chunk besides the isEmpty flag is deleted and ignored, which reduces filesize. Empty chunks are never loaded, and locations where they occur are merely simulated as entities reside in them. The chunk will only load when something requires saving inside it.[/spoiler]

Changes to terrain, ores, etcetera:
[spoiler]Terrain:
By default, nothing will change. Small bits of terrain generation code need to be reconfigured to work properly with Cubic Chunks.

Biomes:
By default, nothing will change.

Ore generation:
By default, nothing will change.

Structures:
By default, nothing will change.

The Void:
After conversion to Cubic Chunks, the void and bedrock layer will still exist and generate as they always have. However, the void(Not the bedrock layer!) will not exist as a hard limit and is able to be moved, but not removed, by editing an associated NBT data tag inside a world's level.dat. This feature, that allows for increasing the maximum depth, is intentionally disabled without external programs, to prevent terrain change of any sort. It is intended to be used by experienced mapmakers and world generation mods only.

Superflat settings:
Existing superflat worlds will not change. However, new superflat worlds will gain a new decoration parameter, 'void'. Inclusion of this parameter will cause the void to form below the lowest defined layer. Exclusion of it will cause all layers below the lowest defined layer to copy the settings of that layer.[/spoiler]

Coping with sunlight:
[spoiler]There used to be a solution here, but it wasn't deemed good enough by Jeb. Suggest solutions in this thread.[/spoiler]

Changes to servers:
[spoiler]Settings:
There's a setting inside the Server.properties file called 'max-build-height'. The setting makes it impossible for any player to place or remove blocks above that height.
With the implementation of Cubic Chunks, a new setting named "maximum-generation-depth" would be added. The void, bedrock layers, and magma layers will generate normally at and above the Y level designated by the value of this setting.

Chunk occlusion/exclusion:
Using the raytracing methods already available in the code and used for explosion calculations, servers can identify which chunks are visible to a player, within safe assumptions, and only send the data for those chunks. This both reduces bandwidth usage, and cripples the usefulness of X-Ray cheats.[/spoiler]

Render/Load distance alterations:
[spoiler]After the implementation of Cubic Chunks, view distances' radii will apply to the vertical axis too. This reduces handled blocks in the cases of tiny and short render distances, and increases them in the cases of normal and far render distances. This can be optimized by utilizing a spherical render distance instead of a cubic one, which would reduce handled blocks in all distances except Far.[/spoiler]

---

Frequently Asked Questions:

[spoiler=FAQ]Q: This is impossible.
A: No it's not. See below.

Q: Is this available as a mod?
A: Not yet! But it will be!

Q: I like X-ray! What if I don't want it to be broken?
A: First of all, breaking X-ray hacks will only be possible to do in multiplayer. That said, the system that would break X-ray would be possible to disable by the server owner. If the owner doesn't disable the system, then they don't want you using X-ray, and you should not be doing what the server owner doesn't want in the first place.

Q: I play on a PvP/Anarchy/Raid/Faction server. Won't this system let people pillar up into the sky and create a base thousands of blocks in the air and never be found?
A: No.

Q: I like Minecraft's current height limits. What if I don't want to have an infinite sky or infinite underground?
A: If this system is added, all worlds will not automatically gain an infinite underground. As stated below, the Void will remain in all worlds, even after the conversion to Cubic Chunks. The ability to remove the Void will simply be there. As for infinite space in the sky, the current build limit is over one hundred blocks above any terrain that vanilla Minecraft can possibly generate. It is ENTIRELY your decision on whether or not you take advantage of this height. If you play on a server, like stated above, the server owner can set a maximum build height. If s/he doesn't, then don't play on their server - you don't play on servers where the server owners allow things you don't like. Why would you play on an anarchy server if you hate being stolen from and killed?

Q: Will this affect Redstone at all?
A: No. This system will simply make it possible to make larger redstone circuitry than before.

Q: Won't this break existing worlds?
A: No. Existing worlds can be easily converted by dividing each MCRegion file into 4 pieces, then slicing the existing 256 block-high chunks inside them into 16 individual chunks.

Q: Won't this affect mods? Won't mod authors have a hard time updating their mods?
A: The answer to this question depends solely on the answer to the following two questions: Do parts of the modification code rely on chunk data/metadata? Does the mod author want to take advantage of the features of the new chunk system? If the answers to the first and second question are both "No", then updating a mod to this system should be very easy and quick. If the answer to the first question is "Yes", then those parts of the code will need to be rewritten somewhat, but in most cases, the changes should be fairly quick and easy. The only time that it should be hard to update a mod to this system, is if the answer to the second question is "Yes".

Q: Won't this require a total rewrite of the mod API if that's released first?
A: No. Whether or not even a small part of the mod API needs to be rewritten depends on the way that it is implemented and whether or not there are API inclusions for chunk handling and other chunk-related behavior.

Q: Could a player fall into unloaded chunks if chunks aren't loaded fast enough?
A: No, they could not, and for several reasons. Minecraft has a terminal velocity, though it might not seem like it. This velocity is slower than it should take to load new chunks below the player. In cases with exceptionally slow computers, even if the player did manage to reach an unloaded chunk, their fall would be paused until that chunk can be loaded.

Q: What would happen when water, sand, or a mob falls into an unloaded chunk?
A: Nothing. The water/sand/mob would freeze in place until the chunk is loaded and it can continue moving. You can already see this same thing happening on the horizontal axis.

Q: What will happen to the Void?
A: It will still exist, along with all its effects. The only difference is that the Void is no longer a hard limit and it can be moved. After the conversion to Cubic Chunks, the Void's location will be stored in a world's ' class='bbc'>level.dat, and this location can be changed with NBT editing tools. When and where the Void exists, chunks will cease to generate.

Q: Will this affect terrain?
A: No. However, terrain generators will gain the ability to use infinite height.

Q: Will this affect ore generation?
A: No. Ore is a part of terrain generation. As stated above, terrain will not be changed.

Q: Won't all current terrain generators be incompatible with this system and need to be rewritten?
A: No. Terrain generators work independently of chunks. When a chunk is generated for the first time, it calls the terrain generator and receives a specific section of the resultant terrain to save inside itself. Because of this, some custom terrain generators can generate steep terrain all the way to Y256, where you can experience a large, flat cut-off. Since there are no chunks above Y256 to call the terrain generator for terrain, no terrain exists there.

Q: What would happen if there's a huge solid ceiling so far above you that it is unloaded? Wouldn't you just see the sky, just with everything being completely dark?
A: Yes. This already happens on the horizontal axis, and it is an issue with sky rendering, not this chunk system. As such, this has nothing to do with this suggestion. Please do not post about this.

Q: If you go deep underground, will your plants grow/ores smelt/animals grow?
A: No, because those chunks would be unloaded, just as if you had walked far away. This is a flaw with any chunk system, regardless of shape. It is a necessary evil that allows Minecraft to have infinite worlds. The only way to fix this would be to introduce a separate new system that works with chunks as they are loaded and unloaded. This suggestion deals with the chunk system itself, and not sister processes. Because of that, that is outside of the scope of this suggestion. Please do not post about this.[/spoiler]

---

[WIP] The Cubic Chunks Mod! (Tall Worlds Mod):

Cuchaz has taken it upon himself to bring us the glorious Cubic Chunks, since Mojang refuses to do so.

Cuchaz is using a API of his own creation to help assist in the making of this mod, and he's quite far along, as seen in these two tech demo videos:
[spoiler=T-Demo 1: Vertical chunk loading][/spoiler]
[spoiler=T-Demo 2: Broken height cap and no lag!][/spoiler]
With the basic functionality in place - a complete overhaul of the basic chunk system, and height limit removed - this whole concept can already be considered proven. What remains is making sure everything else functions correctly under the new chunk system. In any case, stay tuned for future updates if it interests you(If it doesn't, then you are the weakest link - goodbye!).

You can follow the mod's development in much more depth in its very own topic!

---

Gallery:

[spoiler=A mountainside with an experimental engine using Cubic Chunks designed by Nocte. 960 block view radius, and 30 FPS.][/spoiler]
[spoiler=A different view of the mountainside with the same engine by Nocte. This time, with 1600 block view radius and 15 FPS.][/spoiler]
[spoiler="A video demonstrating Nocte's engine."]

---

Support & Submission to Mojang:

If you support this, hit the rep button in the bottom-left corner of this post. It is the only good way of accurately measuring support here.

If you wish, you can put the following banner, courtesy of laz2727, into your signature. It helps to attract support from all parts of the forum!

 [url=http://www.minecraftforum.net/topic/1707097-cubic-chunks-infinite-height-elimination-of-x-ray-and-more-60-supporters/page__st__0][img]http://img833.imageshack.us/img833/443/hov.png[/img][/url]

Please help us get word out of this suggestion! Share this with your friends, with Minecraft celebrities if you're familiar with them, or even with Mojangsters like Jeb or Dinnerbone! (Do not share this with Notch. Notch doesn't work with Minecraft anymore.)

The purpose of this suggestion is to have Cubic Chunks implemented in Vanilla. Being available as a modification does not fulfill that purpose. The modification featured in this suggestion is to act as a proof-of-concept only(Note: Its being featured here is to act as a proof-of-concept. The modification itself is on its way to becoming a fully fledged modification).

---

Special thanks:
Cuchaz, for taking Barteks' proof and running with it, to give us a truly functional Cubic Chunks mod.
Barteks2x, for updating the Cubic Chunks mod to 1.6.2, proving that it is possible.
Azraile, for posting the original suggestion and allowing me to take ownership of it.
Nocte, for helping resolve flaws and designing Hexahedra.
MineCrak, for a large amount of valuable insight and enthusiasm into the topic of Cubic Chunks.
aaronfranke, for helping resolve flaws.
PanJouda, for creating the original banner.
Flexico, for creating the predecessor to the current banner.
laz2727, for creating the current banner.
Robinton, for creating the original Cubic Chunks mod.
The_Watchman13, for answering all those stupid questions so I don't have to.

---

Note: Many calculations and information can be found among the many posts of this topic. There are too many for me to cite here, but if you wish, you can search for them yourself.

A lot of people complain all the time of suffering from slow performance and low FPS in Minecraft, especially after the 1.8 update changed some things. A quick Google search can't give you everything, and it can be tedious to collect every bit of information out there on increasing performance. So, I decided to compile everything I've read and learned into one guide.



Stop!



Before continuing, you must make sure you meet the system requirements for Minecraft. Additionally, this guide is meant for PC vanilla Minecraft only. If you are running a modded client and are experiencing performance issues, you may want to try running a vanilla client first and seeing if that helps. If it does, it is likely an issue with the mod and should be brought up with the author of said mod.



Step 1: Update Java

*Note: If you are using Windows, you should have a new Java installer that automatically updates Java for you. However, if you do not use Windows for your OS or for some reason do not have this automatic updater, you will need to follow the instructions in this step to update Java. This bolded information was contributed by tulir239.

Java is the system that Minecraft uses to run, and is used by many other software systems as well. Having an out-of-date form of Java can affect performance in Minecraft, and may even prevent you from playing altogether. Before going to more drastic measures, try updating Java to the latest version.



Step 2: Install MagicLauncher and Optifine



Out of everything I have done to improve my performance, installing Optifine was the one that did the most. After configuring all of the settings, I immediately saw a major increase in FPS. I had to make some other adjustments before I was able to get to the FPS I run Minecraft at currently, but I saw a 100% increase in FPS almost immediately following optimizing the mod and adjusting the settings to what I figured worked best. Some people have reported even higher percent increases than that. I recommend having the settings set to the following:



Graphics: Fast

Render Distance: Normal

Smooth Lighting: Off

Max Framerate: Unlimited

Smooth Lighting Level: Off

View Bobbing: Off

GUI Scale: Auto

Use VBOs: Off

Brightness: Any setting, does not affect performance

Alternate Blocks: On

Fog: Fast

Fog Start: 0.8

3D Anaglyph: Off

(Following are found under the "Quality" tab)

Mipmap Levels: 4

Mipmap Type: Nearest or Linear, did not see any difference between the two

Anisotropic Filtering: Off

Antialiasing: Off

Clear Water: On

Random Mobs: Off

Better Grass: Off

Better Snow: Off

Custom Fonts: Off

Custom Colors: Off

Swamp Colors: Off

Smooth Biomes: Off

Connected Textures: Off

Custom Sky: Off

(Following are found under the "Details" tab)

Clouds: Fast

Cloud Height: Off

Trees: Fast

Rain and Snow: Fast

Sky: On (Set to Off if you have an extremely slow computer)

Stars: On (Set to off if you have an extremely slow computer)

Sun and Moon: On (Set to off if you have an extremely slow computer)

Show Capes: On

Translucent Blocks: Fast

Held Item Tooltips: On

Dropped Items: Fast

Entity Shadows: On

(Following are found under the "Performance" tab)

Fast Math: On

Smooth World: On

Load Far: Off

Preloaded Chunks: Off

Chunk Updates: 1

Dynamic Updates: Off

Fast Render: On

Lazy Chunk Loading: On

(I recommend leaving all of the settings under the "Animations" tab unchanged unless you have an extremely slow computer. In this case, I recommend turning off all of the settings containing the word "Animated".)

(Following are found under the "Other" tab)

Lagometer: On

Debug Profiler: Off

Weather: On (Turn off if you are using an extremely slow computer)

Time: Default

Fullscreen: On or Off, depending on your preference. Did not affect performance for me.

Fullscreen Mode: Depends on computer capabilities. If you have an extremely slow computer, I recommend the lowest resolution setting. If you have a decent system, I recommend 1600x900. This only applies if you are playing the game in fullscreen mode.

Autosave: 30min (Do not set to 2s. The developer is completely right in saying that the autosave feature causes the infamous Lag Spike of Death. Having that occur every two seconds would not be good.)



The Optifine mod can be found here. Credit for the mod goes to sp614x. Most servers do not have a problem with users using Optifine on their servers. If you are concerned that there will be a problem, contact a server admin and ask them about it.



Step 3: Adjust your Render Distance



Most computers are not powerful enough to run Minecraft at Extreme Render Distance, especially on busy servers. Generally, a computer can run Minecraft smoothly at Normal render distance. However, weaker computers have a tough time with this. If you still desire a faster game and have a slower computer, I recommend either Short or Tiny render distance. Even if you do have a strong computer, I only recommend going up to Far render distance. Extreme render distance is extremely demanding on your system.



Step 4: Set Java to High Priority



*Note: I run Windows 8.1 for my OS. The pictures used for this step were taken on my computer, but the instructions for Windows 7 and Windows 8 should be almost, if not completely, the same. If anyone uses XP or Vista for their OS and is willing to provide screenshots, I'd appreciate it.



Setting Java to high priority can in fact help your performance. Do not be put off by the warnings that it can unbalance your system; I have experienced nothing of the sort so far. By default, Java is set to Normal priority. To change this, press Ctrl+Alt+Delete and select your Task Manager. You must have Minecraft open to continue. Find the program titled "Java Platform SE binary and right-click. Select the option "Go to details". This will automatically take you to where java.exe is located in the list. Right-click on java.exe. Hover over the "Set priority" option and select "High". Note that you will need to do this each time you play Minecraft. Yes, it's tedious. Yes, it does help. No matter what, do NOT select the "Realtime" priority option. This is nearly guaranteed to either freeze your computer or force a shut down. I am not responsible if you go and screw this up and you lose everything you are working on.

Images: (Windows 8)

Images: (Windows 7) (Courtesy of goldensilver853)



Step 4: Change the amount of memory Java uses


*Note: There are multiple ways to do this. All of them work. Just choose the one that seems easiest for you.

Method #1:

Java often automatically uses way more memory than is actually needed to run Minecraft smoothly. 500MB is the required amount of memory to do this. To fix this issue, start up MagicLauncher. Click the Setup button. Click the Advanced tab. Find the spot marked "Memory". Change the current amount used from whatever it is to 500. Click OK.

Images:


Method #2:

Launch the vanilla Minecraft launcher. Once it opens, select the "Edit Profile" option. Find the box marked "JVM Arguments" and select it. Find the part that says "-Xmx1G" and change it to "-Xmx512m". Click "Save Profile". This information was contributed by AppleEater01 and tulir293.

Images:



Step 5: Close all background processes



This dramatically improved performance for me. As much as you like listening to music in the background and having Facebook there to constantly check, it really slows Minecraft down and uses up needed memory. Close out of your browser and any other applications before starting Minecraft. You'll be surprised how much it helps.



Step 6: Set your computer to High Performance


*Note: The instructions for this step are the same for both Windows 8 and Windows 7. Windows Vista and XP users will have to do a Google search for now. Instructions for those OS coming soon.


To adjust your computer's performance, right-click on the battery in your taskbar. Select the "Power Options" option. Click the "Show additional plans" option. Click the "High Performance" option. Be sure to keep your laptop plugged in while on this plan if you are using a laptop. You will lose power a lot faster on this plan than on the other two plans.

Images: (Windows 7) (Courtesy of goldensilver853)


Step 7: Check your Resource Pack



Certain resource packs are only intended for the most powerful systems and highest quality displays. If you are using a resource pack of a higher quality than your system can run smoothly, you need to get rid of it or go down to a lower resolution. I recommend going for 16x16 or 32x32 resource packs. If you have a decent computer, you can easily give 64x64 a try as well. If you have an extremely slow computer, I recommend staying away from resource packs period.



Step 8: Update your drivers



Having out-of-date drivers can affect performance. Finding out if your drivers are out of date is different for each system, and it will require you to do a bit of research to find out how to update them. I recommend doing a check for out-of-date drivers every 6-8 months.

Step 9: Use the default garbage collector

This information was fully and completely contributed by TheMasterCaver.

Quote from TheMasterCaver»

Also, using the default garbage collector, which does full GCs all at once, may improve average performance, at the cost of occasional freezes for a second or so, but they don't occur very often (more can RAM help here; 512 MB is plenty but I've found that 768 MB drastically reduces the frequency, perhaps once an hour, without making the pauses too long; I just use -Xmx768M -Xms768M -Xss1024K, the last because 32 bit Java doesn't allocate enough stack space (64 bit uses 1024K by default, 320K for 32 bit) to avoid this crash, which is for 1.7+ but has also occurred on modded 1.6.4); by contrast, the concurrent collector causes periods of stuttering when it runs, much more frequently and more annoying as a result (this also depends on how many cores you have; I have two, so one can run the client thread and the other the server thread, but more threads can cause issues, as my CPU also doesn't have hyperthreading, which isn't a substitute for a dual-core CPU anyway; having a dual-core CPU also likely explains some of the issues with 1.8, especially the multicore chunk loading, as also seen with Optifine's multicore chunk loading on older versions, which causes the same stuttering and lag spikes 1.8 has). Note also that -Xms forces the JVM to use all the available RAM (100% allocated from the start) as otherwise it may only allocate a portion and GC more frequently as a result.

This guide will be updated frequently as I find more useful ways to run Minecraft at a better rate. If you have found anything yourself that wasn't included in this guide, please let me know! I will be adding guides to Windows 7 and Windows XP OS alongside the Windows 8 ones soon. Screenshots will also be accompanying some steps soon. Feel free to post your FPS differences on here after completing these steps.

Its useless without an iPhone, continuity baby.