Specify source IP address for client

[peerstream]

Hello,

Is it possible to pass the client source IP address to xiloader as an argument when connecting to the private server? If not, are there other ways to specify it?
I'd like to use different source loopback IP addresses when connecting with multiple accounts. Server is of course local.

[whasf]

Sure, you can pull the source to XILoader and add that yourself
https://github.com/DarkstarProject/xiloader

[TeoTwawki]

A better solution would be to make the lobby handle its connections to players per-account. That would also get rid of multibox problems like when your alts randomly don't get variables or keyitems set because the same machine has 2 (or more) accounts sharing a socket and neither the clients or the is sure which one is being talked to..

[peerstream]

Sure, you can pull the source to XILoader and add that yourself
https://github.com/DarkstarProject/xiloader

If I knew how to code it I wouldn't have posted here . I did spend time finding a way to make it work (e.g., forcebindip works with xiloader, but I can't pass it in the windower settings).

Anyway thanks for the answers and for your great project.

[whasf]

A better solution would be to make the lobby handle its connections to players per-account. That would also get rid of multibox problems like when your alts randomly don't get variables or keyitems set because the same machine has 2 (or more) accounts sharing a socket and neither the clients or the is sure which one is being talked to..

I don't think it's a problem with the lobby, that just handles authentication and then passes the character off to the world server. I think the problem is in the game server itself.

[TeoTwawki]

I don't think it's a problem with the lobby, that just handles authentication and then passes the character off to the world server. I think the problem is in the game server itself.

Nope. Its the lobby+loader, and both need modifications.

If you try to log in 2 accounts at the same time before one of them has both selected character and arrived in game, hilarity ensues. That's before you ever hit the game server.

There are a variety of not-worth-documenting obvious problems that begin to happen in multibox situations that work fine if you only log in one character and are not the fault of any scripting mistakes, which sucks for people running servers (and our bug-tracker, occasionally).

[peerstream]

If you try to log in 2 accounts at the same time before one of them has both selected character and arrived in game, hilarity ensues. That's before you ever hit the game server.

That's exactly the issue which from my testing, is not resolved using different source addresses (as you have pointed out the problem is elsewhere).

You need proper timing when logging in, else you bump into errors and you just lose time and get irritated.

[TeoTwawki]

That's exactly the issue which from my testing, is not resolved using different source addresses (as you have pointed out the problem is elsewhere).

You need proper timing when logging in, else you bump into errors and you just lose time and get irritated.

Yeah you stagger/delay logins to get around it to get in. But after you are in, you still run into problems seemingly at random trying to gain or lose a key item, change the value of a variable, sometimes even changing zones (there is a rare crash I am 99% sure is from this last one). This makes a lot of players think Darkstars Lua scripts are wrong when they aren't - its really the network code is just ancient garbage none of us have both the know how and time to properly refactor so far.

p.s.
mis attributed quote