is this a bob ross reference? #167
No reviewers
Labels
No labels
Area-Assets
Area-Backend
Area-Conduits
Area-Datapacks
Area-Lang
Area-Mod Compat
Area-Parity
Area-Rendering
Good first issue
MC-1.19.2
MC-1.20.1
MC-1.20.4
MC-1.20.6
MC-1.21
MC-1.21.1
Modtoberfest
P-0-High
P-1-Medium
P-2-Low
Status-Awaiting Response
Status-Behind-Flag
Status-Blocked
Status-Cannot Reproduce
Status-Duplicate
Status-Help Wanted
Status-Incomplete Report
Status-Invalid
Status-Needs LTS Backport
Status-Needs Updating
Status-Stale
Status-To Implement
Status-Triage
Status-Wontfix
Status-Wontmerge
Type-Backport
Type-Bug
Type-Documentation
Type-Enhancement
Type-Question
Type-RFC
Type-Suggestion
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Team-EnderIO/EnderIO#167
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/painting_machine"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Adds the painting machine, Painted Blocks worked before, this is just a way to obtain them.
Currently this doesn't have a proper front model, I stole the sag mill one
Checklist:
I'll try to get this reviewed for you later tonight
Just a couple of things; but looking good!
@ -0,0 +1,136 @@package com.enderio.machines.common.recipe;Is there any way at all we could not pass the entire block entity in the container?
Could we maybe drive this from config files?
@ -95,3 +97,4 @@EIOEntities.register();// Run datagen after registrate is finished.IEventBus modEventBus = FMLJavaModLoadingContext.get().getModEventBus();I'm in two minds here:
Either we should merge all of these down into a single init class again
-or-
we could further separate these out into more divided chunks to make them easier to navigate.
I'm happy for whichever as long as we're consistent :)
@ -0,0 +1,136 @@package com.enderio.machines.common.recipe;yes, I just copied the sag mill, but I don't need it
@ -0,0 +1,136 @@package com.enderio.machines.common.recipe;I think the config file would become cluttered easily if every machine got an entry
@ -95,3 +97,4 @@EIOEntities.register();// Run datagen after registrate is finished.IEventBus modEventBus = FMLJavaModLoadingContext.get().getModEventBus();oh no, work
@ -0,0 +1,136 @@package com.enderio.machines.common.recipe;That's fair, but its still a really nice way of being able to configure everything, especially when it comes to balance; means we don't have to dig into a massive number of files to find everything
This is the only other thing I can see at the minute :) Thanks
@ -99,6 +102,10 @@ public class EnderIO {modEventBus.addListener(SoulVialItem::onCommonSetup);IntegrationManager.addIntegration(EnderIOSelfIntegration.INSTANCE);new UseGliderTrigger().register();new PaintingTrigger().register();Can we move this up with the others, drop the Decor comment and maybe call BaseNetwork EIONetwork for consistency?
@ -0,0 +1,44 @@package com.enderio.machines.client.gui.screen;Make the painter use the new capacitor tooltip energy widget
Thanks for this agnor, great work!