Hey there, I was just testing a few things out, and it seem as though in the following example, the tool name inside the tool parameter isn't respected and that any Arcane Door Key with the meta ID of 1 can be used to proc the following drops/commands. Or am I just doing something wrong?

IRONCHEST_BLOCKIRONCHEST@1:
    - trigger: [LEFT_CLICK]
      permission: gtt
      tool: THAUMCRAFT_ARCANEDOORKEY@1~&bGolden Treasure Chest Key
      consumetool: 1
      message: '&3You have unlocked the &6Golden Treasure Chest&3.'
      command: ['/$ pex user %p add phatloots.loot.Golden-Treasure-Chest','/$ pex user %p remove otherdrops.custom.gtt']
    - trigger: [HIT]
      command: /$ pex user %p remove phatloots.loot.Golden-Treasure-Chest
      delay: 6000 

What version of OtherDrops are you running?
On 28/01/2015 8:54 pm, "AnodyneEntity" [email protected] wrote:

Hey there, I was just testing a few things out, and it seem as though in
the following example, the tool name inside the tool parameter isn't
respected and that any Arcane Door Key with the meta ID of 1 can be used to
proc the following drops/commands. Or am I just doing something wrong?

IRONCHEST_BLOCKIRONCHEST@1:
- trigger: [LEFT_CLICK]
permission: gtt
tool: THAUMCRAFT_ARCANEDOORKEY@1~&bGolden Treasure Chest Key
consumetool: 1
message: '&3You have unlocked the &6Golden Treasure Chest&3.'
command: ['/$ pex user %p add phatloots.loot.Golden-Treasure-Chest','/$ pex user %p remove otherdrops.custom.gtt']
- trigger: [HIT]
command: /$ pex user %p remove phatloots.loot.Golden-Treasure-Chest
delay: 6000

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

Build 593.

Did you get it working?
On 06/02/2015 10:28 am, "AnodyneEntity" [email protected] wrote:

Closed #354 #354.

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

Oh yes, I did. Sorry about not replying after so long.