Command /whitelist has not been renamed to /allowlist
According to the Bedrock edition release notes (https://www.minecraft.net/en-us/article/caves---cliffs--part-i-out-today-bedrock), the /whitelist command has been renamed to /allowlist in Bedrock edition. Since the corresponding Java edition command has not yet been renamed, this change introduces a parity issue.
steps to reproduce:
- start a server
- type allowlist list
-
the server responds with something like:[20:02:31] [Server thread/INFO]: Unknown or incomplete command, see below for error [20:02:31] [Server thread/INFO]: allowlist list<--[HERE]
- type whitelist list
the server responds with something like:[20:02:36] [Server thread/INFO]: There are no whitelisted players
even though this command should be removed in favor of allowlist
- Unresolved
Steve Hsu
- 6
- 3
- Confirmed
Normal
- Platform
- Parity
- command vanilla-parity
1.17 - 23w35a
1.17 1.17.1-pre1 1.17.1-pre2 1.17.1-pre3 1.17.1-rc1 1.17.1-rc2 1.17.1 21w37a 21w38a 21w39a 21w40a 21w41a 21w42a 21w43a 21w44a 1.18-pre1 1.18-pre2 1.18-pre4 1.18-pre5 1.18-pre6 1.18-pre7 1.18-pre8 1.18-rc1 1.18-rc3 1.18 1.18.1-pre1 1.18.1-rc2 1.18.1 22w03a 22w05a 22w06a 22w07a 1.18.2-pre1 1.18.2-pre2 1.18.2-pre3 1.18.2-rc1 1.18.2 22w11a 22w12a 22w13a 22w14a 22w15a 22w16a 22w17a 22w18a 22w19a 1.19-pre1 1.19-pre2 1.19-pre3 1.19-pre5 1.19-rc1 1.19-rc2 1.19 22w24a 1.19.1-rc1 1.19.1-pre2 1.19.1-pre3 1.19.1-pre4 1.19.1-pre5 1.19.1-pre6 1.19.1-rc2 1.19.1-rc3 1.19.1 1.19.2 22w42a 22w43a 22w44a 22w45a 22w46a 1.19.3-pre1 1.19.3-pre2 1.19.3-pre3 1.19.3-rc1 1.19.3-rc2 1.19.3 23w03a 23w04a 23w05a 23w06a 23w07a 1.19.4-pre1 1.19.4-pre2 1.19.4-pre3 1.19.4-pre4 1.19.4-rc1 1.19.4-rc2 1.19.4-rc3 1.19.4 23w12a 23w13a 23w14a 23w16a 23w17a 23w18a 1.20-pre1 1.20-pre2 1.20-pre4 1.20-pre5 1.20-pre7 1.20-rc1 1.20 1.20.1 23w31a 23w33a 23w35a
Created Issue:
command /whitelist has not been renamed to /allowlist
According to the Bedrock edition release notes (https://www.minecraft.net/en-us/article/caves---cliffs--part-i-out-today-bedrock), the /whitelist command has been renamed to /allowlist in Bedrock edition. Since the corresponding Java edition command has not yet been renamed, this change introduces a parity issue.
steps to reproduce:
- start a server
- type allowlist list
the server responds with something like:
[20:02:31] [Server thread/INFO]: Unknown or incomplete command, see below for error [20:02:31] [Server thread/INFO]: allowlist list<--[HERE]
- type whitelist list
the server responds with something like:
[20:02:36] [Server thread/INFO]: There are no whitelisted playerseven though this command should be removed in favor of allowlist
Environment
Arch Linux, kernel version 5.12.12
AdoptOpenJDK version 16.0.1+9
Thank you for your report!
However, this issue is Invalid.You reported a parity issue. We are only tracking parity issues that meet the following criteria on this bug tracker:
- The feature affected by the parity issue is present in both Bedrock Edition and Java Edition in the latest release or development version
- The feature behaves differently in one edition than in the other
- The parity issue was introduced in Buzzy Bees (Bedrock Edition 1.14 / Java Edition 1.15) or later and was not present before
Any parity issue that does not meet these criteria are not tracked on the bug tracker and should instead be reported on the Feedback website.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
command /whitelist has not been renamed to /allowlistCommand /whitelist has not been renamed to /allowlist
Arch Linux, kernel version 5.12.1
2
AdoptOpenJDK version 16.0.1+9Arch Linux, kernel version 5.12.14
OpenJDK version 16.0.1
Arch Linux, kernel version 5.1
2.14
OpenJDK version 16.0.1Arch Linux, kernel version 5.14.3
OpenJDK version 16.0.2
Arch Linux, kernel version 5.14.
3
OpenJDK version 16.0.2Arch Linux, kernel version 5.14.6
OpenJDK version 16.0.2
Arch Linux, kernel version 5.14.
6
OpenJDK version 16.0.2Arch Linux, kernel version 5.14.8
OpenJDK version 16.0.2
Arch Linux, kernel version 5.14.
8
OpenJDK version 16.0.2Arch Linux, kernel version 5.14.9
OpenJDK version 16.0.2
Arch Linux, kernel version 5.14.
9
OpenJDK version 16.0.2Arch Linux, kernel version 5.14.11
OpenJDK version 17 (build 17+35)
Arch Linux, kernel version 5.14.1
1
OpenJDK version 17 (build 17+35)Arch Linux, kernel version 5.14.12
OpenJDK version 17 (build 17+35)
Arch Linux, kernel version 5.14.1
2
OpenJDK version 17 (build 17+35)Arch Linux, kernel version 5.14.14
OpenJDK version 17 (build 17+35)
Arch Linux, kernel version 5.14.1
4
OpenJDK version 17 (build 17+35)Arch Linux, kernel version 5.14.15
OpenJDK version 17 (build 17+35)
Arch Linux, kernel version 5.14.1
5
OpenJDK version 17(build 17+35)Arch Linux, kernel version 5.14.16
OpenJDK version 17.0.1
Arch Linux, kernel version 5.1
4.16
OpenJDK version 17.0.1Arch Linux, kernel version 5.15.2
OpenJDK version 17.0.1
Arch Linux, kernel version 5.15.
2
OpenJDK version 17.0.1Arch Linux, kernel version 5.15.4
OpenJDK version 17.0.1
Arch Linux, kernel version 5.15.
4
OpenJDK version 17.0.1Arch Linux, kernel version 5.15.5
OpenJDK version 17.0.1
Arch Linux, kernel version 5.15.5
OpenJDK version 17.0.1

Can confirm
Clones
MC-187218. This might not be considered a valid parity issue as discussed in this r/mojira thread.As far as I can tell, BDS did not actually make that change despite the changelog
Why is whitelist considered offensive now anyway?
See the description of
MC-187218for an explanation. Otherwise, let's not discuss the nature of the term here, as this is not a discussion forum.reported @tryashtar's observation as
BDS-14119@Steve Hsu: because the issue is not dependent on which operating system or which JDK you're using, I've removed the environment from your report. But thank you very much for taking the time to update it!