Recent content by electronicboy

1. You have some characters in the file path which are best avoided, the {} is likely to cause issues 2. Don’t run the server in a one drive folder 3. Given that it blows up after trying to init plugins, I’d imagine, test without them. Make sure you download them from a reputable site.

You can’t have actual code inside of the class body, you’d want to place that inside of a method, generally a static method called register is the canonical way to separate that stuff up into classes

We no longer have a git repo for the API and the -Server module, and so it's generally not possible to just have an large patch for either of those folders anymore; you could maybe use feature patches for inside of the Minecraft tree and then use per file outside of that, but, that is probably...

ViaVersion has jars to add protocol support for 1.21.5, however, you might need to pay for the early releases; Geyser apparently works for 1.21.4, however. We do not provide support for server software that isn't ours, noting that running your server on Spigot might cause damage to existing data...

1) update, you're well over 200 builds out of date 2) probably want to check your gamerules, you may need to use a tool to modify the level.dat manually

You more than likely have a plugin overriding the command, you can use Minecraft:recipe to force using the vanilla one

would generally need to see a spark report to see your config, primary suspicion would be the config options for toying with how often certain things can tick, and entity activation ranges

That calculation relies on information that isn't sent to the client. It was wrong for years, and Mojang just opted to remove it in a past update

as I've previously said elsewhere, we have zero bans on record for the information you have provided

it's a standalone piece of software, it doesn't know about events firing on the backend server

I fixed this years ago without a config option, if you create an issue on the tracker, one may get around to adding a config option

Paperweight, our tooling for this, does not support maven. The only options are 1) using the unsupported community maven plugin https://github.com/Alvinn8/paper-nms-maven-plugin 2) Migrate to gradle and follow the supported docs/see the paperweight-test-plugin

The only guess is going to be that you need to reset your spawn position using the command, or, see if when it rains water falls into the room, if it does, that would indicate that your worlds heightmaps are busted and that you'll need to look into rebuilding that information

We're not going to break existing APIs for some sizable period of time; the only immediate difference is us not merging new APIs, but most of the side effects of this have been navigated by plugin developers for years, given that they're often expected or desire to support multiple versions of...

We are still a fork of spigot in terms of what a fork actually is, we are, however, not intending to keep aligned with our quasi closed upstream project, and have decided that we would much rather place ourselves in a position where we can work on stuff without having to worry about conflicts...