Initial Power Generators (and code cleaning) #26
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#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/powergen"
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
Currently has none of the powergen works, this is for tracking as I'm also doing a lot of under-the-hood tweaks.
Current changes:
jarpackage.Todo
Checklist:
@ -0,0 +3,4 @@public enum EnergyTransferMode {None,Insert,ExtractNo both?
@ -0,0 +3,4 @@public enum EnergyTransferMode {None,Insert,ExtractNot taking into account individual sides, it'd only receive or send power at any given time. This is an old enum that's planned to be replaced in my energy rework PR.
What do you mean? Since for example the vacuum chest don't have side control, but still output items. Same for the xp vacuum. But we could also just give them side control
Thats's a good argument, yeah. At the time I just left it as a todo as it needs to be discussed. The entire IO configuration system could do with a once-over with documentation so its clearer.
Merging because there are a lot of dependents on this PR now.