Skip to content
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

[Bug]: Steam singleblock machines sometimes stop accepting steam #1365

Open
talchas2 opened this issue Jan 6, 2025 · 3 comments
Open

[Bug]: Steam singleblock machines sometimes stop accepting steam #1365

talchas2 opened this issue Jan 6, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@talchas2
Copy link

talchas2 commented Jan 6, 2025

Issue Summary

I've had (low pressure) steam machines sometimes stop accepting steam. They keep running just fine until they run out of steam. None of these help: breaking and replacing pipes, using conduits instead of pipes (or vice versa), soft mallet, rotating/moving the vent. Restarting the game does not help, it does persist, though I don't see any relevant difference in /data get block that could explain it. Deleting saves/$foo/data/{gtceu,enderio}* with the game off and starting the game up again in case it was stored in the fluid net/conduit net info, didn't do anything.

Breaking and replacing the machine does help (until it breaks again, which takes a while). Presumably there's some data somewhere in the save that would at least show a difference (and I have a save kept around to look at), but I don't know how to get at it.

Reproduction steps

Sadly I haven't been able to get any sort of consistent repro for the working->broken machine transition. (I've tried a little in a testing world, and a little in a "just gt" instance)

Relevant log output

bad
[23:05:01] [Render thread/INFO] [minecraft/ChatComponent]: [CHAT] -360, 65, -284 has the following block data: {importItems: {storage: {Size: 1, Items: []}, isDistinct: 0b}, z: -284, x: -360, chance_cache: {item: [], su: [], block_state: [], fluid: [], eu: [], cwu: []}, recipeLogic: {isActive: 0b, progress: 0, totalContinuousRunningTime: 0L, fuelTime: 0, suspendAfterFinish: 0b, duration: 0, fuelMaxTime: 0, status: "IDLE"}, steamTank: {lockedFluid: {Amount: 0, FluidName: "minecraft:empty"}, isDistinct: 0b, storages: [{t: 11b, p: {Amount: 10800, FluidName: "systeams:steam"}}]}, cover: {}, paintingColor: -1, y: 65, owner: {type: 1, teamUUID: [I; -582462925, -811251416, -1637194536, -349659323], playerUUID: [I; -582462925, -811251416, -1637194536, -349659323]}, id: "gtceu:lp_steam_forge_hammer", ForgeCaps: {}, exportItems: {storage: {Size: 1, Items: [{Slot: 0, id: "gtceu:impure_redstone_dust", Count: 63b}]}, isDistinct: 0b}, isMuffled: 0b, needsVenting: 0b, outputFacing: "north"}

good
[23:05:28] [Render thread/INFO] [minecraft/ChatComponent]: [CHAT] -360, 65, -285 has the following block data: {importItems: {storage: {Size: 1, Items: []}, isDistinct: 0b}, z: -285, x: -360, chance_cache: {item: [], su: [], block_state: [], fluid: [], eu: [], cwu: []}, recipeLogic: {isActive: 0b, progress: 0, totalContinuousRunningTime: 0L, fuelTime: 0, suspendAfterFinish: 0b, duration: 0, fuelMaxTime: 0, status: "IDLE"}, steamTank: {lockedFluid: {Amount: 0, FluidName: "minecraft:empty"}, isDistinct: 0b, storages: [{t: 11b, p: {Amount: 16000, FluidName: "gtceu:steam"}}]}, cover: {}, paintingColor: -1, y: 65, owner: {type: 1, teamUUID: [I; -582462925, -811251416, -1637194536, -349659323], playerUUID: [I; -582462925, -811251416, -1637194536, -349659323]}, id: "gtceu:lp_steam_forge_hammer", ForgeCaps: {}, exportItems: {storage: {Size: 1, Items: [{Slot: 0, id: "gtceu:impure_pentlandite_dust", Count: 55b}]}, isDistinct: 0b}, isMuffled: 0b, needsVenting: 0b, outputFacing: "north"}
@talchas2 talchas2 added the bug Something isn't working label Jan 6, 2025
@talchas2
Copy link
Author

talchas2 commented Jan 7, 2025

This was on 0.10.5, but it has also now occured on 0.11.2 (and its updated GT version). I've also now seen GT pipe -> (thermal) steam turbine fail, and I think thermal steam boiler -> GT pipe fail as well. I should have checked to see if removing the pipe and replacing it with a conduit worked, but I didn't.

@MatthiasMann
Copy link

The issue seems to be "systeams:steam" - the machines need "gtceu:steam" - I don't think you can use the thermal steam boiler to make steam for GT.

@talchas2
Copy link
Author

talchas2 commented Jan 7, 2025

Hmm, that's not quite correct, systeams:steam works fine. However they don't combine despite what I thought I was seeing, so the problem at least most of the time is that I was trying to also use the much more efficient gt boilers as well, and getting weird behavior from trying to have two fluids in the same pipes/conduits/etc. According to my notes I had one where a machine was stuck with no steam of either sort in it, which this would not explain, but I don't have that one saved and maybe I copied something wrong in that case anyways (and maybe it was something like conduits locking to fluids, depending on what pipes I was trying to use at the time).

Updating systeams to 1.8.2 lets me unify the steam created into gtce:steam with kubejs/data/systeams/recipes/water_boiling.json, no idea if there's any issues with that upgrade though that might be more subtle than "immediate crash/kubejs error".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants