Redstone requester + packager computercraft peripheral

[Karotte128]

This PR adds a CC:Tweaked (computercraft) peripheral for the new Redstone Requester and packager.
Let me know if you want any changes or additional peripheral functions :)

[uthoffcyra]

APIs for these new blocks would be awesome, though some documentation would be very helpful.

Redstone Requester

orderPackage(destination, item, amount)

Creates an order for a specific item from the stock network the Redstone Requester is tuned to.

• destination: string. The address to be added as the package's destination label.
• item: string. The ID of the item to be requested. For example, minecraft:quartz.
• amount: integer. The number of the requested item to be packaged.

Packager

createPackage(destination)

Sends a signal to the Packager to draw items into a package with the specified address.

• destination: string. The address to be added as the package's destination label.

---

1. This is just what I could see from your code, is this correct?
2. Does the function createPackage() throw if there is no destination provided, or does it create a package with no destination. The latter would likely be the desired (expected) outcome.
3. The same goes for orderPackage(). If it was me, I would order the parameters as item and amount first, and then an optional destination at the end. An example in Lua is below.

local requester = peripheral.wrap('back')
requester.orderPackage('minecraft:quartz', 20) -- No destination address provided.
requester.orderPackage('minecraft:coal', 64, 'myfurnace') -- Destination address is provided.

Just my thoughts, however. Thank you for your work.

[Karotte128]

Thank you for helping me on the docs.
The packager peripheral does use the old sign destination mechanic if no destination is provided. If you want a empty destination do not place a sign or give the function empty string.
The redstone requester is a bit different. I did not think about having empty destination because the package would get lost in the chain/belt system.
Currently you could pass a empty string, but if it is useful, I can change the argument order as you recommended.

[uthoffcyra]

Sounds great. Thanks for the clarification. In Create 6, packages without addresses can be picked up by Frogports that aren't given a name, so it may still be useful, but like you said passing an empty string may work just fine.

[McArctic]

Hey! Was looking over this pr, I think you should consider making requester.orderPackage() to be able to take in a table in place for the item string, this would allow the requester to have the same functionailty as in game.

[McArctic]

APIs for these new blocks would be awesome, though some documentation would be very helpful.

Redstone Requester

orderPackage(destination, item, amount)

Creates an order for a specific item from the stock network the Redstone Requester is tuned to.

• destination: string. The address to be added as the package's destination label.
• item: string. The ID of the item to be requested. For example, minecraft:quartz.
• amount: integer. The number of the requested item to be packaged.

Packager

createPackage(destination)

Sends a signal to the Packager to draw items into a package with the specified address.

• destination: string. The address to be added as the package's destination label.

1. This is just what I could see from your code, is this correct?
2. Does the function createPackage() throw if there is no destination provided, or does it create a package with no destination. The latter would likely be the desired (expected) outcome.
3. The same goes for orderPackage(). If it was me, I would order the parameters as item and amount first, and then an optional destination at the end. An example in Lua is below.

local requester = peripheral.wrap('back')
requester.orderPackage('minecraft:quartz', 20) -- No destination address provided.
requester.orderPackage('minecraft:coal', 64, 'myfurnace') -- Destination address is provided.

Just my thoughts, however. Thank you for your work.

Hey, seems like this documentation is wrong

I think the correct way to call this method would be

requester.orderPackage('myfurnace', 'minecraft:coal', 64)

[McArctic]

I got bored and made a new pr build apon this #7757, I just added the changes I stated earlier aswell as a throw if the network does not have the stock requested :)

[Karotte128]

I got bored and made a new pr build apon this #7757, I just added the changes I stated earlier aswell as a throw if the network does not have the stock requested :)

Oh, thank you!
Should I close this my PR now and use the updated one?

[McArctic]

I got bored and made a new pr build apon this #7757, I just added the changes I stated earlier aswell as a throw if the network does not have the stock requested :)

Oh, thank you! Should I close this my PR now and use the updated one?

Honestly, no clue, I am new to contributing to projects lol. Whatever you feel is best :)

[Karotte128]

Closed, please use #7757