metaruss

I recently switched back to Cinnamon from MATE on one of my machines and found I needed to reapply this patch again.  I’ve updated it a bit to support all three modes of operation (workspace desktop preview, workspace labels, and the original useless numbers), selectable from the configuration dialog.  You can also specify the button width in label mode, which can be nice if you want control over the aesthetics.

This patch works for version 6.x of cinnamon:

• workspace-switcher@cinnamon.org.v6.patch

Download it and apply it thusly on a Debian-based system:

$ cd /usr/share/cinnamon/applets/workspace-switcher@cinnamon.org
$ sudo patch -p1 < ~/Downloads/workspace-switcher@cinnamon.org.v6.patch
patching file applet.js
patching file settings-schema.json
$

Then restart cinnamon with Alt+F2 and then “r” and enter.

This is a brain-dump of what I ended up doing to setup an “Eaglercraft Server”.  I’ve been running small Minecraft servers since around 2011.  It was just for myself and a few of my work colleagues.  I enjoyed experiencing MC coming out of beta and eventually growing up.  We ended up with two servers, the original that started in Beta1.3 became a creative server and a “newer” 1.4 server running in survival mode.  Over time, I eventually lost interest in the game but left the servers running.  Like so many kids over the past decade or so, mine inevitably got into MC in a big way and still spend time on the old servers with their friends from time to time.  I also stood up a third server for them to have a fresh start, since the old worlds are massive and had been generated using such old versions (there are some pretty weird chunk transitions in places).  One day, my youngest asked me if I could help him setup an “Eaglercraft Server”.  Boy, what a rabbit hole that turned out to be…

I am by no means an expert here, but I wanted to document what I’ve learned.  At its core, Eaglercraft is a Javascript port of the Minecraft client that can run in a web browser (I’ll leave the reason why it exists and the origin of the name as an exercise to the reader).  Since it was an unofficial port, the project came under fire by Mojang’s current owners and had to go underground to some extent.  The client is only currently available in specific versions: 1.5.2 and 1.8.8.  There is no such thing as an “Eaglercraft server”, per se.  What is actually needed is a Java Edition server configured such that:

1. It’s preferably running in offline mode so that unauthorized users can connect…ah-hem.
2. It’s reachable by Eaglercraft clients from a web browser, preferably via port 80 if possible.
3. It supports version 1.8 clients.

All of these present their own sets of problems, but all are solvable thanks to the amazingly active development community around Minecraft servers.  I am assuming that the reader knows how to administrate a Linux server and has background knowledge of operating a Minecraft server.  If not, there are lots of resources out there.  My goal here was to fill in the missing big picture around what is required.

Authentication

One can, technically, login to an “online” (officially-authenticating) server from an Eaglercraft client by going through a number of convoluted steps to acquire the necessary credentials.  Each player would need to do this on their own, which can be a bit of a pain for the less-technically-inclined.

All of that can be avoided by running in offline mode and setting up an authentication server that users can bounce-through when they first connect.  There are plugins available for forked servers such as Forge, Spigot, and Paper that implement this: nLogin can provide authentication which will then use BungeeCord to tie the servers together.  The authentication server needs to support the same client version(s) as the main server and don’t forget to turn on the whitelist for both if they are going to run offline.  The first time a player connects, they will be asked to set a password, which they then have to remember.  nLogin offers tools for administrators to reset passwords, etc.

One annoying problem is the UUID generation that nLogin does will conflict with any online Java clients coming in, which then causes conflicts in the whitelist.  nLogin has some settings for this, but each has caveats.  One workaround is after adding an online player to the whitelist, look for the actual UUID they are using in the logs and manually edit the whitelist.json file to override the generated one for that player.  You’ll have to issue a “whitelist reload” command afterwards, but they should be granted access then.  The same process needs to be repeated on the main server as well, if it is running a whitelist.

Proxy

To avoid exposing old server versions to the Internet, it is wise to put everything behind a proxy.  The PaperMC project has a lightweight proxy server called Velocity that is a good candidate for this, as it supports BungeeCord and many of the required plugins including nLogin and Eaglercraft.  The main and authentication servers can then be setup to bind only to localhost, preventing direct external connections.  BungeeGuard can also be used as a further protective step.

Note that when using nLogin, the plugin is actually resident on the proxy and not the authentication server.  This can be a little bit confusing when trying to manage the plugin from the local console.  One has to connect to the proxy console, not the authentication server console.

Server

The primary server that players will play on needs to support 1.8 clients.  There are two ways to approach this:

1. Run an actual 1.8 server.
2. Run a more modern server with ViaVersion plugins.

The first approach is the simplest, but it doesn’t scale well thanks to the many bugs present in Minecraft 1.8.  It’s fine if playing among friends that behave themselves or that all agree to use the same exploits.  It can also be more fun and nostalgic to play this way, but it can also go horribly wrong.  At the very least, use a forked server project for this.

Otherwise, it is probably better to run a newer server and support older clients via ViaVersion.  A nice compromise might be to run a 1.12 server, which predates Update Aquatic but fixes a lot of the flaws of earlier servers.  This requires the installation of the following plugins:

• ViaVersion – allows newer clients on older servers for those connecting from a modern Java client.
• ViaBackwards – allows older clients on newer servers.
• ViaRewind – expands ViaBackwards support to really old clients, including 1.8 that EaglerCraft needs.
• ViaRewind-Legacy-Support – fixes a number of glitches and bugs that 1.8 clients would normally experience.

Once everything is setup, players will connect to the proxy which will connect them to the authentication server.  nLogin can be setup a few different ways, but again be sure to turn on the whitelist.  Once authenticated, players are connected to the main server.

Wow, so it’s been almost a decade since I last posted here.  I’ve switched hosting situations multiple times in the intervening years and this site has suffered its fair share of bit-rot along the way.  I actually took it down at one point, as I assumed no one would notice.  It turns out there are a number of forums and whatnot that direct links to files in here, so I brought it back after receiving some frantic emails.  WordPress was hopelessly out of date and when I jumped to the latest release, it broke this ancient theme, a number of plugins, and there were also some problems with the DB due to its age (using a very old storage engine).  I thought all was lost, but I somehow got it going again.  I’m sticking to my guns on this highly dated-looking theme and I absolutely hate the new WordPress editor, but I found this plugin called “Classic Editor” that has saved the day.

So yeah, why am I even posting on here when I know no one will ever read it?  Mostly for my own posterity, I guess…and maybe the web crawlers will find these posts and show them on page 6 in their search results.  I’ve learned a valuable lesson over the past couple of decades: letting a few huge social media corporations hoover-up all of the discourse on the Internet and move it into their walled gardens has effectively ruined it.  A lot of the hobby-related discussions that had moved from email lists into Internet forums back in sepia-times have now moved into Facebook or Reddit.  Many of the forums still physically exist, but they’re mostly cobwebs and crickets and/or a fire hose of spam with maybe a few gray beards lurking here or there.  Facebook Groups are a terrible replacement for something like a forum, as it’s impossible to find anything and the same questions get asked over and over.  Alas, this is where we are now and I don’t see it ever turning around.

I stopped using Twitter about 5 years ago, as my feed slowly morphed into an AI stream of consciousness.  I was never into micro-blogging, but I used it as an RSS feed of sorts for the topics and publishers I was interested in.  Since it was no longer capable of performing that function, I started playing around with things like Mastodon…even setting up my own instance.  It kind of did what I wanted, but like so many before it (Diaspora, GNU Social, etc) it didn’t really work because no one was there generating content.  It’s the age-old problem of adoption.  That all changed in 2022 and now I find Mastodon does pretty much what I want thanks to relays and folks just plain-old posting there.  I do have a Bluesky account and that place feels a lot like Twitter did back when it was useful.  But I think we know the inevitable result will be the same once the VC money runs out.  I’ve also been playing around with Pixelfed and, thanks to the train wreck over at Reddit, Lemmy.  Something to be a bit excited about, at the very least.