ScriptUO
Official ScriptUO EasyUO Scripts => Scripting Chat => Topic started by: Alpha on October 02, 2009, 12:22:18 PM
-
Ok... So what are the common Error checks you guys use when using Event property?
I'm thinking about writing a short script that will churn out masses of Exceptionally crafted leather armor and continue to recycle them until I get ones with the right resists. This will obviously mean using event property on each piece and parsing out the Resist values & comparing. What I'm not too sure about are the Ways that Event property can Fail ??
Example..
set %Scissory_ID XXXXX
set %Armor_type YYY
set %string %Fire , #spc , Resist , #spc , 16%
START:
Finditem %Armor_type C_ , #backpackid
If #findcnt > 0
{
For #findindex 1 #findcnt
{
event property #findid
wait 10
If %string notin #property
{
set #lobjectid #scissor_id
event macro 17 0
Target 2s
set #ltargetid #findid
event macro 22 0
wait 20
}
}
goto START
Anyway... I'm stuck @ work and borred... The whole part where I set String was hopefully enough to convey teh idea I don't actually think that would function like that. I'm just really not sure about other error checking I should be using to make sure that #property updates etc. Maybe I can Save it before the Event & If it's different AFTER the event and NOT just $ it worked or something..
Ah well.. just thinking..
-
Only way i know event property can fail is lag. I dont think ive ever actually expereinced it myself..
-
Only way i know event property can fail is lag. I dont think ive ever actually expereinced it myself..
You've never experienced lag? Cough...cough.....bullshit.... ;)
-
Only way i know event property can fail is lag. I dont think ive ever actually expereinced it myself..
You've never experienced lag? Cough...cough.....bullshit.... ;)
I mean lag enough to mess up an event property reading. At least not that im aware of.
-
Only way i know event property can fail is lag. I dont think ive ever actually expereinced it myself..
You've never experienced lag? Cough...cough.....bullshit.... ;)
I mean lag enough to mess up an event property reading. At least not that im aware of.
Yeah I know.....just yanking on some chains here.....I read somewhere that happens sometimes here.
-
A simple Wait 10 can help a lot before a FindItem command to fight any lag related trouble
cu
-
There are items out there (and especially creatures) where finditem property just doesn't work. Normal Ogres comes to mind. There was a bunch of others. I haven't checked for a while, but throughout 5.x and 6.x clients I would run into this problem.
-
If you've ever Held your mouse over something and it just told you..... NOTHING. Like Ring.... Great...what the F Are the MODS. That IS a situation where event property will mess up, probably caused by lag.
-
Another little hint; movement seems to impact the function of event property. The reason my IDOC scanner works so well is at one time I noticed I was missing a bunch of signs as I was wandering around. So in my experimentation, I found that some items returning a blank value in #PROPERTY would evaluate correctly if the character was standing still. So you'll notice sometimes you are forced to stop walking when running my IDOC scanner and this is why.