Bukkit

@roggbart

For point 3, please open up a ticket so I can get it in my workflow. Please provide steps to reproduce as well as any console or other notes you have. In the meantime, I'll look into the fixes. (Update: I've looked through the associated code, and you should definitely open a ticket about this one, and be precise as you can about how to reproduce the issue and anything else weird that you notice is going on that might be related. I can't see how this would be possible, from looking at my code, so there's likely more to this than what appears to be the issue.)

(Update: I've fixed the first issue, with parents not sticking after a redefine. I'll release a hotfix shortly.)

2. I don't think I intended for anything but plots to be able to be sold. I'll double check that and see what I can do. (Update: I just checked through the code, I'm not certain how you're managing to sell Territories. Can you tell me how you managed to do so?)

4. I'll look into making the sign adjust itself. (Update: Just patched it in, next release will contain this fix).

The "expand vert" bit is carried over from WorldGuard. What you're talking about is a feature, not a bug. It makes the region size flexible vertically, so you could make a small, 3x3x3 "cube" a plot by clicking the corners on the ground, then using "expand 2 up" to expand it from 1 to 3 blocks high.

Update: I've also fixed the bit where someone can scam you by pricing a plot, then falsifying the price on the sign manually. Sorta. The sign can still be falsified, but the player will be warned of the actual price of the plot upon clicking it.

Thanks for the feedback. I'll look into your issues immediately.

The release is out, for the record. *slowpoke*

The next release will contain one new feature and a slew of optimization and code-cleanup.

The new feature is a quick-select tool, for quickly setting your active regions.

All you have to do is have your active Town set (which is normally initialize by default, so you won't have to do anything unless your town is freshly-created). Then, hold the quick select tool in your hand (default is wooden hoe, you can define it in the config file) and upon clicking a block it will attempt to set your active regions based on what exists in that block.

An example: Bob has a plot in a town. He wants you to change something about it. You really hate typing, so you just teleport to him and pull out the quickselect tool. You right click on the ground near him, and it automatically select the Territory, District, and Plot. You can then use /plot commands to do whatever it is Bob wanted.

Normally, if you're setting up your regions right, no regions of the same type should intersect. In the event that there is an overlap and you clicked on a block that belongs to two different Districts or Plots or Territories, it will arbitrarily choose one to use. It'll tell you which regions it's using after it selects them, so you'll always be able to verify.

I'm still working out one last kink, then I have a few other things I want to clean up. Expect a release soonish.

So, with 1.3 coming... at some point vaguely soon, is there anyone who would want this ported ASAP to the mod API?

Right now, I'm planning on doing a bit of an overhaul when I do port it. The whole Town/Territory/District/Plot thing seems a bit too complex. I'm planning on simplifying it by removing districts entirely, as well as some other small changes.

But if anyone needs a full, stable port ASAP when 1.3 hits, I'll see what I can do to accommodate them.

@ajbcamaro

I can make the console log commands, I'll set up a ticket for it.

Mayors should use

/town active reset

in order to select their own town. Mayors will be able to select their own town (and only their own town) with "/town active townname" in a future release.

I only have a few permission nodes because most commands would have very redundant nodes. Most permission checks only consider three things:

• Is the player op or console?
• Does the player have the admin node?
• Is the player a mayor of the town he's trying to perform the command on?

Where the third item is usually the one that determines whether or not a command is allowed. So most commands never need their own permission node.

@javieraizpuru

What exactly should a war option do?

@gabriel11798

I'll consider it. It's do-able, yeah.

@gabriel11798

Really? If using Java 7 causes *most* other plugins to fail, I think you're doing something horribly wrong. I've never encountered a situation where Java 7 wasn't backwards compatible with 6.

MCTowns utilizes the following features that are only in Java 7:

• Switch over strings
• Diamond inference operator
• Catching multiple exceptions from one try block

Additionally, one thing that I may use in the future is the new file I/O package (java.nio) which is vastly superior to the 12 year old packages that it replaces.

Finally, Java 7 is indeed stable. If you visit Java.com's download page, you will notice that the "Recommended Version" is Java 7 Update 4.

@Benoit87

Only players with the mct.admin flag can change their active town, since no-one else should need to. It's a bit of a catch-all in terms of security- no-one else can screw up your town if they can't even select it.

The command:

/town active reset

will set your active town to the one you're a member/mayor of.

Additionally, when you log in (aside from when the town is first created) your active town is automatically set to the same thing /town active reset would set it to.

What I can do, though, is I can specifically allow /town active <my town name> to work if you're setting it to your town, to avoid confusion. I'll put that on my to-do list.