Allow only an input rule

[paulburton0]

This is a suggestion or enhancement request, not an issue or bug. Since ItemExchange chests emit a redstone signal on a successful exchange, it would be nice to be able to have only an input rule without an output rule. That way, IE chests could be used to take material payments for certain redstone actions. For example, an automated toll gate that will only open when the correct material is exchanged.

[ttk2]

so right now you can't have the chest emit redstone when payment is
received?

On Mon, Jul 7, 2014 at 6:50 PM, paulburton0 [email protected]
wrote:

Since ItemExchange chests emit a redstone signal on a successful exchange,
it would be nice to be able to have only an input rule without an output
rule. That way, IE chests could be used to take material payments for
certain redstone actions. For example, an automated toll gate that will
only open when the correct material is exchanged.

—
Reply to this email directly or view it on GitHub
#103.

[paulburton0]

Yes, the chest does emit a signal. Right now there has to be an input rule
and an output rule. What I was suggesting is making it so that the Redstone
signal is the output rule. In other words, instead of getting a physical
entity as the product of he exchange, the result of the Redstone circuit is
the product.

Right now if I wanted to, say, charge admission to an area, I might have an
iron door with an item exchange chest next to it. If I want to charge one
iron ingot to open the door, I still have to have a "dummy" output rule in
order to make the itemexchange chest work. So I might set up the chest to
exchange 1 iron for 1 seeds and open the door with the Redstone signal on
successful transaction. It would be nice to have a "null" output rule so
that I don't have to use the dummy output rule.

---

Paul Burton
[email protected]
http://paul-burton.com/keys
On Jul 8, 2014 9:11 AM, "ttk2" [email protected] wrote:

so right now you can't have the chest emit redstone when payment is
received?

On Mon, Jul 7, 2014 at 6:50 PM, paulburton0 [email protected]
wrote:

Since ItemExchange chests emit a redstone signal on a successful
exchange,
it would be nice to be able to have only an input rule without an output
rule. That way, IE chests could be used to take material payments for
certain redstone actions. For example, an automated toll gate that will
only open when the correct material is exchanged.

—
Reply to this email directly or view it on GitHub
#103.

—
Reply to this email directly or view it on GitHub
#103 (comment)
.

[ttk2]

ok then, I will try to arrange that.

On Tue, Jul 8, 2014 at 9:28 AM, paulburton0 [email protected]
wrote:

Yes, the chest does emit a signal. Right now there has to be an input rule
and an output rule. What I was suggesting is making it so that the
Redstone
signal is the output rule. In other words, instead of getting a physical
entity as the product of he exchange, the result of the Redstone circuit
is
the product.

Right now if I wanted to, say, charge admission to an area, I might have
an
iron door with an item exchange chest next to it. If I want to charge one
iron ingot to open the door, I still have to have a "dummy" output rule in
order to make the itemexchange chest work. So I might set up the chest to
exchange 1 iron for 1 seeds and open the door with the Redstone signal on
successful transaction. It would be nice to have a "null" output rule so
that I don't have to use the dummy output rule.

---

Paul Burton
[email protected]
http://paul-burton.com/keys
On Jul 8, 2014 9:11 AM, "ttk2" [email protected] wrote:

so right now you can't have the chest emit redstone when payment is
received?

On Mon, Jul 7, 2014 at 6:50 PM, paulburton0 [email protected]
wrote:

Since ItemExchange chests emit a redstone signal on a successful
exchange,
it would be nice to be able to have only an input rule without an
output
rule. That way, IE chests could be used to take material payments for
certain redstone actions. For example, an automated toll gate that
will
only open when the correct material is exchanged.

—
Reply to this email directly or view it on GitHub
#103.

—
Reply to this email directly or view it on GitHub
<
https://github.com/gmlaxfanatic/ItemExchange/issues/103#issuecomment-48333454>

.

—
Reply to this email directly or view it on GitHub
#103 (comment)
.

[erocs]

Added f415088