Minecraft clone Archives

1. Archives
2. Root
3. TI-84 Plus CE Programs
4. TI-84 Plus CE Assembly Programs
5. TI-84 Plus CE Assembly Games
6. IcyCraftv2134.zip

Reviews

Versions

1. IcyCraft CE v2.13.4 (published 1 year ago; 2019-08-25 22:49 UTC)

In Part 1 you learned how to set up both an “off-the-shelf,” or unmodified, Minecraft server in Docker and a Spigot server in Docker. This is the first step to building your own Minecraft plugins that can take advantage of the many services, including Watson cognitive services, available on IBM Cloud, IBM’s platform as a service (PaaS) environment. Using these services will make your game experience smarter and more enjoyable.

But you can’t just jump over a mountain in one leap. You need to complete a few more steps before you can build plugins that can use the Watson services. In Part 2 we’ll take you through the next step in setting up your local development environment: setting up Eclipse, then developing, building, and exporting your own server-side Minecraft plugin into a local Docker image.

We’ll do all of the development in the Eclipse integrated development environment (IDE). Eclipse is a free, open-source development environment for Java® and a number of other languages. You can choose almost any Java IDE for Minecraft plugin development, but Eclipse is commonly used in the Minecraft development community among those who use an IDE.

Set up Eclipse in Ubuntu

To use the Eclipse IDE, you need to first install Java in your Ubuntu Linux environment. Eclipse is not only an environment for developing programs in Java, but is itself a Java program. The command to install Java should look familiar because we used it in our Dockerfiles in Part 1. However, this time you need to run the command at the command line of your Ubuntu Linux installation:

Once you’ve successfully installed the JDK version 7, you have a choice:

• If you’re more comfortable using the Ubuntu GUI, go to the Eclipse downloads page and select the Eclipse Mars release, then download the installation file for Eclipse. The installation file is in the form of a Gzipped tar file. Double-click the tar file in the Ubuntu file manager to open it with the Archive Manager. Then use the file manager to extract the contents of the file to a directory named “eclipse”.

• If you’re more comfortable using the command line, issue the following commands one at a time:

Regardless of how you downloaded and installed Eclipse, you start it the same way. Assuming that you installed it off of your home directory, type the following command at the command line to start Eclipse:

Once Eclipse starts, you’ll be asked whether you want to create a new default workspace or use an existing one. Go ahead and create the default workspace in the directory it specifies.

On the Eclipse Welcome screen, click the Workbench icon in the upper right corner to open the workbench.

You see the Eclipse Workbench:

Import the archive file

We’ll use the Eclipse Project import feature to import a Project Archive file that includes our example. Projects in Eclipse are simply directory structures in your workspace directory. A Project Archive is a special zip file format for Eclipse that allows you to share your completely configured projects with others. Once we bring the project into Eclipse, we’ll walk through the example code. The archive import file is located in the root of the minecraft-project directory that you cloned from GitHub in Part 1, so if you’re trying to jump into this tutorial without following all the examples in Part 1, you’ll need to go back and perform that clone.

1. Select File > Import from the menu at the top of the Eclipse Workbench.
2. Select General > Existing Projects into Workspace, then click Next.
3. Select Select Archive File, then click Browse.
4. Navigate to the directory that you cloned to (probably your home directory, although that depends on what you did in Part 1) and open the minecraft-project directory. Select SpigotPlugin.zip and click OK.
5. Click Finish.
6. In the Workspace, you’ll see a red exclamation point (!) beside SpigotProject. That’s okay — it’s just alerting us that we need to patch up the classpath to point to the spigot-1.8.3.jar file so that the Java code for our plugin will compile (because our code relies on the Spigot APIs, we have to import those APIs). Select SpigotPlugin.zip in the Project pane. Left-click (on other platforms, Alt-Enter or click while holding down the Control key) and select Properties from the pop-up menu, then select Java Build Path. Select the Libraries tab.
7. Select Spigot1.8.3.jar, and click Edit.
8. Double-click on minecraft-project, then select Spigot1.8.3.jar in the next pane. If you’re following closely, you may be worried that this Spigot JAR file doesn’t match the level of the Spigot JAR file that we built in the previous example (which was at level 1.11.2). Actually, because we’re using this JAR file only to allow our code to compile, it’s okay if it’s a bit back-level — the API hasn’t changed in awhile. If, in your own code, this does become a problem later, follow the instructions at the Spigot Build Tools wiki to locally build a new spigot JAR file and replace the one you downloaded from GitHub.
9. Click Apply, then click OK, then OK again.

At this point, your workspace should show the SpigotPlugin project with no red exclamation points next to it, which means you’ve resolved the problem and we can get on with our example.

Build plugins for Minecraft

The Spigot plugin API is actually pretty simple. If you’ve ever used Java for other types of server-side programming, like building servlets, you’ll find that it’s a straightforward example of the same principles. The reason we’re installing a specific JDK (Java 1.7) is that plugins in Minecraft (or at least those using the Bukkit APIs) must be built on Java 1.7. Otherwise, you get strange class mismatch errors on the server. This may change in the future, but for now, it’s best to stick with Java 1.7 for your development.

The HelloWorld class

Let’s start by looking at a simple plugin for Minecraft that’s the equivalent of the Hello World program in any programming language. We’ll use this file to review some of the simpler features of the Bukkit API.

1. To start, bring up the plugin source code file from the Eclipse Workbench project pane by clicking and expanding SpigotPlugin.
2. Click and expand src, then expand the com.ibm.minecraftplugin directory.
3. Click HelloWorld.java.

Let’s look at the contents of the HelloWorld.java file:

There are two simple concepts you need to understand. First, building a plugin is as simple as extending the class, so all of your plugins will be subclasses of . Second, you’ll need to implement two methods in each plugin class:

• is an event handler that’s called when the server loads the plugin. You perform any necessary setup for the class in this method (for instance, setting up a database connection). We’re applying a standard debugging method, which is to log some status information to the logger so that when the plugin is loaded, you can see results in the log output.
• is called each time a user issues a Minecraft command with . Each plugin must determine whether the command can be handled by the plugin (which is as simple as comparing the name of the command to a corresponding name the plugin can handle) and then perform any actions that are necessary.

In our example, once we have validated that the command can be handled by the plugin, we simply send the message “Hello Everybody!” to the sender of the command. It’s trivial, but it’s enough to see how the concept works. If you’d like, you can change either the log message that the method writes, or the message that the command sends back to the user to customize your plugin.

Plugin.yml file

The final piece of configuration required for a Bukkit plugin to work involves the Plugin.yml file. This configuration file describes your plugin to the rest of the framework. It’s written in YAML (Yet Another Markup Language) like many other configuration files that you’ll see in this tutorial series. One thing to keep in mind is that you cannot use tabs in YAML plugin files.

To examine your plugin.yml file, double-click the file inside the SpigotPlugin Project. The contents of the file are:

As you can see, it’s pretty simple: you specify the name of your plugin, the main class, and the version at the top of the file. Any commands that are handled by your class must be listed (indented one space) after the section. In the example here, we’re showing only the section of the command, but there are other sections that you can use if you examine the Plugin YAML documentation.

Test locally

Now that you’ve written the code of your first plugin, you’re ready to export it and try it out.

You can skip the next section on exporting a JAR file if you just want to use the pre-built HelloWorld.jar file example provided. If you’ve not made any changes to your code, that’s the fastest option. If you’ve made any changes, you’ll need to follow the steps in the next section to try out your new code.

Export your JAR file

To export your JAR file, complete these steps:

1. In the Workbench, select the SpigotPlugin project, and left-click to bring up the menu, then select Export.
2. In the Export dialog, select Java > JAR file and click Next.
3. In the JAR file specification dialog, click Browse.
4. In the file selection dialog, navigate to the spigot-plugin subdirectory of your minecraft-project directory, and select HelloWorld.jar, then click OK.
5. Back in the JAR file specification dialog, click Overwrite existing files without warning, then click Finish.

Your new JAR file has now replaced the old one. It’s time to see if your code works!

The new Dockerfile

Just as in the last example, we’ll use a new Dockerfile that will build the example inside a Docker image. First, open a second terminal window in Ubuntu — this is so you can run Docker commands while Eclipse is still running. In the new terminal window (assuming you’re in the home directory and that’s also where you cloned the minecraft-project directory), type the following two commands:

You’ll see the new Dockerfile for this example, as shown below. Take a moment to read through it and see if you can spot the differences from our last example Dockerfile.

As you probably noticed, this is very much like the 0.0.3 example Dockerfile we looked at in Part 1 of this series, but with a couple of differences. First, this one creates a new directory called “plugins”. Second, it then performs a new command in Docker that you’ve not seen: .

The command takes a file from your local (host) directory and copies it into the Docker file — this is cool! That’s exactly what we want in our example — we want the ability to change our plugin file while leaving everything else alone. However, unlike the command, which runs every time you start a new container with Docker , the command runs only when you do a Docker . That means that if you make changes to your plugin, you need to rebuild your image. For this example, let’s build our new image for the first time by typing the following command at the command line:

Just as you did in Part 1, replace

Now that you’ve built the new image, it’s time to run it! To do this, type the following command:

Because you’re starting the Docker container at the same port as previously, you shouldn’t need to change the configuration of the Minecraft client. You’ll find the first indication that your plugin is working in the on-screen logs of the Minecraft server — look for a line like this:

Once you’re sure that the server has started successfully, start up the Minecraft client, connect to your server, and then inside Minecraft type:

Your Minecraft command screen should look something like this:

If you see the message “Hello Everybody” (or whatever you changed your message to), it’s working. Congratulations!

Conclusion

In Part 2 of this series, you learned how to build a simple server-side plugin for Minecraft using Eclipse, and how to run it on Docker. In Part 3, you’ll take your plugin to the next level by running it on the web in IBM Cloud.

FANDOM

---

YogLabs

YogLabs is a stunning facility, set into a mountain range, that has been built for Simon and Lewis. It houses them and their experiments in order to test awesome, new, fun, and potentially deadly Minecraft mods.

The entrance to the facility is a large vault door, rumoured to open utilising some of the parts from the infamous Ugocraft mod, that has a much smaller door hidden inside.

There is a Testificate guard that sits on a balcony that protects the facility from intruders. There are several Testificates in the lobby who act as reception staff. 

DescriptionEdit

There is an extremely pixelated periodic table and the molecular structure of caffeine on the walls along with some other unidentified photos. There is a door leading to a nether portal (which has since been turned into Simon's office; this is still a work in progress despite a few episodes starting within Simon's office), and a door leading to somewhere unknown. There also appears to be a balcony above the reception staff that looks very different from the rest of the lobby. There is a door that leads to the testing chambers, and another door next to it which leads into more test chambers.

There are colour coded pathways that lead to different testing groups. There are many gates and doors in the hallway, which contains many robots such as the Lifto-Bot (which lifts things such as logs) as seen in the first YogLabs video. Room apparently has a minecart system in the ceiling. First chamber is a room filled with transparent blocks. It has a minecart, suspended water, a cactus, a ladder, torches and trapdoors, the bottom of the room is made out of transparent blocks and the Void can be seen. Further down the hallway, there is a garage.  There are 2 cars parked inside, 1 made out of brick and 1 made out of an unknown material, possibly iron, and a wall with glowstone, leaves, buttons, glass, ladders, cobweb, wallpaper, torches and redstone torches, with a lever which activates a shutter which destroys the aforementioned materials.Next door is a Piston door with the words "Project Woodchuck" written on a sign above it. Inside, contains a sign saying "Caution: Temporal Shield ACTIVE No watches!!!" on a Lapis Block. On the floor behind the sign are yellow and black caution strips, in front of it, is a blue floating substance that resembles a portal. When entered, it turns back time apparently, by teleporting the user through a different timezone while still being in the same room, somehow, with the use of the portal like substance. Inside, is a strange room with a huge hole in the middle with glass and tons of redstone, there is also a clock on a stick, and two amplifiers. Apparently, it changed the time to lunch time.Further down is Project Lime Jelly, it has a piston door. The contents of the room are unknown but according to Lewis, it produces jelly. Next room, is Project Snuggy, it requires Maximum Security Clearance. Inside of the room, is a mutilated clown face and a sign that tells you to "Rate your terror". Below the sign is a billboard, with several notes on it. The clown face has a mouth, inside of it are 2 buttons. When a button is pressed, it starts chewing. The room is currently off limits until it is shut down or replaced.

In front of a Lifto-Bot, which is carrying logs, is a room with a shutter door, inside is a large room, with several Testificates and several Barbecue Grills. In here, there are display chests with plates, forks, knives and spoons, which oddly resemble Pressure Plates, hoes, swords

and shovels. There is another display chest which has spices and napkins. Near the BBQ Grills in the centre, is five display chests with pork, beef, charcoal, fish and chicken. There are many tables located throughout this room, and most of them appear to have their own grills. The room was destroyed in a fire after Simon grabbed a flint and steel and set the place on fire. He died in the fire due to safety protocols

being offline, leaving Lewis to put out the fire himself. Lewis was unable to do so, and ran out, resulting in the casualties of the Testificate scientists and security guards dining there and the loss of thousands of pounds in stolen government money due to the damage. Fire might have also possibly spread out of the room and destroyed the Lift-O-Bot outside and the garage, but it was probably put out before then. Further down, is a room labeled "Project Triple-Mint." It contains several Scrubber-bots and clocks that are used as targets. There is a chest inside that contains Scrubber Bot building kits but is currently empty for unknown reasons, presumably, they were used to create the ones seen in the video. Next to Project Triple-Mint is a shutter, which opens up to a dark room, which contains a death pit, with trip-wire that triggers dispensers that throw out a hybrid of an owl and a human. The experiment appears to have gone horribly wrong, and the volunteers appear to be very badly mutilated. They are presumably kept there to study why they are so violent and have a craving for brains. Maybe it's because of the experiment making them nearly brain-dead and they want to get their revenge, or it's natural. Either way, they're creepy. There is a cardboard box with swords in it and further in, there is a door which leads to a long hallway, which has a door at the end of it. Through the second door is a tall room with a box and a crafting table, with a huge garage door that is opened by a lever that is very high up.

Further down, there is a piston door with a sign above it saying "Project Gouda". It's contents are unknown, and it isn't mentioned what is inside. Next to it, is another unknown room called "Project Brink." Both are not mentioned in either episode and is only briefly seen in episode 2. Next to Project Brink, is the break room. It has three tables and chairs for people to dine in. There is a highly advanced coffee machine that actually produces coffee, although it is currently out of order, and the break-room presumably serves sausage sandwiches with a choice between a red sauce, brown sauce or no sauce at all. There is an arc which leads to an unknown room, possibly a kitchen in which the aforementioned sausage sandwiches are prepared.

The coffee machine has been used to disinfect the zombie outbreak of YogLabs at one point, but was not compatible with dwarf DNA, so it acted more like a drug to Simon. The first time the coffee machine finally worked, blood leaked into it. This was caused by the mad cow disease spotted in the YogLabs Green Pastures. The machine has also been used to eliminate Testificate workers that were slacking off by thinking they could get free coffee. During the YogLabs space program, aka YASA, an alien disease infected the coffee machine, creating green sludge, that was filled with metal-eating worms. They then grew up and started devouring YogLabs, so Lewis was forced to release a 3-headed giant Creeper from Mars. The YogLabs coffee machine has never successfully produced real coffee.

• Note: Please understand that the server labelled "We have no idea what this one is for sorry" Is currently unknown. We alert you that, though we have no idea what it is for, we promise you it is very important. And has absolutely NOTHING do with the secret missiles aimed at the government that we DO NOT have. Please, do not detonate, cut, or re-wire the server. We honestly have no idea if we'll blow up or not if you do.

Even further down, there is a space auto control room. It is a large room filled with computers and a large countdown timer on the wall. Also on the wall are several large computers showing images of what appears to be the Solar System. There is  a "SkyLadder" which launches people into space. There is a sign in front of it saying "SKYLADDER, for trained individuals only!".The sky ladder leads to a secret spacebase which grows and tames enderdragons.Near the side there is a spaceship launching bay with a builder funded by NASA. Yoglabs successfully made it to the moon, leaving behind a famous mark. They also made it to Mars where they discovered the alien root of creepers.  The back entrance to the labs is a hole on top of the hill which drops you down into the air-vents. This route was taken by Lewis and Simon when Lewis lost the keys to the big main door. The duo got to see the cleaning maids at work in the break-room, then they took two out side using teleporters to go on a monster hunt. Both maids are now missing. The remaining Maids turned out to be government agents that took control of the YogLabs. After messing around with Lewis' company car (a very nice looking BMW), the duo armor up and raid the labs. After blowing up the main door with grenades and a rocket launcher, Honeydew died due to a rocket launcher misfiring. After he had respawned, the two destroyed the mob spawners then proceeded to the security room to activate the backup power generators, to rescue the Testificates from the Medbay. The Maids apparently escaped using the SkyLadder, but reports haven't been confirmed.

The Yoglabs genetics lab was used to take DNA from donors, and extract them into eggs using a centrifuge. Simon successfully cloned himself using this process. Lewis snuck a computer chip into Simons clone when he wasn't looking, allowing him to program the clones mind. It is unknown where the clone went, but the room was changed into a torture room.

After having their gun licenses revoked following the raid (in which the two showed just how inept they were at handling firearms), they were greeted by Dr. Testificate MD, who told them that they needed to re-take their basic firearm and combat training. This involved going into a sophisticated computer simulation, in which they had to kill ten hordes of Nazi zombies. Lewis died just before the end of the simulation, however Simon made it all the way and was granted his second gun license (even though he had stolen a Desert Eagle after the YogLabs raid).

Many of the recently revealed projects involve new weapons of various forms, to aid in the fight with the government. These include Chemical X, a formula that turns mobs into buffed, giant, incredibly dangerous new forms, and 2 forms of exploding pig launchers, the regular and Nyan Pig versions. There is a maze of inter-dimensional gateways riddled throughout YogLabs from research into said doorways. Deep below YogLabs lies Deep Search III, a highly top-secret section of YogLabs housing a mysterious underground pyramid of sorts, in which lies a Stargate. Using this, Lewis and Simon have so far gone to Rssumba, a desert world filled with giant bugs, and a paradise island filled with deer and women. A day afterwards Bixby resigns from the project due to him having his "hands full at the moment." A research team was then sent to investigate the planet Cuthula. After 3 research teams and 64 Honeydew clones were sent, only Honeydew clone 107 returned, insane and broken he was then recycled. Deep search lll and sub levels 42-65 were sealed with ferrocrete and the stargate project was abandoned. Deep Search III is known to practice slave labour on innocent Testificates. There is a camp on Rssumba, consisting of towers, and borderland weapons. The Holo-deck contains a gas containment and a simulation hall in which Simon completely failed his fire test.

Recently, a conspiracy to take over YogLabs was discovered by both Simon and Lewis while they infiltrated the staff Christmas party. The perpetrators, Gosencrantz and Rildenstern, planned to infiltrate the CloneSec and kill the duo's clones, thus making them mortal. The CloneSec room contains all of the players' clones, the source of everyone's respawning ability. Discovering Simon's clone already dead and having saved Lewis' clone, Simon pays the ultimate price for immortality - death. Simon takes his clone's place in the vat and is cryogenically stored for future cloning.

B SiteEdit

In Voltz 25 - Retribution, Simon, Lewis, and Duncan discover that Ridge was getting all his weapons from an abandoned YogLabs B site which handled all the eviler operations (even though the main YogLabs is evil enough already). The B site is later blown up by Ridge's self-destruct, however, Duncan manages to salvage a lot of the missiles.

Episode GuideEdit

Main Channel — YogLabs
Video Name
Minecraft Mods - YogLabs Part 1 - Welcome to the Facility	Watch
Minecraft Mods - YogLabs Part 2 - Having a BBQ	Watch
Minecraft Mods - Spacejump Program - YogLabs Part 3	Watch
Minecraft Mods - Little Maids Mod - YogLabs	Watch
Minecraft Mods - BMW Car Mod - YogLabs	Watch
Minecraft Mods - Ferullos Guns Mod - Taking Back YogLabs	Watch
Minecraft Mods - Zombiecraft - YogLabs	Watch
Minecraft Mods - Galacticraft - Lift Off! - YogLabs	Watch
Minecraft Mods - Galacticraft - Mars Explorers - YogLabs	Watch
Minecraft Mods - Better Animations - YogLabs	Watch
Minecraft Mods - Creeper Splicing Mod - YogLabs	Watch
Minecraft Mods - Mutant Wrestling Mod - YogLabs	Watch
Minecraft Mods - Pig Space Program - YogLabs	Watch
Minecraft Mods - Nyan Tornado - YogLabs	Watch
Minecraft Mods - Hats Mod - YogLabs	Watch
Minecraft Mods - Dimensional Doors - YogLabs	Watch
Minecraft Mods - Kung Fool - Yoglabs	Watch
Minecraft Mods - Fight Night - Yoglabs	Watch
Minecraft Mods - Buy Kea - YogLabs	Watch
Minecraft Mods - Pig vs Cart - YogLabs	Watch
Minecraft Mods - Cloning - YogLabs	Watch
Minecraft Mods - Cannibal Cows - YogLabs	Watch
Minecraft Mods - Iron Dwarf - YogLabs	Watch
Minecraft Mods - Bad Trip - YogLabs	Watch
Minecraft Mods - YogLabs: A Bigger Boat	Watch
Minecraft Mods - Sokoban - YogLabs