mudFTP facilitates the transfer of text files between a MUD server and a client program through a reliable protocol.
mudFTP is a handy protocol designed to enable efficient transfer of text files between a MUD server and a mudFTP client program seamlessly. This means that you can easily transfer notes, programs, room descriptions, and other text files between your server and client. Additionally, once the file is transferred to the client, it is edited locally with the user's favorite text editor.
To install mudFTP on your server, your server should have a centralized mechanism for editing text entries. Generally, most MERC derivatives have a function called string_append, which takes a char** and controls the input from the user, reallocating the text string whenever required. Installing mudFTP will also require an adequate knowledge of the C programming language, and the MUD server is essential.
Once installed on the server side, mudFTP listens on another port usually six higher than the normal port. For example, if your mud server is on port 4444, your mudFTP port would be on port 4450. Your users can then use the mudFTP client program to connect. The client program identifies itself to the server using the MUD username/password and then waits for a request.
When a user with mudFTP enabled edits a text using the text editing mechanism, mudFTP notices that there is a mudFTP connection and sends the text there, rather than to the regular user screen. The user's mudFTP client reads the text and saves it to a temporary file while spawning an editor. The user edits the file and, when satisfied, exits the editor, which prompts the mudFTP client to send the text back to the server. In turn, the server replaces the text the user was editing with the new text from the client.
The server source code is ported to the following platforms: Diku-like servers (Envy 2.2 with ILAB OLC, Mythran 3.1.6b, ROM 2.4b6 with Ivan's OLC 1.72 (by Jessica Boyd), ROT 1.4 (by Dominic J. Eidson), Circle 3.0 (by George Greer)), and non-Diku servers (LDMUD (by Markus Peter) - should be portable to any LP [New!]). Ports under development are available. If interested in porting to a new server platform, send an email.
mudFTP is portable to your server as long as your server has some central mechanism for editing text strings. The C version of the client code works under various platforms such as Linux (libc5 as well as glibc), any UNIX (untested, but the code is reasonably compatible), Windows 95 and NT (port by Cath Allen), and Windows 98 (untested). Similarly, the Java version of the client works on any Java-capable platform. Developers are welcome to port the client to the Macintosh platform.
In conclusion, mudFTP is a valuable tool for MUD server owners and users to transfer text files efficiently. Although it requires some expertise to set up, once installed, it is an incredibly convenient way to share and edit text files between server and client. Additionally, mudFTP’s compatibility with various platforms ensures that users can enjoy its features on their preferred operating system.
To install mudFTP on your server, your server should have a centralized mechanism for editing text entries. Generally, most MERC derivatives have a function called string_append, which takes a char** and controls the input from the user, reallocating the text string whenever required. Installing mudFTP will also require an adequate knowledge of the C programming language, and the MUD server is essential.
Once installed on the server side, mudFTP listens on another port usually six higher than the normal port. For example, if your mud server is on port 4444, your mudFTP port would be on port 4450. Your users can then use the mudFTP client program to connect. The client program identifies itself to the server using the MUD username/password and then waits for a request.
When a user with mudFTP enabled edits a text using the text editing mechanism, mudFTP notices that there is a mudFTP connection and sends the text there, rather than to the regular user screen. The user's mudFTP client reads the text and saves it to a temporary file while spawning an editor. The user edits the file and, when satisfied, exits the editor, which prompts the mudFTP client to send the text back to the server. In turn, the server replaces the text the user was editing with the new text from the client.
The server source code is ported to the following platforms: Diku-like servers (Envy 2.2 with ILAB OLC, Mythran 3.1.6b, ROM 2.4b6 with Ivan's OLC 1.72 (by Jessica Boyd), ROT 1.4 (by Dominic J. Eidson), Circle 3.0 (by George Greer)), and non-Diku servers (LDMUD (by Markus Peter) - should be portable to any LP [New!]). Ports under development are available. If interested in porting to a new server platform, send an email.
mudFTP is portable to your server as long as your server has some central mechanism for editing text strings. The C version of the client code works under various platforms such as Linux (libc5 as well as glibc), any UNIX (untested, but the code is reasonably compatible), Windows 95 and NT (port by Cath Allen), and Windows 98 (untested). Similarly, the Java version of the client works on any Java-capable platform. Developers are welcome to port the client to the Macintosh platform.
In conclusion, mudFTP is a valuable tool for MUD server owners and users to transfer text files efficiently. Although it requires some expertise to set up, once installed, it is an incredibly convenient way to share and edit text files between server and client. Additionally, mudFTP’s compatibility with various platforms ensures that users can enjoy its features on their preferred operating system.
What's New
Version 2.4: N/A