Skip to content
This repository has been archived by the owner on Jun 2, 2023. It is now read-only.

BIG PROBLEM: The variable %player% does not supports names with spaces #222

Open
ghost opened this issue Jul 16, 2021 · 1 comment
Open
Assignees

Comments

@ghost
Copy link

ghost commented Jul 16, 2021

Describe the bug
the variable %player% does not support names with spaces
I tried to add a permission of pureperms when entering a zone, so i put:

rg flag set Shop console-cmd-on-enter setuperm %player% levellimiter.bypass.shop

Because the syntax of pureperms to add a permission to a player is setuperm (player) (permission) (world)

I also tried to put double quote ("") besides %player% variable but does not works ("%player%")

And pureperms says "world not found" but when i put it in the chat as a normal command with double quote
("") it works perfectly so i think the variable %player% does not support names with spaces and this is a big problem

To Reproduce
Steps to reproduce the behavior: This is an example, but can be reproduced with any flag that requires the variable player on a player with spaces in his name

  1. Add a permission for entering a region, for example, ' rg flag set Shop console-cmd-on-enter setuperm %player% levellimiter.bypass.shop'
  2. Login with an account with spaces in their name (e.g Julian alfonso)
  3. Pureperms will say that the world does not exists 'World levellimiter.bypass.shop does NOT exist'
  4. See error

Expected behavior
Being able to execute commands as people with spaces in their name.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: I am using a host but i think the host uses Linux
  • Browser [Opera GX but im using a host so that doesnt matter]
  • Version [WorldGuard version 1.1.95]

Additional context
I explained everything.

@awgybop1
Copy link
Collaborator

Hello,

I see the problem, I will work on getting this fixed for the console-cmd flags.

@awgybop1 awgybop1 self-assigned this Apr 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant