-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot remove Specter + cannot hurt? #9
Comments
Are you using 1.5 and 0.11? If so, there isn't any support yet. |
No, I was using the 1.4.1 version of PocketMine...and 0.10.4 of Pocket Edition |
/kick doesn't work and /s q doesn't work either? For hurting, if a normal player spawned there, can he be hurt? |
When I log out, logging back in, the Specter comes back. |
@HotFireyDeath you need to authenticate your specter to SimpleAuth, or some other plugins blocked the specter from being damaged. Specters work as normal players. They are basically handled the same as normal players except that there isn't a remote device connecting for it. So it's normal that the Specter remains there right? If you don't use /s q or /kick to disconnect the player, what do you use? Do you even know what Specter is about? |
@HotFireyDeath it appears that another plugin is cancelllinf the event. Did you read the console about the messages sent to the specter? |
I cannot kill them manually as I can kill a regular player. They cannot be hurt in any manner, even through the void. @PEMapModder is it supposed to be that they automatically rejoin after you close and open the server? |
No they wouldn't auto rejoin if the server is restarted. About not being able to get hurt, can you create an event listener with |
Hi! When I use Specter to test my plugins, it seems I cannot hurt the generated player! Now, my plugin kind of depended on hurting players. Is that a bug or are there a feature to do so?
Also, I cannot seem to remove my Specter, even through server disconnection. This is an issue because I don't want useless, empty players on my server standing there.
So, are these issues? Or is there a fix?
The text was updated successfully, but these errors were encountered: