How to install MuCMS and configure themes on your MU server site

Once the MU Online server is up, the site is the face of the project. A site that looks good, loads fast, and is well organized conveys seriousness and makes a player trust you before even creating an account. MuCMS is one of the most popular content managers among Brazilian and Latin servers precisely because it combines simple installation with a good variety of ready-made themes. In this intermediate-level tutorial, you'll learn to install MuCMS from scratch and, above all, to configure and customize themes: swap the logo, adjust colors, place banners, and adapt the layout without breaking the system's modules.

The logic behind any MU CMS is always the same: a PHP application that reads and writes to the emulator's database tables (accounts, characters, rankings) and presents everything in web pages. What changes between CMSs is ease of use, panel language, and theme availability. MuCMS stands out on that last point, which is why mastering its visual side adds so much value to your project.

Prerequisites

Make sure of these items before starting. Most installation problems come from skipping one of them.

• A MU server already running with the database accessible. If you're still building the base, first see the guide on how to create a MU Online server.
• A web server with PHP (Apache/Nginx/IIS). The required version varies by version of MuCMS.
• A database driver compatible with your emulator's DBMS (usually SQL Server via sqlsrv/PDO).
• Credentials for a low-privilege database user.
• FTP access or access to the web server's filesystem.
• A code editor (VS Code, Sublime) to edit CSS and templates.

> Warning: the folder, file, and table names mentioned below are examples. The real structure varies by version of MuCMS and by emulator. Always confirm in the panel or in your version's documentation.

Step 1: Download MuCMS

Download the MuCMS package from the official source or a trusted author. Avoid unaudited "modified" forum versions, as they are a classic backdoor vector. Unzip it locally and look at the structure, which usually looks like this:

mucms/
├── index.php
├── config/            # site and database configuration
├── system/            # CMS core
├── themes/            # <- this is where themes live
│   ├── default/
│   └── dark/
├── admin/             # admin panel
└── install/           # wizard (delete afterward!)

Notice the themes/ folder: it's the heart of this tutorial. Each subfolder is an independent theme.

Step 2: Upload the files and adjust permissions

Send the content to the web server's public directory via FTP. Adjust the permissions: folders 755, files 644, and write permission only where the CMS needs to write (cache, uploads). Avoid 777, which is an unnecessary security flaw.

# Example on Linux
find /var/www/mucms -type d -exec chmod 755 {} \;
find /var/www/mucms -type f -exec chmod 644 {} \;
chmod -R 775 /var/www/mucms/cache /var/www/mucms/uploads

Step 3: Run the installer

Go to http://yourdomain.com/install/ in the browser. The wizard will ask, in stages (the flow varies by version):

1. Requirements check (PHP, extensions, permissions).
2. Database connection details (host, port, name, user, password).
3. Mapping of the emulator's tables.
4. Creation of the panel administrator.

At the end, the installer writes the configuration file, which looks something like:

<?php
// config/database.php (example — varies by version)
return [
    'host'   => '203.0.113.10',
    'port'   => 1433,
    'dbname' => 'MuOnline',
    'user'   => 'web_mu',
    'pass'   => 'SenhaForte#2024',
    'driver' => 'sqlsrv',
];

Step 4: Delete the installation folder

As with any CMS, delete the install/ folder immediately after finishing. It allows the entire site to be reconfigured, including the database credentials, and leaving it accessible is handing over the server.

rm -rf /var/www/mucms/install/

Step 5: Understand a theme's structure

Now we get to the central part. A MuCMS theme is a folder inside themes/ with a predictable structure (varies by version):

themes/mytheme/
├── theme.json         # metadata: name, author, version
├── css/
│   └── style.css      # colors, fonts, spacing
├── js/
├── images/            # logo, banners, icons
└── templates/         # .php layout files (header, footer, home)

• theme.json identifies the theme in the panel.
• css/style.css controls the entire appearance: colors, typography, layout.
• images/ holds the logo and banners.
• templates/ are the files that mix HTML with CMS calls (ranking, news, login). Editing here requires more care.

Step 6: Activate a theme

In the admin panel (/admin/), go to Appearance/Themes and select the theme you want. Alternatively, some CMSs set the active theme via config:

// config/site.php (example)
$config['active_theme'] = 'mytheme';

Always test the switch in a staging environment before applying it in production, and back up first. A poorly built theme can break modules like ranking and registration.

Step 7: Customize colors and logo

Here is the most common and rewarding work. To change the logo, replace the file in images/ keeping the same name and proportions, or update the path in the header template.

To adjust colors, edit style.css. A healthy pattern is to use CSS variables so you don't hunt down color after color:

/* themes/mytheme/css/style.css */
:root {
  --cor-primaria: #c8102e;   /* MU red */
  --cor-fundo:    #0d0d0f;
  --cor-texto:    #e8e8e8;
  --cor-destaque: #f2b705;   /* gold */
}

body {
  background-color: var(--cor-fundo);
  color: var(--cor-texto);
  font-family: 'Segoe UI', Arial, sans-serif;
}

.btn-registro {
  background-color: var(--cor-primaria);
  color: #fff;
  border-radius: 6px;
  transition: background-color .2s;
}

.btn-registro:hover {
  background-color: var(--cor-destaque);
  color: #000;
}

With variables, changing the site's whole visual identity is a matter of swapping four values at the top of the file.

Step 8: Place banners and highlights

Banners for events, top donation, or boss timers are usually blocks in the home template. To change a banner's image, replace the file in images/ and confirm the path in the template:

<!-- themes/mytheme/templates/home.php (example excerpt) -->
<div class="banner-evento">
  <img src="<?php echo THEME_URL; ?>/images/banner-evento.jpg" alt="Weekend event">
</div>

Always optimize the images (compress the JPG/PNG or use WebP) so the site loads fast. A heavy banner is the most common cause of a slow home page.

Step 9: Adjust responsiveness

A good share of players visit the site from their phone. Confirm the theme is responsive by testing on small screens. If you need to adjust, use media queries in the CSS:

@media (max-width: 768px) {
  .menu-lateral { display: none; }
  .conteudo { width: 100%; padding: 0 12px; }
}

Step 10: Security when using third-party themes

If you download a ready-made theme, review the .php files before uploading. Malicious themes hide shells that grant server access. Look for suspicious functions like eval, base64_decode, system, exec in places that make no sense in a template. When in doubt, don't upload.

Common errors and fixes

Launch checklist

• Game server and database working before the site
• PHP at the version required by your MuCMS build
• Database driver loaded and confirmed
• Dedicated, low-privilege database user
• Files uploaded with correct permissions (no 777)
• Installer completed and install/ folder deleted
• Theme activated and tested in staging before production
• Logo, colors, and banners customized
• Images optimized for fast loading
• Site tested on desktop and mobile
• Ranking, registration, and login modules validated
• Third-party theme .php files reviewed
• Site and database backup scheduled

Installing MuCMS is the easy part; what separates an amateur server from a professional one is care in the theme. Coherent colors, a sharp logo, up-to-date banners, and fast loading convey trust and convert visitors into players. Start with the simple CSS and image customizations, build confidence, and only then touch the templates. And remember: always test in staging, keep a backup, and review any third-party code before putting it live.

Frequently asked questions