the current minecraft version is b1.1_02.jar

the next version is b1.2_01.jar.

the version will change at midnight central time on 2026-10-06

this version was posted on 2026-09-29

the server is currently: running last checked: 2026-09-30 01:10:04.251550

join the discord!

what is this

cassandracraft is an experimental minecraft server run by cassandra focused on historical minecraft versions. it started on minecraft beta 1.1_02. the version upgrades automatically every tuesday.

how to play

1. install java 8
2. Download and run the betacraft launcher v2. make sure you download v2 (alpha). scroll down.
3. Under the "accounts" tab hit "add account" and follow the directions to connect your microsoft account.
4. Under the "instances" tab hit "add instance." give it a name, select the current minecraft version indicated above, then hit create.
5. press play! Select "multiplayer" from the main menu and put in this address, minecraft.blood.church.
6. when the version updates, go to the instances tab, select your instance, right click, and hit "edit." in the "version" tab, select the new version.

why did you do this?

my girlfriend has never played minecraft, so i bought it for her. i watched her play a little bit and realized how weird it was to have your first experience with minecraft be the minecraft we have in 2026. i'm not even that much of a hater of current minecraft, but the minecraft i fell in love with was minecraft alpha and beta. i think seeing the game as it was back then is important for understanding why it's so great.

how did you do this?

historical server and client versions are archived on omniarchive. most hotfixes and minor versions have been omitted; where a version has hotfixes or minor versions, the latest has been selected. this is to maximize fun by avoiding bugs and boring bugfix-only patches. most prerelease versions have also been omitted, except for a few kept out of historical interest. alpha is excluded because multiplayer was only fully functional starting with beta,

i run the server on an ubuntu digitalocean droplet. i have a big folder with all the jars in it and a file called jars.txt that lists them in the order that they should be played. i have a cron job set up to run a messy python script i wrote which reads the jars list, gets the currently running version from a text file, then replaces the server jar with the new one. the server itself is running as a systemd service, so the cron job actually runs a little bash script which gracefully shuts down the service, runs the upgrade process, and then starts it back up again.

this page is generated by another messy python script using handlebars templates. that one is run on a cron job every minute so the server status should be up to date.

how did you do this?

historical server and client versions are archived on omniarchive. most hotfixes and minor versions have been omitted; where a version has hotfixes or minor versions, the latest has been selected. this is to maximize fun by avoiding bugs and boring bugfix-only patches. most prerelease versions have also been omitted, except for a few kept out of historical interest. alpha is excluded because multiplayer was only fully functional starting with beta.

i run the server on an ubuntu digitalocean droplet. i have a big folder with all the jars in it and a file called jars.txt that lists them in the order that they should be played. i have a cron job set up to run a messy python script i wrote which reads the jars list, gets the currently running version from a text file, then replaces the server jar with the new one. the server itself is running as a systemd service, so the cron job actually runs a little bash script which gracefully shuts down the service, runs the upgrade process, and then starts it back up again.

this page is generated by another messy python script using handlebars templates. that one is run on a cron job every minute so the server status should be up to date.