Project Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Hex Casting 100% 274
Iotaworks
PhLib 100% 1
Sewn Hexes
hexdoc 100% 1

Summary

Language code en_US
Aliased language codes enu, us
English name of the language English (United States)
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 328,284,480
Plural: Default plural 12 translations
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
09/23/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,575 25,474 165,851
Approved 0% 0 0% 0 0% 0
Waiting for review 1% 2 0% 2 0% 58
Translated 100% 1,575 100% 25,474 100% 165,851
Needs editing 0% 0 0% 0 0% 0
Read-only 99% 1,573 99% 25,472 99% 165,793
Failing checks 17% 276 33% 8,543 32% 54,149
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 2,115 changes
SepOctNovDecJanFebMarAprMayJunJulAug

Quick numbers

25,474
Hosted words
1,575
Hosted strings
100%
Translated
13
Contributors
and previous 30 days

Trends of last 30 days

+3%
Hosted words
+100%
+1%
Hosted strings
+100%
—
Translated
+100%
−100%
Contributors
+100%
User avatar Lithyaku

String added
Spellbook
Spellbook
09/09/2026
User avatar pool

Resource updated
Parsing of the “project/iotaworks/src/main/resources/assets/iotaworks/lang/en_us.po” file was enforced. 09/08/2026
User avatar pool

String updated in the repository
Iotaworks
Iotaworks
modmenu.nameTranslation.iotaworks
09/08/2026
User avatar pool

String updated in the repository
A Hex Casting addon for manipulating iotas.
A Hex Casting addon for manipulating iotas.
modmenu.descriptionTranslation.iotaworks
09/08/2026
User avatar pool

String updated in the repository
Etcher's Subpurification
Etcher's Subpurification
hexcasting.action.iotaworks:set_subscript
09/08/2026
User avatar pool

String updated in the repository
Developer's Patchwork Exaltation
Developer's Patchwork Exaltation
hexcasting.action.iotaworks:metatable_abridged
09/08/2026
User avatar pool

String updated in the repository
Patchwork Exaltation
Patchwork Exaltation
hexcasting.action.iotaworks:metatable
09/08/2026
User avatar pool

String updated in the repository
Etcher's Subdistillation
Etcher's Subdistillation
hexcasting.action.iotaworks:get_subscript
09/08/2026
User avatar pool

String updated in the repository
{
"name": "Iota Patching",
"category": "hexcasting:patterns",
"icon": "minecraft:calibrated_sculk_sensor",
"advancement": "hexcasting:root",
"pages": [
"I've discovered a way to create a new type of iota — an abhorrence against Nature of my own doing. This pattern weaves a 'sheath' of _media out of some iota, letting me customize several attributes of the new iota. Though this can make my spells more expressive, this ability is not to be taken lightly — I cannot imagine the mischief others would do with these 'patchwork' iotas.",
"To assemble a patchwork iota, I must provide four source iotas:$(br)$(li)The 'userdata' iota, passed to my overload _Hexes.$(li)The 'display' iota, visible to my eyes.$(li)A color for the iota, as an RGB vector in the 0-1 range.$(li)A pointer to an $(thing)overload map./$",
"Such an 'overload map' is merely a regular $(l:addon/phlib/maps)$(thing)Map/$ iota (mapping patterns to the _Hexes they should be replaced with), but stored within a $(l:properties)$(thing)Property/$. I assume that Nature's reason for boxing like this is to save space: it's likely I'll have many patched iotas all using the same overloads. This also gives me the convenience of updating every instance with merely $(l:properties#hexcellular:set_property)$(action)Schrödinger's Gambit/$, rather than finding and updating them all by hand.",
{
"type": "hexcasting:pattern",
"anchor": "iotaworks:metatable",
"op_id": "iotaworks:metatable",
"input": "iota, iota, vec, property",
"output": "patchwork",
"text": "$(br)Constructs a Patchwork iota from the userdata (iota stored inside), display iota (visible to my eyes), color, and an overload map."
},
{
"type": "patchouli:text",
"flag": "!mod:hexdoc",
"text": "These $(thing)overload maps/$ resemble a technique I've seen before — the concept of redefining patterns on a fundamental level resembles the moon cultists' (little time to explain) $(l:https://www.lua.org/pil/13.html)metatables/$, which allow associating a table with another table to redefine its operations. When my 'metamethods' are invoked, the userdata iota is pushed to the top of the stack. All other information about the patchwork disintegrates: I'll need to recreate it from scratch (maybe I should use a"
},
{
"type": "patchouli:text",
"flag": "!mod:hexdoc",
"text": "'constructor' macro?) if I want to return a new iota of the same type.$(br2)Important note: unlike these 'metatables' I've heard about, patchwork $(o)replaces/$ the behavior of the underlying iota. For example, operators such as <ne,waaw> won't work on two patchwork numbers unless I define it myself. However, I feel uneasy relying on this behavior — Nature will be perfectly happy to change this at any moment."
},
{
"type": "patchouli:text",
"flag": "mod:hexdoc",
"text": "These $(thing)overload maps/$ resemble a technique I've heard of before — the concept of redefining patterns on a fundamental level resembles the moon cultists' (little time to explain) $(l:https://www.lua.org/pil/13.html)metatables/$, which allow associating a table with another table to redefine its operations. When my 'metamethods' are invoked, the userdata iota is pushed to the top of the stack. All other information about the patchwork disintegrates: I'll need to recreate it from scratch (maybe I should use a 'constructor' macro?) if I want to return a new iota of the same type."
},
{
"type": "patchouli:text",
"flag": "mod:hexdoc",
"text": "Important note: unlike these 'metatables' I've heard about, patchwork $(o)replaces/$ the behavior of the underlying iota. For example, operators such as <ne,waaw> won't work on two patchwork numbers unless I define it myself. However, I feel uneasy relying on this behavior — Nature will be perfectly happy to change this at any moment."
}
]
}
{
"name": "Iota Patching",
"category": "hexcasting:patterns",
"icon": "minecraft:calibrated_sculk_sensor",
"advancement": "hexcasting:root",
"pages": [
"I've discovered a way to create a new type of iota — an abhorrence against Nature of my own doing. This pattern weaves a 'sheath' of _media out of some iota, letting me customize several attributes of the new iota. Though this can make my spells more expressive, this ability is not to be taken lightly — I cannot imagine the mischief others would do with these 'patchwork' iotas.",
"To assemble a patchwork iota, I must provide four source iotas:$(br)$(li)The 'userdata' iota, passed to my overload _Hexes.$(li)The 'display' iota, visible to my eyes.$(li)A color for the iota, as an RGB vector in the 0-1 range.$(li)A pointer to an $(thing)overload map./$",
"Such an 'overload map' is merely a regular $(l:addon/phlib/maps)$(thing)Map/$ iota (mapping patterns to the _Hexes they should be replaced with), but stored within a $(l:properties)$(thing)Property/$. I assume that Nature's reason for boxing like this is to save space: it's likely I'll have many patched iotas all using the same overloads. This also gives me the convenience of updating every instance with merely $(l:properties#hexcellular:set_property)$(action)Schrödinger's Gambit/$, rather than finding and updating them all by hand.",
{
"type": "hexcasting:pattern",
"anchor": "iotaworks:metatable",
"op_id": "iotaworks:metatable",
"input": "iota, iota, vec, property",
"output": "patchwork",
"text": "$(br)Constructs a Patchwork iota from the userdata (iota stored inside), display iota (visible to my eyes), color, and an overload map."
},
{
"type": "patchouli:text",
"flag": "!mod:hexdoc",
"text": "These $(thing)overload maps/$ resemble a technique I've seen before — the concept of redefining patterns on a fundamental level resembles the moon cultists' (little time to explain) $(l:https://www.lua.org/pil/13.html)metatables/$, which allow associating a table with another table to redefine its operations. When my 'metamethods' are invoked, the userdata iota is pushed to the top of the stack. All other information about the patchwork disintegrates: I'll need to recreate it from scratch (maybe I should use a"
},
{
"type": "patchouli:text",
"flag": "!mod:hexdoc",
"text": "'constructor' macro?) if I want to return a new iota of the same type.$(br2)Important note: unlike these 'metatables' I've heard about, patchwork $(o)replaces/$ the behavior of the underlying iota. For example, operators such as <ne,waaw> won't work on two patchwork numbers unless I define it myself. However, I feel uneasy relying on this behavior — Nature will be perfectly happy to change this at any moment."
},
{
"type": "patchouli:text",
"flag": "mod:hexdoc",
"text": "These $(thing)overload maps/$ resemble a technique I've heard of before — the concept of redefining patterns on a fundamental level resembles the moon cultists' (little time to explain) $(l:https://www.lua.org/pil/13.html)metatables/$, which allow associating a table with another table to redefine its operations. When my 'metamethods' are invoked, the userdata iota is pushed to the top of the stack. All other information about the patchwork disintegrates: I'll need to recreate it from scratch (maybe I should use a 'constructor' macro?) if I want to return a new iota of the same type."
},
{
"type": "patchouli:text",
"flag": "mod:hexdoc",
"text": "Important note: unlike these 'metatables' I've heard about, patchwork $(o)replaces/$ the behavior of the underlying iota. For example, operators such as <ne,waaw> won't work on two patchwork numbers unless I define it myself. However, I feel uneasy relying on this behavior — Nature will be perfectly happy to change this at any moment."
}
]
}
/assets/hexcasting/patchouli_books/thehexbook/%s/entries/addon/iotaworks/metatables.json
09/08/2026
User avatar None

Resource updated
File “project/iotaworks/src/main/resources/assets/iotaworks/lang/en_us.po” was added. 09/07/2026
Browse all changes for this language