My bot isnt working :( - Page 1

ercalote

Sept. 24, 2014, 6:18 p.m.

Same here. Also, some customers add me and say that they could not buy items using the bot.

ussjtrunks

Sept. 24, 2014, 7:17 p.m.

Mine fixed itself :)

Siera #noSound

Sept. 24, 2014, 7:27 p.m.

I suppose Joto was the one to fix not the site itself x)

ultrazars

Sept. 24, 2014, 7:55 p.m.

looks like this bug is per-user, i still cant do anything.

ocolus

Sept. 24, 2014, 8:12 p.m.

It worked for 20 mins about 2 hours ago. Since then nothing again.

rabsym

Sept. 24, 2014, 8:14 p.m.

Mine isn't working too, looks like a general issue with all shops broken... :(

ultrazars

Sept. 24, 2014, 8:43 p.m. (Last edited by ultrazars on Sept. 24, 2014, 8:50 p.m.)

WORKAROUND

I think i managed to find a workaround - with like 20 page refreshes i got functional version of admin panel and withdraw some keys.

Looks like problem lies in fact that some very important scripts are loaded AFTER all gift images load. And looks like most of the time those images DO NOT load. Example how looks partially loaded gift images:
https://dl.dropboxusercontent.com/u/846888/dispenser/bugs.009.partial.png

When your bot have a lot of trades (like mine) its almost impossible to get fully downloaded page for some reason. This issue appered today.

So - just hit refresh as much as you can while you get all images loaded. Then you can use buttons. Also looks like firefox achieves this a little better.

EDIT:
looks like in chrome, even if tradeoffer images are loaded, it works 33% of the time (managed to get images loaded 3 times, and buttons worked 1 of those times). So site works little less crappy with firefox.

Jon Irenicus

Sept. 24, 2014, 11:10 p.m.

I've had 3 people add me to manually trade since they couldn't get anything from my dispenser.

ocolus

Sept. 25, 2014, 12:09 a.m.

This sounds similiar to the wishlist loading issue to me. :O

Noob

Sept. 25, 2014, 1:18 p.m.

same

Linuxoed

Sept. 25, 2014, 4:01 p.m.

same trouble

Joto

Sept. 25, 2014, 4:14 p.m. (Last edited by Joto on Sept. 25, 2014, 4:16 p.m.)

We updated the script and found out it was a bit broken with Chrome, and we quickly updated it again and put it up. I am not aware of the problem because this was done over 24 hours ago and we cannot reproduce similar problems anymore. I believe why some of you are still experiencing the problem is because your browser is still trying to run the old script from the cache. I suggest deleting the cache or Ctrl+F5 and refresh the page.

If you use firefox you should not run into the problem at all.