-
-
Notifications
You must be signed in to change notification settings - Fork 352
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
Exception when you delete Town #3398
Comments
The town that was deleted is having a hard time reverting the blocks back to their pre-claimed state. Maybe the town was claimed on an older version of minecraft and towny? |
I had only made the claim about 30 minutes prior. Didn't change the version minecraft or Towny in between. I only installed Towny today. Just checked my console and it's throwing a new exception literally every single second: |
Stop the server and delete the towny\data\regen.txt file. |
Having the same issue, world regen is turned off. Config syntax is valid. Paperspigot 172 |
@winnipeg21 turned off in teh config or turned off in the world (use /tw toggle revertunclaim) the config is only for default settings. |
Same issue: Paper 176 (1.14.4), Towny 0.94.0.6. |
I can confirm that toggling revertunclaim off before the town is deleted prevents this from happening. |
@Momshroom anything that would make this town's plot snapshots strange? Which version of Towny were they claimed with, was it pre 0.93.1.0? |
No. I claimed it immediately before the /ta newday command in 0.94.0.6. I was testing your iConomy fix. (Ty for that!) |
Can you tell from the log if the snapshot had finished being made? |
I included the whole latest.log file. Or did you mean the towny log?
…On Tue, Sep 3, 2019 at 7:42 AM LlmDl ***@***.***> wrote:
Can you tell from the log if the snapshot had finished being made?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3398?email_source=notifications&email_token=AEATM2D26UYRFPFY2JWOZILQHZLSXA5CNFSM4IPI4BYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5YBZKI#issuecomment-527441065>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEATM2HIHLWW3E6DUIQQUW3QHZLSXANCNFSM4IPI4BYA>
.
|
Okay, after updating to 0.94.0.7, I toggled revertunclaim back on, made a new town, waited until the log said the plot snapshots were completed, and then caused the town to fall with /ta newday. It still spams console with the errors:
|
Ok, tracked this down to a change I made to removing TownBlocks. I'd made the change to greatly reduce spam Exception messages when a town has many townblocks removed. Looks like the fix I made has the side effect of deleting the townblocks too early. Probably have to revert the whole mess and see if there's another better way to solve the exception spam. |
on Townblocks (Ticket #3398) - Had to revert a previous fix for Exception spam that involves the now-unused RemoveManyTownblocks.
This is not longer an issue as of 0.94.0.8, we are reverting the above fix. |
This ticket template is for bug/error reports. If you are suggesting a feature and not reporting a bug please delete all the text here and begin your ticket Title with Suggestion:
What steps will reproduce the problem?
What is the expected output?
What is your Towny version?
0.94.0.5
What is your spigot/craftbukkit version?
Paper version git-Paper-135
Please use Pastebin.com to link the following files:
Skipping these files is not an option. It is the easiest way to diagnose an issue ticket properly. If you do skip this step then your ticket will most likely be deleted and you will be asked to resubmit.
Your full server startup from the logs\latest.log :
https://pastebin.com/YHyGfRsv
Your Towny config.yml (if using MySQL please remove password,) :
https://pastebin.com/YuryB2GZ
Your townyperms.yml :
https://pastebin.com/180Sgtzt
Your log's error :
https://pastebin.com/XmiiBk6K
(optional) If this is to do with permissions,
5. Your permissions file :
N/A
(optional) If this is to do with chat,
6. Your chatconfig.yml : N/A
7. Your channels.yml : N/A
The text was updated successfully, but these errors were encountered: