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

Bug with death achievement #67

Closed
JohOply opened this issue Jul 31, 2016 · 11 comments
Closed

Bug with death achievement #67

JohOply opened this issue Jul 31, 2016 · 11 comments
Labels
invalid Not a valid issue. investigate Let's figure out what's going on here!

Comments

@JohOply
Copy link

JohOply commented Jul 31, 2016

Hi guys,

I think there is a bug with death achievement: i obtain first achievement for each new type of death (first time with /slay command, next time with a fall down, another time when a zombie killed me...)

It's really interesting to have achievements for each type of death, but for now seems be a bug

I use AACH 3.0 and Spigot 1.10.2

@PyvesB
Copy link
Owner

PyvesB commented Jul 31, 2016

Hello,

Death achievements do not currently support different types, only Kills, Places, Crafts and Breaks do. ;-)

Cheers,

Pyves

@JohOply
Copy link
Author

JohOply commented Jul 31, 2016

Yeah i understand that. But the problem seems be here! I will try to explain: i tried the plugin today, and i kill myself many times. First i used /slay, i got achievement. Next /slay, no achievement, next the same, etc.
Some time later, on the same session, i dead because of a zombie. Achievement appear (there is only an achievement for the first death in config).
Some time later again, i fall on the ground and i was dead. Achievement appear again.

@PyvesB PyvesB added the investigate Let's figure out what's going on here! label Jul 31, 2016
@PyvesB
Copy link
Owner

PyvesB commented Aug 5, 2016

I have not been able to reproduce this bug.

  • What version of the plugin are you using?
  • What database type?
  • Can you show me the Deaths section of your config?
  • Have you got any plugin errors or warnings in the console?
  • Did you change anything in the config between two same achievement receptions?

@JohOply
Copy link
Author

JohOply commented Aug 13, 2016

  • Plugin version 3.0.2
  • Mysql
  • http://pastebin.com/133uPVhy (i'm not sure that was the config when the problem happen :/)
  • I don't remember any error (i can't check right now)
  • I don't remember anything like, BUT if it is the case, what happen? :)

@PyvesB
Copy link
Owner

PyvesB commented Aug 15, 2016

I do currently not have enough spare time, but I'll look into it again eventually with the information you added. ;-)

@JohOply
Copy link
Author

JohOply commented Aug 16, 2016

Mhhh, i think there is the same with other achievements.. i will investigate too ^^

@JohOply
Copy link
Author

JohOply commented Aug 17, 2016

Yesterday i got "first hour" achievement. Today, i joined the server, a few time later : got achievement again

Here 2 books: i got one yesterday, another today
http://i.imgur.com/WJ65OKO.png
http://i.imgur.com/8w2P7Vg.png

No changes between.

@PyvesB
Copy link
Owner

PyvesB commented Aug 17, 2016

Did any errors appear in the console yesterday or today? Could you please send me your full config?

@JohOply
Copy link
Author

JohOply commented Aug 17, 2016

Oh wait, lot of errors

The last packet successfully received from the server was 102,347 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.
[18:57:44] [Server thread/INFO]: [AdvancedAchievements] Player JohOply received the achievement: playedtime_1 (First Hour)
[18:58:06] [Server thread/INFO]: JohOply issued server command: /aach book
[18:58:06] [Server thread/ERROR]: [AdvancedAchievements] SQL error while retrieving achievements: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
[19:04:32] [Craft Scheduler Thread - 1127/ERROR]: [AdvancedAchievements] SQL error while handling play time registration: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure. The last packet successfully received from the server was 379,150 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.

Loading seems OK

[06:22:25] [Server thread/INFO]: [AdvancedAchievements] Enabling AdvancedAchievements v3.0.2
[06:22:25] [Server thread/INFO]: [AdvancedAchievements] Backing up and loading configuration files...
[06:22:25] [Server thread/INFO]: [AdvancedAchievements] Loading configs, registering permissions and initialising command modules...
[06:22:25] [Server thread/INFO]: [AdvancedAchievements] Loaded 75 achievements in 36 categories.
[06:22:25] [Server thread/INFO]: [AdvancedAchievements] Backing up database file...
[06:22:25] [Server thread/INFO]: [AdvancedAchievements] Checking for plugin update...
[06:22:26] [Server thread/INFO]: [AdvancedAchievements] Registering listeners...
[06:22:26] [Server thread/INFO]: [AdvancedAchievements] Initialising database and launching scheduled tasks...
[06:22:28] [Server thread/INFO]: [AdvancedAchievements] Plugin successfully enabled and ready to run! Took 2825ms.

First error (with first connected player)

[13:35:00] [Server thread/ERROR]: [AdvancedAchievements] SQL error while handling play time registration: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 25,952,620 milliseconds ago. The last packet sent successfully to the server was 25,952,637 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.

Config http://pastebin.com/2zeZUR3X

@PyvesB
Copy link
Owner

PyvesB commented Aug 17, 2016

Okay, no wonder you are having issues. This is weird though, I have never encountered this type of errors before. Most related topics I found generally point out to a problem on the client side. Could you make sure you are using the latest version of the MySQL JDBC driver? Also, can you try restarting your database service. If you still have problems after this, there are additional steps you can try out, described in the top answers of the following links: link 1, link 2

@PyvesB PyvesB added the invalid Not a valid issue. label Sep 3, 2016
@PyvesB
Copy link
Owner

PyvesB commented Sep 3, 2016

Hello,

As it has been more than two weeks, I'm assuming you managed to solve the issue with the links I gave you, and am therefore closing the issue.

Cheers,

Pyves

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
invalid Not a valid issue. investigate Let's figure out what's going on here!
Projects
None yet
Development

No branches or pull requests

2 participants