Bebot 0.6.2 + Slaves 1.3

This MAY be slaves related. However I think the slaves may have just been invoked because of the enormous number of blobs that needed to be sent. Splitting the results like that also made the results appear out of order.

"!items 100 ring" returned 109 tells to me, with each page having only a single element (like 1 blob would have an icon of a ring, next blob would have name of a ring with links to various QLs of the item, next blob would have another ring icon, etc).

An !items request that only returns 7 items like "/tell botname !items pure novictum" works fine, all on 1 page.

"!items implant" worked fine too, all 50 were on a single page blob.

"!items 100 implant" gave me 109 pages like the ring ... so the bug seems to be when you get 50 items AND links to a specific middle QL.

Maybe the blob size is a bit too much and the bot decides to chunk it up? However since I'm using a fairly unmodified 0.6.2 so its likely happening to others.

But since it DOES work without the middle QL ... it is -weird- that 1 page with 50 results becomes 100+ pages with 1/2 of a result per page. I would have expected it to become 2 pages if the blob size broke.

"!items 100 ring" results sample:
[Botname2]: 50 Results :: Click to View (page 5 of 109)
[Botname]: 50 Results :: Click to View (page 1 of 109)
[Botname]: 50 Results :: Click to View (page 2 of 109)
[Botname]: 50 Results :: Click to View (page 3 of 109)
[Botname]: 50 Results :: Click to View (page 4 of 109)
[Botname3]: 50 Results :: Click to View (page 9 of 109)
[Botname2]: 50 Results :: Click to View (page 6 of 109)

(etc all the way to 109)

!history doctorhyde

returns 124 pages on my slaved bot and 3 pages on my unslaved bot

ty, upgraded and confirmed ... soooo much better.