Support & Resources
Find help, tools, and resources for your TinyMUX server
Community Support
Get help from the TinyMUX community and connect with other administrators.
- TinyMUX Wiki - Community documentation and guides
- GitHub Issues - Report bugs and request features
- Discord Community - Real-time chat with other MUSH admins
- Email Support - Direct communication with the development team
Admin Tools
Useful tools for managing and maintaining your TinyMUX server.
- Omega Flatfile Converter - Convert between different MUSH database formats
- Contribution Repository - Community-contributed tools and utilities
- Sandbox Globals Project - Global commands and systems for your game
- Modules Repository - Loadable modules to extend your server
Documentation
Comprehensive guides and reference materials.
- Official Documentation - Complete server documentation
- Javelin's Guide - Useful MUSH administration reference
- Softcode Tutorials - Learn to write effective MUSHcode
- Version History - Detailed changelog for TinyMUX versions
Downloads
Get the latest versions and updates for TinyMUX.
- FTP Repository - All versions and distributions
- GitHub Releases - Latest source code releases
- Patches Guide - How to apply updates and fixes
- Windows Binary Package - Pre-compiled Windows version
Database Conversion & Migration
Converting between different MUSH server platforms or upgrading from older versions of TinyMUX can be straightforward with the right tools and procedure.
Omega Flatfile Converter
The recommended tool for converting between different MUSH server formats. It supports conversion between TinyMUSH 3.x, PennMUSH, RhostMUSH, and TinyMUX formats, and can also help with password resets.
Download OmegaConverting from Other Servers
- Make a complete backup of your existing game
- Generate a flatfile from your current server
- Use the Omega Flatfile Converter to convert the flatfile to TinyMUX format
- Follow the installation instructions in the INSTALL file
- Load the converted flatfile using db_load
- Configure your new TinyMUX server with appropriate settings
- Start your server and test thoroughly before going live
Upgrading from Older TinyMUX Versions
- @shutdown your existing game and make a flatfile backup
- Install TinyMUX 2.13 following the instructions in INSTALL
- Copy your flatfile to the new game/data directory
- Use db_load to convert the flatfile to the binary format
- Copy your mail.db and comsys.db files to the new installation
- Update your configuration file with any new options
- Start your upgraded server
For more detailed instructions, see the CONVERSION document.
Common Support Questions
Use the Omega Flatfile Converter to modify your flatfile and reset the password. First, make a flatfile backup of your database, then run Omega with the appropriate options to change the password. Alternatively, you can use Omega to extract Wizard's encrypted password from a different database where you know the password, and then set it in your current database.
Check that your server is running, your firewall allows connections on your game port, and you've set up port forwarding if you're behind a router. You can test locally with telnet localhost portnumber
. Also verify the port configuration in your .conf file is correct.
Use the Omega Flatfile Converter to convert your flatfile to TinyMUX format. This is generally more reliable than older conversion methods. See the CONVERSION document for detailed instructions.
Reporting Bugs
If you encounter a bug in TinyMUX, please report it to help improve the server for everyone. Follow these steps to submit an effective bug report:
- Verify it's actually a bug and not a configuration issue or intended behavior
- Try to reproduce the issue and document the exact steps that trigger it
- Check if the bug has already been reported on GitHub Issues
- Collect relevant information:
- TinyMUX version
- Operating system and version
- Error messages from the log
- Steps to reproduce the issue
- Any relevant configuration settings
- Submit your bug report to brazilofmux@gmail.com or create a new GitHub issue
For crashes, if possible, include the output of debugging tools:
gdb bin/netmux core (gdb) where (gdb) info locals (gdb) quit