Recent content by Squat500

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

    Bug Fatally Missing Registry Entries

    This is very strange. It did, as you say, swap some of the items. It was relatively limited in most cases. 4/4 clients are connected now, but I lack the knowledge to identify which was the primary culprit. Strangely, restoring a previous backup (world backup first, then a full image of the...
  2. S

    Bug Fatally Missing Registry Entries

    I have bypassed with /ftb confirm to boot up. The mising registry errors continued. I then ran the install once more, and launched from the start script and it appears that something got corrupted during a backup. What is strange is that 2/4 test clients were able to connect. I am digging...
  3. S

    Bug Fatally Missing Registry Entries

    I wonder if this error is associated with the issue, since "Santa" likely is time dependent. [16:01:09] [Server thread/ERROR] [FML]: Unidentified mapping from registry minecraft:villagerprofessions [16:01:09] [Server thread/ERROR] [FML]: stevescarts:santa: 16 [16:01:09] [Server thread/WARN]...
  4. S

    Bug Fatally Missing Registry Entries

    Server side set to 23:30 12/31/19 Client side also set to the same. Restarted server and client. Encountered same error. I pasted the last few lines from the client here. ** Pastebin is pending approval. So here is the overview paste. inal.jar:4.1.9.Final] at...
  5. S

    Bug Fatally Missing Registry Entries

    Server side set to 23:30 12/31/19 Client side also set to the same. Restarted server and client. Encountered same error. I pasted the last few lines from the client here. https://pastebin.com/y4048DUn Server here. https://pastebin.com/8UuuNhLV
  6. S

    Bug Fatally Missing Registry Entries

    I experienced this the moment my server (east coast) ticked midnight 2020. I have clients in several time zones. Similar errors. Folks that WERE running and actively connected to the server during the new year stayed connected. Folks that joined shortly after were greeted with that error...