Search the Forums BEFORE making a new post.

How to disable forge's "freezing registries" log?

Posted September 13, 20196 yr

When launching forge, it outputs all entries of all registries:

[22:11:22.233] [Server-Worker-3/DEBUG] [ne.mi.re.GameData/REGISTRIES]: Freezing registries
[22:11:22.236] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry Block Sync: FROZEN -> ACTIVE
[22:11:22.265] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry Fluid Sync: FROZEN -> ACTIVE
[22:11:22.265] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry Item Sync: FROZEN -> ACTIVE
[22:11:22.278] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry Effect Sync: FROZEN -> ACTIVE
[22:11:22.279] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry Biome Sync: FROZEN -> ACTIVE
[22:11:22.280] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry SoundEvent Sync: FROZEN -> ACTIVE
[22:11:22.291] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry Potion Sync: FROZEN -> ACTIVE
[22:11:22.294] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry Enchantment Sync: FROZEN -> ACTIVE
[22:11:22.299] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry EntityType Sync: FROZEN -> ACTIVE
[22:11:22.300] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry TileEntityType Sync: FROZEN -> ACTIVE
[22:11:22.301] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry ParticleType Sync: FROZEN -> ACTIVE
[22:11:22.302] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry ContainerType Sync: FROZEN -> ACTIVE
[22:11:22.303] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry PaintingType Sync: FROZEN -> ACTIVE
[22:11:22.303] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry IRecipeSerializer Sync: FROZEN -> ACTIVE
[22:11:22.304] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry StatType Sync: FROZEN -> ACTIVE
[22:11:22.304] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry VillagerProfession Sync: FROZEN -> ACTIVE
[22:11:22.304] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry PointOfInterestType Sync: FROZEN -> ACTIVE
[22:11:22.304] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry MemoryModuleType Sync: FROZEN -> ACTIVE
[22:11:22.305] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry SensorType Sync: FROZEN -> ACTIVE
[22:11:22.305] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry Schedule Sync: FROZEN -> ACTIVE
[22:11:22.305] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry Activity Sync: FROZEN -> ACTIVE
[22:11:22.306] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry WorldCarver Sync: FROZEN -> ACTIVE
[22:11:22.306] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry SurfaceBuilder Sync: FROZEN -> ACTIVE
[22:11:22.306] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry Feature Sync: FROZEN -> ACTIVE
[22:11:22.308] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry Placement Sync: FROZEN -> ACTIVE
[22:11:22.308] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry BiomeProviderType Sync: FROZEN -> ACTIVE
[22:11:22.308] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry ChunkGeneratorType Sync: FROZEN -> ACTIVE
[22:11:22.309] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry ChunkStatus Sync: FROZEN -> ACTIVE
[22:11:22.309] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry ModDimension Sync: FROZEN -> ACTIVE
[22:11:22.309] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRIES]: Registry DataSerializerEntry Sync: FROZEN -> ACTIVE
[22:11:22.753] [Server-Worker-3/DEBUG] [ne.mi.re.ForgeRegistry/REGISTRYDUMP]: Registry Name: minecraft:block
	Entry: 0, minecraft:air, Block{minecraft:air}
	Entry: 1, minecraft:stone, Block{minecraft:stone}
	Entry: 2, minecraft:granite, Block{minecraft:granite}
	Entry: 3, minecraft:polished_granite, Block{minecraft:polished_granite}
	Entry: 4, minecraft:diorite, Block{minecraft:diorite}
	Entry: 5, minecraft:polished_diorite, Block{minecraft:polished_diorite}
	Entry: 6, minecraft:andesite, Block{minecraft:andesite}
	Entry: 7, minecraft:polished_andesite, Block{minecraft:polished_andesite}
	Entry: 8, minecraft:grass_block, Block{minecraft:grass_block}
	Entry: 9, minecraft:dirt, Block{minecraft:dirt}
	Entry: 10, minecraft:coarse_dirt, Block{minecraft:coarse_dirt}
	Entry: 11, minecraft:podzol, Block{minecraft:podzol}

...and it keeps logging every block, item, biome, etc. entrry.

Is there a way to disable this output in the IDE or in the mod itself? like change the log level or something?

It happens right after assets load, so it makes it harder to debug issues with models and such.

Quote

September 13, 20196 yr

Remove the REGISTRYDUMP log marker from your run configurations in the minecraft > runs section of build.gradle and then re-run the genIntellijRuns or genEclipseRuns task to re-generate the IDE run configurations.

For a less-permanent option, you can edit your IDE's run configurations directly instead.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Quote

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.

Reply to this topic...

https://forums.minecraftforge.net/topic/75991-how-to-disable-forges-freezing-registries-log/

Followers

Go to topic listing

IPS spam blocked by CleanTalk.

Announcements

Cannot find client log entries

hello everyone..!

By AydenPulse · 42 minutes ago42 min
Failed loading villager cartographer registered at cartographer - frozen tick

Allocated 10 Gb of ram. Could try again with more but I read using too much can slow things down as well. Going to try another big modpack and see if i can replicate the problem. It seems like this cartographer problem is kind of popular and doesn't have a solid solution yet, but i suspect its some generation mod since it's a crash that happens when specific chunks are being loaded. so i'll still try to lookout for what mod it could be as i add. i'll report back after testing as you suggested for a bit

By chemba21 · 1 hour ago1 hr
Failed loading villager cartographer registered at cartographer - frozen tick

I have no idea - is enough RAM allocated?
Do other pre-configured modpacks work? Maybe use such a modpack as working base and add new mods one by one

By TileEntity · 2 hours ago2 hr
Minecraft Mod Gradle Build not working

<repository> looks like a placeholder
url "https://maven.minecraftforge.net/<repository>"

By TileEntity · 2 hours ago2 hr
Minecraft Mod Gradle Build not working

The settings.gradle file has been fixed. But, the build.gradle has an error now.
Error:
* Where:
Build file 'C:\Users\csonn\OneDrive\Desktop\fusionlucky\build.gradle' line: 3
* What went wrong:
Plugin [id: 'net.minecraftforge.gradle', version: '6.1.+'] was not found in any of the following sources:
- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Included Builds (No included builds contain this plugin)
- Plugin Repositories (could not resolve plugin artifact 'net.minecraftforge.gradle:net.minecraftforge.gradle.gradle.plugin:6.1.+')
Searched in the following repositories:
Gradle Central Plugin Repository
MinecraftForge
Forge Maven
Forge Maven
Maven Repository for Minecraft Forge. <br/>You should be on:)
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Get more help at https://help.gradle.org.

Build.Gradle File:
plugins { id 'java' id 'net.minecraftforge.gradle' version '6.1.+' } group = 'io.github.csonnic03.fusionlucky' version = '1.0.0' archivesBaseName = 'fusionlucky' java { toolchain { languageVersion = JavaLanguageVersion.of(17) } } repositories { mavenCentral() maven { name "forgeMaven" url "https://maven.minecraftforge.net/<repository>" } } dependencies { minecraft 'net.minecraftforge:forge:1.20.1-47.1.0' } minecraft { mappings channel: 'official', version: '1.20.1' runs { client { workingDirectory project.file('run') } server { workingDirectory project.file('run') } } } tasks.withType(JavaCompile) { options.encoding = 'UTF-8' } jar { manifest { attributes( "Specification-Title": "Fusion Lucky Block", "Specification-Vendor": "example", "Implementation-Title": project.name, "Implementation-Version": project.version, "Implementation-Vendor": "example", "ModLauncher-TargetFMLVersion": "[47,)" ) } }

By Fairygamer03 · 4 hours ago4 hr

TileEntity

Sign In

How to disable forge's "freezing registries" log?

Featured Replies

Join the conversation

Posts

Cannot find client log entries

Failed loading villager cartographer registered at cartographer - frozen tick

Failed loading villager cartographer registered at cartographer - frozen tick

Minecraft Mod Gradle Build not working

Minecraft Mod Gradle Build not working

Topics

Cannot find client log entries

Failed loading villager cartographer registered at cartographer - frozen tick

Minecraft Mod Gradle Build not working

[SOLVED][1.21.8 | Forge 58.0.5] How to cancel InputEvent.MouseScrollingEvent?

Mod not building

Who's Online (See full list)

Important Information

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)