[SPIGOT-6358] /trigger does not work Created: 11/Feb/21 Updated: 18/Feb/21 Resolved: 18/Feb/21 |
|
| Status: | Resolved |
| Project: | Spigot |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Michael Schaefer | Assignee: | Unassigned |
| Resolution: | Invalid | Votes: | 0 |
| Labels: | 1.16.5, command, trigger, vanilla | ||
| Environment: |
Debian 10 with Java Runtime |
||
| Version: | 2991-Spigot-018b9a0-f3f3094 (MC 1.16.5) |
| Guidelines Read: | Yes |
| Description |
|
The /trigger command outputs the error-message 'You cannot trigger this objective yet' even if the trigger is enabled.
Steps to reproduce the bug: Install Spigot Server (Version as above) Install VanillaTweaks in datapacks folder (e.g. Coordinates HUD) Reload Server in the case it was running during installation of datapack Check wether the trigger is enabled (by issuing '/scoreboard player @a enable ch_toggle') Output: 'Nothing changed. That trigger is already enabled' Issue command '/trigger ch_toggle' Output: 'You cannot trigger this objective yet'
Minimal Commands: Register a trigger (this will not do anything, but that should not be a problem): /scoreboard objectives add test trigger Output: 'Created new objective test'
Enable trigger for next player: /scoreboard players enable @p test Output: 'Enabled trigger test for Username'
Test the trigger: /trigger test Output: 'You cannot trigger this objective yet' Since the trigger was enabled before, this should not appear.
Enabling command blocks does not change anything. |
| Comments |
| Comment by Michael Schaefer [ 14/Feb/21 ] |
|
Thank you for your replies. I should have tested it without plugins before opening an issue... I am sorry for concerning you with this problem. You may close this, since it is not an bug of spigot but of one of the plugins I had installed.
If anyone else encounters this problem: It might be a problem of PlaceholderAPI or Beauty Indicator plugin. Without these two it works fine for me. |
| Comment by md_5 [ 13/Feb/21 ] |
|
Those 3 commands work fine for me on spigot [10:12:55] [Server thread/INFO]: md_5 issued server command: /scoreboard objectives add test trigger [10:12:55] [Server thread/INFO]: [md_5: Created new objective [test]] [10:13:00] [Server thread/INFO]: md_5 issued server command: /scoreboard players enable @p test [10:13:00] [Server thread/INFO]: [md_5: Enabled trigger [test] for md_5] [10:13:02] [Server thread/INFO]: md_5 issued server command: /trigger test [10:13:02] [Server thread/INFO]: [md_5: Triggered [test]] Make sure you don't have any plugins installed when testing |
| Comment by Michael Schaefer [ 13/Feb/21 ] |
|
I have added a short way to reproduce the bug. |
| Comment by Michael Schaefer [ 13/Feb/21 ] |
|
I will try to find the minimal commands, but right now I have no access to my Minecraft.
I have tested the Datapack before installation on the Spigot Server on a Vanilla Server and in Single-Player. In both cases it works perfectly fine. Therefore it cannot be an issue of the Datapack. |
| Comment by md_5 [ 12/Feb/21 ] |
|
It would be nicer if you could include just the minimal commands needed to show the bug, not a whole datapack |