InventivetalentDev / NickNamer

Spigot Name & Skin changer plugin
https://www.spigotmc.org/resources/5341
MIT License
104 stars 28 forks source link

Json Error #6

Closed M9GLiquid closed 8 years ago

M9GLiquid commented 8 years ago

What steps will reproduce the problem?

  1. Running Your plugin and a custom plugin using JSON chat ( TextComponent(); )
  2. It doesn't brake the plugin just pumps out 700 rows of errors each time you click/hover or anything else json related
  3. What were you expecting to happen? What happened instead?

Should happend: No errors and my Json to be shown normally Actually happend: Alot of Errors and my json displayed normally

What version of the plugin are you using? Type /version <Plugin Name>

PacketListenerAPI_v3.4.2.jar with NickNamer 3.11.4

What Spigot version are you using? Type /version

Spigot 1.9.4

What plugins ae you using? Type /plugins

Plugins

Do you have an error log? Use pastebin.com. If you're not sure, upload your whole server log

Part involving NickNamer (PacketListener) Partial Log

Did your client crash? Upload errors in .minecraft/logs/latest.log as well

No.. Full Log: Full Log

Additional information? (Are you using Bungeecord? Did it work in previous versions? etc.)

Test Server with my own custom plugin.

Code I used that it dislikes: `/**

Regards, Thomas

InventivetalentDev commented 8 years ago

Please try disabling the chat-replacement options. Does the message you try to send contain any names if nicked players?

M9GLiquid commented 8 years ago

No only help options for support but it might in the future as I got my own placeholder system for my own game.

I'll try disabling the chat-replacement

M9GLiquid commented 8 years ago

Did not work by disabling the chat...

Config.yml: Config.yml

M9GLiquid commented 8 years ago

*Updated the url's in here :D

M9GLiquid commented 8 years ago

Solvable Solution: Other servers have to use Package Json (example: FancyMessage) As it does not interfere with other Json Packaging

InventivetalentDev commented 8 years ago

Fixed in version 3.11.7.