A
Alan
Guest
The word is that the new version, 1.8, will be launching tomorrow (or today, for those of you not in the Americas). The server currently does not support 1.8, however, so here's what you can do:
Note: If you already know this information, disregard the entirity of this post. Don't tell me you already know, as this is for people like me who've never dealt with an update before. I know there's a few of us lurking around these parts :)
How to play a previous version of Minecraft:
Since we're still testing the server, it's probably a good thing we've run into this issue *during* testing instead of after, so we all know what to expect, as well as knowing how quickly the issue can be resolved -- whether it be by way of a small patch, or a new release of the server software.
---
As for the question of whether we're still actually testing, the answer is yes. However, it's partly due to some real-life things that have come up. Real life, after all, should be addressed before anything else, right? If nothing else, it's given many of us an opportunity to decide what we're going to do, and how we're going to do it, when we go live.
Note: If you already know this information, disregard the entirity of this post. Don't tell me you already know, as this is for people like me who've never dealt with an update before. I know there's a few of us lurking around these parts :)
How to play a previous version of Minecraft:
- Start the Minecraft Launcher.
- You can elect to create a new profile (call it something like "Old Minecraft Version") or edit your main profile. The steps are the same from here.
- Upon clicking "New Profile" or "Edit Profile," you'll be greeted with a configuration screen. A little more than two-thirds of the way down the new window, you will see "Use Version" and a drop-down menu. From that list, you should select 1.7.10.
- Click "Save Profile" and launch.
- Click "Play" and continue to immerse yourself in the world of Iwaku Minecraft!
Since we're still testing the server, it's probably a good thing we've run into this issue *during* testing instead of after, so we all know what to expect, as well as knowing how quickly the issue can be resolved -- whether it be by way of a small patch, or a new release of the server software.
---
As for the question of whether we're still actually testing, the answer is yes. However, it's partly due to some real-life things that have come up. Real life, after all, should be addressed before anything else, right? If nothing else, it's given many of us an opportunity to decide what we're going to do, and how we're going to do it, when we go live.
