ID:174711
 
Well, I have tried several login codes, but could get none of them to work for me. Could someone please send me a working one with some instructions. Either that or direct me to one that will work.
...Login screen tells us nothing what type one that you see for a sec then disapears or one that you have to use the arrows to move around on or one you have to click?
In response to Hendrix
The kind that you see for a sec.
In response to SS4Nate
Well you need to make one a bimap or whatever then add it to your game stick it on the map somewere and add the coding to your login like

sleep(20)
usr.loc=locate(where ever that bitmap is)
sleep(20)
usr.loc=locate(somewere else)
In response to Hendrix
Hendrix wrote:
Well you need to make one a bimap or whatever then add it to your game stick it on the map somewere and add the coding to your login like

sleep(20)
usr.loc=locate(where ever that bitmap is)
sleep(20)
usr.loc=locate(somewere else)

usr is a bad statement in a Login() procedure.

The safest way and best way to go around using your Login() procedures for mob location settings and what have you would be to use the src method.

--Lee
In response to Mellifluous
lol i havent coded in a while sorry about that your right use scr insted of usr
In response to Hendrix
well, I tried what you told me to do, and instead of appearing when you are logging in, it appears for a little while after you log in, and then takes you to the right location. Is there any way to fix this, I have tried finding a better place for it in the coding and messing with it myself, but it still doesn't go to the right place.
In response to SS4Nate
Your using deadrons char handeling?
In response to SS4Nate
If you're using what Hendrix showed you above, then you problem is the bolded "sleep()" procedure:

sleep(20)
usr.loc=locate(where ever that bitmap is)
sleep(20)
usr.loc=locate(somewere else)

All you need to do is remove the bolded out "sleep(20)" procedure and then it should work how you wanted it, if it does not then I would have to ask you to allow me to see your Login() procedure...

--Lee
In response to Mellifluous
I think hes using deadrons charhandeling 2 seconds wouldnt make a difference lee i bet whats happening is when he goes to load or creat a new char it pops up.
In response to Hendrix
Hendrix wrote:
I think hes using deadrons charhandeling 2 seconds wouldnt make a difference lee i bet whats happening is when he goes to load or creat a new char it pops up.

Yes, but, the point is that he asked why he was having to wait...

On some systems, that 2 seconds can be longer than 2 seconds, trust me.

On my oldest PC, a 2 second cycle time would have me waiting around 10 - 15 seconds. I know this from personal experience like, but still, I doubt his PC is as old as my old one :P

Anyway, Deadrons Character Handling will more than likely have nothing to do with this waiting time...

Plus, most people who don't create their own unique login procedure use Deadrons Character Handling, I for one use Deadrons Character Handling because I feel much more safer when I create my projects... Using a library that works with 100% efficiency, I see no reason to go about trying to make my own unique login procedure...

--Lee
In response to Mellifluous
I always make my own login coding. But the first game i made i did use deadrons char handeling. And from doing that i learn a little about how it works. So I think before we srgue about what is going wrong we should wait untill he tells us all if he is using the lib.