At the time this was re-added, there was concern around how the JIT would handle the system property that enabled it. This shouldn't be a problem, and as such we no longer need to block access to it. The Vanilla Method Profiler will not provide much to most users however there is no harm in providing it as an option. For most users, the recommended and supported method for determining performance issues with Paper will continue to be Timings.
27 lines
1.1 KiB
Diff
27 lines
1.1 KiB
Diff
From d6e9b9c825d7abaea63c248016e31e2ce9c41766 Mon Sep 17 00:00:00 2001
|
|
From: BillyGalbreath <Blake.Galbreath@GMail.com>
|
|
Date: Fri, 19 Jan 2018 08:15:29 -0600
|
|
Subject: [PATCH] PlayerAdvancementCriterionGrantEvent
|
|
|
|
|
|
diff --git a/src/main/java/net/minecraft/server/AdvancementDataPlayer.java b/src/main/java/net/minecraft/server/AdvancementDataPlayer.java
|
|
index 6896b709..8913e274 100644
|
|
--- a/src/main/java/net/minecraft/server/AdvancementDataPlayer.java
|
|
+++ b/src/main/java/net/minecraft/server/AdvancementDataPlayer.java
|
|
@@ -196,6 +196,12 @@ public class AdvancementDataPlayer {
|
|
boolean flag1 = advancementprogress.isDone();
|
|
|
|
if (advancementprogress.a(s)) {
|
|
+ // Paper start
|
|
+ if (!new com.destroystokyo.paper.event.player.PlayerAdvancementCriterionGrantEvent(this.player.getBukkitEntity(), advancement.bukkit, s).callEvent()) {
|
|
+ advancementprogress.b(s);
|
|
+ return false;
|
|
+ }
|
|
+ // Paper end
|
|
this.d(advancement);
|
|
this.i.add(advancement);
|
|
flag = true;
|
|
--
|
|
2.14.3
|
|
|