I need some feedback on this. Block Extenders is becoming much larger than just Block Extenders and should focus on things that do not already exist in other mods (I was not aware the Block Extender concept existed already when I started it). The current filtering system is very powerful and is something no other mods currently do, the focus should be put on things like that.

Integration with other mods is also very important for Block Extenders, it should be able to fill in a gap in the current FTB/Tekkit/ForgeCraft packs. For example the Filtering Chests fill in the gap between manual sorting and a Applied Energistics system.

Because of all this, a name change is very needed, Block Extenders is so much more than just extending blocks. 'Transportation' may be a good name because it's broad enough, but does say something about what the mod is.

I need more suggestions and I need more people to help with things like a wiki and a good MCF post. I hope I can find a way to make more people hear about the mod!

Was just thinking about this recently as well. A major thing that made me interested in this mod was the custom wildcard filtering, which is something I always thought should exist.

However, I'm not sure if expanding the scope of the mod is necessarily better (for now) than keeping the scope small and really working to make the existing stuff extremely solid. For example, it might be better to focus entirely on block extenders/buffers and make sure that they work correctly, have as much mod interaction as they possibly can, that they work in multiplayer, do not cause any tick lag, etc. To me, it seems like making a smaller mod good might be more important than making a bigger mod that could be frustrating to use (due to bugs/incorrect functionality/untested or poorly implemented things).

The filtering chest is a good idea and I really like it, but I feel that there is still a lot to be done in making sure that the block extenders and buffers are as good as they can be. Adding more and more means that it's more likely that things slip through the cracks and turn out half as good as they should.

My vote would be to keep it as Block Extenders, even going so far as to hold off on including filtering chests in the next update, and focus entirely on block extenders and buffers to make them as functional as possible (and well tested), and then after that, increase the scope and consider a name change. The core idea is a good one and I think it's good enough to gain interest on its own (there are a lot of applications for it).

I agree with you on that a small good mod is better than a large buggy/meh mod. But, it will be very confusing for people if we change the name. The fact is, at this point there are not a lot of people using this mod (yet), so the earlier the name is changed, the less people are confused.

I also think we should focus on the stuff we have right now and make it better. But, I do think filtering chests should be a part of that, I think it's the easiest/best implementation of the current filtering system.

The biggest problem right now is the amount of work I put into this mod. If you didn't pick the mod up, it would probably have died. I just don't have the patience to redo stuff, if I have time I want to make new things, I'm the opposite of a perfectionist.

And this doesn't only have it's effect on the code, but also on all the activities that come with managing a mod. I don't have the patience/skill to make a good wiki, make a good MCF post, make more explanation videos. And on top of that, my native language is not English, which makes all of that a lot harder. I just have to find someone that does like (and is good at) doing that.

Yeah, I can understand that. I don't really know what goes into making a Minecraft mod popular. And you're probably right that changing the name sooner rather than later is a good idea. I'll try to come up with some possibilities.

I also agree that filtering chests are a really good usage of the filtering mechanics of this mod, but I think they might need some more time to mature before they'd get much use in a real playthrough (however, maybe I just need to know more about what they're meant to be used for). For example, with the current implementation, you can still manually put items into chests that shouldn't be allowed by the filter, which seems confusing, and I'm unclear on whether or not that's intended or just something that hasn't been fully implemented yet. It'd be nice to have a clearer idea of what you are intending when you add new stuff to the mod, so that I can be of more help in making sure that it's functioning properly.

As an aside, I think that a super cheap, manual-insertion-only (no pipe connections allowed) filtering chest that is only made with a chest and some iron bars would be both a good usage of the filtering system and a good solution for extremely early game sorting, as long as the manual insertion can be filtered (I'm pretty sure it can, I did some messing around with it a while back). However, there is a bug with inventory tweaks that makes the Move All shortcut give up whenever any item is unable to be moved, but I'll try to submit a pull request to get that fixed.

The filtering chests work like this: They will automatically put the inserted item (piped/manual) into the chest that allows the item to be inserted in. Chests will create a 'group' when placed next to each other. One of the chests will automatically be selected as the leader (he knows about all connected chests in the system) and all 'children' will only communicate with the leader (the leader will try to put the item in all chests if a child asks for it).

Like most Block Extender features this is a bit hacky (the current MC inventory system is horrid), but it seems to work perfectly and is not too memory heavy (only leader knows about all chests in the group). I have not tried Inv Tweaks with the chests, but I think it shouldn't be a problem.

The only thing is: all group members need to work correctly, if not it can f up the whole group. This is the reason I made the filtering member a abstract class and not an interface, but it is very hard to create working integration with other mods (like IronChests). I basically need to copy all functions of that mod into a class in Block Extenders, which is something I'd rather not want to do. I'd like to brainstorm with you about a good way to do this, there might be a way I do not know.

Question: Do you want people to be able to manually insert any item into a filtering chest no matter what? Like, say, a filtering chest is whitelisted for ingots only and I try to shift click an ore block into it, should it go in the chest or not be allowed in? If the goal is to not have it allowed in, I can try to work on that.

As for a name change, here are some random ideas:

• Clean Conveyance
• Refined Transport / Refined Transportation

Filtering chests will put items in the best possible connected inventory. So a blacklisting inv, is a lower priority than a whitelisted one. If you put an item in a inventory that is not linked to a blacklisted inv, it will also put it in the best possible inventory, which would be the inventory the user is trying to put it in.

The problem is, I hack into the setInventorySlotContents method. This method doesn't have a return, so it's too late to not allow it in. You could try to stop it earlier (on isItemValidForSlot), but that would mean checking every filter of every connected inventory twice, that kills performance (the filtering is heavy performance wise). Caching can be an option, but filter settings can change.

So it's a bit of both, the current inventory system is horrible (but it's changing in 1.8 YAY!), so it's hard to make this not accept the item and I like it more when it only auto-sorts and not blocks items (but that might just be me).

Oh and I like those name suggestions :D

It would sound cool if the name alliterates something like:

• Refined Relocation
• Terrific Transportation
  or as you said:
• Clean Conveyance

I like Refined Relocation best. If there are no other suggestions I'm probably gonna go with this.

Sounds good to me.