Problem ChickenChunks .cfg not working as expected

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

R4b

New Member
Jul 29, 2019
16
0
0
Hey all,

This is my first post here so hi!

I have been running a server with FTB Ultimate 1.0.1 for just over a month now and we have encountered quite high RAM usage lately so I am in the process of putting a few measures in place to bring this down. One of these is changing the 'allowoffline' default setting in the ChickenChunks .cfg file to 'false'. I left the setting for OP's to 'true'. However when testing this in game I have found that ChickenChunks Chunk Loaders are now behaving as if 'allowoffline {DEFAULT=false}' is applicable to everyone, including OP's such as myself. Therefore not keeping chunks loaded from my own loaders when I am offline. This is vital due to some of the shared resources we have on the server.

I have also alternatively tried putting my own in game player name into the config as suggested also with no joy.

Has anyone else had problems with this? Could any other configs be clashing with this one (although the only other config I've touched is mystcraft)? Could a plugin perhaps be interfering (can give more details about what were running if necessary)?

This is my current config - http://pastebin.com/fZrFyQqR

I hope someone can help! Thanks for reading!
 

cjm721

New Member
Jul 29, 2019
734
0
1
Was it working with op=false? Also remember you have it set to they stay active for 1 minute after logout.
 

R4b

New Member
Jul 29, 2019
16
0
0
I didn't try that because I wanted OP's to have thier chunks loaded while offline. awayTimeout is set to 1.
Since we changed these settings we've also been noticing issues with quarries resetting! :S
 

cjm721

New Member
Jul 29, 2019
734
0
1
From how you wrote the OP make it sound as if it worked with OPs set to false. Only thing I can think that would cause this is something in the forgechunk loading being changed, or it was fixed in the update to 1.1.2 ultimate.
 

R4b

New Member
Jul 29, 2019
16
0
0
We're updating to 1.1.2 on Saturday, so i'm not gonna worry about it for now. Thanks very much for your input, i'll come back if i'm still stuck after the update! :)