Skip to content
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

Caveat emptor fixes #3

Open
aravol opened this issue May 29, 2015 · 2 comments
Open

Caveat emptor fixes #3

aravol opened this issue May 29, 2015 · 2 comments

Comments

@aravol
Copy link
Contributor

aravol commented May 29, 2015

"Let the buyer beware" - Given the namability of stones, there exists at least some potential for abuse in the ability for a player to name a stone, only to have it lead somewhere else, potentially somewhere disastrously dangerous. This could be fixed in one of several ways

  • Create a new, noncraftable grade of Recall Stone, such that they can only be made and linked by Admins - thus, they can (almost) always be trusted
  • Allow for stones which are keyed to a chunk, instead of specific coordinates, perhaps randomly selecting a spot based on openness to the sky, or teleporting to y-256 and granting enough featherfall to survive the results. This reduces the possibility of abuse and makes for more interesting "waypoints" and reception areas (and some hilarity if people must fall from the sky)
  • Allow for an "only admins can link" rule. This means while Admins are in charge of setting up the inital waypoints, the ability to copy stones (see feature request Add "Copy Stone" recipie #2 ) allows for players to make more from these initial presets
@Vanhal
Copy link
Owner

Vanhal commented Jun 2, 2015

The position is mentioned on the stones though...

@aravol
Copy link
Contributor Author

aravol commented Jun 2, 2015

Position is mentioned, which might arouse some suspicion, but few will think to memorize positions of various locations - especially if they have a stone to do that for them!

Perhaps the easiest implementation to add an extra NBT tag like "Admin certified" or such, if the stone was Marked by someone Opped on a server? Also slightly more useful than a username, I think, since the list of Ops may not be well-known

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants