FTB Infinity Custompack Ticking Screen Error

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Bugs for older packs will not be fixed, unless they are critical.
  • 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

Muvanu

New Member
Jul 29, 2019
7
0
0
Title FTB Infinity Custompack Ticking Screen Error

Launcher Type Curse App

Modpack FTB Infinity Evolved

Modpack version 2.6.0

Have you modified the pack? Yes

Link to log file http://paste.feed-the-beast.com/view/b09fa573

Details of the issue I recently customized the FTBIE 2.6.0. pack for my kids and made a server. When I launch the client, I can make a single player world with no issues. I can take that exact same world and copy it and launch it as a server with no errors at all whatsoever in the server console.

However, when I try to connect any of the kid's client's to the server, I receive the attached Ticking Screen error.

I read about an issue with render distance and have the render distance on the clients set at 8. I have the server currently set at 16, but I have tried setting it to 8 and 10 with no change.

Thank you to everyone that has time to help.
 
Last edited by a moderator:

Muvanu

New Member
Jul 29, 2019
7
0
0
One of the kids clients was able to connect to the server one time last night, but it was throwing the attached error when I tried it again this morning.
 

Muvanu

New Member
Jul 29, 2019
7
0
0
For anyone that has been following this thread, I narrowed the issue down to the fact that Roguelike dungeons and Reliquary have newer builds that were incompatible with the modpack I had created. Rolling roguelike dungeons back to 1.4.4 and Reliquary to 1.2 resolved the ticking screen issue.