Search results

The completions are just strings... I'm not sure if I've seen a plugin that tries to handled commands in multiple languages. You would have to add those translations based on the player's locale and then automatically handle that in the logic for handling your commands.

You are using the wrong TranslatableComponent, probably the deprecated one (which is a good clue it's not what you want). Use adventure's components via Component#translatable which returns and adventure TranslatableComponent. Note that server-side translations will not work with ItemMeta...

Yeah, I'm not sure. I think the documentation on spigot does talk about logic in chunk gen needing to be thread-safe. But I'm not sure if it actually uses multiple threads. Either way, should be fixed as of build 383 for 1.20.4

Yeah, looks like a legit bug to me. The map that is used to convert between API enums (like PointedDripstone$Thickness) and their nms counterparts was just a regular HashMap so it's conceivable that this could happen. I've opened a PR that should resolve it.

Neither vanilla nor paper support downgrading. There is a whole process for converting chunks, entities, player data, everything to newer versions that is only written in one direction. Which is why you can't just go back to an older version, the game could be expecting data to be structured one...

That setting was available pre-1.20.2 on paper. It isn’t there anymore

Mojang fixed that bug in 1.20.2. We removed the option.

The link in the previous post shows you mappings so you can translate the type/method/field names.

Post the full latest.log.

Paper 1.8.8 is many, many years old and is not supported anymore.

The best way to fix this is to just update. 1.20.1 is not supported. Are you using a plugin.yml or paper-plugin.yml? The cause of this issue is probably that you are using paper-plugin.yml which does not include any bytecode remap fixes (on purpose). Upstream changed the type from...

You do not register commands in the paper-plugin.yml. You must handle command registration yourself by adding a class that extends command and adding it to the command map. Future API will be added to better handle command registration for plugins using the Paper Plugin system. Feel free to...

The player's active item is not the item currently in their main hand. You want player.getInventory().getItemInMainHand(). Also, that will only return > 1.0 if the item is a tool of some sort, shovel, axe, hoe, sword, shears, or pickaxe as those are the only items that affect the breaking speed...

The time command sets or mutates the fulltime which is the "day" time or the time used to calculate the sky progress/moon, etc. It is also the time that is frozen if the daylight cycle gamerule is set to false. EDIT: actually it looks like setTime also calls setFullTime behind the scenes with...

Mojang fixed that bug in 1.20.2. That setting no longer has any effect. You can only get a discount from 1 zombie conversion.

There is API to serialize an entity to a byte[] which is then not human-readable. If you don't care about that, you can use that API in UnsafeValues. I don't recall exactly what it serializes, so if it includes passengers or not.

I think that's the impropper way to define an empty list in YAML. that looks like a list of size 1 with the contents []. You probably just want to put the [] after the key directly. The "unknown" command is probably it trying to run the command /[] which would be unknown.

set/isPersistent do not do what you think they do. It is about saving the entity to disk, not whether they despawn. The other method you found, setRemoveWhenFarAway is the correct way to control that.

You are going to have to be more specific. The item sorting method with hoppers+comparators works just fine.

Check to make sure the config.yml file is in the jar file. You can just unzip the jar and see for yourself. If it isn't, you probably need to configure maven to copy it over.

That’s because the default permissions in Bukkit also have defaults. The correct ones default to true on players that are opped. So changing that setting shouldn’t have any difference. Here is a scenario that shows its use. Op a player (with level 4). Remove the Bukkit permission for the stop...

So vanilla doesn’t have the same permission system that Bukkit does. Vanilla has op levels, 0-4. What this setting does is ignore those op level requirements for any command that has them, basically making the Bukkit permission system the sole arbiter of who has what permission.

If this is some packet-related thing, protocol lib has helper methods for doing that. Not sure if we want to add more API surrounding the numerical entity ID. It really isn't a good way of identifying an entity.

Take a look at the documentation for how to configure anti-xray. It describes how to enable it for multiple worlds.

Paper has all of the Spigot/Bukkit API. There should be no types on spigot that also aren't present in Paper. Can you give an example of what you are talking about?

While that does work, it really violates a core concept about object-oriented programming. Using static to store state like that can lead to issues if someone uses the unsupported reload command. It's highly recommended to stick to using objects as the language intended and pass state around...

Paper provides an example of declaring a dependency on its API for both maven and gradle which can be found here.

You create a constructor in JoinEvent that takes an instance of your main plugin and then assign it to a field in JoinEvent. Then when you register the event in your main class' onEnable method, you can pass this to the constructor for JoinEvent.

Well, that specific issue about spawning a large number of entities can be somewhat mitigated by using paper's chunk entity save limits. Basically it prevents more than a configured number of a specific entity from being saved in a chunk. So like if you set it to 4 for boats, then only 4 boats...

You probably don't have the craftbukkit-added permission to use selectors which is minecraft.command.selector.