Fado MUD client

The Joystick That Moves Worlds

The first thing you notice is the joystick. It sits at the bottom of the screen, ready to translate physical swipes into text commands. You push it up, and your character walks north. Push it left, and they turn west. The feedback is immediate. No typing required. The joystick is configurable—you can adjust its size, position, and sensitivity. The app even supports multiple joysticks, gestures, and gyroscope tilts. For a text-based game, the controls feel surprisingly physical.

The gesture system works alongside the joystick. You can assign specific commands to swipes, taps, or long presses. A swipe up might send "look," while a double-tap sends "inventory." The gyroscope adds another layer: tilting the device can trigger movement or actions. These features are not just gimmicks. They reduce the friction of typing on a small screen. A player can explore a dungeon, fight monsters, and interact with objects without ever opening the keyboard.

The app's name comes from Portuguese fado music—a genre known for melancholic songs about fate and longing. The irony is not lost. A client for text-based adventures, where every choice shapes a character's destiny, carries a fitting name. The developer, JDA, is based in Mafra, Portugal. The app reflects its origins: thoughtful, understated, and built with a specific community in mind.

How Fado Compares to BlowTorch

BlowTorch is the other major MUD client on Android. It has been around longer and has a loyal following. Users describe it as "easily the best of the Android apps," but note that development has stalled. Fado, by contrast, is actively maintained. The latest version, 1.6.2, was updated in July 2026. That is a significant difference. An active client means bug fixes, new features, and compatibility with modern MUD protocols.

Where BlowTorch focuses on custom buttons and seamless gameplay, Fado emphasizes accessibility and modern protocols. Fado supports GMCP, MSDP, and MCCP_V2—protocols that BlowTorch either lacks or implements poorly. These protocols enable features like mapping, health tracking, and server-side scripting. For players who want a modern MUD experience, Fado is the better choice. For those who prefer a simpler, button-based interface, BlowTorch might still appeal.

The comparison is not just about features. It is about philosophy. BlowTorch feels like a relic from an earlier era of mobile gaming. Fado feels like a tool built for the future. The joystick, the gesture system, the Lua scripting—all of it points to a client that understands how people actually play MUDs on a phone. The developer's active presence on the Iberia MUD project reinforces that commitment.

The Changelog and What It Doesn't Say

The official changelog for version 1.6.2 is one line: "Bug fix." That is it. No details about what was fixed, no list of improvements, no acknowledgment of user-reported issues. The previous version, 1.6.1, was also vague. This lack of transparency is a pattern. The developer does not share detailed patch notes. Users are left to discover changes on their own.

This silence has consequences. Players who encounter problems do not know if their issues have been addressed. The AppRecs review mentions that "scripting doesn't work aliases won't pull from triggers." Is that fixed in 1.6.2? The changelog does not say. Another reviewer notes that "the input requires you to send each command twice." Is that still happening? Without detailed notes, users have to test and guess.

The absence of changelog details is not unique to Fado. Many indie developers skip detailed notes. But for a client that relies on community trust, transparency matters. Players invest time in configuring triggers, aliases, and scripts. They need to know if an update will break their setup. The current approach—a generic "Bug fix"—does not inspire confidence.

The Lua Scripting IDE and Its Limitations

Fado includes a dedicated IDE for Lua scripting. This is a powerful feature. Players can write scripts to automate tasks, respond to events, or create custom interfaces. The IDE provides syntax highlighting, error checking, and a console for testing. It is designed to be accessible, even for players who are not professional programmers.

However, the scripting system has limitations. The AppRecs review notes that "the new version scripting doesn't work aliases won't pull from triggers .call and a bunch." This suggests that the scripting implementation is buggy or incomplete. Users who rely on complex scripts may encounter issues. The lack of detailed documentation exacerbates the problem. The official website provides an overview of features but does not include a scripting reference.

The IDE itself is functional but basic. It does not include features like auto-completion, debugging tools, or library management. For simple scripts, it works fine. For advanced automation, players may need to use external tools or switch to a different client. The potential is there, but the execution falls short.