Skip to content

Mission guidelines

Til edited this page Aug 8, 2026 · 15 revisions

This page contains some guidelines relating to mission making, it is not a complete list.

Folder structure

  • World file structure convention: GlobalConflictsMissions/worlds/AuthorName/MissionName/MissionName.ent
  • Custom prefabs which are only meant to be used by this particular mission should be saved in worlds/AuthorName/MissionName/Prefabs/prefab.et, so together with the world. Prefabs useful to everyone should usually be contributed to GC Units.
  • World naming convention: Mission world names do not include spaces, type or player count, also keep them in PascalCase like e. g. "RoutePierre". Header naming convention: The name of the mission header config file matches the name of the world file, but the mission name specified in the header follows the "TYPE (MIN-MAX) MissionName" format, so for example "COOP (5-13) Gull Bay Guns". Only that last part is mandatory, file names are a recommendation. The mission name in the header can not be longer than 50 characters, else the upload will fail.
  • In the bottom of your mission header, you MUST define "GC Metadata" - this is used to fill info on the website. Explanations can be found when hovering over the attributes.

Content

  • Mission authors should never create overrides, whether to scripts or to prefabs, since they affect everything on the server.
  • Do not use content from mods which are not part of the modpack without approval - otherwise, your mission will likely not be accepted.
  • When changing existing content that was not created by you (often welcomed), please discuss it with the original author.
  • You cannot include newly generated navmesh data (for file size and maintainability reasons), use the TILW_NavmeshRegenComponent instead.

Images

When adding new images (such as preview images for mission headers), you should consider the following:

  • Do not do this unnecessarily. It is okay if you add a special preview image for a special mission, or add one that you will use many times, but you should not add images with every new mission as they consume a lot of space, which increases upload duration.
  • Keep the resolution as low as possible. You do not need a 1080p image as scenario pictures only make up a small portion of the screen (at 1440p, only ~950x600 pixels), and are only displayed for a couple of seconds. Something like 800x400 is enough.
  • For mission preview images, do not delete the original image from the mod, and import a JPG, not a PNG. The original image is required for publishing, and should be a JPG for reduced size.
  • Ensure image width and height are divisible by 4. This is a requirement for DXT compression, without which EDDS file size is going to be significantly larger.
  • Make sure to reimport the image in "To sRGB" colorspace. This is possible in the import settings on the right, and ensures the image is displayed in the correct colorspace ingame - otherwise, its colors will look off (e. g. unnaturally bright).
  • To give a rough order of magnitude, preview images (jpg + edds combined) should usually not be much larger than a couple hundred KB.
  • If the image is commonly useful, like for example for all missions using a certain faction, consider adding it to the public GlobalConflictsMissions/UI/Textures/MissionLoadingScreens/ folder instead.

Briefing

Briefings should include the following information (this is not a complete list, obviously):

  • Overview description that is visible before slotting and summarizes what the mission is about, if that is not obvious
  • Briefing, visible in the briefing phase - e. g. five paragraph order, but following this format is not mandatory
  • The mission notes should contain a summary of end conditions, setup timer duration and other relevant information

Workshop Terms

All content (this also applies to GC Units) is uploaded to the Arma Reforger Workshop, which is subject to the Workshop Terms and additional moderation policy not directly mentioned in the TOS. Any content you create has to comply with these rules, otherwise we risk getting in trouble with BI.

Some of these rules are:

  • Do not upload content that infringes on commonly enforced copyright (e. g. don't upload license-restricted music or ripped assets)
  • Do not upload obscene, offensive, sexual, racist or otherwise clearly objectionable content.
  • Do not actively depict things like acts of terrorism (a military fighting members of a terror group is fine, but not e. g. a mission where one faction commits an actual terror attack and actively murders civilians etc.)
  • Avoid directly depicting the most extreme real-world groups like ISIS or the SS. You can take inspiration (e. g. unspecified, generic or fictional faction inspired by the real one) but there should not be any direct depiction or mentioning of the real group.
  • Do not upload banned logos / insignia, like e. g. a swastika or IS flag.
  • No direct depiction of currently ongoing real-life conflicts (e. g. no Russia-Ukraine), though taking inspiration is fine (e. g. Russia vs. modern day CDF)

When in doubt, you can ask in the ARMA discords #workshop_admin channel.

Clone this wiki locally