#(daxz_) was there ever a build version for 1.21?
28 messages · Page 1 of 1 (latest)
(daxz_) was there ever a build version for 1.21?
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.
you can't use 1.21.1 instead?
nope, writing a script for someone else and they need it on 1.21. ill try to get them to update but well
You know we don't support 1.21.0.
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.)
@crimson locust
oh what
i thought denizen supported 1.20.6+
??
Are you memeing?
the .0 is in emphasis
!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
1.21.0 specifically is dangerous.
Due to the crash exploit that was fixedi n 1.21.1.
gotcha
If you're desperate you know where to look, but we seriously don't recommend it.
or was i thinking about how 1.20.6 and the latest patchvers was supported
#news doesnt have it so thats why i had to make this post
1.19.4, 1.20.6, and 1.21.5 are fine. (1.21.4 too technically since paper is experimental.)
i see okay
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.)
@crimson locust