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

Minecraft Input Plugin broken for 1.13 based servers #5477

Closed
jhg03a opened this issue Feb 24, 2019 · 6 comments · Fixed by #5733
Closed

Minecraft Input Plugin broken for 1.13 based servers #5477

jhg03a opened this issue Feb 24, 2019 · 6 comments · Fixed by #5733
Assignees
Labels
bug unexpected problem or unintended behavior
Milestone

Comments

@jhg03a
Copy link
Contributor

jhg03a commented Feb 24, 2019

Relevant telegraf.conf:

Any stock Minecraft input plugin config pointing to a valid Minecraft 1.13 based server.

System info:

Found with telegraf 1.9, but should affect all prior versions as well.

Steps to reproduce:

  1. Create a Minecraft 1.13 server
  2. Connect telegraf via the Minecraft input plugin to it

Expected behavior:

Some data as configured in the Minecraft scoreboard settings

Actual behavior:

No data

Additional info:

The input plugin is broken as a result of a change/bug in the RCON api. The plugin could be updated to instead of relying on a single RCON call for all the data to instead make +1 RCON calls to fetch player stats individually which does still work.

The plugin does still work for servers prior to the 1.13 update I believe.

@danielnelson
Copy link
Contributor

Might be some time before Mojang gets to this, so the workaround might be the way to go. Do you know the command to list all players?

@danielnelson danielnelson added the bug unexpected problem or unintended behavior label Feb 25, 2019
@jhg03a
Copy link
Contributor Author

jhg03a commented Feb 26, 2019

/scoreboard players list * would be replaced with a combination of /scoreboard players list and /scoreboard players list <playername> I believe.

@danielnelson danielnelson self-assigned this Feb 26, 2019
@danielnelson danielnelson added this to the 1.10.1 milestone Mar 6, 2019
@danielnelson danielnelson modified the milestones: 1.10.1, 1.10.2 Mar 19, 2019
@danielnelson danielnelson modified the milestones: 1.10.2, 1.10.3 Apr 2, 2019
@pkramme
Copy link

pkramme commented Apr 12, 2019

Anything I can do to help?

@danielnelson
Copy link
Contributor

I worked on this a bit last night but I still have a few hours of work. Turns out the response text changed as well so it has been a bit more work than expected, but I should have something ready for testing soon.

@danielnelson danielnelson modified the milestones: 1.10.3, 1.11.0 Apr 16, 2019
@danielnelson
Copy link
Contributor

Moving to 1.11, the changes are a bit too large for a patch release. Should have a build for testing this evening.

@pkramme
Copy link

pkramme commented Apr 16, 2019

This is great, thank you for keeping us in the loop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants