search

mekanism / Mekanism-Feature-Requests

All enhancements and feature requests for Mekanism (for current and future releases) should go here.
11 stars 4 forks source link

Ability to restrict in the configs how big a Dimensional Stabilizer can chunk load #499

Open JustAnotherGhostName opened 1 year ago

JustAnotherGhostName commented 1 year ago

Describe the feature you'd like

Add a config option to specify the maximum chunk size of the dimensional stabilizer. The current chunk size is a 5x5 square which you can select which chunks. Ideally you could make it only do one chunk.

Describe alternatives you've considered

I considered the chunk loading upgrade, however, its draw back is that its hard to detect from a server administration standpoint. It is much harder to detect how many chunk loading upgrades a user has compared to how many Dimensional Stabilizers a user has. This is because the Dimensional Stabilizer is a block that is dedicated for its one task, loading chunks. If a player has a large base with multiple machines, and you allowed chunk loading upgrades, it would be almost impossible to know which one has the upgrade without looking at every single individual machine.

Of course FTB Chunks is an option for chunk loading, however, FTB Chunks gets corrupted very fast and common in 1.19.2 in ATM8 1.0.7. Not only this, but it also creates ghost chunks that cannot be removed without unclaiming every single chunk that is on the server with a command, or deleting the ./ServerFiles/world/data/chunks.dat file. See the following issue: https://github.com/FTBTeam/FTB-Mods-Issues/issues/101

Then the other option would be to add another mod such as chicken chunks which has 1x1 chunk loaders. The issue with this is that the server is running a pre-made pack that we do not have authorization to push an update to. It is rather unlikely that a new player will join a server if they have to download another mod. I am going to request the ATM team to add say chicken chunks aswell in a future update, but I cannot guarantee that this will occur.

Additional context

The main reasoning for this request is that from a server administration standpoint, currently on Forge 1.19.2, there is not a better option to chunk loading if a pack if there is not a mod dedicated to chunk loading and FTB Chunks is in the pack. Unfortunately right now FTB Chunks gets corrupted fairly frequently, which causes the server to not stop properly. Not only this, but the ghost chunks do provide an extra hindrance in the server's TPS.

pupnewfster commented 1 year ago

I will consider this as I definitely see why server owners may want this (no idea when it may happen though). In the meantime you could set the energy usage of the chunk loader at a value that basically makes it so you can only afford to chunk load the single center chunk.

JustAnotherGhostName commented 1 year ago

I will consider this as I definitely see why server owners may want this (no idea when it may happen though). In the meantime you could set the energy usage of the chunk loader at a value that basically makes it so you can only afford to chunk load the single center chunk.

That is definitely a solution to consider, although I dont believe it would work in my case since you could theoretically pump a crazy amount of power in it with flux networks and Entangled Blocks. It also would further gate its usage when its replacing a free alternative that gets corrupted, which would likely anger my player base too much.

I currently have it configured so that the recipe is not changed, but there is no power cost, and a server wide rule restriction on how many a player can own. It certainly is not ideal since it requires manual staff inspection, but using the world edit //count command and viewing the loaded chunks with crash utilities, it makes things a bit easier than it would be otherwise.

I appreciate the prompt consideration of this suggestion, and your time spent developing the mod.

pupnewfster commented 1 year ago

Pumping infinite power into it wouldn't make a difference because I only suggested upping the energy usage config not the energy storage config. AKA if it can't store enough energy (even with upgrades) to load more than one chunk you can only ever have that one chunk loaded. Granted thinking about it the other solution would be to just lower the buffer instead of raise the usage.

JustAnotherGhostName commented 1 year ago

Ah I see, that's a good idea. I'm going to have to try that out, thank you very much for the suggestion.