Little Fix for Pickuping Infernal Key and stacking them

I had one key picked up....missed another one:

[18:12:55.434 N] [2AC73E70] Type: Item Name: DemonTrebuchetKey-26158 ActorSNO: 166943

 

[4ABDFB68] Type: Item Name: DemonTrebuchetKey-16955 ActorSNO: 166943

It missed this act3 key.

 

would you please check your log if there is System.AccessViolationException near your miss looting key.

 

I had a key farming profile and run around 7 circles this morning with this fix.

It seems only act 1 key and act 3 key has been picked up and stashed.

I am not with my computer, so I can't do debugging, but does anyone sucessfully pickup act 2 key?

Maybe I am just not lucky enough? I am running on MP3 with 77 paragon level.

 

it didn't pick up... saidly i don't have a chance to get a full log about what happened when looting.
the plugin itself should not have problem to pick it up with 1.6.3.1+.

 

Thanks for your reply. Maybe I should change my profile to run with A2 only and monitor it for a while.
Since latest DB is not quite stable and lack of RadsAtom support. 1.6.3.1 with your fix might be the stable version one for the moment.

By the way, Elderberries_Oasis.xml profile on CIGGARC should cover the key keeper in act 2, isn't it?

 

er.... I see 1.6.3.3 actually make something wrong about keys. i will fix this soon

 

Thanks ksmaze - that was a very silly mistake. In truth it's evidence of why I shouldn't be sat on a computer yet, I'm still not well, but to be frank I was growing to hate being stuck on a sofa/bed all day long.

Just a note though - reason why some of your changes I haven't put in, you are trying to add the SNO to some cache lists which are "RactorGUID" based - every individual item has it's own ractorguid, uniquely identifying it, valid only for the duration of a game. So say four different keys drop in one session - they would all have a unique and individual "RactorGUID" when on the floor. Not to be confused with the "SNO" code (which just represents a certain type of item - so all infernal keys, I believe, have the same SNO code to represent what "type" of item it is).

Still I'll edit the stupid DiaUnit->DiaItem in for next release, thanks for catching it, that should fix it alone. Unless there's other SNO's missing, or those objects are missing certain data items need from memory (in which case we're going to need some more hacky workarounds like the forcing to DiaItem I was doing).

Edit: proof keys have suspicious data in D3 memory;
[10:27:45.218 N] [2AC24988] Type: Projectile Name: DemonTrebuchetKey-13085 ActorSNO: 166943, Distance: 15.42938
[18:55:50.807 N] [13CAF358] Type: ServerProp Name: DemonTrebuchetKey-21789 ActorSNO: 166943, Distance: 9.441039

DB should read them both as Items automatically - let alone two completely different object types (a projectile, then a serverprop). I'll see if Nesox can find any and it might need a fix in Db rather than from me, to be 100% reliable.

 

you are welcome.

 

New DB version doesnt fix the issue with keys instead when ever a mirror image of the keywarden in act3 dies he stops doing anything looking for keys it seems... (talking about Giles newest version)

 

yes, sir