🎮 I Built an AI Game Master That Runs a Living RPG World (OpenClaw Challenge)

Sreenandhan pp — Thu, 23 Apr 2026 14:28:09 +0000

🚀 What I Built

I built AI Game Master, a web-based, AI-powered text RPG where the story doesn’t just respond to you — it evolves around your actions.

Unlike traditional chat-based games, this system behaves like a living world simulation:

🌍 The world persists across turns
🧠 The AI remembers your decisions
⚖️ Actions have consequences
🔁 The story adapts dynamically

You’re not just playing a story — you’re interacting with an autonomous system that acts as a Dungeon Master.

🤖 How I Used OpenClaw

Instead of building a simple prompt-response app, I implemented an OpenClaw-inspired agent architecture.

🧠 Core Idea

The backend is designed around:

Agent (GameMasterAgent)
Memory (persistent history in MongoDB)
Context (full world + player state)
Autonomous loop (decision-making per turn)

⚙️ Agent Workflow

Every time the player takes an action:

The agent receives:
- Current world state
- Player state
- Recent history
It reasons about consequences
It generates:
- Story progression
- New choices
- Implicit world updates
The backend:
- Updates persistent state
- Stores memory
- Returns structured output

🛠️ Tool System (OpenClaw Concept)

I implemented a tool-like system where the agent can influence:

Inventory changes
Health changes
World events
Location updates

Due to current limitations in Groq’s tool-calling support, I implemented a hybrid approach:

AI suggests changes
Backend validates and applies them

🔁 Autonomous Behavior

The system is designed so the AI:

Doesn’t just respond
Simulates consequences
Maintains continuity
Evolves the world over time

This aligns closely with OpenClaw’s philosophy of agent-driven systems.

🎮 Demo

✨ Gameplay Highlights

Dynamic story generation
Clean separation of story and choices
Persistent world state
Smooth UI with real-time updates

👉 Example flow:

You encounter a fox near a stream…

Choices:

Approach the fox

Follow the stream

Investigate a growl

Retreat

Each choice leads to different long-term consequences.

🔗 Project

story-weaver-ai.onrender.com

🎥 Demo

🧠 What I Learned

This project taught me that building with agents is very different from building with LLMs.

🔑 Key Takeaways

Prompting is not enough — you need structure
Memory is everything in agent systems
State management is the real challenge, not UI
AI becomes much more powerful when it:
- tracks context
- simulates outcomes
- persists decisions

⚠️ Challenges

Groq tool-calling limitations required fallback logic
Ensuring consistent output format (story vs choices)
Preventing hallucinated state updates

💡 Biggest Insight

The shift from “AI that answers” → “AI that acts” is HUGE.

This project helped me understand how agent systems like OpenClaw move us toward autonomous software, not just assistants.

🎉 ClawCon Michigan

I did not attend ClawCon Michigan, but I followed the challenge closely and built this project inspired by the ideas shared in the community.

🔥 Final Thoughts

This was one of the most fun and insightful builds I’ve worked on.

AI Game Master is not just a game — it’s a proof of how agent-based systems can create dynamic, interactive worlds.

If you have ideas to improve it or want to collaborate, feel free to reach out 🙌

I Built a Small Tool to Fix a Small Problem (And That’s Enough for Me)

Sreenandhan pp — Sun, 19 Apr 2026 03:46:52 +0000

My next little SaaS is out. It’s not a big project. Not a startup idea. Not something that will change the world. Just a small tool to solve a small problem.

As a solopreneur, I’ve realized something. Most of my ideas don’t fail because they’re bad. They fail because I overthink them. I try to make everything perfect, add more features, and make it “launch-worthy.” And in the process… I don’t ship.

This time, I did it differently.

The problem was simple. Every time I took a screenshot for a tweet or a demo, it looked… bad. So I’d open design tools, tweak things, and waste time — for something that should take seconds. That small frustration kept repeating. So instead of ignoring it again, I built a small tool for it.

I call it imgly. It takes your screenshot and makes it clean and shareable in seconds. Nothing fancy. No complex features. No overwhelming UI. It also includes a text-behind-image effect to make your visuals stand out. Just something that works.

And honestly, it’s not perfect. There are bugs. The UI can be better. Some things still feel incomplete. But I shipped it anyway.

Because I’m trying to change one thing about myself: Ship small. Learn fast. Move on.

I’m not expecting users. Not expecting revenue. Right now, I’m just testing it. Seeing if anyone finds it useful. Seeing if it solves the problem even a little.

This is something I’m slowly understanding: not every project needs to be big. Not every product needs to succeed. Some projects are just practice, learning, and momentum.

And that’s enough.

If you’re also building something, don’t wait for perfect. Just ship the small thing. You might learn more from that than from planning something big.

This is just another step in my journey. Nothing crazy. Just showing up.

If you’re curious, you can try it here:
https://www.imgly.shipextensions.com/
Would love to hear what you think.

Forem: Sreenandhan pp