←back to thread

Show HN: Pumpkin – A Modern Minecraft server written in Rust

(github.com)
419 points alex_medvedev | 4 comments | 15 Oct 24 09:18 UTC | HN request time: 0.682s | source
Show context
alex_medvedev ◴[15 Oct 24 09:18 UTC] No.41846637[source]▶
Hello. I recently developed Pumpkin, Its a efficent and fast Minecraft server completely written in Rust from the ground up, Check it out :D
replies(2): >>41848101 #>>41848102 #
lesuorac ◴[15 Oct 24 12:58 UTC] No.41848101[source]▶
> What Pumpkin will not

> Be a drop-in replacement for vanilla or other servers

It seems to me that unless it's a drop-in replacement its not a Minecraft server? Akin to how say an Uno deck isn't a drop-in replacement for a Hearts deck but still both card games but not both Uno decks.

Or is it just meaning that Pumpkin (besides the network) do things differently than vanilla and so you might not be able to open a vanilla created world using Pumpkin?

replies(3): >>41848586 #>>41850403 #>>41851119 #
looperhacks ◴[15 Oct 24 13:49 UTC] No.41848586[source]▶
The common problem with Minecraft server implementations is that they are not bug-for-bug compatible, which will lead to certain techniques (especially redstone contraptions) breaking. The technical Minecraft community depends on many implementation details which not all servers support
replies(2): >>41849631 #>>41850516 #
Scaevolus ◴[15 Oct 24 15:31 UTC] No.41849631[source]▶
In addition to the hundreds of blocks and mobs that would need to be implemented properly and rarely are, the lack of mod support is a killer.

The only "complete" reimplementation of Java Minecraft that I'm aware of is Bedrock.

replies(1): >>41849655 #
1. dmonitor ◴[15 Oct 24 15:34 UTC] No.41849655[source]▶
Far from it. The versions lack a lot of parity and Bedrock is called "bugrock" by the community for a reason
replies(2): >>41849927 #>>41854034 #
2. Scaevolus ◴[15 Oct 24 15:59 UTC] No.41849927[source]▶
I edited in scare quotes for "complete" to make that clearer, but I mean in terms of at least having matching blocks/mobs despite many differing details.
3. lupusreal ◴[15 Oct 24 23:08 UTC] No.41854034[source]▶
A lot of the parity issues are due to Bedrock not reimplementing bugs from Java (quasi-connectivity aka "droppers are doors".)
replies(1): >>41865235 #
4. archargelod ◴[17 Oct 24 00:22 UTC] No.41865235[source]▶
There are issues other than not ported bugs. Redstone in bedrock is know to be unreliable.

For example, in Java version if you take a circuit and activate it with a button/lever - it would always behave in the same way. In bedrock same setup could have random result. And "random" is something you don't want in a large sophisticated contraption.

I'd guess it's caused by some race-conditions in bedrock implementation, but alas it wasn't fixed in 7 years.