mushcode | RhostMUSH meant to facilitate

Obtain a SQL Database, Username, and Password. If you're on shared hosting, your provider should be able to give these to you.
Run the Schema.sql file from this repository. The easiest way to do this would be putting it in your shell account, browsing to the file, and then typing mysql -u <username> -p <database> < Schema.sql replacing the appropriate fields.
For PennMUSH, edit your mush.cnf so that the sql_* entries are appropriate. Note that MariaDB is counted as MySQL. Just use MySQL style if you're using MariaDB. For RhostMUSH, the file you want is game/rhost_mysql.conf
This readme assumes you at least know the basics of what you're doing by installing softcode and running a game, have a host, know how to get the game running and back it up, edit its files, etc. If you don't, I'd suggest checking out these fine people over at MUS*H, PennMUSH's development/social hangout establishment, available at: http://mush.pennmush.org/ - most coders there could easily get you going in a flash.
Examine your mush.cnf, make sure it has the following: Event Handler and Ancestors will be handled by the #1 Startup - leave these alone. function_invocation_limit 100000 queue_entry_cpu_time 4500 null_eq_zero yes pueblo yes Under the help section, comment out ahelp, anews, and news. max_named_qregs 250
Recommendations in mush.cnf: These are not NECESSARY, but are nice to have. mud_name - set it to something short but respectable, it'll be showing up in my code a lot! Uncomment all the dump_* messages and then clear dump_complete - this'll get rid of that annoying 'GAME: Save Complete.' Instead of using the built-in txt files, create in-game objects and put the displays there? It'll protect them from Git updates and lets you use ANSI and softcode displays! player_name_spaces yes page_aliases yes Under Flags section: You may also want to include ANSI and COLOR256 as a default but some clients might barf at this.
In your restart file, uncomment and ensure your LANG=en_US to enable the expanded charset. This is required because many SQL queries utilize unusual characters as delimiters. Some server OSes might need the ISO version of en_US specified, typically: LANG=en_US.ISO-8859-1
Logon to your code-WIZARD character who will own the code. Run the CORE 01 file from PennMUSH folder to create the Core Code Parent.
Next, logon to #1 and run CORE 02.
Return to your WIZARD character and run CORE 03, CORE 04, and CORE 05.
@shutdown/reboot to make sure all of the STARTUPS are working.
At this point, you can choose to install whatever you want.
Use +gameconfig to configure all relevant settings as appropriate to your game.
Have fun!
Be sure you are saving the .conf files with UNIX linebreaks if you're on Windows! I recommend notepad++ for the job. netrhost.conf options: A) includenest 15 B) includecount 50.
This readme assumes you at least know the basics of what you're doing by installing softcode and running a game, have a host, know how to get the game running and back it up, edit its files, etc. If you don't, I'd suggest checking out these fine people over at MUS*H, PennMUSH's development/social hangout establishment, available at: http://mush.pennmush.org/ - most coders there could easily get you going in a flash. Even if you're using RhostMUSH.
Logon to your Immortal character who will own the code. Run the CORE 01 file to create the Core Code Parent.
Run CORE 02. Unlike Penn this will be run off the same character, not #1.
Run CORE 03, CORE 04, and CORE 05
@reboot to make sure all of the STARTUPS are working.
At this point, you can choose to install whatever you want. HOWEVER, do note that the helpfiles for each system are included in the system's file. If you want to use my Help System, install it FIRST. This will ensure the helpfiles are entered as the systems are installed.
Use +gameconfig to configure all relevant settings as appropriate to your game.
Have fun!