ChickenChunks config questions

  • 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
Status
Not open for further replies.

seattleda

New Member
Jul 29, 2019
42
0
1
For my server OP:
  • 24/7 chunkloaders
  • as many as they want
  • where ever they want
  • logged on or not
For non-OP
  • Only have 1 chunkloader
  • Only in Overworld
  • Disable within 1 hour of log off
What would I change in the config?

Thanks!

ChickenChunks default config
#Per player chunk limiting. Values ignored if 0.:Simply add <username>=<value>
players
{
#Forge gives everyone 12500 by default
DEFAULT=5000
#For server op's only.
OP=5000
}

#If set to false, players will have to be logged in for their chunkloaders to work.:Simply add <username>=<true|false>
allowoffline
{
DEFAULT=true
OP=true
}

#Set to false to deny a player access to the chunk viewer
allowchunkviewer
{
DEFAULT=true
OP=true
}

#The number of minutes since last login within which chunks from a player will remain active, 0 for infinite.
awayTimeout=0
 

Francis Baster

New Member
Jul 29, 2019
295
0
0
This should do it:

Code:
#Per player chunk limiting. Values ignored if 0.:Simply add <username>=<value>
players
{
#Forge gives everyone 12500 by default
DEFAULT=9
Notch=5000
#For server op's only.
OP=5000
}
 
#If set to false, players will have to be logged in for their chunkloaders to work.:Simply add <username>=<true|false>
allowoffline
{
DEFAULT=false
Notch=true
OP=true
}
 
#Set to false to deny a player access to the chunk viewer
allowchunkviewer
{
DEFAULT=true
OP=true
}
 
#The number of minutes since last login within which chunks from a player will remain active, 0 for infinite.
awayTimeout=60

Note that you can add players' names to the config, I used Notch as an example, if you want to apply the 24/7 chunkloading to non-ops, perhaps donators.

I set the default number of chunks per player to 9, as this is the amount of chunks loaded by one normal chunkloader set to a radius of 2, which is the default.

If you want to restrict placement just in the overworld, and are not running Bukkit, you can use AlphaEst's PEX and ModifyWorld Forge mods to control where certain blocks are placed using a permissions system. There may be other mods which can help do this too.

If you are running MCPC+, you can use any of the main Bukkit plugins such as Essentials AntiBuild, WorldGuard or ModifyWorld. Note that WorldGuard's blacklist is NOT metadata sensitive, so that particular feature is not recommended by me for Forge servers. Of course WorldGuard is still very useful to have for other reasons.
 
  • Like
Reactions: seattleda

KnightOwl

New Member
Jul 29, 2019
197
1
1
That won't actually do it as it would require you to manually add a name every time a player joins. That could probably be automated though so the bigger problem is that you would have to restart your server to get the new config to load unless I'm missing a bukkit plugin that would let us reload mod configs?

That said.. if you are restarting your server at regular intervals you just let people know that it takes time before they can access their chunk loader.
 

Eyamaz

New Member
Jul 29, 2019
2,373
0
0
Just make all chunkloaders/anchors uncraftable and give your players 9 spot loaders each spawned by an admin.
 

Francis Baster

New Member
Jul 29, 2019
295
0
0
That won't actually do it as it would require you to manually add a name every time a player joins. That could probably be automated though so the bigger problem is that you would have to restart your server to get the new config to load unless I'm missing a bukkit plugin that would let us reload mod configs?

That said.. if you are restarting your server at regular intervals you just let people know that it takes time before they can access their chunk loader.

The entry labelled DEFAULT applies to all users not listed explicitly. So in fact the config in my post would work as OP described.
 
Status
Not open for further replies.