Update dependency com.palmergames.bukkit.towny:towny to v0.102.0.5 #3438
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.102.0.3→0.102.0.5Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
TownyAdvanced/Towny (com.palmergames.bukkit.towny:towny)
v0.102.0.5: for MC 1.19.* & 1.20.* & 1.21.*Compare Source
the town will turn into a ruin instead of being immediately removed.
Cumulative changes since 0.102.0.0
0.102.0.4
but due to database instability this was not something that was considered a smart change. Database stability was majorly improved years ago
however and starting in 2022 and 2023 I (LlmDl,) had pull requests on deck exploring/planning what a UUID-based database would look like for
Towny. In the middle-to-late 2025 Warrior decided to revive the UUID database concept, breaking things into bite-sized pull requests that
made the concept easier to review and merge. Those pull requests are as follows:
Thanks to Warrior's efforts the UUID database has become a reality!
nation folders, and UUIDs in the lists of friends, enemies and allies.
database if you have backups enabled in the Towny config.yml and you are using Towny in flatfile!
nations with special (usually accented,) characters.
immediately fail to load!
would not allow in the filesystem, this database update will make this issue non-existant, which is why the benefits of this update
outweigh the cons.
mayor's last-known name. All residents, towns and nations files will contain their last-known name in their files.
change in order to reduce the complexity of the codebase and to improve how Towny runs on varied server hosts.
0.102.0.3
0.102.0.2
0.102.0.1
townyperms.yml.Towny Sponsors
I want to give a big thank you to all of my sponsors:
These are the people that help to make Towny's support and development as active as it is,
and who supported me during this pre-release of Towny.
If you want to support the developer, become a sponsor.
(It's just like Patreon but instead 100% of your support goes to the developer.)Plus there are Sponsor Plugins!
Questions
Placeholders
⏬ Download available as a .jar file in the Assets section below:
v0.102.0.4: for MC 1.19.* & 1.20.* & 1.21.*Compare Source
but due to database instability this was not something that was considered a smart change. Database stability was majorly improved years ago
however and starting in 2022 and 2023 I (LlmDl,) had pull requests on deck exploring/planning what a UUID-based database would look like for
Towny. In the middle-to-late 2025 Warrior decided to revive the UUID database concept, breaking things into bite-sized pull requests that
made the concept easier to review and merge. Those pull requests are as follows:
Thanks to Warrior's efforts the UUID database has become a reality!
nation folders, and UUIDs in the lists of friends, enemies and allies.
database if you have backups enabled in the Towny config.yml and you are using Towny in flatfile!
nations with special (usually accented,) characters.
immediately fail to load!
would not allow in the filesystem, this database update will make this issue non-existant, which is why the benefits of this update
outweigh the cons.
mayor's last-known name. All residents, towns and nations files will contain their last-known name in their files.
change in order to reduce the complexity of the codebase and to improve how Towny runs on varied server hosts.
Cumulative changes since 0.102.0.0
0.102.0.3
0.102.0.2
0.102.0.1
townyperms.yml.Towny Sponsors
I want to give a big thank you to all of my sponsors:
These are the people that help to make Towny's support and development as active as it is,
and who supported me during this pre-release of Towny.
If you want to support the developer, become a sponsor.
(It's just like Patreon but instead 100% of your support goes to the developer.)Plus there are Sponsor Plugins!
Questions
Placeholders
⏬ Download available as a .jar file in the Assets section below:
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.