ink VS dioxus

What does this have to do with Inkle's Ink? Well, Ink is a form of engine-agnostic game data creation. At heart, Ink is a narrative scripting language but because it was conceived as middleware, it can be used by many game development stacks. The primary integration is Unity which supports many platforms on its own but Ink scripts can also be run in the browser, Defold, Godot, Unreal and more. You can write Ink once, test it using Inky or Inklecate and deploy it using your desired framework. I can personally attest to running the same Ink script in the browser with ink.js and in the Defold, Godot and Unity game engines.

That's awesome, thanks!

I am aware of Inform 7, I think it is awesome. A few months ago I made a quick demo using Inklescript[1], which I found simpler and more suitable to my project (a Star Trek adventure). Inform 7 remains something I wish to explore in the future when I need something more complex.

Thanks! ;)

---

[1] https://www.inklestudios.com/ink/

As others have said, Twine is really a great starting point for text or choice-based games. If you'd like to get into the weeds a little more, I'd also shout out Ink, which is incredibly flexible and really fun imo, altho it def requires a bit more coding experience.

On the technology side, you might want to check out Inkle: https://www.inklestudios.com/ink/

Start writing in ink or twine.

Otherwise, Inkle is also quite good. (and people have made players for it in Unreal and Unity, so it's not hard to attach to existing game projects.) I don't think it has the nifty visual flowchart though, if that's a piece you care about.

I really like Ink. The developers made tons of games with it like the Sorcery! series, so it has a good foundation, and it's quite easy to write and organize, more than twine in my opinion.

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...

Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).

Floneum is a graph editor for local AI workflows. It uses llm to run large language models locally, egui, and dioxus for the frontend, and wasmtime for the plugin system. If you are interested in the project, consider joining the discord, or building a plugin for Floneum in rust using WASI