I had something like this happening. I was at an idoc with an unbonded beetle and filled it with loads of goodies worth lots of money. Then my client when i tried to sit up on the beetle. After logging in again the beetle was gone and no corpse, all items lost.

Think i may have lost an agapite runic a week ago also while throwing away my dull copper and shadow runics, cant blame anyone for that though

I did a fast count, about 130 entries from that kind of variables in my registry. Only a month old install though

Hmmm, can't you just set the expected login time/date when you logout. For example:

set %logindate #date + 1
set %logintime 033000
and then:

Repeat
until #date >= %logindate && #Time >= %logintime
Login script goes here.
I guess you could calculate the time to wait instead of using a repeat until to save some cpu but i'm to tired for that right now

Thx for the quick help. Found two return in the middle of subs without namespace pop which probably caused it. Will try again to see if i get some hickups.

Now for an offtopic question: I am writing a script that uses another persons sub/script (craftinfo.txt by kal in ex). How do you go about to give proper thanks/acknowledgement when you have written a script that calls someone elses? Is it enough just to put the persons name in your header and a link, or should you ask the author for permission first?

Lol i seem to have stumbled upon yet another strange error (probably because i really don't have any clue about the inner workings of easyuo).

I have a sub which is suposed to open a bod, then click all the apropriate items in the backpack. Usually it works fine but sometimes it gets stuck and gets quite a weird behavior. In the code (to open the bod i have:

fillbod:
set #LOBJECTID !bod
event macro 17 0
This always seems to work the first time the bod is supposed to open. But if some errors are detected the code jumps to "fillbod:" again to restart. When that happens it doesn't manage to set the variable #LOBJECTID. I have checked by stepping thrue the code and saw that sometimes the line "set #LOBJECTID !bod" didn't set #LOBJECTID to the value in !bod (even though the value in !bod was set).

Has anyone got any idea what can make the set-command stop working sometimes?

Something like this?
retry:
if %stay = enjoy
  return #true
set %stay enjoy
goto retry
Welcome

Ahh thx, i'll try your wait times to see if i get better results

Hmmm, true. I will test that, thx