From 8880020c39ba7b9e2789203d8818a51d63547cf4 Mon Sep 17 00:00:00 2001
From: KermanIsPretty <46640204+KermanIsPretty@users.noreply.github.com>
Date: Wed, 22 Jan 2025 20:53:00 -0600
Subject: [PATCH] Update docs

---
 .../PlayerBlockTouchTickIntegrationTest.java         | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/src/test/java/net/minestom/server/collision/PlayerBlockTouchTickIntegrationTest.java b/src/test/java/net/minestom/server/collision/PlayerBlockTouchTickIntegrationTest.java
index e6e5bf95e..2a00fb075 100644
--- a/src/test/java/net/minestom/server/collision/PlayerBlockTouchTickIntegrationTest.java
+++ b/src/test/java/net/minestom/server/collision/PlayerBlockTouchTickIntegrationTest.java
@@ -3,8 +3,6 @@ package net.minestom.server.collision;
 import net.minestom.server.coordinate.Point;
 import net.minestom.server.coordinate.Pos;
 import net.minestom.server.coordinate.Vec;
-import net.minestom.server.entity.Entity;
-import net.minestom.server.entity.EntityType;
 import net.minestom.server.instance.block.Block;
 import net.minestom.server.instance.block.BlockHandler;
 import net.minestom.server.utils.Direction;
@@ -21,8 +19,14 @@ import java.util.Set;
 import static org.junit.jupiter.api.Assertions.assertEquals;
 import static org.junit.jupiter.api.Assertions.assertTrue;
 
-// Separate because of how movement is calculated between players and entities.
-// We should expect this bad behavior from the player but not entities. unless the physics engine has gets a controller input vector.
+/**
+ * This is really a test between fast and slow touch methods.
+ * As player cannot touch "quickly"
+ * <p>
+ * There is a bad behavior between the two, and it has to do with how entities are in blocks.
+ * We should expect this bad behavior from the player but not entities.
+ * Unless the physics engine gets updated to include a controller input vector.
+ **/
 @EnvTest
 class PlayerBlockTouchTickIntegrationTest {
     @Test