I am not using performance mods.

• Confirm

Description

Probably more of a feature request here. It seems odd that a compact machine, designed to be placed in the world, doesn't have chunkloading once you leave it.

It was pointed out to me that this was an intentional decision because folks in multiplayer could abuse compact machines. I agree with the principle, but it seems like the behavior change is odd to have as a default.

Suggestion 1: Automatically chunkload all compact machines, possibly gated behind an option in config.

• This has the advantage of parity with 1.16.5 or earlier (if I remember correctly) - I found it very confusing when suddenly my machine wasn't working after I left it.
• The disadvantage, of course, is that if it's not an option, it leaves the abuse loophole open.

Suggestion 2: Have compact machines inherit the chunkloading setting of the chunk where the single block resides.

• This has the advantage of being fairly transparent - if you're chunkloading your base, the machines in the base work as expected. If you're not, you shouldn't expect the compact machine to work either.
• The disadvantage (in my mind) is that it still leaves routes for abuse, but I assume a server admin could nuke a single chunk a lot more easily than some jerk placing random machines all over the world. :p

Mod Version

compactmachines-forge-6.0.0.0-nightly.jar

Forge Version

1.20.1 - 47.3.0

Link to Crashlog

n/a

Screenshot (if available)

n/a

How to reproduce

Pretty much as described. Make a compact machine, do something automated in it, leave the machine, and then yell "Y U NO WORK" at it.