MCT Wand Tool does not work
apengstrom opened this issue ยท 5 comments
When I use the default tool (wooden hoe) and click anywhere, it sets my active town to the same town (I have 4 towns now) and territory: null and plot: null. It does not work at all, it sets to the same town no matter what town I'm in or where I'm located.
I am using the latest release build (not the RC2), and I have MC 1.6.4 dev (one of the latest, can't recall which). I can't revert my MC to 1.6.2, as that would mess up the entire server at this point. I've been actively working on debugging 1.6.4 plugins and craftbukkit this time instead of waiting for a beta build, as I want a head-start as soon as 1.7 comes out.
Thanks for looking into this :)
The quick-select tool doesn't change the town for you- you need to manually change that yourself.
I remember putting this restriction in because there was a good reason to... but upon reviewing the code just now, I can't imagine what that reason was.
I'll set this to be fixed in the next version.
What was the point of leaving a quick select tool at all, in that case? What other purposes does it have?
Having a tool to be able to quickly select a plot, including its town / territory, would be VERY useful. As of right now I have 4 towns and that number is soon to grow to 15 or more. I can't imagine having to switch and set the active town, territory and plot every time I want to change something.
I can see it setting the active town if there is no territory or plot that you are in. I can also see it setting the active town and territory, if there is just no plot. I can also see it selecting a plot if there is a plot without a town and/or territory.
What are the restrictions / functionalities associated with deleting a town/territory? Do the sub-regions (territories/plots) get automatically removed as well as all their associated users/data?
Thanks!
The idea is:
- Set a town
- The QS tool lets you pick any territory/plot combo in the town
And yes, deleting territories is recursive (will delete all plots in the territory).
Ah, I see it now. This would make a lot of sense as to why I did not see the tool working before. It does work as you described. Is there a way we can add this to the documentation?
Personally at this point as long as it works as you described, I do in fact see no serious issue in keeping it where the user has to type /town active [townname] in order to change towns. Sure, using the tool would still be faster, but it's not that big of an issue as long as the rest works.
Thanks for the info!
The docs already mention that, though it was arguably not obvious enough. I've fixed that, and also removed another reference to districts... I swear, I'll never finish finding those...