[BDS-4911] Documentation of console command mismatches actual syntax: permission/permissions

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

permissions <list | reload> list prints the current used operator list.
reload makes the server reload the operator list from the ops file.
See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
Unknown command: permissions. Please check that the command exists and that you have permission to use it.
permissions reload
Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

permission list
###*

{"command":"ops","result":["2535450022930213"]}

*###
###* {"command":"permissions","result":[

{"permission":"operator","xuid":"2535450022930213"}

]}
*###

   permission reload
   Ops reloaded from file.
   Permissions reloaded from file.

Suggested solution: Either adapt documentation, or change command syntax in server.

Separate suggestion but maybe not worth a separately mentioned issue: Could mention the other working server commands with their correct syntax in the documentation, e.g. gamerule. Found out about this command by typing help. Works fine, just not mentioned in documentation file.

Thanks!

Linked Issues

duplicates1

BDS-2341Typo in html help file for reloading permissionsFixed

Comments1

IonicEcko 2020-05-02, 10:13:42 AM

edited 2020-05-02, 10:13:59 AM

We're tracking this issue as ~~BDS-2341~~, so this ticket is being resolved and linked as a duplicate.

If you aren't already, please don't forget to use the search feature, the less time volunteers spend linking duplicates the more time we have to update new reports.

Voting on an existing report has a greater impact on getting the bugs most important to you fixed!

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs

History9

Thomas 2020-05-01, 07:08:41 PM

Changed description:

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0permissions reload
0Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

permission list

0
1. 0
  1. 0
    0
  0
0

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

permission list

0
1. 0
  1. 0
    - {{0{"command":"ops","result":["2535450022930213"]}0
      }}{{ *###}}
      0
    - {"command":"permissions","result":[}}{{Unknown macro: \{"permission"}}}{{]}
      0{{ *###}}
      0{{ permission reload}}
      0{{ Ops reloaded from file.}}
      0{{ Permissions reloaded from file.}}
    0
  0
0

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Thomas 2020-05-01, 07:11:22 PM

Changed description:

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

{{0{"command":"ops","result":["2535450022930213"]}0

}}{{ *###}}

{"command":"permissions","result":[}}{{Unknown macro: \{"permission"}}}{{]}
0{{ *###}}
0{{ permission reload}}
0{{ Ops reloaded from file.}}
0{{ Permissions reloaded from file.}}

permission list

0
1. 0
  1. 0
    - {{0{"command":"ops","result":["2535450022930213"]}0
      }}{{ *###}}
    - {"command":"permissions","result":[}}{{Unknown macro: \{"permission"}}}{{]}
      0{{ *###}}
      0{{ permission reload}}
      0{{ Ops reloaded from file.}}
      0{{ Permissions reloaded from file.}}
    0
  0
0

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

permission list
0###* {"command":"ops","result":["2535450022930213"]}
0{{ *###}}
0{{###* {"command":"permissions","result":[0{{ Ops reloaded from file.}}0{{ Permissions reloaded from file.}}

0{"permission":"operator","xuid":"2535450022930213"}0

]}}}
0{{ *###}}
0permission reload
0Ops reloaded from file.
0Permissions reloaded from file.

000

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Thomas 2020-05-01, 07:11:59 PM

Changed description:

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

permission list
0###* {"command":"ops","result":["2535450022930213"]}
0{{ *###}}
0{{###* {"command":"permissions","result":[

0{"permission":"operator","xuid":"2535450022930213"}0

]}}}
0{{ *###}}
0permission reload
0Ops reloaded from file.
0Permissions reloaded from file.

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

permission list
0 {{###*

0{"command":"ops","result":["2535450022930213"]}0

}}0}
0 {{ *###}}
0 {{###* {"command":"permissions","result":[

00{"permission":"operator","xuid":"2535450022930213"}00

]}}}
0 {{ *###}}
0permission reload
0Ops reloaded from file.
0Permissions reloaded from file.

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Thomas 2020-05-01, 07:14:56 PM

Changed description:

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

permission list
0 {{###*

0{"command":"ops","result":["2535450022930213"]}0

}}0 {{###*
0 {{ *###}}
0 {{###* {"command":"permissions","result":[

00{"permission":"operator","xuid":"2535450022930213"}00

]}}}
0 {{ *###}}
0permission reload
0Ops reloaded from file.
0Permissions reloaded from file.

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

00{"command":"ops","result":["2535450022930213"]}0

permission list
0###* {"command":"ops","result":["2535450022930213"]}
0{{ *###}}
0{{###* {"command":"permissions","result":[

0{"permission":"operator","xuid":"2535450022930213"}0

]}}}
0{{ *###}}
0permission reload
0Ops reloaded from file.
0Permissions reloaded from file.

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Thomas 2020-05-01, 07:15:30 PM

Changed description:

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

permission list
0###* {"command":"ops","result":["2535450022930213"]}
0{{ *###}}
0{{###* {"command":"permissions","result":[

0{"permission":"operator","xuid":"2535450022930213"}0

]}}}
0{{ *###}}
0permission reload
0Ops reloaded from file.
0Permissions reloaded from file.

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

permission list
0
0
0
0
0
0
0
0
{"command":"ops","result":["2535450022930213"]}
0 *###
0
{"command":"permissions","result":[0
Unknown macro: {"permission"}
0
]}
0 *###
0permission reload
0Ops reloaded from file.
0Permissions reloaded from file.
0}0{{ *###}}0{{###* {"command":"permissions","result":[
00{{ *###}}000
0
0
0
0
0
0
0

00{"permission":"operator","xuid":"2535450022930213"}00

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Thomas 2020-05-01, 07:16:04 PM

Changed description:

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

permission list
0
0
0
0
0
0
0
0
{"command":"ops","result":["2535450022930213"]}
0 *###
0
{"command":"permissions","result":[0
Unknown macro: {"permission"}
0
]}
0 *###
0permission reload
0Ops reloaded from file.
0Permissions reloaded from file.
0
0
0
0
0
0
0
0

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

   permission list
0   ###* {"command":"ops","result":["2535450022930213"]}
0    *###
0   ###* {"command":"permissions","result":[

0{"permission":"operator","xuid":"2535450022930213"}0

]}0 *###
0    *###
0   permission reload
0   Ops reloaded from file.
0   Permissions reloaded from file.

000

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Thomas 2020-05-01, 07:16:32 PM

Changed description:

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

   permission list
0   ###* {"command":"ops","result":["2535450022930213"]}
0    *###
0   ###* {"command":"permissions","result":[

0{"permission":"operator","xuid":"2535450022930213"}0

]}
0    *###
0   permission reload
0   Ops reloaded from file.
0   Permissions reloaded from file.

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

Hi,

upon experimenting with the server I found a mismatch between documentation and actual behaviour for the /permission command.

Version: Bedrock dedicated server 1.14.60.5

Documentation (HTML file that comes with the downloaded server) states, in chapter Permissions:

If you change this file while the server is running, then run the command permissions reload to make sure that the server knows about your new change. You could also list the current permissions with permissions list.

Also mentioned with this same syntax in the commands list.

000000

permissions <list | reload> list prints the current used operator list.
0reload makes the server reload the operator list from the ops file.
0 See the Permissions section for more information.

Actual behaviour when typing the commands into the server console:

permissions list
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.
0 permissions reload
0 Unknown command: permissions. Please check that the command exists and that you have permission to use it.

Accepted syntax is permission without the s:

permission list
0 ###*

0{"command":"ops","result":["2535450022930213"]}0

*###
0 ###* {"command":"permissions","result":[

00{"permission":"operator","xuid":"2535450022930213"}00

]}
0 *###

00{"permission":"operator","xuid":"2535450022930213"}0

   permission reload0    *###0   permission reload
0    Ops reloaded from file.
0    Permissions reloaded from file.

Suggested solution: Either adapt documentation, or change command syntax in server.

Thanks!

IonicEcko 2020-05-02, 10:13:42 AM

Added duplicates link:
BDS-2341Typo in html help file for reloading permissionsFixed

IonicEcko 2020-05-02, 10:13:42 AM

Resolution: Unresolved → Duplicate