{"id":1649554,"date":"2026-07-31T07:11:08","date_gmt":"2026-07-31T07:11:08","guid":{"rendered":"http:\/\/vJhmk4ZHyubbcJB56w7yEH"},"modified":"2026-07-31T07:11:08","modified_gmt":"2026-07-31T07:11:08","slug":"godot-natively-supports-coding-in-sumero-akkadian-cuneiform-if-you-needed-another-reason-to-switch-game-engines","status":"publish","type":"post","link":"https:\/\/arcader.org\/news\/godot-natively-supports-coding-in-sumero-akkadian-cuneiform-if-you-needed-another-reason-to-switch-game-engines\/","title":{"rendered":"Godot natively supports coding in Sumero-Akkadian Cuneiform, if you needed another reason to switch game engines"},"content":{"rendered":"
\n

In a time when the dominant game engines are contorting themselves<\/a> to accommodate generative AI toolsets and the resurrected specter of NFTs, game developers who might be investigating alternatives should be asking themselves one very important, yet all too often overlooked question:<\/p>\n

Does this engine’s built-in scripting language allow me to write code using the finest and most adaptive logo-syllabic writing system ever devised in ancient Mesopotamia<\/em><\/p>\n

\n

Daily reminder that GDscript supports the Sumerian clay table alphabet, Akkadian cuneiform of ancient Mesopotamia. This is perfectly valid code you can write in your game:<\/p>\n

\u2014 @steinmakesgames.bsky.social (@steinmakesgames.bsky.social.bsky.social<\/a>) 2026-07-30T22:07:29.801Z<\/a><\/p><\/blockquote>\n

Well, if you’re considering Godot for your next project, the answer is a resounding \ud808\udc2d\ud808\ude3e. As noted on Bluesky<\/a> earlier today by independent game developer SteinMakesGames, GDscript\u2014Godot’s built-in, Python-like scripting language\u2014supports coding in Sumero-Akkadian Cuneiform, a feature that’s sadly neglected by many of the standard languages used in software development.<\/p>\n

“Daily reminder that GDscript supports the Sumerian clay tablet alphabet, Akkadian cuneiform of ancient Mesopotamia,” SteinMakesGames said, before demonstrating with a screenshot of “perfectly valid” cuneiform code that I can definitely read and absolutely understand. I just don’t want to show off. It’s rude.<\/p>\n

By supporting the world’s earliest known writing system, GDscript is the perfect choice for developers who might want to comment their code with a dedication to divine and benevolent Enlil, from whom the princes and kings of the earth derive their authority, or ensure they’re using a language truly capable of conveying their frustrations with being sold a shipment of sub-standard copper ingots<\/a> despite earlier assurances of their quality.<\/p>\n

It’s worth noting that SteinMakesGames\u2014whose strategic mining roguelike Dig Dig Boom<\/a> is set to launch on Steam next year\u2014seems genuinely invested in ensuring that other developers are aware of GDscript’s cuneiform support. While it isn’t exactly a daily reminder as claimed, the developer has previously posted on Reddit<\/a> to give other Godot users a heads-up that they could be coding in Akkadian. Can you imagine? Not knowing you could be coding in Akkadian?<\/p>\n

If you’re wondering why <\/em>GDscript supports cuneiform, it’s because its parser accepts the use of most Unicode Standard Annex #31 characters in identifiers when some languages\u2014like C#\u2014do not. That means, in addition to cuneiform, Godot devs could also be coding with Futhark runes, Egyptian hieroglyphs, and Mycenaean Linear B. And GDscript isn’t alone in that capability: Python, JavaScript ES6+, and Rust let you play Unicode jazz, too.<\/p>\n

As history tells us, It’s nice to have choices\u2014both in writing systems, and in ingot providers.<\/p>\n

\n
<\/div>\n<\/p><\/div>\n