Bukkit

Bergerkiller, in addition to my earlier suggestion ("chest in 0:4"), I would REALLY really like another improvement:

• currently, the plugin uses a X radius slice search around the block the sign is attached to meaning "chest in 4" searches 4 blocks in horizontal AND vertical. This screws up totally my warehouse, since I have rows of different items, and the rows are exactly 4 blocks apart. Each row consists of stacks of chests 5 high. See my picture: https://dl.dropboxusercontent.com/u/6411310/2013-04-26_08.00.10.png

• now, in order for the "chest in" to reach to topmost chest in pile, it needs to be "chest in 4". But: then the sign reaches horizontally the other shelf also - in practise filling it with cobble, instead of what I want (which is stone)

-> What I'd really like is a modifier to your "radius" function, which would enable the players to ignore either horizontal or vertical dimension from the search. In practise this would mean:

1. "chest in 4" -> search 4 blocks horizontally and vertically
2. "chest in 4:h" -> search 4 blocks horizontally only
3. "chest in 4:v" -> search 4 blocks vertically only

I'm sure this feature can be easily implemented, since you need to modify only your radius function.

Now, the following would be a little more complicated, but you could even combine this with my earlier suggestion to make the chest retrieval and distribution enourmously efficient:

• "chest in 0:4" -> fill out the chests horizontally AND vertically, from nearest to farthest
• "chest in 0:4:v" -> fill out the chests from nearest to farthest, ignore horizontal direction. In practise, this is exactly what I would want, to fill out the piles of chests in one row, ignoring the next row.

@NorbuGames

No, seriously, can you spend 1 minute and read the opening message please?

@leagris: :D

@porthos203

Here you are: http://dev.bukkit.org/server-mods/bkcommonlib/pages/dev-bukkit-commenting-practises/#w-asking-for-updates

There is a link (in _big_ text) just above your posting. The link leads to development builds, which surely work for 1.5.1 (we use them).

@bergerkiller

Yes, closest to farthest is what I meant. I added the chest numbering to my earlier picture: https://dl.dropboxusercontent.com/u/6411310/proposal2_numbered.png

1. the rightmost case represents ordering from "top to bottom", meaning the topmost chest in the stack gets filled first, then the next etc. until the closest one. So: "chest in 4:0"

2. the middle case represents what I am mostly looking for: fill out the chests from bottom (closest to the track) to top (farthest from the track). So: "chest in 0:4"

3. In case the user would want to align the track in the middle of the chest stack, rather than on the bottom, then the chests below the track level would be represented as negative numbers. So for example: "chest in 2:-2". In the leftmost stack of my picture, then the chests would again be filled from topmost to the bottom one.

Ie. in all cases, the parameter for "chest in" can be thought of as an offset (positive or negative) to the track level

Does this clarify what I mean?

I have some questions and a request for Bergerkiller:

1. If I have some stacked chests beside my track, what is the true radius for the "chest in" sign, with the default radius of 2? I searched the wiki but did not find an explanation for this. Then I did some experiments and found that if the track is on level 0, then the plugin's chest in radius seems to extend 2 above and 2 below the track level, ie. +2, +1, 0, -1, -2. Is that correct?

2. Extending the question 1: in what order does the minecart start filling out the chests? I have noticed that sometimes it starts from the upmost one ie. level 2 in my example...but not always?

3. Would it be in any way possible to extend the "chest in" parameter as this:

• the plugin would have "0" as the relative Y coordinate of the track level. Then for the old "chest in 2", the plugin would behave as usual (ie. using the range +2...-2)
• but if the player wants a different scenario, he would write for example "chest in 4:0". Then the plugin would fill out the chests in the order of 4, 3, 2, 1, 0 and not fill out the ones below the track level at all
• in case the player would like the chests filled out in the opposite order (ie. bottom up, as I would like it), then "chest in 0:4" would do the job; filling out the chests in the order of 0, 1, 2, 3, 4

I made a picture to clarify my meaning; I think it is pretty much self-explanatory. https://dl.dropboxusercontent.com/u/6411310/proposal.png

How does that sound? I personally think this would improve the "warehouse" operations tremendously!

@bergerkiller

As usual, this fixed the issues I was seeing. Now also the amount parameter works correctly. Thanks, bergerkiller!

@bergerkiller

No, it takes 20 stone AND 20 dirt. And those are not of the same data value at all.

Thank you so much Bergerkiller about the new "target" feature. It works - but you might want to check your code for the amount parameter; seems like it takes twice as much from the inventory. If I write a sign

[+train]
chest out
5 target

it takes 10 out from the chest. For "10 target" it takes 20 and so on. For "1 target" it does not seem to take one but rather all of the matched items from the chest.

EDIT: Weird, the amount seems to work for some items, but doesn't for some others. For smoothstone and dirt, for example, the behaviour was as described above. But for cookies, the amount taken from the chest is correct.