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 compatibility bug loading add-on to towny itself #835

Open
CatCosYT opened this issue Jul 2, 2024 · 3 comments
Open

Towny compatibility bug loading add-on to towny itself #835

CatCosYT opened this issue Jul 2, 2024 · 3 comments
Labels
Configuration Caused by using a configuration incorrectly.

Comments

@CatCosYT
Copy link

CatCosYT commented Jul 2, 2024

Server Implementation

Paper

Server Version

other

Describe the bug

When the server start, the add-on loads first and then towny

Reproduction Steps

1.Run server 1.16.5 paper
2.See the bug

Expected behaviour

When the server start, the add-on loads first and then towny

Screenshots / Videos

image

latest log file (if applicable)

No response

CombatLogX Version

10.3.8.1 and lastet

Anything else?

No response

@CatCosYT CatCosYT added the Bug An issue that is not supposed to happen label Jul 2, 2024
@SirBlobman
Copy link
Owner

SirBlobman commented Jul 6, 2024

Please ensure that both Towny and CombatLogX are updated. I can't see which Towny version is on the server nor can I check if its loading properly without a full log.

@SirBlobman SirBlobman added Configuration Caused by using a configuration incorrectly. and removed Bug An issue that is not supposed to happen labels Jul 6, 2024
@CatCosYT
Copy link
Author

Worth the latest version of both

@Olivoz
Copy link
Contributor

Olivoz commented Aug 21, 2024

Worth the latest version of both

The Towny expansion is not up to date in that image. There's a reason why we ask for the full output from /clx version in the issue template.

EDIT: To clarify the version of CombatLogX/Towny expansion most likely being run does not support the Towny version being used. While it probably was the newest version on Spigotmc at the time, it was not the latest build from our jenkins. Though unclear what exactly they were running at the time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Configuration Caused by using a configuration incorrectly.
Projects
None yet
Development

No branches or pull requests

3 participants