Re: Minecraft Installer
People seem to be making this more complicated than it needs to be.
I have been running Minecraft in Linux since I think 1.8 beta in 64-bit 11.10 and subsequent snapshots and releases with no major problems using the default openjdk installed by ubuntu-restricted-extras. MC 1.2.3 had occasional freeze issues in SMP (survival multi-player), but people had those issues in Windows too using Sun Java. At least in Linux it eventually thaws, although, if it freezes too long you get disconnected from the server. I don't remember having that issue in MC 1.2.4 yet, which runs smoother even if it is so busy that rendering is delayed (especially jungles).
If you create a bin directory in your home directory, once you log out of X and log back in, that directory is in your $PATH. Then you can create a script in that bin called minecraft something like this:
It does not matter which version minecraft.jar you use to launch it, just that it is a complete minecraft.jar with the launcher, not one from .minecraft/bin, nor a prerelease snapshot (which you have to put in .minecraft/bin).
# Change cd line to your path to orig minecraft.jar, NOT ~/.minecraft/bin
java -Xmx1024M -Xms512M -cp minecraft.jar net.minecraft.LauncherFrame
Although if you have the RAM, 1.2 versions work better with -Xmx2G -Xms2G because when I use that I have sometimes seen it use more than 1 GB which would keep more in RAM instead of having to reload data.
Then for a Unity launcher in Dash search for "main menu" (which should come up after you type main) and add something to launch the minecraft script in a terminal. Once you launch it from Dash you can check Keep in launcher.
For an icon I use or for the server I use
I did update the lwjgl version in the .minecraft directory to 2.6, because the 2.4 version that comes in minecraft (which may be changed soon) occasionally results in stuck movement keys (or press same key in direction you are moving to unstick it). That requires replacing a bunch of files in different paths with the newer versions.
When a new version comes out and I want to be able to run both versions, I just copy the entire .minecraft directory with a number appended representing the version, for example I copied it to .minecraft-123 before updating minecraft to 1.2.4. Then to switch versions, I run this mineswitch script (modify MINEA and MINEB for new versions):
As I mentioned earlier, the minecraft.jar you use for the launcher does not matter, because it will launch whatever is in an existing .minecraft directory.
ls -la |grep minecraft
if [ -d "$MINEA" ]; then
echo "** Switching to 1.2.3"
mv $MINE $MINEB && mv $MINEA $MINE
elif [ -d "$MINEB" ]; then
echo "** Switching to 1.2.4"
mv $MINE $MINEA && mv $MINEB $MINE
And if you are looking for a *nix friendly place to play, check out http://sdf.lonestar.org/
They run NetBSD on their shell accounts, but I think their MC servers run on Ubuntu. They have 5 worlds on their main Bukkit server (currently running 1.2.3), another server running most recent vanilla version (currently 1.2.4 on a 1.1 world), and a development server for testing or fixing Bukkit plugins before updating the main server (currently running a 1.2.4 world).
I thought if I looked like one they might ignore me. Nah.
i5 650 3.2 GHz, 8 GB, nvidia GTX 750 Ti, 32" 1080p | i7-4700MQ, 8 GB, Intel HD 4600/nvidia GTX 765M, 15.6" 1080p | etc.