lassevk/DropChest — comment on commit 6f0618de51a6f0e7ff34376e5207a2c52b4a6215
File:  line 0
By lassevk:

I already nuked one other part of that equation; when you (re)start the
server, the addon would preload any chunks with a chest in.

It should not do that any more (I hope); I should check that I did in fact
do that.

As such, unloading chunks with chests is probably good too.

I don't mind "officially forking" this addon, though I don't really know
what I should do in that regard.

Since I've added new stuff to it, it isn't quite the same addon any more.
For instance, one of the latest changes I did to it was to add "dropzone"
functionality. Basically, for a chest you can choose whether to use the
radius system, centred on the chest itself, or a dropzone system, which is
a rectangle block-shaped system consisting of 2 3D coordinates in the world.

This would allow you to have chests pick up items from a very precise area,
not centred on the chest.

For instance, I have created a storage room consisting of a cube-shaped
room with chests lining the walls from floor to ceiling (except the topmost
row), and they all have suck filters for their particular item, for a
dropzone in the middle of the room. All you have to do is drop items from
your inventory in the middle of the room, and it'll end up in the right
chest(s).

I also added a data structure that prefilters the chests it analyzes for
each item, depending on the item type. For instance, if you drop a stack of
dirt, it will first check all chests that has a suck filter that contains
dirt, and if none of those can pick it up (out of range, full, etc.) it
will check all chests with no filter at all. This means that it will never
analyze a chest with a stone filter (for example) if you drop dirt. With
diligent use of suck filters, you should have little impact on server
performance even with a huge number of diverse chests (unless you add
thousands of chests with no filter.)

--
Lasse Vågsæther Karlsen

On Wed, Feb 15, 2012 at 17:25, sorklin <
reply@reply.github.com
> wrote:

> I already did :). I was just wondering if you knew why he did it? I
> can't think of a good reason to keep them loaded. I didn't want to break
> internal functionality by just disabling it.
>
> Have you thought about officially forking this? They don't seem to be
> actually doing anything with this plugin, except for changing the POM for
> new RBs.
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/lassevk/DropChest/commit/6f0618de51a6f0e7ff34376e5207a2c52b4a6215#commitcomment-969979
>