Windows .exe Chunk Loader Crashing (Ultimate 1.1.0)

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

AshtenD

New Member
Jul 29, 2019
50
0
0
Hey guys! I need some help.

This has been happening since 1.0.2 and I just assumed it was a bug that would be fixed in the new update. Well... It hasn't.

Whenever I right click on a chunk loader, it crashes me and throws an http://pastebin.com/5hnLR9M1 No Such method error. It seems to be an error with giving me the value of the radius or the total chunks loaded error. Anyone also have this issue? This is a fresh install of 1.1.0.
 

Tjezee

New Member
Jul 29, 2019
24
0
0
I have the exact same problem, I put down a chunkloader in 1.0.2 and can't right-click it in 1.1.0 with the same No Such method error. Then I went back to 1.0.2 and it works again.
 

AshtenD

New Member
Jul 29, 2019
50
0
0
Unfortunately, the problem still persists in 1.0.2 for me. :/ I wonder what is going on.
 

Medwise

New Member
Jul 29, 2019
7
0
0
I get the same crash. Removed chickenchunks and all chunkloaders. server crashes with forgechunkloader error. deleted forcedchunks.bat still crashes server. think ill go back to 1.02. Tried to go back to client 1.02 I get some retarded secretrooms mod error. Copied the old version of secretrooms mod from my saved 1.01 folder fixed it. Tells me that the FTB launcher is broken for regressing your client, NICE. So Looks like FTB team needs to actually test their modpack before they release it OR call it a BETA.
 

AshtenD

New Member
Jul 29, 2019
50
0
0
I get the same crash. Removed chickenchunks and all chunkloaders. server crashes with forgechunkloader error. deleted forcedchunks.bat still crashes server. think ill go back to 1.02. Tried to go back to client 1.02 I get some retarded secretrooms mod error. Copied the old version of secretrooms mod from my saved 1.01 folder fixed it. Tells me that the FTB launcher is broken for regressing your client, NICE. So Looks like FTB team needs to actually test their modpack before they release it OR call it a BETA.
To be fair. 1.0.2 and 1.1.0 ARE BETAS. It is the reason they are not listed as recommended. People who play on them are at risk for facing these bugs because they are not perfect. So they are in the process of testing.
 
  • Like
Reactions: Ashzification

Tjezee

New Member
Jul 29, 2019
24
0
0
OR call it a BETA.
They can slap ' beta ' onto anything because beta pretty much means its a ' work in progress ', which in turn means it can still have bugs. Its why people test these beta's to find them and fix them.

Go to Chickenbones' forum thread and download the latest MC1.4.7 version of ChickenChunks. I was having the same exact crash issue, but that fixed it.
This fixed it for me, thanks for sharing.
 

Nerixel

New Member
Jul 29, 2019
1,239
0
0
Yep, from what I can tell that's a bug in the actual Ender Storage mod, I could only fix it by disabling Ender Storage. Updating apparently works, which means I can start using ender chests again :D
 

Moasseman

New Member
Jul 29, 2019
1,679
-2
1
I have the latest version of chickenchunks for 1.4.7 (ChickenChunks 1.3.1.1) but the Chunkloaders still make the server go bat**** crazy, wat do <.>

E: Nvm, I'm dumb
 

Ashzification

New Member
Jul 29, 2019
7,425
1
0
So Looks like FTB team needs to actually test their modpack before they release it OR call it a BETA.

"Release" is when the development builds become the Recommended.
The dev builds were put on the launcher for a few reasons that I know of: to test issues that might occur with the launcher (ie. download issues), and to satiate the demanding public.

As the OP posted, if you aren't using the recommended build, then you are using the packs at your own risk. That's common sense.
 

Medwise

New Member
Jul 29, 2019
7
0
0
My apologies, I did not realize that the 1.0x releases were beta, I was frustrated with the attempt to use the 1.1.0 release. Thanks for the help.
 

RoloisRight

New Member
Jul 29, 2019
39
0
0
In one of the silent updates to 1.0.2, ChickenChunks was updated from 1.3.1.1 to 1.3.1.2.
In 1.1.0, ChickenChunks is back down to 1.3.1.1.
I don't know if this might've been related to your problem, but if anyone else runs into it, they can try updating their ChickenChunks back to 1.3.1.2 and see if that fixes it.
 
Status
Not open for further replies.