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

Improvement: Tool or command to show Town Protected area. #888

Closed
Wissi opened this issue Apr 28, 2017 · 3 comments
Closed

Improvement: Tool or command to show Town Protected area. #888

Wissi opened this issue Apr 28, 2017 · 3 comments
Assignees

Comments

@Wissi
Copy link

Wissi commented Apr 28, 2017

I believe there is a great demand and really necessary to have a tool or command to show (turn on/off maybe) the Town's protected area of a player or other players in general. Showing maybe an outline in red or the last blocks withing the radius have a ghost block on top (that part is up for the coders to decide?).

So that everyone can know exactly where their Town area is as well as other player's Town area limits. Definitely synced with the server side for other players.

@AndrewTru
Copy link

the thing I think this may work is if you copy the outline from the building code and reword it to town limit, yes this change will help other players with remembering the limits, if a block that is a lot like the keep out tape that you use with the building code, just recode it to say city limits.
The only issue I see with it is how it will have to dynamically redo itself every time the limit changes (SSP will not be the issue but SMP will) , when we get to that part that is. I think the limit is fixed at this time, can someone from the team confirm this?

@marvin-bitterlich
Copy link
Member

@AndrewTru I am against placing blocks to visualize borders, rendering it clientside would be easier imo

@AndrewTru
Copy link

good point.

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

4 participants