←back to thread

419 points alex_medvedev | 3 comments | | HN request time: 0.493s | source
Show context
FrustratedMonky ◴[] No.41848136[source]
Love the idea. Especially as a learning example. Always fun to learn a language by implementing a popular game.

Am confused by these two lines. Maybe it is just difference between the 'goal' and the 'current state'.

Goal:

"Compatibility: Supports the latest Minecraft server version and adheres to vanilla game mechanics. "

But NOT:

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

Will it be a replacement for Vanilla or not?

replies(2): >>41848490 #>>41849818 #
1. alex_medvedev ◴[] No.41849818[source]
Hey, With Compatibility i mean be compatible with existing Minecraft vanilla client's and also use vanilla logic. With "Be a drop-in replacement for vanilla or other servers" i mean that if you just replace the existing server file with pumpkin, pumpkin will not load configs/plugins from vanilla/other servers
replies(2): >>41850736 #>>41858323 #
2. giancarlostoro ◴[] No.41850736[source]
> i mean that if you just replace the existing server file with pumpkin, pumpkin will not load configs/plugins from vanilla/other servers

Will it ever though? Is this a goal?

3. FrustratedMonky ◴[] No.41858323[source]
Hello

I see it is not a drop in when using other tools, plug ins, 3rd party things.

But what about just a plain vanilla world.

Can Pumpkin read in and use the plain vanilla files? Does it do some kind of conversion and have it's own file structure?

So if I had a simple server, it could be a drop-in.

Or does the world need to be generated new inside Pumpkin? I can't use existing worlds.