Razor only tries to open containers at login, and that is only because it needs to open them to count resources (which can be disabled via the "AutoSearch new containers" checkbox)
Razor attempts to queue doubleclick actions that the user (or the client) try to perform too quickly. You can disable this by disabling the 'queue delay actions' check on the more options tab.
If you have both of these unchecked, razor wont be doing anything at login and the client should behave exactly as normal. It's been my experience that the client is very unreliable with which gumps it opens when you login, and stuff like this. So.. are you sure this is even a razor issue? Consider performing the same tests lsited above while razor is not running, and post the results? Maybe do it a few times to be sure?
__________________
Zippy, Razor Creator and RunUO Core Developer
The RunUO Software Team
"Intuition, like a flash of lightning, lasts only for a second. It generally comes when one is tormented by a difficult decipherment and when one reviews in his mind the fruitless experiments already tried. Suddenly the light breaks through and one finds after a few minutes what previous days of labor were unable to reveal."
~The Cryptonomicon
|