Error: Argument 1 passed to pocketmine\utils\Binary::writeVarLong_64() must be of the type integer, null given, called in phar:///home/gs/gs/data/servers/4009632/PocketMine-MP_1.6.2dev-157_c445db42_API-3.0.0-ALPHA5.phar/src/pocketmine/utils/Binary.php on line 650
File: /src/pocketmine/utils/Binary
Line: 677
Type: notice
Code:
[668] return self::writeUnsignedVarLong_32($v);
[669] }
[670]
[671] /*
[672] * 64-bit VarLong encoder.
[673] *
[674] * @param int $v
[675] * @return string
[676] */
[677] public static function writeVarLong_64(int $v) : string{
[678] return self::writeUnsignedVarLong_64(($v << 1) ^ ($v >> 63));
[679] }
[680]
[681] /*
[682] * Writes a 64-bit integer as a variable-length long
[683] *
[684] * @param int|string $v
[685] * @return string up to 10 bytes
[686] */
[687] public static function writeUnsignedVarLong($v) : string{
Backtrace:
PocketMine-MP version: 1.6.2dev #157 [Protocol 113; API 3.0.0-ALPHA5]
Git commit: 0000000000000000000000000000000000000000
uname -a: Linux *.*.* 3.14.32-xxxx-grs-ipv6-64 #5 SMP Wed Sep 9 17:24:34 CEST 2015 x86_64
PHP Version: 7.0.9
Zend version: 3.0.0
OS : Linux, linux
Plugin issue.
are you sure? i don't see "This crash is caused by a plugin"
6 /Slapper_v1.3.3.phar/src/slapper/entities/SlapperHuman(77): pocketmine\Player->dataPacket(pocketmine\network\mcpe\protocol\AddPlayerPacket object)
Slapper_v1.3.3.phar
why it causes error?
Error: Argument 1 passed to pocketmine\utils\Binary::writeVarLong_64() must be of the type integer, null given, called in phar:///home/gs/gs/data/servers/4009632/PocketMine-MP_1.6.2dev-157_c445db42_API-3.0.0-ALPHA5.phar/src/pocketmine/utils/Binary.php on line 650
;)
@ExaSonit Because the plugin needs to be updated to match all the changes in v1.1, as do many plugins that are suddenly spitting out errors.
In the future, test WITHOUT plugins before submitting a report. If the issue disappears, it's a plugin and the devs here are not going to do anything but tell you it's a plugin issue. so you would be wasting everyone's time opening a bug report here; you would need to contact the Plugin developer.
yes, now it works don't worry, thanks for support
Most helpful comment