ASCII Name Rule Enforcement
Non-ASCII nickname for @candid magnet changed to base username. Please only use a readable+typable US-English ASCII nickname.
29 messages · Page 1 of 1 (latest)
Non-ASCII nickname for @candid magnet changed to base username. Please only use a readable+typable US-English ASCII nickname.
(patronioo) Denizen v1.3.1-SNAPSHOT (build 7225-DEV)
Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
!logs
Please post your full latest log file.
Background Info: One of the most helpful tools to identifying the source of a problem is your server logs file! Logs contain all sorts of important information like server and plugin versions, any error messages, and a lot more important information (More Info).
How To: Your log can be found in the logs folder within your server folder. The most recent log is a text file labeled latest.log. To get help using these logs, please open that file in a text editor and copy all of the text, then open https://paste.denizenscript.com/New/Log and paste the text into the box on the page. Then click "Submit" and copy the URL and paste that back into this channel.
Please do not upload the file to Discord or to other pastebin services, use the log pastebin linked above.
!logcheck
Incorrect upload of log reuploaded to pastebin at https://paste.denizenscript.com/View/136916
Paper version 1.21.1-132-ver/1.21.1@b48403b (2024-11-21T10:14:27Z)-- ((Version tracker error))
Denizen v1.3.1-SNAPSHOT (build 7223-DEV) -- (Outdated build, behind by 2)
@sour python
WorldGuard v7.0.12+829a4a4
FastAsyncWorldEdit v2.13.1 - This plugin has been known to break the plugin load order on many servers, due to usage of the 'loadbefore' directive in its 'plugin.yml'.
Caused by: java.lang.ClassNotFoundException: net.md_5.bungee.chat.ChatVersion :warning: Log contains error messages.
1.21.1 isn't supported, update to 1.21.10
What do you mean, completely? I have no choice. I read in the reviews that they wrote that 1.21.1 is possible. I've already started doing everything, I can't just change it now. I started preparing the build, the resource pack is specifically for this version.
!patchversion
We support only the latest patch-version of Minecraft for any recent main version (and Mojang, Spigot, Paper, etc. all generally also follow the same rule).
"Patch version" means the last number in a version label, for example in 1.20.6, the main version is 1.20, and the patch version is .6.
So if 1.20.6 is the latest patch version, then 1.20.3, and 1.20(.0) are all outdated patch versions, and therefore are unsupported.
Note that we do still support recent older main versions (such as 1.19 and 1.18) so long as you are on the latest patch-version of those main versions (like 1.19.4 and 1.18.2).
See also CitizensWiki/Supported_versions
Can you help me in any way? I've done a lot of work, and upgrading will ruin everything.
You can try #news for a working build, but you'll have to update if you encounter any issues
I initially took 1.21.5, but it's difficult to work with the resource pack there, and it doesn't have the necessary mods.
^
Sorry, I'm communicating through a translator. Can you explain what exactly I should do in the news channel?
It may have a link to the last build that'll work for your particular version
Also, please
!disablereplies
+++ Info disablereplies: Please disable reply-pings when responding to helpers. This relates to Rule #3: https://denizenscript.com/discord_rules#rule3
https://denizenscript.com/discimg/disable_replies.png
Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.
If not yet resolved, please reply below to tell us what you still need.
(Note that if there is no reply for a few days, this thread will eventually close itself.)
@candid magnet
Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.
If not yet resolved, please reply below to tell us what you still need.
(Note that if there is no reply for a few days, this thread will eventually close itself.)
@candid magnet
oh
@candid magnet
Thread was closed either automatically by timeout or by the Discord manual close button. If closing was intentional, please use </resolved:1028673926114594866> or </invalid:1028673926898909185>.