Map packs

Publish a bundle of maps once, and let your customers install it in one click.

Every server the pack matches then shows a Map Packs tab.

The first half of this page is for you. The second half is what your customer does, also covered in Map packs.

Publishing a pack

Open Admin > Map Packs. The page lists every pack that you published.

Creating a pack

1. Click New pack. A panel named New map pack opens below the table.
2. Select the source: URL, Workshop, or Upload.
3. Fill in the fields:

Field	Description	Default
Name	The name that the customer sees, for example dust2 + Iceworld. This field is required.	empty
Egg	The egg that gets this pack. Leave the field on All eggs to give the pack to every server.	All eggs
Description (optional)	A short line under the name on the customer card.	empty
Download URL (URL source)	A direct https:// link to the archive.	empty
Steam Workshop item ID (Workshop source)	The numeric ID of the Workshop item.	empty
Archive (.zip / .tar.gz / .tgz) (Upload source)	The archive file.	none
Install path (relative to server data dir, optional)	The directory inside the server that receives the files, for example cstrike/maps. Leave the field blank to write to the server root.	empty

4. Click Save.

Where a pack can come from

Source	Where the files come from
URL	The node downloads the archive at install time. The panel stores the link only.
Workshop	The node runs SteamCMD at install time. SteamCMD downloads the Workshop item, and the node writes the files into the install path.
Upload	The panel stores the archive. The node fetches it from the panel at install time.

A Workshop pack needs no archive and no link. Give the numeric item ID only. The node reads the Steam app ID from the egg of the server, so the same pack works for every server that uses that egg.

Size limits

• Maximum size: 500 MB.
• Accepted extensions: .zip, .tar, .tar.gz, and .tgz.

URL restrictions

The panel checks the URL host at install time, not when you save the pack. By default the panel accepts these hosts only:

steamcommunity.com, steamusercontent.com, steamcontent.com, github.com, githubusercontent.com, and objects.githubusercontent.com.

If you host archives somewhere else, add that host to the MAP_PACK_ALLOWED_HOSTS setting on the panel. Add the host before you publish the pack.

Your packs

Column	Contents
Name	The pack name, with the description below it.
Source	Upload, Workshop, or URL.
Egg	The egg name, or any for a global pack.
Path	The install path, or / for the server root.
Size	The archive size. This column is blank for URL and Workshop packs.

The newest pack is at the top.

Deleting a pack

Click Delete on the row and confirm. The dialog reads:

This removes the map pack and its files. Servers using it will lose access.

The delete removes the pack record. For an upload it also removes the stored archive. Files that a customer already installed stay on that server.

Deleting an egg also deletes every pack that is scoped to that egg.

Editing a pack

There is no edit action. To change a pack, delete it and create it again.

Installing a pack on a server

Finding the tab

Open the server and look for Map Packs in the sidebar.

The tab appears only when at least one pack applies to that server. A pack applies when it is global, or when its egg matches the egg of the server. One global pack therefore puts the tab on every server in the panel.

The panel caches the pack list for about a minute. After an administrator adds the first pack, the tab can take that long to appear.

The pack cards

Each pack is a card. The card shows:

• The pack name and its description.
• Installs to <path>, or Installs to server root.
• The archive size, when the panel knows it.
• A green Installed mark, or the source name.
• An Install button, or a Reinstall button after a first install.

Installing

Click Install. The install starts at once. There is no confirmation dialog.

The button turns into a spinner. A message reads Installed "<name>" when the install finishes. A large pack can take several minutes with no other progress display.

The server keeps running. Restart it yourself to load the new maps.

WARNING

An install overwrites any file that has the same name in the target directory. The panel takes no backup and there is no undo. Take a manual backup first if you want to keep the current files.

Reinstalling a pack

After a first install, the card shows a green Installed mark and the button reads Reinstall.

Click Reinstall to write the pack files again. Use it after a server reinstall, or after somebody deletes a map file by mistake. A reinstall follows the same rules as a first install, and it overwrites files that have the same name.

Next steps

• Eggs - how to scope a pack to one egg.
• Server Management - the other server tabs.