Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot access any commands after installation via RCON #54

Closed
lccpianoman opened this issue Oct 25, 2021 · 1 comment
Closed

Cannot access any commands after installation via RCON #54

lccpianoman opened this issue Oct 25, 2021 · 1 comment

Comments

@lccpianoman
Copy link

Hello,

I have been using this plugin for a while now, and all of my friends and I love it. I have recently moved my server to my own equipment to self-host, and I need to access the console via RCON so I can send commands on the go. My problem is that while I am in the console via RCON, I have no permission to perform any commands, with the exception of Spigot specific commands (/restart, /tps, and /timings). I don't even have permission to use /help. I believe the issue lies somewhere in the vane-permissions plugin, because a fresh installation without the plugin can send commands just fine. Here is my config.yml contents for vane-permissions, if anything else is needed I would be happy to share it:

# vim: set tabstop=2 softtabstop=0 expandtab shiftwidth=2:

# The language for this module. The corresponding language file must be named
# lang-{lang}.yml. Specifying 'inherit' will load the value set for vane-core.
# Default: "inherit"
lang: "inherit"

# The module will only add functionality if this is set to true.
# Default: true
enabled: true

# Enable plugin metrics via bStats. You can opt-out here or via the global bStats
# configuration.
# Default: true
metrics_enabled: true

command_permission:
  # Enable command permission
  # Default: true
  enabled: true

command_vouch:
  # Enable command vouch
  # Default: true
  enabled: true

  # The group to assign to players when someone vouches for them.
  # Default: "user"
  vouch_group: "verified"

# The permission group that will be given to new players.
# Default: "default"
default_group: "user"

# The permission groups. A player can have multiple permission groups assigned.
# Permission groups can inherit other permission groups by specifying
# vane.permissions.groups.<groupname> as a permission.
# Default:
#   default:
#     - bukkit.command.help
#     - bukkit.broadcast
#     - bukkit.broadcast.user
#   verified:
#     - vane.permissions.groups.user
#     - vane.permissions.commands.vouch
#   admin:
#     - vane.permissions.groups.verified
#     - vane.admin.bypass_spawn_protection
#     - vane.*.commands.*
#   user:
#     - vane.permissions.groups.default
#     - vane.admin.commands.spawn
#     - vane.admin.modify_world
#     - vane.regions.commands.region
#     - vane.trifles.commands.heads
groups:
  default:
    - bukkit.command.help
    - bukkit.broadcast
    - bukkit.broadcast.user
  verified:
    - vane.permissions.groups.user
    - minecraft.command.whitelist
  admin:
    - vane.permissions.groups.verified
    - vane.*.commands.*
    - minecraft.*
  user:
    - vane.permissions.groups.default
    - vane.trifles.commands.heads
    - minecraft.command.msg
    - minecraft.command.me
    - minecraft.command.help
    - backpack.use
    - backpack.fullpickup
    - backpack.size.2
    - backpack.clean

# Remove all default permissions to start with a clean preset.
# Default: true
remove_defaults: true

# DO NOT CHANGE! The version of this config file. Used to determine if the config
# needs to be updated.
version: 1

Any help would be appreciated!

-Luke

@oddlama
Copy link
Owner

oddlama commented Oct 26, 2021

Oh thanks for the report, I have never tested it with RCON and of course this shouldn't be the case. I will have a look if I can reproduce the issue myself and report back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants