Lacewing server object... name set issues

[Konidias]

I'm trying to do some external login verification for the players when they attempt to login to my server. When the client sends a name set request to the server, the name sent is "username@password". Then in the server, it checks for "On name set request" and it needs to:

1. parse the requested name so that it can look at both the username and password
2. verify the username and password is correct via an external method of checking a database
3. if information is correct, it allows for set name... if not, it denies.

So my problem is that "deny request" is only valid when it is used in the "On name set request" condition. But if I'm having to run several other conditions after the fact, it's no longer in the "On name set request" condition. So how do I deny the name if I have to run through several separate conditions to verify the login details?

What the events look like:

On name set request
- parse requested name
- send the two parsed strings to a login php script to check in a database
- then what? I can't deny at this point because it doesn't know if the login info is valid or not.

Condition here to confirm if it is valid
- allow name set

Condition here to confirm it is not valid
- deny name set

But I can't do those conditions. It's all or nothing. I have to deny in the same condition as the request... which is not really going to be possible.

[RickyRombo]

On Get Complete

and

Compare Two General Values

are what you're looking for.

[Konidias]

no no I mean I know what conditions to put... The problem is that in the "On Get Complete" condition, I can't do the "deny name set" action with lacewing because it's no longer in the "On name set request" condition.

[LB]

On name set request: GET Url, Start loop "Wait" -1 times (infinite)
On Get Complete: Stop loop "Wait"
On name set request & Received$ == whatever: Deny Name Set

No idea if it will work.....give it a try

[Konidias]

I would imagine no, simply because "On name set request" is run at the start of the loop and once it's done it the one time, it isn't going to wait for any other conditions to do it again. It would need to receive another name set request.

[LB]

Um, no, MMF2 triggers ALL Immediate events no matter what. The only way the second one would not run is if it returned false to MMF2, and most immediate events without parameters simply return true, such as this one.

Also, since the fastloop keeps it on that event, you will have plenty if time to respond.

You may want to change the fastloop from -1 to just a high number so after 5 seconds it finishes anyway. (Don't want to freeze the server permanently if it can't get the URL) You may also need an "On Loop" event with at least 1 action.