A client-side Fabric mod that reads the OptiFine formats resource packs use for connected textures, block emissive textures and custom block layers, so those packs work alongside Sodium and Iris. It changes nothing by itself: the effect comes from a pack, including two built-in ones that start switched off.
Continuity is a Fabric mod that lets Minecraft read the connected-texture files resource packs were written for OptiFine. Install it and nothing changes on screen. Add a pack that ships those files and glass walls lose their grid of frames, bookshelves run together and sandstone reads as one surface. It exists for players who want those packs on a Sodium and Iris setup, where OptiFine is not an option.
That dependence on packs is the part most people miss, and it explains most "Continuity does nothing" reports. The mod is an interpreter. The look comes from whatever pack you give it.
OptiFine gave pack authors a long list of extra formats. Continuity implements three of them:
Every other OptiFine pack feature is a separate format that Continuity ignores: custom item textures, custom entity models, random mob textures, custom skies. A pack page that says "requires OptiFine" can mean any mix of those, so check which ones before assuming Continuity alone will do. Visible Ores is a clean example of a pack that needs exactly what Continuity provides: the glow on the ore is emissive, and the single outline around a whole vein is connected textures. New Glowing Ores goes further with its Border edition, which its author says runs on Continuity and not on OptiFine.
Continuity carries two small resource packs inside its JAR. Default Connected Textures adds connected glass, sandstone and bookshelves, similar to what OptiFine ships out of the box. Glass Pane Culling Fix hides the faces between vertically stacked glass panes, so a tall window reads as one sheet rather than a column of framed rectangles.
Neither is switched on for you. The mod registers both as optional packs, so they wait in the Available column of the Resource Packs screen until you move them across. Someone who installs Continuity, loads a vanilla world and sees ordinary glass has done everything right except that one click.
Continuity follows its own specification, a superset of OptiFine's that the developer documents on the project wiki. Unless the wiki says otherwise, a CTM file behaves as it would under OptiFine, which is why most packs work unchanged. The differences are small but real, and they account for the occasional "this looks slightly off":
For a player, a pack authored and tested against OptiFine will usually look the same and occasionally not quite. Where a pack author publishes a Continuity-specific version, prefer it.
Continuity draws its connected textures through the Fabric Rendering API. Sodium replaces the game's renderer, and for years it did not implement that API, so Sodium users needed a bridging mod called Indium, and Indium's original description named Continuity among the mods that needed it. That changed with Sodium 0.6, which implements the API itself, and Indium's page now says it is not needed with those versions and not compatible with them. So the answer depends on your Sodium, not your Continuity. With a current Sodium, leave Indium out. On an older Minecraft version whose newest Sodium predates 0.6, Indium is still the bridge, and the FAQ lists where that line falls.
Iris sits on top without trouble. Shaders change lighting and post-processing, while the choice of texture for a block face is made before any of that. Recent Continuity builds also add their options to Sodium's video settings screen, next to the rest of your graphics settings, as well as behind Mod Menu.
Continuity is written for Fabric. The Forge and NeoForge files on its download pages contain the same Fabric code with extra metadata, and rely on Sinytra Connector and Forgified Fabric API to run it. Each exists for a single older Minecraft release, and the developer has said a native NeoForge version is not planned because the two APIs differ too much. On those loaders a connected-textures problem can come from the translation layer rather than from Continuity, so report it with the versions of all three mods.
Work through these in order. The first two cover most cases, and if the pack itself will not load, fixing texture packs that are not working covers the broader problems.
config/continuity.json.Continuity is one JAR plus Fabric API. The step that decides whether you see anything comes afterwards, in the Resource Packs screen.
Open the Continuity Downloads section on this page and filter it by your exact Minecraft version and loader. Click Download on the matching row and you continue to that file on Modrinth. Alongside it you need:
Several recent files carry "beta" or "test" in their version number but are published on Modrinth's release channel. That is how the developer names them, and they are the current files for those Minecraft versions.
mods folder. On Windows the default is %appdata%\.minecraft\mods. Launchers such as Prism keep a separate folder per instance.Only for Minecraft versions that have a Forge or NeoForge row in the table. Install Sinytra Connector and Forgified Fabric API for that version alongside Continuity, in place of Fabric API. For every other version there is no supported route on those loaders.
Build a small wall of glass with Default Connected Textures enabled. One clear sheet with a frame only around the outside means everything loaded. If the game started but the glass is still gridded, the pack is not enabled or sits below one that overrides glass. If the game refused to start, logs/latest.log names the missing or mismatched mod, usually Fabric API.
Continuity is client-side, so it goes in your own game and never needs to be on the server you join. The mod installation guide covers loaders and the mods folder from scratch, and installing texture packs covers the Resource Packs screen.
No builds match these filters.
It lets Fabric read three resource-pack formats that began in OptiFine: connected textures, emissive textures for blocks, and custom block layers. On its own it changes nothing. The visible effect comes from a resource pack that uses those formats, including the two small packs built into the mod.
Most often no connected-textures pack is enabled. The built-in Default Connected Textures pack stays off until you move it to Selected in the Resource Packs screen, and many third-party packs ship connected textures as a separate add-on. After that, check pack order, Continuity's three toggles, and that Indium matches your Sodium version.
It depends on your Sodium version. Sodium 0.6 and newer implement the Fabric Rendering API that Continuity draws through, so Indium is not needed there and is not compatible with them. That covers Minecraft 1.21 onwards. On Minecraft 1.20.6 and older, the newest Sodium is 0.5 or earlier, and Indium is still what lets Continuity render alongside it. Without Sodium, Fabric API's own renderer handles everything.
Yes, and it is a common pairing, since it restores connected textures on a setup that cannot run OptiFine. Keep all three on builds for the same Minecraft version. Recent Continuity versions add their options to Sodium's video settings screen.
Close, not identical. Continuity implements a superset of OptiFine's format and most packs look the same. It does not override vanilla block models the way OptiFine does for glass panes, it orients textures on rotated blocks differently by default, and it treats mixed horizontal and vertical connections slightly differently.
Only through Sinytra Connector and Forgified Fabric API, and only on the versions that have such a file: Minecraft 1.20.1 on Forge and 1.21.1 on NeoForge. Those files contain the Fabric code with extra metadata. The developer has said a native NeoForge version is not planned.
No. Its emissive support covers block models and item models, while glowing mob textures are handled by Entity Texture Features. Item models also have a gap: Continuity's own release notes flagged emissive item textures as missing from its 1.21.5 port onward, and they were still absent in the 26.1 and 26.2 builds. The code for them is back in the 26.3 build, although that release's notes do not mention it.
Continuity's notes for its 1.21.11 port say vanilla removed the cutout_mipped render type and Continuity no longer recognises it, which may partly break packs that use overlays or custom block layers. If overlays look wrong from that version on, check whether the pack has been updated for your version.
No. Choosing which texture a block face shows happens entirely in your own game, so Continuity has no role on a server and is listed as unsupported there. Join any server as usual. The connected textures exist only on your screen.
A client-side mod by Traben that loads OptiFine-format Custom Entity Models, the packs that reshape and animate mobs. It is what makes Fresh Animations move without OptiFine, and it works as a pair with its texture companion, Entity Texture Features.
Traben's client-side mod that lets resource packs texture mobs the way OptiFine packs do: random and conditional mob variants, glowing emissive layers, blinking eyes and optional player-skin effects. It changes textures only, and custom mob models are the job of its companion mod, Entity Model Features.
Distant Horizons is a client-side Minecraft mod that renders simplified Level-of-Detail terrain far beyond your normal render distance, replacing the fog wall with actual landscape at a fraction of the cost of loading real chunks. It builds that terrain from areas you have explored and caches it per world. Shaders work with it only when the shaderpack itself supports Distant Horizons.