Constructing the Daemon Core: Background and Delayed Hexes in Base Hex Casting
Posted: Fri Mar 13, 2026 6:19 pm
Consider this part 1 in a series of posts about Daemon Cores. I will attempt not to yap too much about the details and get down to business.
However, before starting to explain anything, let me explain what a daemon is for those who are not in the know.
A daemon is a background hex that continuously evaluates every a set amount of ticks. This is normally done through the use of Hexcassettes, or wisps and genies. I wished to recreate this using spell circles, and I believe I succeeded.
This is a spell circle that casts a list of Daemons each tick, each with their own local stack, without interfering with one another.
TERMINOLOGY
Materials
The Daemon Core needs to be symmetrical to ensure each impetus reaches the loop at the desired time. Each next impetus starts 1 GAME tick after the other to ensure 20 casts per second.
Instead of pasting each screenshot, I will link to the album showing and describing every step.
https://imgur.com/a/constructing-daemon-core-usz9WDb?
Creating the Magus
The Magus should hold a reference to the item frame holding the Archdaemon list.
Note that I am using consideration embeds here for performance and optimization reasons.
While staring at the item frame:
When saved to a thought knot, it should look like this:
Copy this to three more thought-knots and place them in the item frames on cleric impeti.
Creating Archdaemons
These can be made in many ways, but they all share one thing in common; they MUST end in a consideration. This is necessary to remain on the stack after the first cast of the Magus.
In this post I will only give an example of a basic Archdaemon, one that casts its Daemons each tick while preserving their stack and passing it to the next impetus. My next post will include more such Archdaemons, to fully show the capabilities of the Daemon Core.
Similarly to the Magus, you must be staring at an item frame while doing this. It will contain a focus with the list of your daemons. In my case it will be the first gold block.
This should result in something like the following:
Now, since we're adding it to the Archdaemon list, we should wrap that using Single's Purification, too, and place that on the diamond block.
For this Archdaemon, each daemon has to be saved in the following format:
[stack iota 1, stack iota 2, ..., [hex, Consideration]], as part of the list of daemons.
I made an example hex that summons a greater sentinel at my feet each tick, and went ahead and put it in the list.
Now we want to place this list in the item frame we stared at while creating the 1-tick stack preserving Archdaemon:
And done! If we've built everything correctly, it should be summoning a greater sentinel each tick. Note: this is extremely expensive and in survival would require you to properly fuel the Daemon Core with hoppers, and also only resummon if the player walks too far away to limit costs. This kind of hex should not be attempted without a large media farm.
You can add as many daemons as you can fit in that Daemon list, and the 1-tick Archdaemon will cast all of them in a similar way. Similarly, you can also create as many Archdaemons as you can fit in the Archdaemon list, and give each of them different methods to cast their lists. I will go over some of these methods in a future post. For now, this should be all you need to create a basic Daemon Core of your own.
However, before starting to explain anything, let me explain what a daemon is for those who are not in the know.
A daemon is a background hex that continuously evaluates every a set amount of ticks. This is normally done through the use of Hexcassettes, or wisps and genies. I wished to recreate this using spell circles, and I believe I succeeded.
This is a spell circle that casts a list of Daemons each tick, each with their own local stack, without interfering with one another.
TERMINOLOGY
- Daemon Core - the spell circle structure. Capable of consistently casting a hex once per GAME tick, with synchronization between the impeti. Loads a magus on startup.
- Magus - the controller, this is what initializes the stack for each impetus. Likely shouldn't be changed. It runs every Archdaemon each tick.
- Archdaemon - casts each hex within its Daemon list each tick in some specific way. These are customizable, and you are free to add new ones that implement some new functionality. They are reloaded upon startup of the daemon core.
- Daemon - already gone through this, but this is a hex that is cast in the background once every the specified amount of ticks. These are stored in a list for an Archdaemon to cast.
Materials
- 4 cleric impeti
- 1 empty impetus
- 5 mason directrices
- At least 2 foci
- 4 thought-knots (can replace them with foci)
- ~32 slates
- At least 6 item frames
- 3 repeaters, 2 observers, 2 glass, 2 scaffolding, some solid blocks, buttons and a trapdoor.
The Daemon Core needs to be symmetrical to ensure each impetus reaches the loop at the desired time. Each next impetus starts 1 GAME tick after the other to ensure 20 casts per second.
Instead of pasting each screenshot, I will link to the album showing and describing every step.
https://imgur.com/a/constructing-daemon-core-usz9WDb?
Creating the Magus
The Magus should hold a reference to the item frame holding the Archdaemon list.
Note that I am using consideration embeds here for performance and optimization reasons.
While staring at the item frame:
Code: Select all
Introspection
Consideration Consideration
Bookkeeper's Gambit: -
Chronicler's Purification
Consideration Consideration
Bookkeeper's Gambit: -
Numerical Reflection: 5
Prospector's Gambit
Surgeon's Exaltation
Retrospection
Numerical Reflection: 1
Mind's Reflection
Compass Purification
Mind's Reflection
Alidade's Purification
Scout's Distillation //gets the item frame
Surgeon's Exaltation //embed
Numerical Reflection: 4
Introspection
Consideration Consideration
Bookkeeper's Gambit: -
Jester's Gambit
Thoth's Gambit
Consideration Consideration
Bookkeeper's Gambit: -
Numerical Reflection: 5
Prospector's Gambit
Surgeon's Exaltation
Retrospection
Numerical Reflection: 1
Introspection //this part is changeable if you wish to change the behavior of the Magus
Gemini Decomposition
Integration Distillation
Hermes Gambit
Retrospection
Surgeon's Exaltation
Surgeon's Exaltation
Copy this to three more thought-knots and place them in the item frames on cleric impeti.
Creating Archdaemons
These can be made in many ways, but they all share one thing in common; they MUST end in a consideration. This is necessary to remain on the stack after the first cast of the Magus.
In this post I will only give an example of a basic Archdaemon, one that casts its Daemons each tick while preserving their stack and passing it to the next impetus. My next post will include more such Archdaemons, to fully show the capabilities of the Daemon Core.
Similarly to the Magus, you must be staring at an item frame while doing this. It will contain a focus with the list of your daemons. In my case it will be the first gold block.
Code: Select all
Introspection
Consideration Consideration
Bookkeeper's Gambit: -
Consideration Consideration
Bookkeeper's Gambit: -
Chronicler's Purification
Thoth's Gambit
Consideration Consideration
Bookkeeper's Gambit: -
Jester's Gambit
Chronicler's Gambit
Consideration Consideration
Retrospection
Numerical Reflection: 1
Introspection
Flock's Disintegration
Gemini Decomposition
Integration Distillation
Hermes' Gambit
Flock's Reflection
Flock's Gambit
Retrospection
Surgeon's Exaltation
Mind's Reflection
Compass Purification
Mind's Reflection
Alidade's Purification
Scout's Distillation
Undertaker's Gambit
Numerical Reflection: 3
Jester's Gambit
Surgeon's Exaltation
Numerical Reflection: 7
Rotation
Surgeon's Exaltation
Now, since we're adding it to the Archdaemon list, we should wrap that using Single's Purification, too, and place that on the diamond block.
For this Archdaemon, each daemon has to be saved in the following format:
[stack iota 1, stack iota 2, ..., [hex, Consideration]], as part of the list of daemons.
I made an example hex that summons a greater sentinel at my feet each tick, and went ahead and put it in the list.
Now we want to place this list in the item frame we stared at while creating the 1-tick stack preserving Archdaemon:
And done! If we've built everything correctly, it should be summoning a greater sentinel each tick. Note: this is extremely expensive and in survival would require you to properly fuel the Daemon Core with hoppers, and also only resummon if the player walks too far away to limit costs. This kind of hex should not be attempted without a large media farm.
You can add as many daemons as you can fit in that Daemon list, and the 1-tick Archdaemon will cast all of them in a similar way. Similarly, you can also create as many Archdaemons as you can fit in the Archdaemon list, and give each of them different methods to cast their lists. I will go over some of these methods in a future post. For now, this should be all you need to create a basic Daemon Core of your own.