Talk:Login

From libopenmetaverse - libomv - Developer Wiki

Jump to: navigation, search

Has anyone tried instead of using "last" or "home" for "start" (location), use a coordinate in secondlife:// form? Such as sim/x/y? I think that should be acceptable since uh 1.9.1? I recall a Linden in a debug reply that it uses the / instead of a space, I'm not sure if the "secondlife://" is added on to the front silently or not. I might try this myself. Oz Spade 11:32, 25 July 2006 (PDT)

Doing a little research of my own on this... it seems that "<member><name>start</name><value><string>uri:Ahern&125&125&0</string></value></member>" is being sent on login instead of "last" or "home". However I'm missing something because this alone does not work. I get the error: "Unable to connect to a simulator." Another thing to note is that "<member><name>start_location</name><value><string>url</string></value></member>" is given in the methodResponse, the difference here being "url" instead of "home" or "last". Sending say "secondlife://ahern/125/125/0/" does not work either, nor do any variants. Ideas? Oz Spade 15:17, 25 July 2006 (PDT)


In your code, use NetworkManager.StartLocation(simname, x, y, z); which will return a string you can pass to Client.Network.Login() to start at a specific location. Keep in mind that this won't override landing spots that people have set on their land or bans, so you aren't guaranteed to land exactly where you specify. And if the simname doesn't exist or can't be contacted at the time login will fail. Jhurliman 14:13, 10 April 2007 (PDT)



As per the libsecondlife-dev mailing list, one now needs to send a new field for proper authentication:

<member><name>agree_to_tos</name><value><string>true</string></value></member>

... or else you'll just get a copy of the ToS instead of a "successful login" response :)

Gwyneth Llewelyn 19:11, 29 July 2006 (PDT)


Also, the MAC address should be MD5'ed.

Gwyneth Llewelyn 05:03, 30 July 2006 (PDT)


Oz, I've tried for several hours to understand that format as well! In my case, I'm able to see that you get to send indeed &amp;, but somehow, my own XML-RPC library seems to eat up some characters in there. In any case, what LL servers get is definitely NOT what they expect to receive! Some character translation is needed, and I tried as many possible tricks, but utterly failed to get it working as well.

The rest works fine, though :)

Gwyneth Llewelyn 15:38, 30 July 2006 (PDT)

It'd be interesting to see if slurl links provided any information when sending to the client somehow. I haven't tried using snowcrash or anything, but that might also help in seeing what exactly is going on with the whole location thing. Oz Spade 23:46, 31 July 2006 (PDT)