[X] My Assistant

Really, super? (IMG:[invalid] style_emoticons/default/dry.gif)

What exactly is going on here? I see that that item isn't owned by End Of All Hope / Juggernaut Santa, and he clearly held the winning bid. Do you guys need my help work out a solution that you both can live with?

just to add a couple details, that user is a lv442 (hence in soulbind-able range) player who previously bidded on another heavy armor in the same auction. while i can guess it was a genuine error, first thing i'd send a pm to the user asking him not to soulfuse the item yet.

This post has been edited by Scremaz: Jul 24 2019, 18:39

What exactly is going on here? I see that that item isn't owned by End Of All Hope / Juggernaut Santa, and he clearly held the winning bid. Do you guys need my help work out a solution that you both can live with?

clearly super sending to wrong person.

[Hea05] Legendary Ruby Power Boots of Slaughter (500, ADB 67%) (seller: kamio11) End Of All Hope 700k Proxy bid after #63; winning for 37.1h / 50.7h; -0.0%
[Hea06] Legendary Ruby Power Gauntlets of Slaughter (444, ADB 44%) (seller: poi999poi) UAENA- 405k Proxy bid after #63; winning for 46.9h / 46.9h; -0.0%

he sent it to the winner of a bid for the next item.

oh, wow. i didn't even think about checking the following line. i had the solution on my nose, and still... thanks fudo.

...and the new auction started.
Well, seems like there is no direct human interaction with the auction system since months...

...and the new auction started.
Well, seems like there is no direct human interaction with the auction system since months...

there are ways to get attention. Imagine if we locked the current auction?

there are ways to get attention. Imagine if we locked the current auction?

i thought it too. but better to solve it with pms. i waited a bit to see if he answered here or showed up on irc, but, uh...

i thought it too. but better to solve it with pms. i waited a bit to see if he answered here or showed up on irc, but, uh...

Yep, PM is better. IRC won't work: -ChanStat- Superlatanium (~Superlata@optimal.methods.exist) was last seen quitting for "Ping timeout: 240 seconds" on Tue June 11 01:24:19 2019 UTC (44 days, 15 hours, 7 minutes ago)

looks like super automated almost everything...
it wouldn't be strange that the mistake in sending was because a bug on his script from difference between santa's name and what registered on the autobid site...
that's just my speculation though.

anyway, have anybody tried to PM UAENA- ? I mean, he might didn't realize that he accept it by mistake too...
It should be fine if he send the item to santa with the same CoD right? at least for this case.
though, we still need at least an acknowledgement from super that this problem exist too for transparency and such.

anyway, have anybody tried to PM UAENA- ?

i'm on it.

Apparently it won't even matter anymore...

edit: well, hv may get saved so I'll probably try to get the equipment anyway (IMG:[invalid] style_emoticons/default/duck.gif)

This post has been edited by Juggernaut Santa: Jul 26 2019, 00:18

I'm guessing that Superlatanium's method of sending isn't fully automated because I've gotten minor mistakes that were easily resolved in the past as well, or it might have been from another auction.

looks like uaena sent the item back to latanium...

and now juggy santa has it, already soulfused, forged, whatnot. any feedback?

This post has been edited by Scremaz: Jul 30 2019, 13:27

and now juggy santa has it, already soulfused, forged, whatnot. any feedback?

All ok now.

All ok now.

But I still can't understand how they could end up in the "Bid Warning" MM, that Super auction bot sent me.

It's not like he sends those warning manually, so how was it even possible ? (IMG:[invalid] style_emoticons/default/wacko.gif)

PS. You don't have to clean & disinfect them, Santa;
I swear I didn't put my dirty feet in your boots while I briefly owned them (IMG:[invalid] style_emoticons/default/tongue.gif)

This post has been edited by mundomuñeca: Jul 30 2019, 18:25

But I still can't understand how they could end up in the "Bid Warning" MM, that Super auction bot sent me.

It's not like he sends those warning manually, so how was it even possible ? (IMG:[invalid] style_emoticons/default/wacko.gif)

PS. You don't have to clean & disinfect them, Santa;
I swear I didn't put my dirty feet in your boots while I briefly owned them (IMG:[invalid] style_emoticons/default/tongue.gif)

What I think happened was:

1. Bot attached boots to MM and tried to send to "End of All Hope"
2. That does not work, but the next MM that is made has the boots already in the attachment. this is a known bug in MM/HV (not a but, a feature?)
3. Bot makes that next MM and sends 2 items to that other dude
4. Other dude returns them to super
5. Super / bot again tries to send them to End of All Hope, attaching it to a MM adressed to EOAH
6. MM fails, and next MM that is made has the boods already in the attachments
7. Bot send MM to mundo, with the boots already added, because of this known 'feature'/bug
8. All's well that ends well.

What I think happened was:

1. Bot attached boots to MM and tried to send to "End of All Hope"

aye. guess it doesn't work well with namechanges.

What I think happened was:

1. Bot attached boots to MM and tried to send to "End of All Hope"
2. That does not work, but the next MM that is made has the boots already in the attachment. this is a known bug in MM/HV (not a but, a feature?)
3. Bot makes that next MM and sends 2 items to that other dude
4. Other dude returns them to super
5. Super / bot again tries to send them to End of All Hope, attaching it to a MM adressed to EOAH
6. MM fails, and next MM that is made has the boods already in the attachments
7. Bot send MM to mundo, with the boots already added, because of this known 'feature'/bug
8. All's well that ends well.

Thank you for the step-by-step explanation.

It is quite interesting, and I never noticed such bug feature (IMG:[invalid] style_emoticons/default/biggrin.gif)

I will double check all my sent MM attachment, now (IMG:[invalid] style_emoticons/default/heh.gif)

The name issue is now fixed by the way.