DEV Community: Evolved-Tech

Limn Engine Just Got Smarter — Here's What We Added (And Why It Matters)

Evolved-Tech — Mon, 07 Sep 2026 19:08:00 +0000

The question that started it all: "Why do we have to write the same code in every single game?" So we built Limn Engine — a zero-configuration, browser-based 2D game engine that hits 60 FPS on hardware old enough to vote. It got published on SitePoint and ranked #3 among 2D JavaScript game engines, which we now mention in every conversation, including this one.

Today's post is about what's new. And to be crystal clear: all of it is live right now. Not "coming soon," not "in beta," not "works on our machine." You can go use every single feature below today, this minute, before you even finish this sentenc—okay you finished it, go use them.

Fair warning: some of these features exist purely because we got tired of doing something annoying, several times, in a row, forever.

📋 The TL;DR (For Those Who Scroll First, Read Later — No Judgment)

Feature	What It Does	Why You'll Care
🔐 Google OAuth	One-click sign-in via Google, plus email OTP as backup. Powered by Supabase Auth.	No passwords, no forms, no "forgot password" emails haunting your inbox at 3 AM.
🔗 Shareable Code Snippets	Write code in the playground, hit Share, get a unique URL.	Send exact working code to friends instead of dumping 200 lines into Discord like a ransom note.
🔍 Universal Search	Global search overlay — hit ESC or click the icon.	Find docs, API refs, tutorials, and community posts instantly. Even we use it now.
📱 Touch-Friendly Design	Fully responsive interface across desktop, tablet, and phone.	Build your game from the couch. We don't make the rules, we just enable them.
💬 Inbox & Messaging	Built-in messaging system for updates and collaborator chats.	Stay in the loop without alt-tabbing to five other apps.

Status: all shipped. All live. Go bother them.

Now, for those of you who like the director's commentary — here's the full story behind each one.

The Problems That Kept Us Up At Night

Rule one of building Limn Engine: "Common outcomes should be functions." Edge detection, camera math, collision loops — if we typed it twice, it became move.bound(player) or camera.shake(5,5) before we typed it a third time out of spite.

But the engine's infrastructure needed the same intervention. Three problems in particular were staging a nightly protest in our brains:

· Authentication — every game needs users, and building sign-up/login/password-reset from scratch takes weeks we do not have and would rather spend on, frankly, anything else.
· Collaboration — "send us your code" in Discord meant receiving 200 unformatted lines that looked like a ransom note.
· Discovery — finding anything on our own website had become a scavenger hunt with no prize at the end.

So, in the spirit of turning problems into functions, we fixed them. All three. They're live. We already told you that but it bears repeating because we're proud of ourselves.

🔐 Google OAuth: One Click, No Passwords — Live Now

Nobody has ever, in the history of the internet, been excited to "Create an account." You see that button, your soul leaves your body a little, and you close the tab. We know. We've done it to other websites while building the fix for our own.

So Limn Engine now runs on Google OAuth as the primary login method:

· One click, and you're in. No forms, no email verification purgatory, no "forgot password" email arriving at 3 AM to remind you of your own incompetence.
· Instant onboarding — straight to building, zero friction, zero excuses left to procrastinate with.
· We never see your password, mostly because we don't want that responsibility. Google can have it. Google seems more organized than us.

Prefer not to hand Google the keys? We also added email OTP login, because choice is nice and so is not being cornered.

Under the hood, this runs on Supabase Auth, a real production-grade auth system built by people who are much better at this than we are. We know our strengths, and "building auth from scratch" is not one of them. We have games to make.

The takeaway: authentication should never be the reason someone bounces off your engine. Consider that reason eliminated. You're welcome.

🔗 Shareable Code Snippets: Collaboration Without The Crime Scene — Live Now

This one's personal.

Every debugging session in Discord went the same way: "send us your code," followed by 200 lines of unindented JavaScript arriving like evidence at a trial nobody asked for. Our DMs looked less like a support channel and more like a crime scene with syntax errors.

So now the playground has a Share button that generates one clean URL, sendable anywhere — Discord, WhatsApp, Twitter, email, and yes we did consider carrier pigeon and no it did not make the roadmap.

What that gets you:

· Debugging that doesn't require detective work — stuck on a physics bug? Send the link. Your friend sees exactly what you see, and "works on my machine" officially retires.
· A place to flex — nailed a particle effect in 30 seconds? Send the link and let people watch it run live, no copy-paste required.
· A Discord server that's actually readable — no more scrolling past a wall of code to find the one message that matters. Our eyes, and yours, say thank you.

The takeaway: sharing code is now exactly as easy as sharing a meme, which was frankly always the bar.

🔍 Universal Search: Find Anything, Instantly — Live Now

Our website had grown a lot of rooms and forgotten to build any hallways. Docs, API references, tutorials, community posts — all real, all somewhere, none easily findable, including by us. We have genuinely spent 10 minutes hunting for our own documentation, which is a special kind of humbling.

So we built a global search overlay. Hit ESC, or click the icon, type your question, get your answer. No reloads, no menu spelunking.

Searchable: API references, documentation, community threads, game templates, tutorials, and everything else we forgot to list here (which the search bar will also find, conveniently).

It's fast, it's obvious, and it makes Limn Engine feel like a serious tool built by serious people — a costume we are, at this point, fully committed to wearing in public.

📱 Touch-Friendly Design: Build Anywhere — Live Now

Games get played on desktops, tablets, and phones, so it never made sense that you could only build one hunched over a laptop like it's a ritual. We rebuilt the interface to be genuinely touch-responsive, whether you're:

· Skimming docs on a tablet in bed
· Managing your community from your phone on a lunch break
· Poking at your game on whatever screen happens to be nearby

No pinch-to-zoom archaeology, no buttons sized for a smaller species of thumb. Just an interface that works wherever you decided to be productive today, including the couch, which we fully endorse.

💬 Inbox & Messaging: Stay Connected — Live Now

Building alone is fine. Building with people who occasionally message you back is better. So we added a built-in inbox and messaging system for:

· Getting updates and announcements, so "what's new" isn't a mystery
· Talking to collaborators without leaving the platform
· Staying plugged into the wider Limn Engine community

It's a small feature that makes us feel disproportionately like a real company — one with an actual office, not just a room, some laptops, and a shared refusal to give up.

🎮 What's Next?

Currently in the workshop (these ones, unlike everything above, are genuinely not out yet — we'd tell you):

· TypeScript support — for developers who like their errors caught before runtime, understandably
· An NPM package — npm install limn-engine is coming, we promise, for real this time
· More game templates — for when the blank canvas is scarier than the actual coding
· Better physics and particles — because if something explodes in your game, it should look incredible

We're building this for the long haul, and we'd like some company.

🙌 Join The Community

Already here? You're basically family at this point, and we mean that with zero legal obligation attached.

New? Come say hi:

· #beginner-help — no question is too small, we've asked worse
· #showcase — show us your first game, we will cheer, possibly too loudly
· #engine-dev — help build the engine itself, we need every hand we can get
· #performance — help us make this thing run on a toaster, we're only half joking

🏁 Final Thoughts

We started with a Toshiba laptop, 4GB of RAM, and one stubborn question: "Why do we have to write the same code in every single game?"

That question is now a real, live, shipped engine with:

· Zero configuration, because life is complicated enough already
· 60 FPS on low-end hardware, yes, even that one
· Google OAuth, one click, no passwords, no drama
· Shareable code snippets, because copy-paste had its moment and that moment ended
· Universal search, so nobody has to hunt for their own documentation again (looking at us)
· Touch-friendly design, because the couch is a legitimate workstation
· A community that keeps showing up, which is honestly the part we're proudest of

Built by a team that refused to give up, mostly out of stubbornness.

🔗 Links


💬 Discord	discord.gg/kVpSmYWXr
💻 GitHub	github.com/terracodes004
✉️ Support Email	evolvedtech004@gmail.com

Got questions, bugs, or just want to show off what you built? Drop into the Discord or email us — we read everything, we promise, we're not just saying that like a company that doesn't.

Draw your game into existence — the easy and advanced way.

How We Upgraded Our Limn Engine Playground Editor To Support Version 4

Evolved-Tech — Mon, 24 Aug 2026 23:17:17 +0000

Introduction: See What We Built

Every game engine creator dreams of a seamless developer experience. Imagine opening a web-based playground, clicking a version dropdown menu, switching to Version 4, and instantly seeing your game run with brand-new features like built-in particle systems and audio management. Today, we want to walk you through how we updated our custom HTML5 canvas framework editor—Limn Engine—so it dynamically detects and routes Version 4 (epic.js) alongside our older releases.

Step 1: Download Limn Engine

Before writing or running any editor logic, you need to acquire the core engine build:

Go to the official website and download the core engine script file named epic.js.
Keeping this file hosted and accessible allows your playground editor to inject it directly into runtime previews whenever a developer tests their game.

Teaching Style: Understanding How Version Routing Works

Let me explain what this means for our editor architecture. A web-based code playground does not magically know which engine version a developer wants to use; it has to inspect the user interface dynamically. Here's what each part does:

Our editor scans the DOM for any select dropdown elements.
It evaluates their text content for version numbers.
It maps that selection to the correct script file URL.

Let's look at how we implemented this logic.

Breaking Down the Code Line by Line

Before looking at code, here is what we are about to build: a two-part update to our editor's runn() function that checks for Version 4 and maps it to our new asset URL.

1. Updating the Scanner Loop

First, let's examine how we updated the scanner loop to recognize V4:

for (let select of allDropdowns) {
  let text = select.textContent.toUpperCase();
  // Include V4 so the version detector targets it correctly
  if (text.includes('V2') || text.includes('V3') || text.includes('V4') || select.value.toUpperCase().includes('V')) {
    versionDropdown = select;
    break;
  }
}

text.includes('V4'): We added this check so that when the editor reads our UI elements, it officially registers Version 4 as a valid release option instead of skipping it.

2. Updating Script Routing Conditionals

Next, let's look at how we updated the script routing conditionals:

if (versionDropdown) {
  let selectedVersion = versionDropdown.value.toLowerCase();
  if (selectedVersion.includes('v2')) {
    engineScriptFile = "tcjsgame-v2.js";
  } else if (selectedVersion.includes('v3')) {
    engineScriptFile = "tcjsgame-v3.js";
  } else if (selectedVersion.includes('v4')) {
    engineScriptFile = "[https://limn-engine-doc.vercel.app/asset/epic.js](https://limn-engine-doc.vercel.app/asset/epic.js)"; // Points to v4
  }
}

selectedVersion.includes('v4'): When a user selects v4 from the dropdown, this conditional matches the string and targets our newly hosted epic.js file for preview injection. After coding, what we've accomplished is a lightweight, zero-dependency version switcher that connects UI dropdowns directly to our core framework files without requiring a heavy backend server.

Honesty About Our Limitations

While string-matching UI elements is a fast and straightforward way to build a custom code playground, we have to be honest about its trade-offs:

If someone alters our HTML label text or renames option values without updating the script check, version routing can fail.
Larger commercial IDEs use robust configuration objects or package manager manifests instead.

However, for a lightweight, custom-built framework like Limn Engine, string filtering keeps things simple and easy to maintain. We believe in letting developers choose the architecture that best fits their project goals.

What You've Learned

To summarize the key concepts we covered while making these changes:

DOM Traversal: Dynamically scanning page dropdowns using querySelectorAll('select').
String Filtering: Extending conditional logic to recognize the V4 keyword.
Dynamic Script Injection: Mapping user version selections directly to the core epic.js source URL.

Resource Hub

If you want to check out our framework files or connect with our creator community, explore these links:

Documentation & Assets: Visit the Limn Engine Vercel Assets.
Community & Support: Join our Discord server to share feedback and get help.
Source Code: Review updates and templates on GitHub.