Minecraft @ 3decibels.net

Hi All,

I'm currently in the middle of moving. Since the server is hosted on physical hardware it will be down until I complete the move and reassemble all my tech gear.

Thanks!

I might just leave it as-is for now. I'm fairly sure our daily active user count has finally dropped to 0 and has been there for several weeks.

For mapping I was looking at BlueMap as it seems to be the hot new replacement for the software we used before.

I took some time today to look at installing a newer JDK onto the Minecraft server and was able to get it working.

The big question now is what to do about the map. Minecraft 1.21 features changes to terrain generation. In the past when we encounter updates like this we have tended to wipe the map and start fresh as not to have discontinuity between old and new terrain generation (ex: a forest generated before the update is suddenly next to a giant mountain 100 blocks higher).

Are there any preferences on what to do here? I know hardly anyone uses this server anymore but I figured I'd ask before making a decision that might go against the wishes of those who do still play.

At some point the Minecraft server builds started requiring Java 21 to run. The OS our server is running on only has Java 17 available. This is going to prevent me from updating Minecraft beyond the version currently installed (1.20.4) until I can figure out a nice way to get the Java 21 runtime onto the system. I have no ETA for this.

The short answer is that the software we used to create the maps no longer works and is effectively dead. It will take some effort to rebuild the map creation process around something different and I just don't have the energy to do it at the moment.

Someday I will hear the map calling to me and decide to answer its plea for help, but I can't really say when that day will be. Knowing people are waiting for it does help a little

I checked the logs and there was a random person who logged in for the first time on Feb 13th. They appeared at spawn and... Well, the logs tell the tale:

Quote2024-02-13T03:33:23,143 INFO  [server0]: tevapharm joined the game
2024-02-13T03:33:23,146 INFO  [server0]: tevapharm[/10.88.99.1:50873] logged in with entity id 287549 at ([3decibels-1.19]107.5, 66.0, 347.5)
2024-02-13T03:33:53,160 INFO  [server0]: tevapharm has made the advancement [Diamonds!]
2024-02-13T03:33:53,403 INFO  [server0]: tevapharm has made the advancement [Acquire Hardware]
2024-02-13T03:34:30,419 INFO  [server0]: tevapharm has made the advancement [Stone Age]
2024-02-13T03:34:31,701 INFO  [server0]: tevapharm has made the advancement [Ice Bucket Challenge]
2024-02-13T03:36:06,955 INFO  [server0]: tevapharm has made the advancement [We Need to Go Deeper]
2024-02-13T03:39:23,235 INFO  [server0]: tevapharm has made the advancement [Hot Stuff]
2024-02-13T03:54:37,835 INFO  [server0]: tevapharm lost connection: Disconnected
2024-02-13T03:54:37,858 INFO  [server0]: tevapharm left the game

They haven't been back.

Now, normally I would offer to restore your area from backup but I see it's been a few weeks and you've been on since your initially discovery, so I assume you're probably not interested in that. Is there anything important you lost that I can replace for you?

On a separate note, we're in an era where all Minecraft servers on the net are routinely scanned and indexed by 3rd parties who make the details available to anyone who wants to look. Public servers are sadly often visited by people only looking to cause trouble and with a small server like ours it's very difficult to catch them in the act. I also don't like the idea of imposing a static player whitelist, I'd rather be able to welcome anyone who wishes to join.

What I would like to do is create a form on the website where a player can enter their name and be immediately added the whitelist. This would keep out the random griefers because the server would show up as using whitelisting but would enable anyone who learned about the server organically to join. Griefers using minecraft search engines wouldn't be able to find the form because they only know the service IP, not the FQDN (assuming I remove it from the MOTD of course).

Since you're someone I know and a longtime user of the server I have decided to deputize you as a server OP. In addition to the normal operator tools available in Minecraft you also now have access to the CoreProtect plugin which provides block level event logging, rollbacks and restores. Use this power as you see fit.

Edit: Gave you global forum mod too. You can edit your user profile and enter your cheese of choice under "Custom title"

Surprise! Now it's on 1.20.4!

I guess by "very soon" I meant "two weeks".

1.20.2 is go!

I have eyes on it, waiting for a release on the server software we use. Should be very soon.

https://purpurmc.org/downloads/1.20.2

Wireguard. Always Wireguard.

Wireguard yearns for a static NAT but I don't want to configure a static NAT. Every tweak I make brings me closer to a solution but it's not there yet.

Minecraft 1.20 is live continuing to use the 1.19 world. Mapping is still not finished, and now that the software we used is now officially end-of-life it's going to take an overhaul to get something back up and running. I have an idea of what to use as a replacement, but I can't say when I'll be able to get around to implementing it.

For those of you still around, have fun!
--3dB

Yep, did the version bump, seems like everything is good!

I finally figured out what the longstanding issue with Wireguard was and it should be fixed now.

The mapping software never updated to 1.19 (even their 1.18 was half finished) and the author finally threw in the towel. There are newer, shiner options available but their implementation is contingent on me gaining enough interest to work on them. No idea when that will be back.

Wireguard issue. I moved over to it from OpenVPN and I'm not totally impressed with it. It likes to randomly go dead sometimes.

Should be fixed now.

Edit: Also be aware, the MC server we use hasn't been updated to 1.19.4 yet.

Yep, sorry about that. Sometimes dhclient gives up the ghost and I've been having trouble figuring out why, though I think I found my answer now. Should be working again!

Quote from: smithadmin on June 12, 2022, 07:31:11 PMI'm having difficulty connecting to the server.  Error message is that the connection is timing out.  Thoughts?

Sorry about that, Wireguard broke unexpectedly. It's fixed now, I'm going to keep my eye on it to see if it happens again.