LuckPerms

LuckPerms

41.4k Downloads

Target selectors not working on sponge with functions

DaveDevil opened this issue ยท 2 comments

commented

Description

Target selectors not working on spongeforge server if executed from functions

Reproduction steps

  1. Create a spongeforge server. I'm actually using forge-1.12.2-14.23.5.2847 with spongeforge-1.12.2-2838-7.2.0 only as mod, and LuckPerms-Sponge-5.3.34 as plugin.
  2. Start your server, let the world be generated.
  3. Stop the server. Go to .root_server_directory/world_directory/data/functions
  4. Create a folder named "custom"
  5. Insert a file named "test.mcfunction"
  6. Insert in that file these commands:

say @a message with selector say message without selector

  1. From console, try the command "say @A message with selector", it works fine
  2. From console, try the command "function custom:test", it prints only "[server]message without selector". The command with the selector won't work

Expected behaviour

I'm expecting that both commands from the functions works, because the single commands are working if executed from console

Environment details

Removing luckperms plugin fixes the problem

  • Server type/version: Forge 1.12.2 - 14.23.5.2847 with SpongeForge 1.12.2 2838 7.2.0
  • LuckPerms version: v5.3.34

Any other relevant details

The console says "INFO Executed 2 command(s) from function 'custom:test'" but before this it only says "INFO [Server] playername message without selector", it's missing the line "INFO [Server] playername message with selector". It's not like it does not find the player, it should say "INFO [Server: Selector '@A[name=playername]' found nothing]"

commented

Hello! Does this still occur with the latest version of SpongeForge and the latest version of LuckPerms from https://luckperms.net ? If so, could you please send console logs of the attempt to supplement your description?

commented

I'm going to close this on the assumption that something has changed and this is no longer a problem. If you or anyone else reading this happens to encounter it again, please do open a new issue and fill out the new issue template. Thank you!