Printable View
In an "On Name Set Request" event, it seems that calling the "Change Requested Name" action is not working as it should. I have enabled the trigger and verified that the event is triggered.
Trying to select the client before calling the action did not see to help either.
What I'm trying is a quick authentication by receiving "username:password" and if password is correct set the name to "username".
Is this a bug in the extension or am I missing something?
Might be a bug - are you sure the condition is enabled as interactive?
Yes, and the "Deny" branch works to prevent the change.
Ok, must be a bug then! I'll fix it for the next build.
I did a little workaround on that. Might not be that good, but it works.
In short, if the username matches, set the username to a global string.
then disconnect and reconnect using the username from the global stirng on another screen that goes straight through.
There is no verification from that screen, but the user had to be verified to get there.
It worked for me! I just made a small test and the change requested name feature works fine.
LB, are you using beta 14?
Can you send me the .mfa file?
There is no beta 14...
Build 14
The minimal example attached actually "crashes" the server when I set the name. This should make it easy to track down the bug (or the misuse in my code if any).
The server doesn't crash, and it works properly for me. I did notice, however, that holding down the F2 key in the client causes it to freeze up when you let go. Which, is probably my fault anyway XD
Can you try this client mfa with the server mfa I uploaded earlier and let me know if it changes the name correctly for you?
Yes, it changes correctly. Maybe the behavior is different due to the bug?
What bug? If we're using the same version then we should have the same bug.
I must be using the wrong version of something. The one I'm using was built on 03/05/2010. Is that what you're using?
Hmm, I redownloaded both extensions, and now the name changing doesn't work. No crash, though.
So it used to work in the old one but not in the latest version. Then it is indeed a bug and not just me.