-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Storage blocks #4
Comments
Definitely would like that. Requirements:
|
Slime block logic isn't necessarily needed; I didn't like the way Mojang implemented it anyway. Just having a way to store all of the slime in a more compact way would definitely be a welcomed addition though. If you need textures, I'd be happy to help you out there. I guess block IDs are the biggest issue. Would it be necessary to have a separate ID for each new block or could you implement / extend a base storage block (GPEBlockStorage) and use metadata to differentiate the individual blocks? That would allow up to 16 new blocks if I'm not mistaken. Similar to what FlowerChild did with FCBlockAestheticOpaque. |
Yes, I don't like the bouncy slime block either, the way it interacts with pistons is more of an interest... I also like the idea of encouraging the use of the Hardcore Packing feature. The list so far:
|
I like what you've come up with and definitely think hardcore packing could use more uses. The one thing I would change is the recipe for the sawdust block. I would make it one glue surrounded by eight sawdust. This would give another use for glue as there isn't enough uses for it at the moment and would make more sense, in a Minecraft shirt of way. It would also make cooking/ smelting |
…l, sugar, bone, sawdust, nitre, potash, ash, flour; global Hardcore Packing hook to allow packing the above, plus redstone and lapis
As the title suggests, would there be any chance to add more storage blocks; ex., bone blocks, rotten flesh blocks, back-porting slime and coal blocks, etc.
The text was updated successfully, but these errors were encountered: