Energy conduits + FE p2p interaction killing tps #878
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#878
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Is there an existing issue for this?
Current Behavior
An interaction between FE P2p (https://www.curseforge.com/minecraft/mc-mods/modern-ae2-additions) and energy conduits caused my tps to drop to 12. This happened using 1:1 FE p2ps, with energy conduits set to insert only on the side providing the power, and extract only on the side consuming the power. The issue wasn't noticable until I had ~30 or so p2ps + conduit pairs
Expected Behavior
No response
How to Test
I'm attaching my spark profile file, but renaming it to a .txt because github won't let me upload the real extension. To use: swap the extension to .sparkprofile and upload it to https://spark.lucko.me/
FeKqQdq5lY.txt
Local Environment
Any Additional Information?
No response
This is a fundamental limitation of how conduits and P2P FE works. It would require a rework of either part and we're not changing conduits in substantial ways on 1.20.1 anymore so unfortuantely I'll have to close this issue as wontfix.