Minecraft Forums

Pack-wise, I've taken care of the elephant in the room.

Forestry pack: http://www.curse.com/mc-mods/minecraft/231147-storage-drawers-forestry-pack

Order with a side of inPureCore if you don't want your NEI spammed up too badly, until such a time I have a config for that in place.

Wow! Amazing mod! I have wanted a lot of mods to update to 1.8, but its hard to come by good mods in 1.8, due to lots of code rewriting. This is a great mod for 1.8, and I hope you make more things like it in the future! Keep up the good work!

Storage Drawers 1.7.10 branch and all wood packs updated. The terror is over -- you can hide the extra 9000 blocks from NEI or Creative Tabs.

Version 1.5.4:

• Add config options to control NEI and Creative Tabs use in wood addon packs.

All Packs:

• Fix recipe precedence causing drawers to be uncraftable in some packs.
• Use global config options to control NEI and Creative Tab visibility.
• Requires Storage Drawers 1.5.4 or later.

The slave does not extend range. Its purpose is to provide additional "surfaces" for the controller, e.g. put one on the edge of your network to attach a pipe, or build some columns of them and cover them in super crafting frames. They're very lightweight so this is preferable to placing multiple controllers, which was previously done.

The 12 block range is already pretty OP, since that encompasses anything within a 25x25x25 cube centered on the controller.

With just a little outside help, you can create multi-bank systems using multiple controllers. It's been demonstrated in the last few pages with hopper ducts on 1.8.

Jaquadro,

Am working on the pack for Ancient Trees...and I have a problem right off the bat:

The API does not expose BlockDrawers or BlockTrim...

To implement the pack, I would have to go outside the API...and bear the risks of volatile code living outside the API. Unless the API is changing, Maybe I should fork SD and add the pack to your repo via pull request?

Also could work out a system for you so that the packs don't have to be separate if you want....

What do you suggest?

S

Quote from Dodge34»

Thanks for the quick informations, now I just have one request, we need some kind of terminal like in AE2 to interact with the stuff in the drawers, search for some stuff, craft items and such, but without the need of power or complex building systems that takes forever to build, just a simple thing to quickly access everything at one spot, this is the only thing I really miss from AE2 or Logistic Pipes.

Another precision, I use the 1.7.10 version, most of the mods I use aren't in 1.8 yet.

It's a very complex thing, I don't think I will be adding something like that to this mod.

A new terminal from the Ender-IO mod was demonstrated on ForgeCraft and it's quite powerful like AE2, but it's still beholden to power requirements and stuff. I encourage other authors to step in and try to fill this void.

Quote from ScottKillen»

Jaquadro,

Am working on the pack for Ancient Trees...and I have a problem right off the bat:

The API does not expose BlockDrawers or BlockTrim...

To implement the pack, I would have to go outside the API...and bear the risks of volatile code living outside the API. Unless the API is changing, Maybe I should fork SD and add the pack to your repo via pull request?

Also could work out a system for you so that the packs don't have to be separate if you want....

What do you suggest?

S

The packs were intended to have a hard dependency on the SD base mod, as they extend block classes. Submitting it back to the main repo is fine, as that's where I'll be sticking any of the packs I make.

Though I assume you were intending a standalone addon mod, it wasn't clear from your previous post if you were going to try and create another pack using an existing one as a template, or if you were going to try and integrate it into Ancient Trees. If the later, I could see it being a bit annoying since the mod isn't in Maven anywhere.

The gradle dependency issue is a huge pain right now. I would love to somehow clean up or fix that, because I have to temporarily copy around an SD base jar into each pack to compile it, and then remove it so I can run them all together in dev. I do want the packs to compile separately though, so I don't end up with a meg or more of assets and the risk of chewing up a lot of block IDs and texture space before someone has a chance to work out configs.

Quote from jaquadro»

The packs were intended to have a hard dependency on the SD base mod, as they extend block classes. Submitting it back to the main repo is fine, as that's where I'll be sticking any of the packs I make.

Though I assume you were intending a standalone addon mod, it wasn't clear from your previous post if you were going to try and create another pack using an existing one as a template, or if you were going to try and integrate it into Ancient Trees. If the later, I could see it being a bit annoying since the mod isn't in Maven anywhere.

The gradle dependency issue is a huge pain right now. I would love to somehow clean up or fix that, because I have to temporarily copy around an SD base jar into each pack to compile it, and then remove it so I can run them all together in dev. I do want the packs to compile separately though, so I don't end up with a meg or more of assets and the risk of chewing up a lot of block IDs and texture space before someone has a chance to work out configs.

I understand, but I thought, based on one of your previous replies, that you intended no hard dependencies.

My intention was to have the SD support integrated into Ancient Trees so that it activated when SD was present, just like the support for Garden Stuff currently does.

You could resolve your concerns by having everything in one mod and defaulting to "off" for the packs...and printing a warning to the log and/or console when a relevant mod was detected. Textures could be compressed using TinyPNG to reduce jar size...etc.

Regarding gradle dependencies, you could upload to the local maven cache via the 'install' task (see: https://docs.gradle.org/current/userguide/maven_plugin.html) and have a maven dependency in the packs. As long as SD was in the local maven cache, gradle would pick it up to fulfill the dependency.

I will work on a plugin for Ancient Trees and submit it. Thanks for the help!

Hey Jaq,

Any chance of getting the ability to set the trim style on the different storage mediums? I know it takes the colour of the last upgrade used. But It might be nice to also be able to shift-right-click with say. A trim block to change the trim to that style.

OR, if thats a bit too much, perhaps using an empty upgrade on it will set it's trim style to its non upgraded colour?

Thanks for reading <3

Quote from Rorax»

Hey Jaq,

Any chance of getting the ability to set the trim style on the different storage mediums? I know it takes the colour of the last upgrade used. But It might be nice to also be able to shift-right-click with say. A trim block to change the trim to that style.

OR, if thats a bit too much, perhaps using an empty upgrade on it will set it's trim style to its non upgraded colour?

Thanks for reading <3

The upgrade overlay is probably my least favorite part of the mod. There is a config option to not render it, though you will need to remember where you applied storage upgrades, or open the upgrade management UI to check. The trim override is an interesting idea though. If you have other ideas related to styling, I'm also interested to see them.

Quote from ScottKillen»

I understand, but I thought, based on one of your previous replies, that you intended no hard dependencies.

My intention was to have the SD support integrated into Ancient Trees so that it activated when SD was present, just like the support for Garden Stuff currently does.

You could resolve your concerns by having everything in one mod and defaulting to "off" for the packs...and printing a warning to the log and/or console when a relevant mod was detected. Textures could be compressed using TinyPNG to reduce jar size...etc.

Regarding gradle dependencies, you could upload to the local maven cache via the 'install' task (see: https://docs.gradle.org/current/userguide/maven_plugin.html) and have a maven dependency in the packs. As long as SD was in the local maven cache, gradle would pick it up to fulfill the dependency.

I will work on a plugin for Ancient Trees and submit it. Thanks for the help!

I gave it some more thought, and if you can wait another day or so, I think it's reasonable to provide an interface for you to implement, and a factory method to get back some block and item objects that you can do with as you need. Then you can copy in the API and provide this in-mod.

Quote from neros64»

Any news on wood pack for ExtraBiomesXL?
Could you add a config option to move where the text is for displaying how many items are in a drawer? My hotbar is in the way so its hard to see how many items I have in the drawer. That or make it show the item icon with number next to it instead.

I don't follow. Are you talking about the WAILA display? That can be controlled within WAILA -- somewhere. The only other way to see exact counts is pulling up the GUI, and then it's like any other GUI.

EXBL is on my list, but might be small enough that I don't want to break it out into a dedicated pack.