Problem Chunk Loading Problem

  • 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
I

iMontouch

New Member
Jul 29, 2019
147
0
0
hey there,

there is a problem on the server which throws this error to the log:
Code: 
[ForgeModLoader] The mod MiscPeripherals attempted to force load a chunk with an invalid ticket. This is not permitted.
The source are some turtles with chunkloader upgrades.
Our forgeChunkLoading.cfg is configured like that:
Code: 
defaults {
    # Unloaded chunks can first be kept in a dormant cache for quicker
    # loading times. Specify the size (in chunks) of that cache here
    I:dormantChunkCacheSize=0
 
    # Are mod overrides enabled?
    B:enabled=true
 
    # The default maximum number of chunks a mod can force, per ticket,
    # for a mod without an override. This is the maximum number of chunks a single ticket can force.
    I:maximumChunksPerTicket=25
 
    # The default maximum ticket count for a mod which does not have an override
    # in this file. This is the number of chunk loading requests a mod is allowed to make.
    I:maximumTicketCount=1000
 
    # The number of tickets a player can be assigned instead of a mod. This is shared across all mods and it is up to the mods to use it.
    I:playerTicketCount=1000
And thats the Chicken Chunk config file:
Code: 
#ChunkLoader Configuration File
#Deleting any element will restore it to it's default value
#Block ID's will be automatically generated the first time it's run
 
 
#The number of minutes since last login within which chunks from a player will remain active, 0 for infinite.
awayTimeout=0
 
block.id=243
 
#The number of ticks to wait between attempting to unload orphaned chunks
cleanuptime=0
 
#The maximum number of chunks per chunkloader
maxchunks=400
 
#Set to false to disable the automatic reloading of mystcraft dimensions on server restart
reload-dimensions=true
 
#Set to false to deny a player access to the chunk viewer
allowchunkviewer
{
    DEFAULT=true
    OP=true
}
 
#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
}
 
#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
}

any suggestions? More information needed?

thanks!
 
Either it is really sending a messed up packet (unlikly) or you have more then 1000 tickets from computercraft for loading chunks which will throw that error.
 
there are about 70 turtles. Thats all :/
The server is claiming that every package is wrong. So there must be something in the configs we have overseen. Any suggestions?
 
hum well then something is not right. Do /chunkloaders from ingame and look at the tickets and chunks and look around and see if a world has a high amount and track it the spot.



You also could try deleting all the forcedchunks.dat (after backing them up) and that will cause everyone to have to replace anything that chunkloads.
 
If your using tickthreading it could be as it does modify how chunks unload / load. I think its just a broken turtle somewhere.
 
And this one turtle affects all the others? Thats sad :/

Well, our host crashed the world and now its corrupted so I think the problem kinda solved itself..

Lessons Learned: Is there any config I oversee in the TickThreading file doing the chunk limits or stuff? Or is this all managed by the forgeChunkloading cfg?
Would be nice to know for upcomming worlds.
 
You must log in or register to reply here.
Top Bottom