FTBTeam / FTB-Mods-Issues

Any mod issues, be it FTB Teams, Quests or any other of our mods can be reported here!
22 stars 1 forks source link

[Bug]: chunks forceloading #523

Open Malaxis12 opened 1 year ago

Malaxis12 commented 1 year ago

Mod

Ftb chunks

Mod version

1.16.5 latest

Forge / Fabric version

java 8, forge 36.2.35

Modpack & version

Ragnamod 6

What issue are you having?

Hello, im struggling with chunk loading, when players are on server forceloaded chunks are working but when server is empty, chunks stop loading In config is allowed to chunkload offline Machines like teleporter with anchor upgrade also not work or command /forceload add

Crashlogs

No response

Steps to reproduce

1.Create team with players

  1. Claim chunk
  2. Force load him
  3. Leave the game.

Anything else to note?

No

DelviousCrafts commented 1 year ago

Noticed this issue as well in 1.18.2 when the force_load_mode option was set to "always".

Found that the config max_idle_days_before_unclaim default value had an L after the 0 which seemed strange for a numeric value. Changing this to just 0 fixed the issue of force loading when offline for some reason. Might be that the config was bugged completely due to this extra value added where it shouldn't be.

Uncertain if this is the case with 1.16 though.

Versions:

Fayorg commented 9 months ago

Had the same issue on the 1.20.1 with the ftb-chunks-forge-2001.2.4 version. Removing the extra d after the max_idle_days_before_unclaim fixed the issue.

MacChuck commented 9 months ago

This may be changed in 2001.2.5. I removed the "d" from the idle settings, and when I started the server back up, the d reappeared. (I found this report trying to chase down an intermittent chunk loading issue)

desht commented 9 months ago

The config value was changed from an integer to a double (to allow for fractions of a day to be specified) back in 1.19.2, and the config system we use appends a "d" to double values. See #688.

Found that the config max_idle_days_before_unclaim default value had an L after the 0 which seemed strange for a numeric value

Not strange; it used to be a long value, and our config system appends an L to long values.