What's been in the Wind: Two Projects, One Developer Block

Sometimes the best thing you can do with a stalled project is pause it and let your mind breathe.

Travel to keep your mind off things

I was on a trip. I prefer not to disclose where or when. It's important to take breaks away from your daily routine. Allows you to reflect.

The timing was perfect. I'd just finished the intense debugging rush on my main client project. Happy to see it coming to conclusion. The kind of crunch where you're deep in legacy code, wrestling with functionalities, and the product owner not knowing the rules of his own product or forgetting them.

Teaching him minor debugging through client screenshots. Now we're transitioning from frantic bugfixes to the more methodical world of DevOps: building container images, setting up CI/CD pipelines, making infrastructure decisions. What I've been waiting for, for 2 years now.

It's a different kind of work. Less adrenaline, more architecture. And honestly? It's been a relief.

My Game That Lost Its Wind

I'd been working on a game project for months. Making progress, building systems, solving problems. Searching for fun games, ideas, looking at other people's work for inspiration. Then one day I opened the project file and just... didn't feel it anymore.

No dramatic reason. No major blocker. Just that subtle shift where what was exciting becomes work, and work becomes something you avoid.

So I did something I don't do enough: I paused it.

Not abandoned. Not deleted. Just set aside. Because I had a backlog of projects I'd been meaning to get to, and two of them were starting to feel more urgent than the game I'd lost steam on.

Project One: Constituant: Civic Engagement That Actually Works

This one went from idea to production in a single session. A civic engagement platform where people can vote on real EU and French legislation, see aggregate results, and follow links to the actual legislative texts.

Why it matters: Most people have no idea what their representatives are voting on. Only what main stream media tells them. This makes it visible and participatory, I'd like to eventually have an IA decrypt it so the comman individual can understand what's at play.

What Works

• Real-time voting system (Pour, Contre, Abstention)
• Live vote counts with progress bars
• Direct links to official legislative documents
• Secure admin panel for managing bills
• Mobile-responsive design
• IP-based duplicate vote prevention

What Broke (And Got Fixed)

• French Assembly URLs were 404ing : turns out the legislative period changed (dyn/16 → dyn/17). Switched to using dossier URLs instead of texte URLs because dossiers track the entire legislative process and never expire.
• Files were nested too deep : classic o2switch multi-domain setup issue. Had to configure the domain root correctly.
• Missing .htaccess file : no security headers, no directory protection, no URL rewriting. Created a comprehensive configuration.
• Admin panel edit/delete buttons broken : bill titles with newlines breaking JavaScript. Documented for future fix.

The platform is live. It works. Early testers can use it. And documented everything : 11 comprehensive guides covering deployment, troubleshooting, and French legislative URL structure.

Next steps: Turn it into an association loi 1901, get community involvement, build trust with transparency.

Project Two: DreamLoom : The Furcadia Successor We Deserve

This one's personal. A spiritual successor to Furcadia : that cozy isometric social MMO from the late 90s where players could create their own worlds, roleplay, and just... exist together in creative spaces.

But with modern twists:

• Furcadia + Roll20 + AI art generation ; players write roleplay actions and generate AI art from their descriptions
• Self-hostable shards : communities can run their own servers
• Light RPG mechanics : 1-10 stats, dice rolls, optional combat
• Broad fantasy avatars : not just furry, any fantasy character
• Simple scripting : text-based DreamScript for world creation

What I've Built So Far

• Complete project documentation (GDD, README, CONTRIBUTING)
• Godot 4 client with isometric movement and chat UI
• Rust WebSocket server for real-time communication
• Tilemap system with isometric rendering
• AGPL-3.0 license (keeps it open forever)
• GitHub repo set up and public

The Writer's Block

I've built minigames. Systems work. The foundation is solid. But now I'm stuck.

Not technically stuck : creatively stuck. I know what the game should feel like, but translating that feeling into actual gameplay loops and progression systems? That's where I'm hitting the wall.

The core vision is clear:

"Community over commerce. DreamLoom will never have pay-to-win mechanics, lootboxes, or paywalled gameplay features. The codebase stays open forever, sustained by community contributions, grants, and optional services around the free core."

But the specific game mechanics : how do stats interact? What makes exploration rewarding? How do we balance creative freedom with structured play? : that's the part I'm wrestling with.

The Current Blocker

Right now, DreamLoom has technical blockers too:

• GDScript errors with tilemap constants
• Spritesheet paths need fixing
• Rust won't compile : missing Visual Studio Build Tools

But those are solvable. The harder block is the design one: what makes DreamLoom worth playing beyond nostalgia?

The Pattern I'm Noticing

Both projects started from the same place: frustration with how things currently work. I learned something as well : I want to bring value to the world.

Constituant exists because civic engagement is broken. People don't know what their representatives vote on. There's no easy way to track legislation or signal your preferences.

DreamLoom exists because modern MMOs forgot how to be cozy. Everything's about grinding, monetization, and FOMO. I wanted something that felt like Furcadia did in 2000 : a place to just exist, create, and play without pressure.

Both are reactions to systems that prioritize profit over people.

What's Next

For Constituant: Testing with early users, fixing the admin panel JavaScript bug, updating French Assembly URLs, and starting the process to formalize it as an association.

For DreamLoom: Installing Visual Studio Build Tools, fixing the compile errors, and then... figuring out what the core loop actually is. Maybe that means building a simple prototype and seeing what feels fun. Maybe it means stepping back and playing more isometric MMOs to understand what works.

For the paused game project: Let it breathe. Maybe I'll come back to it with fresh eyes. Maybe I won't. Either way, I'm not forcing it.

The Lesson (Again)

I keep learning this lesson and then forgetting it: You can't force creative work when the wind isn't there.

Sometimes the best move is to pivot to something that has momentum. Let the stalled project rest. Trust that if it's meant to continue, the energy will return.

And in the meantime? Build something else. Ship something. Make progress somewhere.

That's what I'm doing. Two projects, one developer, and a growing suspicion that the blockages aren't technical : they're creative signals telling me to slow down and think harder about what actually matters.

If you're curious about either project, feel free to reach out. Constituant is live and looking for early testers. DreamLoom is open source and looking for contributors who remember what made Furcadia special.