Sorry, fell asleep in my chair xD (long night/day)
Anyway issue should be fixed now, there was a caching issue where if a certain type of music bot connected, it would think users of the same type was also a music bot, owned by the original music bot owner and check if the original music bot owner ip matched the ip of the user joining the ts
Heads up
Server group revoked with the API method
Removed the old API key and generated a new one :
Service Link Status
Service Service Link
GuildWars 2 jdkL.xxxx
Website Nirnee
Teamspeak
It would recognize my TS id before changing the API key, but would still revoke my server group assignment.
It still recognizes your id, but when you change your API key, it refreshes the cache and removes the old cached name. I guess it doesn't really have to, but for now i have just changed it to say that it doesn't have the name cached. Will probably change it later.
As long as it doesn't in red say "Not Linked" you are good
Also people putting their API key gets refused or something ..
Anyone you can referere me to? might just be the same old, people forgot they had a second account with the api key already but maybe not. (Or maybe people entering their api key name as their api key, that one is a classic
![Smiley :)](/Smileys/FlatEmoji/smiley.gif)
)
Just created new gw2 accounts both for fsp, linked and not linked worlds, all work fine, both for ts only linking and forum+ts linking