This is the online version of the Hexal documentation.
This page is built from the latest code on GitHub. It may describe newer features that you may not necessarily have, even on the latest Modrinth/CurseForge version!
Entries which are blurred are spoilers. Click to reveal them, but be aware that they may spoil endgame progression. Alternatively, click here to get a version with all spoilers showing.
The past is a foreign country; they do things differently there.
Getting StartedThe practitioners of this art would cast their so-called Hexes by drawing strange patterns in the air with a Staff -- or craft powerful magical items to do the casting for them. How might I do the same?
SlipwaysI have heard tales of some geodes in which glowing portals called slipways lie. These slipways are regularly depicted with glowing sparks surrounding them that bear an incredible resemblance to the wisps that I have heard tell of, which may be a connection to look into.
ItemsI devote this section to the magical and mysterious items I might encounter in my studies.
RelayOften I wish to link together multiple wisps, so that they can share media and information over long distances. However running long chains of wisps to transfer these over great distances is inconvenient, and has great upkeep costs. To resolve this issue I have made Relays. Since they are solid blocks rather than media constructs themselves, they are able to maintain the links without any upkeep costs at all.
Any relays connected together will form a network, with any wisps connected to a relay network able to share media between each other as if they were directly connected. Further, any iota sent to one relay in the network is passed on to every other non-relay connected to the network. Relays have a range of 32 blocks (this means two relays can connect at a distance of 64 blocks). The colour of a network's links can be changed by right clicking on any relay with a colouriser.
Relays have no owner, so if you want your wisps to transfer media with them you must specifically allow them to do so.
Cross-Mod CompatibilityIt appears I have installed some mods Hexcasting interoperates with! I've detailed them here.
Fabric-Only Hexal SpellsTakes a position and a number, and phases the block at that position out for that many seconds. Costs one ten-thousandth of an Amethyst Dust times the square of the time to phase out for.
PatternsA list of all the patterns I've discovered, as well as what they do.
Hexal Basic PatternsAdds a number to the stack which seems to be related to how Nature represents time; If I cast the pattern, then cast the same pattern a second later, the number it adds has increased by 20.
Removes a Living entity from the stack and returns how much breath it has left (i.e., how close it is to drowning).
Removes a Living entity from the stack and returns how much health it has left (i.e., how close it is to dying).
Removes a Living entity from the stack and returns how much armour it has.
Removes a Living entity from the stack and returns how much toughness it has (another property of armour).
Removes a position vector from the stack and returns the light level at that position.
Hexal MathsTakes a number from the stack and computes its factorial, for example inputting 4 would return 4*3*2*1=24.
Takes a list from the stack and computes its running sum, for example inputting [1,2,5] would return [1,3,8].
Takes a list from the stack and computes its running product, for example inputting [1,2,5] would return [1,2,10].
EverbookYour Everbook is a strange space that your broken mind can now reach. There are many yous that seem to share this record, worlds and worlds of progress, beginning again and again. Your Everbook can store patterns paired with iotas like an Akashic Record, though the fragile nature of your mind these days makes it best to route all access to your Everbook through an Akashic Record. Any world that you reach enlightenment in, you will have access to the entries you add to it now.
Takes the position of an Akashic Record, as well as a Pattern as a key, and retrieves the iota at that key from your Everbook, storing it in the given Akashic Record if able.
Takes the position of an Akashic Record, as well as a Pattern as a key, and stores the iota in that record at that key to your Everbook at the same key.
Takes a pattern and removes the entry with that pattern key from your Everbook.
Takes a pattern and marks that entry of your Everbook as a Pattern that when drawn by your hand will be treated as any other of Nature's patterns.
When you draw the key of an Everbook entry that has been marked as a Pattern, if that entry is a list Nature will execute each element of the list as it would with Hermes' Gambit, though it does not use up an evaluation. Attempting to mark an entry as a Pattern if it is non-existent or infinitely recursive will fail.
Everbook EntriesEvery page in this entry displays the pattern key for one of the entries of your Everbook.
SpellsPatterns and actions that perform a magical effect on the world.
Hexal SpellsRemove a location, item entity, or mote from the stack, then either smelt the block at the location or smelt all the items in the item entity or mote.
Costs three quarters of an Amethyst Dust per item smelted (i.e. three quarters of an Amethyst Dust for smelting a block, 6 Amethyst Dust to smelt a stack of 8 items.)
Freezes the block at a block location. For example, turns water into ice, and ice into packed ice. Costs one Amethyst Dust.
Remove a location from the stack, and force the block there to fall as if it were sand or gravel. Costs one and a half Amethyst Dust.
Accepts an item type or mote and a location, and attempts to place a block of that item type at that location. If a mote was passed it will instead place from the record referenced by that mote. Costs an eighth of an Amethyst Dust.
Accepts a location or a list of locations, and either creates a particle at the location, or creates lines of particles between the locations in the list. Costs two thousandths of an Amethyst Dust per location.
WispsI have discovered a way to create constructs from the media itself, visible to others and able to move and act somewhat on their own. They are able to cast hexes in my place, similar to how a Hermes' Gambit evaluates patterns. They do take some of my attention to operate this however, and if too many try and execute at once I will only be able to run some of them, leaving the rest for the next instant.
When they are created I assign them a 'reservoir' of media that they have access to, which is taken from me and used to form the wisp. A wisp uses up part of its reservoir simply existing, and when it evaluates the pattern list it is carrying any costs incurred are removed from its reservoir. All wisps seem to take three Amethyst Dust to summon, in addition to whatever media is used for their reservoir.
This wisp is summoned and launched like an arrow, casting its hex on whatever it hits. The initial stack when it executes will be a reference to itself, then a reference to what it hit.
This could be a block position or an entity reference. The first vector accepted is the location the wisp will be summoned, while the direction of the second is the direction the wisp will be launched, and the second's magnitude seems to affect the wisp's velocity. The cost of the spell increases with the squared magnitude of velocity. The number accepted determines the wisp's reservoir in Amethyst Dust. It loses approximately 3 tenths of an Amethyst Dust of media every second once summoned, and has a range of influence of 4 blocks.
Similar to Summon Projectile Wisp, but with only one vector input for the position to summon the wisp. Cyclic wisps are unmoving once summoned, instead executing their hex up to 20 times each second.
The first time it casts the stack will start with a reference to itself, from which point it will always start with the stack and ravenmind in the state they finished on the last cast. This wisp has a less stable form making it lose significantly more media every second, losing approximately seven tenths of an Amethyst Dust per second once summoned. It has a range of influence of 8 blocks.
Add a reference to the casting wisp to the stack. This must be cast by a wisp; trying to cast it through a staff will fail rather spectacularly.
Add the amount of media in the wisp's reservoir to the stack. This must be cast by a wisp; trying to cast it through a staff will fail rather spectacularly.
Removes a reference to a wisp from the stack, and replaces it with the wisp's contained hex. Must be a wisp you summoned, or a wisp that has allowed transfer with the caster or caster's owner.
Removes a reference to a wisp and an entity from the stack, and returns true if that entity owns that wisp, and false otherwise.
Removes a position vector from the stack; The Cyclic Wisp that executed this pattern will move in a straight line towards that position (colliding with terrain in its path) until it reaches it.
Adds to the stack the position vector that the executing Cyclic Wisp is currently moving towards.
Removes a number from the stack, and sets the executing Cyclic Wisp's maximum speed to that number.
When two wisps are linked together, they transfer media between each other until they are balanced. By default this only happens between wisps with the same owner. This takes an index, and explicitly allows the wisp to exchange media with the linkable at that index.
Correspondingly, this takes an index and disallows the wisp from exchanging media with the linkable at that index.
This takes a wisp that you own and an index, and allows the wisp to exchange media with the linkable at that index.
This takes a wisp that you own and an index, and disallows the wisp from exchanging media with the linkable at that index.
Transform the position on the stack into the wisp at that location (or Null if there isn't one).
Take a position and maximum distance on the stack, and combine them into a list of wisps near the position.
Take a position and maximum distance on the stack, and combine them into a list of non-wisp entities near the position.
Removes an integer from the stack, then delays the wisp's next cast until at least that many twentieth's of a second have passed. This and other triggers like it will halve the wisp's upkeep cost while it isn't casting.
The wisp's next cast will not occur until it has reached the position it is navigating towards.
LinksThese patterns outline a system that I have found for communicating information from one wisp to another, among other things. There are a number of patterns related to creating these links, and a number of patterns related to sending and receiving iotas over a link once it is created. A wisp can have any number of links active, with each costing a negligible amount of media to maintain each twentieth of a second.
The links of a given linkable are indexed by the order they are created, with this number used by a number of patterns. "Linkable" is not its own type, but a shorthand for any type that can be coerced into a linkable (e.g. Entity -> Linkable entities, Vec -> Linkable blocks, ...). Links can span up to double the sum of the two linkable's ranges. To connect linkables over truly vast distances I would do well to look into building some Relays.
Links the caster to the entity removed from the stack, which must be linkable. This costs one Amethyst Shard.
May be evaluated by any casting instrument. Links two entities, which must be linkable. This costs one Amethyst Shard.
Removes the link at the given index from the caster's links. This costs two Amethyst Dust.
Takes two linkables and unlinks them if they are linked. This costs two Amethyst Dust.
Removes an index from the stack, and adds the entity connected to the link at that index to the stack.
Removes an entity from the stack, and adds the index to the link to that entity to the stack (or -1 if the caster isn't linked to that entity).
Removes an iota from the stack, then removes an index from the stack and sends the iota along the link at the given index. This costs one hundredth of an Amethyst Dust.
When something receives an iota along a link it is added to a queue. This pattern adds the first iota in the queue to the stack, removing it from the queue.
Adds to the stack the number of unread iota in the caster's received iota queue.
Similar to Introspection, until drawing a Close Transmit all patterns I draw are sent along the link whose index is at the top of the stack.
When drawn after Open Transmit I stop transmitting drawn patterns. If either Open Transmit or Close Transmit are executed by an intermediary caster such as a wisp, they will mishap.
MotesThis entry deals with bringing items into the media, making them referencable, countable, bringing order to them and to me and to my mind and-. A mediafied item iota (known as a mote) that has been added to the stack references a specific mote record in a Mote Nexus, since without something holding the thought-pattern of the item to this world it will wither away -away like my cognition is flensing-.
Any duplicate of that first mote iota referencing a record references the same record, and any change to one affects them all for they all point to the one and only in the media. Splitting and merging and crafting and trading all affect all affect all-.
A Mote Nexus is limited in some ways, but only some. It can contain 1023 different records, but each record can store items innumerable. I have yet to find any limit, I can merge and merge and merge forever and the record keeps growing and growing and growing...
Villager must be a Apprentice Cartographer or higher
The Mote Nexus is built from the mind of a cartographer endlessly mapping the contents of the Shulker Box that it has been flayed into.
Target a Mote Nexus block in the world and bind yourself to it, meaning all items you mediafy will be added to that nexus' capacity. Targeting any other block will unbind you from your currently bound nexus. Costs 32 Amethyst Dust.
Target a Mote Nexus block in the world and bind to it for the remainder of this cast, temporarily overriding your primary binding. Costs one thousandth of an Amethyst Dust.
Gets all the types of motes contained in the currently bound Mote Nexus.
Gets all the mote records from the currently bound Mote Nexus that match the passed item type or could be combined with the passed mote.
Returns true if the Mote Nexus at the given position contains a mote of the given type, or that would stack with the given mote, and false otherwise.
Convert an item in the world (either an item entity or an item frame) into a mote on your stack. If passed an existing mote instead adds the items from the entity to the mote. Mediafying an item costs a tenth of an Amethyst Dust.
Returns all the items from a mote to the world at the location of your choosing. If passed a number returns at most that many items. Costs a tenth of an Amethyst Dust.
Accepts a mote and returns the number of items in the record referenced by that mote.
Combines two motes into one, merging the mote records they point to. Any pointers to the second mote will become null, any pointers to the first will remain. This can make motes holding many more items than I could carry in a stack naturally!
Returns true if the first mote can be combined with the items in the second argument (which can be a mote, item stack, item entity, or item frame), and false otherwise.
Splits the specified number of items off of the passed mote, creating a new mote pointing to a new mote record.
Move the record referenced by the passed mote to the Mote Nexus at the passed position. This returns a new mote pointing to that record, and invalidates all previous motes pointing to that record.
Takes a mote, list of motes, or list of list of motes. returns a list containing the results of crafting with those items. For example, the input Stone x128 would return [Stone Button x128].
For more complex crafts, inserting nulls to space items properly will be required. A diamond pickaxe for example would require [[Diamond x2, Diamond x2, Diamond x2], [null, Stick x2], [null, Stick x2]] to get [Diamond Pickaxe x2]. Costs a tenth of an Amethyst Dust.
Takes the same input as Craft, except it can take Item Stack Iotas as well as motes. Returns a list of Item Stack Iotas representing what the results of Craft would have been with motes containing those inputs.
Accepts a villager, returns a number representing that villager's seniority and skill at their craft.
Accepts a villager and returns all of the trades that villager is offering. This is a list of lists of lists. Each trade comprises two lists, the cost, and the returned items. The returned items is a list containing the type of item, and the number of items.
The cost is a list of one or two pairs of item and number of items required by the villager for the trade to be accepted. For example, one trade offer could be [[[Emerald, 1]], [Redstone, 1]].
Accepts a villager, a list of motes to trade with to villager, and optionally an int for which of that villager's trades to attempt. (int? above means that you can pass 2 or 3 arguments, the optional 3rd being an int).
If no trade number was passed, it will try each of the villager's trade until finding one that accepts the passed items. If a trade number was passed it will skip straight to using that trade. It will then repeat that trade for as long as it has enough items and the villager is still willing to trade. It will then return the items the villager traded away as a mote to the stack.
The villager will find this trade to be a learnable experience as it would if trading with you directly, and will improve its skills and trade offerings commensurately. Costs a tenth of an Amethyst Dust.
Accepts a mote, and either an entity, or a target block and a normal vector. Uses the item on the entity/block. The mote must either only have one item in it, or the items contained must be extremely simple (no NBT data).
Great SpellsThe spells catalogued here are purported to be of legendary difficulty and power. They seem to have been recorded only sparsely (for good reason, the texts claim). It's probably just the ramblings of extinct traditionalists, though -- a pattern's a pattern.
What could possibly go wrong?
AccelerateCauses the block at the passed vector to perform its normal actions faster in the instant that this spell is cast.
Casting it costs a tenth of an Amethyst Dust, plus a thousandth of an Amethyst Dust for each time it has previously been cast on that block in this hex.
Great Wisp SpellsRemove a wisp from the stack, and disassemble the wisp. The patterns contained are lost, but the media that it contained can be repurposed if this spell is cast by another wisp.
Costs either an Amethyst Shard if the wisp is owned by you or has allowed transfer with the caster or caster's owner, or half again as much media as the consumed wisp contains if the wisp is owned by another and has now allowed it. Repurposing the media is not completely efficient, losing one twentieth of the consumed wisp's reserve in transfer.
Bind one of my wisps closer to me; I may only have one bound wisp at a time, but whichever wisp is bound costs significantly less upkeep and increased range.
Returns my currently bound wisp. A new wisp can only be bound when this returns null. (This is not a great spell, I have simply placed it here for convenience.)
GatesGates are the latest in my long line of experimentation with breaking space to connect distant points and allow instantaneous travel. What gates allow me to do, that none of my previous attempts have succeeded at, is to do it efficiently. There are three varieties of gates that I have learned how to construct, all of which take a large amount of media to burn into reality, but are significantly cheaper to operate afterwards.
Location Anchored Gates are bound to a specific position in the world, and send all that move through them to that position. Entity Anchored Gates are bound to a being that inhabits the world, and send those moving through them to the position of that being (plus an offset, chosen when burning in the gate).
Drifting Gates are not bound at all, and can be used to send entities anywhere, however they lose efficiency as a result, and can only send entities to places that are in my ambit. When a gate is burnt in I will obtain on my stack a reference to that gate. With that gate reference, I can mark entities with that gate, and I can close the gate, which sends all entities marked with that gate to the gate's destination. Note that closing a gate doesn't use it up; once I have acquired a gate iota I can use it in perpetuity.
Adds a new gate iota to the stack. Any copy of this iota will point to the same numbered gate. Costs 32 Charged Amethyst. If passed null, makes a Drifting Gate. If passed a vector, makes a Location Anchored Gate, If passed a vector and an entity, makes an Entity Anchored Gate.
Consumes a gate iota and an entity. Marks that entity to be teleported the next time that gate is closed. Costs one twentieth of an Amethyst Dust.
Consumes a gate iota and an entity. Unmarks that entity so that if it was marked with Gate's Opening it will no longer be teleported the next time that gate is closed.
Consumes a gate iota, returns how many entities are marked by that gate.
Consumes a gate iota and an entity, returns whether that entity is marked by that gate.
Consumes a non-drifing gate iota, or a drifting gate iota and a position. Transports all the entities marked with the passed gate to the stored or given position, as relevant. Costs half an Amethyst Shard, plus an Amethyst Dust per metre transported per entity, if the gate was drifting.