PlayerSQL Breaks CombatTag

[gh0ztbuster]

RE: PlayerSQL Breaks CombatTag

When just PlayerSQL and CombatTag are installed at the same time one of two weird things happens. The player logs out and in chat is declared dead on the server. Then one of two weird things happen (it appears to choose 1 or 2 randomly):

Player logs back on and after clicking the respawn button is back where he/she died with the same inventory. The player's "body" or skin is frozen in death animation (sideways, vibrating, and flashing red).
Player logs back on and is in stuck in the respawn screen. Clicking "Respawn" does nothing and the only way to leave the menu is "Title screen".
I think the cause of the confliction is in CombatTag because I am currently using No PvP Log and it works perfectly fine with PlayerSQL. No PvP Log, however, lacks many features and does not protect players in Worldguard or Safezone Faction Areas.

I apologize that I can't explain it any further. Thank you so much for looking this over.

No PvP Log: http://dev.bukkit.org/bukkit-plugins/no-pvp-log/ PlayerSQL: http://www.spigotmc.org/resources/playersql.552/

[gh0ztbuster]

Update: AntiCombatLogging works with PlayerSQL. I think this is because it kills the player when they log off and when they log back on. I saw two death messages in vanilla, one when logging out, and one when logging in. On my server, I use PrivateDeathMessage so it only displays the one on log out.

Hope this helps :)

AntiCombatLogging (premium): http://www.spigotmc.org/resources/anti-combat-logging.2026/

[Techcable]

I know right where the problem is.
CombatTag saves to the player file.
PlayerSql saves to a sql database.

Unfortunately i'm keeping most issues on hold until i rewrite combat tag (horrible code).