From 6fdcb098918174410be662525d2fb86ed1daf0cd Mon Sep 17 00:00:00 2001 From: "Dylan K. Taylor" Date: Sun, 21 Jul 2019 18:52:33 +0100 Subject: [PATCH] fix PhpStorm's screwup with World->setBlock() doc comment it's not the first time i've seen it do this, and i still have no idea why it does this. --- src/pocketmine/world/World.php | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/pocketmine/world/World.php b/src/pocketmine/world/World.php index 54289f06f..b4d7034b7 100644 --- a/src/pocketmine/world/World.php +++ b/src/pocketmine/world/World.php @@ -1446,6 +1446,7 @@ class World implements ChunkManager{ /** * Sets the block at the given Vector3 coordinates. + * @see World::setBlockAt() * * @param Vector3 $pos * @param Block $block @@ -1454,8 +1455,6 @@ class World implements ChunkManager{ * @return bool Whether the block has been updated or not * * @throws \InvalidArgumentException if the position is out of the world bounds - *@see World::setBlockAt() - * */ public function setBlock(Vector3 $pos, Block $block, bool $update = true) : bool{ return $this->setBlockAt((int) floor($pos->x), (int) floor($pos->y), (int) floor($pos->z), $block, $update);