blocks|key|2473029|text|将您的事件优先级设置为HIGH或HIGHEST，以便在以后的中按时间顺序执行代码。这给了你如何处理事件的“最终决定权”。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2473030|@EventHandler(priority=EventPriority.HIGH)
public+void+onPlayerBreakBlock(BlockBreakEvent+e){
+++...
}|code-block|syntax|javascript|2473031|不过，不要仅仅因为你能做到这一点就自动选择HIGHEST。通常倾向于最不极端的优先级，仍然可以实现你的目标。然后，如果另一个插件与您的插件冲突，他们可以设置更高的优先级。有关更多详细信息，请参阅此链接：https://bukkit.gamepedia.com/Event_API_Reference#Event_Priorities|2473032|仅使用您根本不打算更改事件的MONITOR优先级。它旨在指示事件的最终状态。比如它是不是取消了。|2473033|entityMap|0|LINK|mutability|MUTABLE|url|https://bukkit.gamepedia.com/Event_API_Reference#Event_Priorities^0|B|4|G|7|0|0|L|7|2T|1T|0|0|E|7|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@$9|15|A|16|1|17]]|E|$]]|$1|M|3|N|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

Set your event priority to <code>HIGH</code> or <code>HIGHEST</code> in order to have your code executed later chronologically. This gives you the "final say" in how the event is handled.

<pre><code>@EventHandler(priority=EventPriority.HIGH)
public void onPlayerBreakBlock(BlockBreakEvent e){
 ...
}
</code></pre>

Don't automatically chose <code>HIGHEST</code> just because you can though. Generally prefer the least extreme priority that still accomplishes your goal. Then, if say, another plugin was conflicting with yours, they can make an even higher priority. See this link for more specific details: <a href="https://bukkit.gamepedia.com/Event_API_Reference#Event_Priorities" rel="nofollow noreferrer">https://bukkit.gamepedia.com/Event_API_Reference#Event_Priorities</a>

Only use the <code>MONITOR</code> priority of you don't intend on changing the event at all. It is intended to indicate the final state of the event. Such as whether it was cancelled or not.

blocks|key|20685|text|其他的答案和评论实际上是不正确的，我想添加更多的细节，并可能提供一些关于如何清理您的代码的建议。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|20686|当一个块被破坏时，Bukkit会按照它们的优先级将BlockBreakEvent发送给所有注册的监听器。默认情况下，优先级始终为EventPriority.NORMAL。侦听器接收事件的顺序如下所示：|offset|length|style|CODE|20687|20688|LOWEST|ordered-list-item|20689|LOW|20690|NORMAL|20691|HIGH|20692|HIGHEST|20693|MONITOR|20694|20695|HIGHEST优先级被倒数第二激发的原因是因为它意味着“这个事件是最重要的，因此拥有操纵该事件的最终决定权”。|20696|在这种情况下，你不想成为最后一个处理事件的插件，你想成为第一个。然而，将优先级设置为LOWEST或HIGHEST是有风险的，因为在某些情况下，其他插件可能需要在您之前或之后处理信息(例如WorldEdit)。因此，您应该将事件优先级设置为LOW。|20697|我想提的最后一件事是你有很多重复的代码。当涉及到速度时，这不一定是一个问题，但它确实使阅读变得更加困难。下面是一个解决方案，既可以清理代码，也可以修复事件优先级问题。|20698|@EventHandler(priority+=+EventPriority.LOW)
public+void+onPlayerBreakBlock(BlockBreakEvent+event)+{
++++List<Material>+materialList+=+Arrays.asList(Material.COAL_ORE,+Material.IRON_ORE,+Material.GOLD_ORE,+Material.DIAMOND_ORE,+Material.EMERALD_ORE);
++++Material+type+=+event.getBlock().getType();
++++Player+player+=+event.getPlayer();

++++if+(materialList.contains(type)+&&+!player.hasPermission("PluginName."+%2B+type.name().toLowerCase().replace("_ore",+""))+&&+!player.isOp())+{
++++++++event.setCancelled(true);
++++++++player.sendMessage(ChatColor.DARK_RED+%2B+"You+do+not+have+permission+to+mine+"+%2B+StringUtils.capitalizeFully(type.name()));
++++}
}|code-block|syntax|javascript|20699|编辑：我只想多加一点说明。有很多建议将你的优先级设置为HIGH或HIGHEST，但玩家被垃圾邮件的原因正是因为你的事件在另一个事件之后触发。这意味着即使你成功地取消了活动，它也会取消所有9个活动，并在玩家每次试图打破一个区块时向他们的聊天发送9条垃圾消息，而不仅仅是1条消息。|BOLD|20700|entityMap^0|0|P|F|1S|K|0|0|0|6|0|0|3|0|0|6|0|0|4|0|0|7|0|0|7|0|0|0|7|0|16|6|1D|7|3B|3|0|0|0|0|2|R|4|W|7|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1D|8|@$D|1E|E|1F|F|G]|$D|1G|E|1H|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1J|8|@$D|1K|E|1L|F|G]]|9|@]|A|$]]|$1|L|3|M|5|K|7|1M|8|@$D|1N|E|1O|F|G]]|9|@]|A|$]]|$1|N|3|O|5|K|7|1P|8|@$D|1Q|E|1R|F|G]]|9|@]|A|$]]|$1|P|3|Q|5|K|7|1S|8|@$D|1T|E|1U|F|G]]|9|@]|A|$]]|$1|R|3|S|5|K|7|1V|8|@$D|1W|E|1X|F|G]]|9|@]|A|$]]|$1|T|3|U|5|K|7|1Y|8|@$D|1Z|E|20|F|G]]|9|@]|A|$]]|$1|V|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|22|8|@$D|23|E|24|F|G]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|25|8|@$D|26|E|27|F|G]|$D|28|E|29|F|G]|$D|2A|E|2B|F|G]]|9|@]|A|$]]|$1|10|3|11|5|6|7|2C|8|@]|9|@]|A|$]]|$1|12|3|13|5|14|7|2D|8|@]|9|@]|A|$15|16]]|$1|17|3|18|5|6|7|2E|8|@$D|2F|E|2G|F|19]|$D|2H|E|2I|F|G]|$D|2J|E|2K|F|G]]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|2L|8|@]|9|@]|A|$]]]|1B|$]]

The other answers and comments actually aren't correct, and I wanted to add a few more details and potentially offer some recommendations on how to clean up your code a tad.

When a block is broken, Bukkit will send the <code>BlockBreakEvent</code> to all registered listeners in the order of their priority. By default, the priority will always be <code>EventPriority.NORMAL</code>. The order in which listeners receive the event occurs in the following order:

<ol>
<li><code>LOWEST</code></li>
<li><code>LOW</code></li>
<li><code>NORMAL</code></li>
<li><code>HIGH</code></li>
<li><code>HIGHEST</code></li>
<li><code>MONITOR</code></li>
</ol>

The reason the <code>HIGHEST</code> priority is fired second-to-last is because it means "this event is the most important, and therefore gets the final say to manipulate the event."

In this case, you don't want to be the last plugin to process the event, you want to be the first. However, it is risky to set priorities to <code>LOWEST</code> or <code>HIGHEST</code> as there might be cases where other plugins need to handle information before or after you (WorldEdit for instance). Thus, you should set your event priority to <code>LOW</code>.

The last thing I want to mention is that you have a lot of duplicate code. This is not necessarily a problem when it comes to speed, but it does make things much harder to read. Below is a solution to both clean up your code and also fix the problems with event priority.

<pre><code>@EventHandler(priority = EventPriority.LOW)
public void onPlayerBreakBlock(BlockBreakEvent event) {
 List&lt;Material&gt; materialList = Arrays.asList(Material.COAL_ORE, Material.IRON_ORE, Material.GOLD_ORE, Material.DIAMOND_ORE, Material.EMERALD_ORE);
 Material type = event.getBlock().getType();
 Player player = event.getPlayer();

 if (materialList.contains(type) &amp;&amp; !player.hasPermission("PluginName." + type.name().toLowerCase().replace("_ore", "")) &amp;&amp; !player.isOp()) {
 event.setCancelled(true);
 player.sendMessage(ChatColor.DARK_RED + "You do not have permission to mine " + StringUtils.capitalizeFully(type.name()));
 }
}
</code></pre>

Edit: I just want to add a little bit more clarification. There are a LOT of suggestions saying to set your priority to <code>HIGH</code> or <code>HIGHEST</code>, but the reason the player is being spammed is exactly because your event fires after the other event. That means even though you successfully cancel the event, it cancels all nine events and will spam the player's chat with 9 messages each time they try to break a block, rather than just 1 message.

I'm developing a plugin to prevent players from mining ores unless they have a permission. However i'm running into an issue where users are using another plugin alongside mine where it allows for them to mine 9 blocks at once. Well this spams the player with "You do not have permissions to mine this!" Can someone advise me a workaround for the messaging system? (Basically not spam the player).

<pre><code> switch (type) {
 case COAL_ORE: {
 if (!player.hasPermission("PluginName.coal") &amp;&amp; (!player.isOp())) {
 event.setCancelled(true);
 player.getPlayer().sendMessage(ChatColor.DARK_RED + "You do not have permission to mine Coal Ore!");
 }
 break;
 }
 case IRON_ORE: {
 if (!player.hasPermission("PluginName.iron") &amp;&amp; (!player.isOp())) {
 event.setCancelled(true);
 player.getPlayer().sendMessage(ChatColor.DARK_RED + "You do not have permission to mine Iron Ore!");
 }
 break;
 }
 case GOLD_ORE: {
 if (!player.hasPermission("PluginName.gold") &amp;&amp; (!player.isOp())) {
 event.setCancelled(true);
 player.getPlayer().sendMessage(ChatColor.DARK_RED + "You do not have permission to mine Gold Ore!");
 }
 break;
 }
 case DIAMOND_ORE: {
 if (!player.hasPermission("PluginName.diamond") &amp;&amp; (!player.isOp())) {
 event.setCancelled(true);
 player.getPlayer().sendMessage(ChatColor.DARK_RED + "You do not have permission to mine Diamond Ore!");
 break;
 }
 }
 case EMERALD_ORE: {
 if (!player.hasPermission("PluginName.emerald") &amp;&amp; (!player.isOp())) {
 event.setCancelled(true);
 player.getPlayer().sendMessage(ChatColor.DARK_RED + "You do not have permission to mine Emerald Ore!");
 }
 break;
 }
 }
}
</code></pre>

Minecraft: Multiple messages being sent

我正在开发一个插件，防止玩家在没有许可的情况下开采矿石。然而，我遇到了一个问题，用户在我的插件旁边使用另一个插件，它允许他们一次挖掘9个区块。这会给玩家发送垃圾邮件：“你没有挖掘这个的权限！”有人能给我一个消息系统的变通方法吗？(基本上不会给玩家发垃圾邮件)。        switch (type) {    cas...

问我的世界:发送多条消息
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我的世界:发送多条消息EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我的世界:发送多条消息
EN