5 replies to this topic

[Creator]

It would make programing management systems that utilize turtles so much easier.

turtle.suck and the like should return true and the the slot number.

[Dog]

That would be very useful!

[Creator]

However, brainderp! Just realized items are put into the selected slot.

My suggestion then would be to put it into the next empty slot and return the slot number.

[Bomb Bloke]

Creator, on 26 May 2016 - 03:11 PM, said:

My suggestion then would be to put it into the next empty slot and return the slot number.

That sounds like a massive backwards compatibility issue to me. And what if there is no empty slot, but there are some half-filled ones?

Heck, even if you stick with the current system, there's no guarantee that the items won't be distributed over multiple slots.

I'm also not seeing the benefit here, either. It's already far easier to rig things so you know exactly where the sucked items will go, then it would ever be to try and figure that out after the fact.

[Sewbacca]

Whats like this:

turtle.suck(side)

returns string what, table successful{
[slot] = count,
...
}, number failed (-- 1 by sucking 64*16+1 stones)

Edited by Sewbacca, 29 May 2016 - 01:40 PM.

[apemanzilla]

All of this can be emulated with the functions available. You can loop throughout the turtle's inventory before and after sucking up items and check what slots changed. There's no need to alter existing functions in a way that would cause compatibility issues.