Cyclops Core guide for All the Mods - Gravitas 2.4 to 2.9

Same as in the All the Mods 10 2.12 guide

Cyclops Core is a mod that ships in the pack as version 1.25.5, built for Minecraft 1.21.1 on NeoForge (file cyclopscore-1.21.1-neoforge-1.25.5-683.jar). It has been in the pack since version 0.32 or earlier, so it's a long-standing part of the mod list.^[1]

Unverified The sources I have don't describe what Cyclops Core does or who it is for, so I'm not guessing about its features here. They also don't show any quests that involve it, and it isn't on the ATM Star path, so there's no progression placement to give you. Check back if more details get added.

Same as in the All the Mods 10 0.50 guide

Cyclops Core is a library mod, and the sources here show no items to craft for it. What its language file does show is some command feedback and a few shared screen labels, so this section covers those instead.^[2]

What you will notice in game

• Config command feedback: the mod has chat messages for setting config values. It replies with "Updated %s to: %s" when a change works, and with "Invalid new value" or "Please define one new value" when it doesn't.^[2]
• If nothing can be changed, the message is "There were no config values found that can be set".^[2]
• Ignite command feedback: the mod has a message for lighting a player on fire, "The player '%s' was lit on fire for %s seconds". If the name is wrong, it says the player '%s' was not found.^[2]
• Screen labels: the mod provides text for an "Information Book" screen, plus "Rewards", "Search" and "Scroll", and the directions Up, Down, Left and Right.^[2]

Unverified The sources here show no recipes, quests or config files for Cyclops Core in this pack, so they do not confirm a first item to craft or a quest to follow for this mod.

Here's the honest picture: the only thing I can confirm about Cyclops Core in this pack is its common config file. That file covers startup and loading behavior. It says nothing about machines, multiblocks, power, fluids or item automation, so this section stays short.^[3]

What the pack's config sets

• core.general.analytics is set to true in the pack. It controls whether an anonymous mod startup analytics request may be sent to the mod's analytics service. core.general.anonymousAnalyticsID holds the anonymous id that service uses.^[3]
• core.general.crashOnInvalidRecipe is false. If you turned it on, the recipe loader would crash when it finds invalid recipes. With the pack's value, it doesn't.^[3]
• core.general.crashOnModCompatCrash is false. If it were true, the mod compatibility loader would crash hard when errors happen in that process.^[3]
• core.general.debug is false. Setting it to true enables a development debug mode, and the config warns that this lowers performance.^[3]
• core.general.versionChecker is true, so the version checker is enabled.^[3]
• general.general.devWorldButton is false. Turning it on adds a main menu button to open a dev world, and shift-clicking it creates a new world.^[3]

Cyclops Core keeps its settings in one file, config/cyclopscore-common.toml. Most of it is housekeeping you can leave alone. These are the options worth knowing about, with the values this pack sets.^[3]

Crash behavior

• core.general.crashOnInvalidRecipe is set to false. The recipe loader will not crash when it finds invalid recipes.^[3]
• core.general.crashOnModCompatCrash is set to false. The mod compatibility loader will not crash hard if errors occur in that process.^[3]

Debugging and menu extras

• core.general.debug is set to false. The file warns that development debug mode results in lower performance, so leave it off unless you are tracking down a problem.^[3]
• general.general.devWorldButton is set to false, so there is no extra main menu button for opening a dev world. If a button is added, shift-click creates a new world.^[3]

Analytics and version checking

• core.general.analytics is set to true. This allows an anonymous mod startup analytics request to be sent to the mod's analytics service.^[3]
• core.general.anonymousAnalyticsID holds the anonymous ID used by the analytics service. You have no reason to edit it.^[3]
• core.general.versionChecker is set to true, so the version checker is enabled.^[3]