Trevy the Great said:If I try to go buy another one, it tells me that I already have it!
Bishop said:
I jacked his account for testing. He has a key so he can't buy one, but it doesn't let him in because he's missing a key. :slapface:
Trevy can't chat
- Thread starter Bishop
- Start date
-
The masquerade of murder returns! A new game of Vampires Amongst Us has begun. Unmask the killers, trust no one, and try to survive the night. Find out more and sign up now!
I jacked his account for testing. He has a key so he can't buy one, but it doesn't let him in because he's missing a key. :slapface:
Change the name back for testing. Kye could be tied to an id, but validation on chat could be done via username.
Why not have a separate account for chatting? It's not as though there's a post-count or avatar in the chat room, just a username. It'd be a much simpler, albeit less sophisticated, solution.
Yeah, but if others change their usernames (which anyone can do now with Zombies) then the chat function may be broken for that user as well. It'd be better to fix the issue.
Ah, indeed. In the mean time let's hope nobody does, although you might need a non-moderator and non-true blood test subject...
Yep. That's exactly (what I think) is happening.
1) I created a test account and bought a chat key. I could chat.
2) I changed the username and then I get the same errors that Trevy is getting.
1) I created a test account and bought a chat key. I could chat.
2) I changed the username and then I get the same errors that Trevy is getting.
Ok, I will have to go back to the author of the plugin. It was meant to be tied to the user ID instead of the name.
@Bishop: it's a small test, I say do it. You don't know if a name change generates a new ID or not.
A name change does not generate a new ID, the ID remains the same (I can check on this in the ACP).
At the moment the coding for buying the key seems to refer to the ID, whilst the check when attempting access is somehow checking on the name. Its all very odd...
At the moment the coding for buying the key seems to refer to the ID, whilst the check when attempting access is somehow checking on the name. Its all very odd...
Could be a case of lazy programming. Where the name was easily accessible but the ID was not.
Also, his software may be configured to accept only one parameter, and if it accepted an ID, then the ID would be shown. Unsure. So the coder might have picked a quick and dirty way of getting it done.
Also, his software may be configured to accept only one parameter, and if it accepted an ID, then the ID would be shown. Unsure. So the coder might have picked a quick and dirty way of getting it done.
I have a coding change to fix this, but now there is an issue with our VPS blocking all FTP connections! I have reported it to our host who is investigating....
Permanently fix. References to the username have been removed / replaced with referencing the user ID only.