ScriptUO

Official ScriptUO EasyUO Scripts => Scripting Chat => Topic started by: Paulonius on September 01, 2010, 02:23:51 PM

Title: Reliable Container Open Confirmation
Post by: Paulonius on September 01, 2010, 02:23:51 PM
I am wondering whether anyone has a reliable means in EUO to drop in a check to confirm whether an event macro 17 0 has been effective to open a container.

My thoughts:
1.   I could look for an item in the container and if my #FindCnt is greater than zero its open, but that won't work for containers that are empty.

2.   I was hoping that I might be able to reset one of the related values other than #LobjectID and then look for a change, but it appears that the container variables are not two way variables, so that is not a very promising venue.

3.  My last idea was to use option 1 first, and if it doesn't detect anything, switch the current container to the backpack by opening it before attempting the container again, and then checking against container ID.  This would be slower, but ought to be reliable.

Anyone have a better solution?
Title: Re: Reliable Container Open Confirmation
Post by: Cerveza on September 01, 2010, 03:15:23 PM
Gumpwait?
Title: Re: Reliable Container Open Confirmation
Post by: TrailMyx on September 01, 2010, 03:32:21 PM
I've developed LOTS of different methods for this.  My favorite and one that works for most instances is:

1. Note present #CONTID
2. open target container
3. wait until present container doesn't match noted container

If you know the #CONTSIZE that's going to be opened, that'll help filtering things out.

The CLAw has a REALLY aggressive filtering scheme because of all the errant gumps that fly around during combat.
Title: Re: Reliable Container Open Confirmation
Post by: Endless Night on September 01, 2010, 04:05:09 PM
I've developed LOTS of different methods for this.  My favorite and one that works for most instances is:

1. Note present #CONTID
2. open target container
3. wait until present container doesn't match noted container

If you know the #CONTSIZE that's going to be opened, that'll help filtering things out.


Dito .. thats the method i use as well.   Also if reopening the same type of containor over and over.. you can have it store the contkind on the first open and check that on successive openings.  (rember contkind changes after each patch so script must learn it to use it)
Title: Re: Reliable Container Open Confirmation
Post by: Paulonius on September 01, 2010, 07:10:53 PM
I like the ID check, that should work for what I am doing - which is opening a series of ten containers, a miss on any of which causes the script to go wanky.

Thanks gentlemen.