Stop explicitly blocking Vanilla Method Profiler

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.
This commit is contained in:
Zach Brown
2018-03-31 14:51:21 -04:00
parent 4502a946d7
commit 9bafd0634e
89 changed files with 192 additions and 278 deletions

View File

@@ -12,7 +12,7 @@ This then triggers async chunk loads!
What in the hell were you thinking?
diff --git a/src/main/java/net/minecraft/server/BlockBeacon.java b/src/main/java/net/minecraft/server/BlockBeacon.java
index f07ac0186..21075974d 100644
index f07ac018..21075974 100644
--- a/src/main/java/net/minecraft/server/BlockBeacon.java
+++ b/src/main/java/net/minecraft/server/BlockBeacon.java
@@ -0,0 +0,0 @@ public class BlockBeacon extends BlockTileEntity {