This should download “Pixelmon-1.7.10-3.3.7-universal.jar” or similar.

3. Minecraft Forge: http://files.minecraftforge.net/ – open that link and download the “Installer-Win” version that matches the version of the Mod you are wanting to run – I wemt for Pixelmon 1.7.10 above, so I need the same version of Forge to run that – clicking the “*” link just after the “(Installer-Win) link as shown here should give you a direct download to the file you need:

Once that’s downloaded run the exe and you should see a screen like this:

Leave the default “Install client” selected and take a note of the directory mentioned here (C:\Users\don\AppData\Roaming\.minecraft in my case) – this is your Minecraft install directory and you will need to know it later.

Install Java if required:

If you get the error message “This application requires a Java Runtime environment 1.6.0”, you need to install a Java runtime. Ok’ing the Launch4j message box should open a link to the Oracle website where you can install the latest version of Java (you don’t need 1.6 specifically).

If during the Forge installation you get the message “You need to run the version 1.7.10 manually at least once”:

then start-up Minecraft, click on “Edit Profile” and select “release 1.7.10” from the “Use version:” dialog as shown here:

This step is needed as Forge creates a modified version of this specific version of Minecraft – running it once will make the Minecraft Launcher program download all of the files that are required for this version to work on your machine, which Forge will then use. Start up a normal Minecraft game using 1.7.10 then exit, and restart the Forge installation – it should work now. If you have played 1.7.10 before you should already have everything already though.

Once that’s done you should see a message saying something like “Successfully installed client profile Forge for version…” etc. Ok that and launch Minecraft again. You should now have a new Profile called “Forge” (see the dropdown box in the lower left corner), which you can select and Edit like this:

You need to run Minecraft with the Forge profile whenever you want to play with a Mod, but you can select your normal profile to go back playing normal Minecraft.

Again, note that Game Directory location, and open it up in Windows Explorer:

There is no “mods” directory there yet – this is created by Forge the first time it runs.
Click “Play” with the Forge Profile selected and Minecraft Forge should start-up and create the directory for you:

Now exit Minecraft and all you need to do to install Pixelmon Mod is to copy the Pixelmon-1.7.10-3.3.7-universal.jar file in to the mods directory, restart Minecraft using the Forge profile, and that should be it:

You can see there are now 4 mods loaded, and clicking on the Mods button will show the details – all done!

Update: my daughters PixelMon screenshot gallery…

Flying on a Staraptor

Army of Donphans

Charizard training session

Talking to Farfetchd

Walking an Arbok

Coming soon, a write up on setting up a server running Minecraft Forge with Pixelmon on Ubuntu Linux…

Bans player from the server with the message “Banned by admin”, banned players who attempt to connect are presented with the message “You are banned from this server!”

ban username

pardon

Removes the specified player from banned-players.txt, allowing them to connect to the server again

pardon username

ban-ip

Bans an IP address from the server, the full IP address must be specified; wildcards are not valid. Players who are banned through this method will see “Your IP address is banned from this server!” when attempting to connect

ban-ip ipaddress

pardon-ip

Removes the specified IP from banned-ips.txt, allowing players with that IP to connect to the server again

pardon-ip ipaddress

op

Writes the players name to ops.txt, giving them access to the op commands

op player

deop

Removes a player from ops.txt, revoking their access to the op commands

deop player

tp

Moves the first player specified to the location of the second player specified

I was asked to set up some Home LAN Minecraft and Pocketmine Servers for my children, so they can play at home and online with their friends in a safe/private environment – I was also interested in the geekier side of setting these servers up and seeing what all the Minecraft fuss is about 🙂

This post covers:

setting up a “normal” Minecraft Server on Linux

setting up a Minecraft Pocket Edition Server on Linux

getting started with the Linux “screen” command to manage multiple Minecraft Server processes

Setting up a normal Minecraft server on Linux (and I’d imagine any other OS) is very easy – you just need Java and the minecraft server jar file which you can get here:

And as that page says, just sort out Java then kick off the process like this:

java -Xmx1024M -Xms1024M -jar minecraft_server.jar nogui

Making sure you change the minecraft_server.jar to match the name of the file you downloaded (e.g. minecraft_server.1.7.4.jar or whatever).

I originally put that command in a script and started it with nohup, but realised that you then lose the ability to interact with the process, so I have changed my approach and use the screen command which is much better – see the notes below on how that can be done, it’s easy and very useful.

Also, I think it’s safer to stop your Minecraft server/world cleanly by doing “stop” in the console, rather than Ctrl-c or killing the PID – after doing this I stopped getting these error messages in the console output:

but this really didn’t work for me and led to a catalogue of vague errors and a whole load of googling which took me back to the olden times of fighting with make, configure, libraries, conflicts, missing tools and config files and installing all sorts of things based on vague hints from obscure error messages found in cryptic log files… you get the general idea I guess.

It has a simple and happy ending (below), but my experience started off something like this…

And that was after running the installer provided on the homepage and checking the dependencies were all there… so I debugged the steps in that script and was then on to the log files… where one thing led to another for quite a while… some of the more memorable ones are…