Different drops for clicking ANVIL@0, ANVIL@1, and ANVIL@2

Question

Different drops for clicking ANVIL@0, ANVIL@1, and ANVIL@2

sehrgut opened this issue 12 years ago · 6 comments

sehrgut commented 12 years ago

I'm trying to implement anvil repair with the following drop:

ANVIL:
  - action: LEFTCLICK
    tool: IRON_INGOT
    consumetool: 1
    replacementblock: ANVIL@0
    event: LIGHTNING@HARMLESS
    message: Your anvil has been repaired.

What I'd like to do is have separate rules with separate costs and effects for each damage level, so that repairing ANVIL@0 would be a no-op, repairing ANVIL@1 would yield ANVIL@0, and repairing ANVIL@2 would yield ANVIL@1. 4 could then yield 3, and 5 could yield 4, preserving orientation.

Would this be a feature you could add?

Zarius · Answer 1 · 2013-04-02T23:15:19.000Z

Already added :-)

You need to start with replacementblock: anvil@1 though because anvil@0 is just a normal anvil.

Zarius · Answer 2 · 2013-04-02T23:16:54.000Z

Note: perhaps it does effect orientation, well have to test and perhaps try higher numbers like anvil@12

sehrgut · Answer 3 · 2013-04-03T03:18:35.000Z

Okay, silly me forgot that data values were multiplied by orientation, and only tried the entity data values 0-3. A full mapping of 0-11 covers it. This is, then, a non-issue . . . thanks again for the great plugin! It's one of the central plugins to every server I've run.

Edit: Oh, for reference:

New Anvils: 0-3
Slightly-Damaged Anvils: 4-7
Badly-Damaged Anvils: 8-11

They group like: 0->4->8 through 3->7->11.

sehrgut · Answer 4 · 2013-04-03T01:07:40.000Z

I'll retest when I get home, because I may have been trying to repair an ANVIL@4 with a rule for ANVIL@2.

Sent from my iPhone

On Apr 2, 2013, at 7:15 PM, Zarius [email protected] wrote:

Already added :-)

You need to start with replacementblock: anvil@1 though because anvil@0 is just a normal anvil.

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

CelticMinstrel · Answer 5 · 2013-04-05T01:55:34.000Z

In that case, perhaps OtherDrops should provide aliases to split the data, as I believe it does with other things. For example:

ANVIL@NEW - matches any new anvil
ANVIL@DAMAGED - matches any damaged anvil
ANVIL@NORTH - matches any anvil facing north

And so forth.

sehrgut · Answer 6 · 2013-04-05T04:59:15.000Z

That would be absolutely wonderful.

Sent from my iPhone

On Apr 4, 2013, at 9:55 PM, CelticMinstrel [email protected] wrote:

In that case, perhaps OtherDrops should provide aliases to split the data, as I believe it does with other things. For example:

ANVIL@NEW - matches any new anvil
ANVIL@DAMAGED - matches any damaged anvil
ANVIL@NORTH - matches any anvil facing north

And so forth.

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

Share to