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

Towny sends incorrect message in claim process #4272

Closed
hydridity opened this issue Aug 17, 2020 · 3 comments
Closed

Towny sends incorrect message in claim process #4272

hydridity opened this issue Aug 17, 2020 · 3 comments

Comments

@hydridity
Copy link

What steps will reproduce the problem?

  1. Have town with reached town size (for example town size with 8/8 without any bonuses)
  2. Trying to claim more using rect or circle (/t claim rect 4)

What is the expected output?

  1. Towny to notify with message: Not enough available town blocks to claim this selection.
    Instead it sends incorrect message: This area has already been claimed.
    It even says that "area has already been claimed" if the specified area is not attached to town edge and there are no claimed areas around
    Trying to claim only one town block with /t claim, sends correct message with not enough town blocks or area not being attached to town edge

What is your Towny version?

0.96.2.0

What is your spigot/craftbukkit version?

git-Spigot-9639cf7-8fb6585 (MC: 1.16.1)

@hydridity hydridity added the bug label Aug 17, 2020
@LlmDl
Copy link
Member

LlmDl commented Aug 17, 2020

You skipped the form. Please include it.

@hydridity
Copy link
Author

It's been tested on clean server setup it's all default settings for towny

  1. Server log : https://pastebin.com/K898eTiK
  2. Towny config.yml : https://pastebin.com/Fb3R1DpX
  3. townyperms.yml : https://pastebin.com/HLTKVeuj
  4. log's error : there is no error

Test environment plugin collection:

  • Essentialsx - 2.18
  • Towny - 0.96.2
  • TownyNameUpdater - 5.0
  • Vault - 1.7.3-b131

@LlmDl
Copy link
Member

LlmDl commented Aug 17, 2020

Thanks. I know where the issue is I just have to clear it up.

@LlmDl LlmDl added this to the 0.96.3.0 milestone Aug 17, 2020
@LlmDl LlmDl closed this as completed Aug 17, 2020
LlmDl added a commit that referenced this issue Aug 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants