Search results

This is an issue with bungeecord, or proxies in general, and how they handle commands/chat. I have a patch or two in Waterfall (but, that is EOL) that improves the situation for commands, Velocity has the Signed Velocity plugin which also further improves the situation a whole lot more until we...

the scheduler in velocity is always "async", I generally suggest using your own thread pool for this sorta stuff, however

You're using purpur, that is a modifcation, or a fork, of our software.

you're using an unsupported version of a fork which isn't ours, looks like something is wrong with their timings server, you'd need to speak to them for support (assuming they'll give you any)

There is no new commands implementation that has been released, that just looks like you're trying to use the old bukkit command system manually, which was a bit of a "at least there's something of fall back to". if you want good commands, you'd be better off looking towards a command framework...

well, fabric is vanilla + some bootstrap/API stuff, if your farm isn't working, then it's probably something wrong with the farm/your setup of it

fabric doesn't come with performance optimisations, but you can get mods which improve performance which aren't as behaviorally invasive as a full plugin API

The issue isn't generally the performance patches, most of what exists in terms of performance that breaks stuff is things like entity activation range, which is configurable. What often breaks more edge case farms is the changes craftbukkit/spigot made to support plugins, you can't really...

The server software works the exact same as the vanilla software in this regard in that you can enable the experimental packs inside of server.properties before the world is created, otherwise, the only (unsupported) mechanism of enabling that stuff is to modify level.dat; as for how that will...

adventure was added in 473, minimessage was not bundled until 1.18.x, you'd need to shade it yourself, but MM is not compatible with much older versions of adventure, and so you'd be unable to use the built-in stuff if you wanted a nicely working setup.

You need to be op'd and in creative mode to place them from what I recall?

Not really, disabling that prevents chunks unloading in general

our only real understanding of this is that mojang might be causing IO to be overloaded with map files, otherwise all we can see is that the thing stalled writing to the disk

that API is just blatently too limited/broken for your usecase

Yes, the PlayerInfo packet was essentially rewritten/replaced, so it is that https://mappings.cephx.dev/1.20.4/net/minecraft/network/protocol/game/ClientboundSetEntityDataPacket.html I would generally suggest trying to learn what the code is actually doing and then aiming to understand the...

Paper is a modification of the java server software, we have nothing to do with bedrock at all. You're probably looking towards projects like geyser.

https://gist.github.com/electronicboy/031df94bb2ba120ceebb8c7f8a3f8425 here is some code I threw together at 6am a few years ago for the most part, you can basically copy what Ess's code is doing, that code was written for a multi year old fork of Essentials, and might be missing some...

https://mappings.cephx.dev/1.20.4/net/minecraft/network/protocol/game/ClientboundAddEntityPacket.html

Papers tooling uses Mojangs mappings, and so if you're missing classes, it's likely because you're trying to use spigot names for stuff; https://mappings.cephx.dev/1.20.4/ will let you look up mappings to convert your code over

well, yes, if you relocate adventure then you can't call the native paper methods as it breaks the ABI for those methods

It doesn't return components, however, sending commands/chat to the server is 100% raw strings; The only thing that can be a component is the tooltips

You have a configuration file from a newer version of paper, downgrading is not supported. The easiest option is to delete the config folder or delete the setting it is complaining about.

I mean, it's not a magical fix, you'd need to look into providing diagnostics information such as spark reports, but people are generally not inclined to bother digging into them on unsupported versions

for 1.19.x? it gives you a years worth of performance improvements made to the server software by us and mojang, outdated versions are also generally a pita to support as stuff changes and so most of us generally do not care to provide support for outdated versions

are you still holding onto the old player reference? if so, that is why. Your reference is holding onto an entity which is dead and no longer valid, you would need to get the new player instance.

This is paper, we can't help with issues relating to software that has nothing to do with us

No, but if you show your build config somebody might be able to tell you what is wrong

You have outdated plugins, etc

Yes, which is why I suggested grabbing jstack reports. I don't have any tutorials, it's a program which takes the PID of java and spits out info about the JVM, there is probably a few guides on google

it failed to start because the old server is still running, you'd need to work out why; look at jstack, etc