Tesana Rebuilds Game Stack Around Three.js

This is a pragmatic infrastructure pivot that makes prompt-driven game iteration far more viable, though Three.js shifts more engine responsibility onto Tesana itself.

• –Eliminating Godot project files and export steps should reduce build failures and shorten feedback loops.
• –Standard TypeScript, Vite, and Three.js output makes games easier to inspect, edit, export, and run across browsers.
• –The change strengthens Tesana’s no-code pitch: creators can iterate on playable games in minutes instead of waiting an hour.
• –Three.js is a rendering library, not a complete game engine, so physics, tooling, multiplayer, and production-grade workflows remain Tesana’s burden.
• –Browser-native delivery lowers friction for sharing and publishing, but generated-game quality still depends heavily on prompt specificity and iterative refinement.