You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2018. It is now read-only.
So far, the routine man_where_is_my_pack does not check if the backpack has already been picked up by the player or emptied. Therefore a player could teleport to this position as long as he or she wants to or if a new backpack position has been set because of a new death. It should be added, that the command does only work, if the backpack still exists.
The text was updated successfully, but these errors were encountered:
…o have playerdata available there ^^
only currently online players should be checked in the playerobserver, but I leave the choice to the action / module writers. witch access to the playerpoll there should be no limits really. We have full db access and full playerdata access. this should do for about 95% of bot functions. probably fixes#18fixed#17 and also disabled being able to get back to spawn by entering the password again.Simply deleting the locations backpack (created on death) and spawn (created on very first log-in)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So far, the routine man_where_is_my_pack does not check if the backpack has already been picked up by the player or emptied. Therefore a player could teleport to this position as long as he or she wants to or if a new backpack position has been set because of a new death. It should be added, that the command does only work, if the backpack still exists.
The text was updated successfully, but these errors were encountered: