[bc-dev.net]

FMud is a simple web based Flash mud client.

http://bc-dev.net/projects/fmud

[Kepo]

Very cool. I just checked out the demo and it was great even though it's only the first release version. I hope you'll continue to develop it because I'll definitely be using it.

[kodath]

Ooh, nice. If I would own a mud, I'd definately be interested.

[tyme]

Very awesome. I will probably wait for the next release and deploy it on our MUD's website. This seems so much better than the Java clients I've used so far.

-Duren

[bc-dev.net]

FMud version 0.2 released | bc-dev.net

This version is just a small update to include support for ANSI grey (black) colour.

Bugs, comments, feedback or suggestions to fmud@bc-dev.net

[Threshold]

Wow. That is GREAT WORK.

Is this an open source project?

[Threshold]

Limitations: The security sandbox used by the Adobe Flash player means that FMud can only be used to connect to a mud running on the same domain as the FMud.swf file itself. However this restriction does not apply if the domain running the mud has a crossdomain.xml file allowing connections from the domain hosting the FMud.swf binary.

Could you explain how one uses the crossdomain.xml file (or point me in the direction of a web page/site) so the flash client can be located on a web host and connect to a mud that is on a different machine?

[Threshold]

Are you interested in bug reports or anything of that nature?

If so, what method of reporting do you prefer?

This is a very cool project, with potentially huge benefits to all muds.

[bc-dev.net]

I am going to wait until I have a stable version before I release the source.

As regards to the crossdomain.xml file, unfortunately that is now obsolete with the latest version of Flash Player. I hadn't realised Adobe changed the security model in the latest version and forgot to upgrade. I've posted about it on my site and updated the download package with the necessary files and instructions.

Security changes in Flash Player 9.0.124.0 | bc-dev.net

That post has more detail as well as links to the Adobe documentation. The essential differences are that a socket policy file is now compulsory, even for apps connecting to servers on the same domain, and this policy file has to be served on either port 843 or the port the mud server is running on.

I am happy to get feedback either as comments on the website or via email if you prefer.

[bc-dev.net]

FMud version 0.3 released | bc-dev.net

Bright versions of ansi colours are now displayed correctly and fully configurable, and I've also improved the parsing so most of the colour bleed type bugs should be gone.

I'd also be interested in hearing what other features people would like to see in FMud, bearing in mind that it's supposed to be a basic generic client. There are a lot of things you can do with flash in terms of custom windows, buttons, gauges etc., but most of these would be game specific.

Bugs, comments, feedback or suggestions to fmud@bc-dev.net

[Kylotan]

I'd love to use this, but since I can't use port 843 on a shared host, it would presumably involve hacking in HTTP support into the MUD's connection code, which looks like too much work.

[bc-dev.net]

Originally Posted by Kylotan I'd love to use this, but since I can't use port 843 on a shared host, it would presumably involve hacking in HTTP support into the MUD's connection code, which looks like too much work.

You could try approaching your host and asking them to serve a master socket policy file for all their hosted games on port 843. It shouldn't be too difficult for them to setup - the adobe site has several premade scripts which can be used to serve the file.

[bc-dev.net]

FMud version 0.4 released | bc-dev.net

I've added a split screen scrollback mode and command echo colour is now configurable under settings. I've also added support for password hiding which should work with standard server implementations of ECHO.

I am also able to offer game specific custom versions of the client, please contact me for details.

FMud Customisation | bc-dev.net

[scandum]

Linux VT100 support would be nice. It's documented in 'man console_codes' - particularly cursor handling and scrolling region handling.

[bc-dev.net]

The major change this version is a rewrite of the way the display is handled. This should dramatically reduce the memory usage of the client, particularly after extended use.

Full release notes and download link:

FMud version 0.5 released | bc-dev.net

[bc-dev.net]

Version 0.6

Released on 15th October 2008.

1. Removed extra spacing from between lines in the output window.
2. Settings are stored locally between sessions in a “Flash cookie”.
3. You can now set the dimensions of FMud in the embedding page.
4. Added ability to set default font, font size and window title.
5. Updated README and FMud.html files.

Please see the README for information on the new parameters that need to be set in the html page. If you drop this release into your existing html page it will NOT work correctly.

FMud version 0.6 released | bc-dev.net

FMud Downloads | bc-dev.net

[Orrin]

Version 0.7

Released on 7th November 2008.
1. Fixed major bug when using FMud with Linux.
2. Removed display_height parameter. The dimensions of FMud are now calculated automatically from the height and width set in the embedding page.
3. Added policy_port parameter. This allows you to specify the port where the socket policy file is served. However, this file will be ignored if there is a master socket policy file on port 843.
4. Added support for aliases, triggers, macros and scripting with javascript. See this post for details.
5. A log of the output window can be saved in plain text or HTML format.
6. Updated README and FMud.html files.
Saving and loading features require Flash player version 10.


FMud version 0.7 released | bc-dev.net