Dealing with Damage gumps!!!

[_C2_]

Alright-  I was trying to farm in the cave of discarded and the constant damage gumps were rolling above the head non stop and making it hard for my looter to keep pulling corpses which started to slow the script.  I know I heard TM talk about them once - anyone else been dealing with them or have ideas.

[TrailMyx]

You should dissect how I did it in the CLAw.  Khameleon and I did a bunch of work trying to filter it out and I think it's dead nuts now.  You might even think about grabbing my OpenContainer sub because that will also return the correct #CONTID for you to loot from.

[manwinc]

I Played with using #contid for looting a while back, I just said F' It, and went with good old.


nextcpos 0 0
set #Lobjectid #findid
event macro 17 0
wait 20 (25)

and then I just loot from all containers (Excluding paperdoll and backpack.)

[TrailMyx]

When you have streaming damage gumps, you run the risk of missing the correct #CONTID.  On OSI, you have to be aware that the #CONTID from the body is different than the ID that comes from the actual container when you open the body.  So you have to filter this value, and it becomes much harder when you have 3 energy vortexes spamming gumps.  My OpenContainer handles all this and will return the real #CONTID, and does it pretty fast as well.

[_C2_]

When you have streaming damage gumps, you run the risk of missing the correct #CONTID.  On OSI, you have to be aware that the #CONTID from the body is different than the ID that comes from the actual container when you open the body.  So you have to filter this value, and it becomes much harder when you have 3 energy vortexes spamming gumps.  My OpenContainer handles all this and will return the real #CONTID, and does it pretty fast as well.

That is basically my problem but it does eventually get the container pulled but with a lot of fuss

[TrailMyx]

That is basically my problem but it does eventually get the container pulled but with a lot of fuss

Definitely check out my OpenContainer sub then.  I've optimized the crap out of it to handle things like looting rights, accessibility, container spamming, etc.  Also has timers to handle the un-openable.

[Cerveza]

Isn't there a way to modify the client to eliminate them?

[TrailMyx]

I don't think there was a setting for that in the setup.  Also, there would be no way for the script to know of anything, so it's best to optimize the script to just filter it out.  Makes for less, "Your script doesn't work." posts. 

[Cerveza]

Right, but I think there is a way to modify the client to avoid the messages. I know there was a way of removing the "you can not gain any more valor" type messages. I suppose damage would be similiar.

[xapcx]

have been working on the same issue for the past two days.

[TrailMyx]

Right, but I think there is a way to modify the client to avoid the messages. I know there was a way of removing the "you can not gain any more valor" type messages. I suppose damage would be similiar.

Hmm, probably not.  This is actually data that comes through the #CONTNAME, #CONTSIZE variables.  This isn't journal spam, but rather packet level information that's coming from the server to the client.

If you quickly sample #CONTNAME and post the values, you'll see "damage_numbers_gump" show up, but then be replaced by whatever gump happens to be selected and is on "top".  I have a test script I wrote at one time to sample this so I could more effectively determine what checks I needed to put in.

Now if you are talking about a client hack or patch, then that's possible.  I don't talk much about those; I work just with EasyUO and the client to keep a scripts dependencies to a minimum.

[Thimotty]

@TM I'm sorry i have to say this but i have just checked your OpenContainer sub and ...... why are you alway try to kill a fly with a tank

Here is the solution:
(this is something i just wrote here, don't try to use it directly, it is only to show the idea)

Code: [Select]

findItem YFM_JNF_QNF_YNF_MNF_LNF_WNF_VNF_KNF_PNF G_2
if #FINDTYPE <> X
   {
   set #LOBJECTID #FINDID
   try_again:
   event macro 17 0
   wait 5
   str right #FINDID 4
   if #STRRES notin #CONTID
      goto try_again
   event ExMsg #charID 3 %color body ignored
   set %real_body_cont_ID #CONTID
   }


[TrailMyx]

Heh, it's amazing how similar your sub is to what mine started out as.  Put some mileage on yours and see how it performs in heavy spawns, invalid targets, etc, etc.  It LOOKS easy at the start... Trust me.  

And BTW, tanks are required so that I can release a script and KNOW I don't have to answer constant questions about little corner cases of function.  You tend to over-design something when you release it for mass-consumption. 

[Thimotty]

Maybe you are correct but I do riki often alone and it never fails.

Edit: Yes you are correct about scripts designed for public use. I have never deal with that side of the problem

[TrailMyx]

Maybe you are correct but I do riki often alone and it never fails.

Well what you have to do is release your script and let 100s of people use it to really see where the corner cases are.  That sub has been iterated from the beginnings (much like yours), but has taken into consideration much input from many different players with different playstyles.  It's probably still not perfect, so whenever someone else comes up with an issue I tend to incorporate that feedback.