UNITAF Future
UNITAF

Caution

This site is a work in progress

This site is finished to different degrees. Feedback is welcome. Please bear in mind that most of what you see, if not everything, is still a work in progress.

Data from the live site is synced here every hour. Anything you do on this site stays here. It is not copied back to the live site until we switch over.

Discord and permissions are linked. Be careful with admin actions. Some of them also change Discord.

UNITAF members during an operation

Operations

Manage loadouts

Slug

operations.loadouts.manage

Positions

3

Add, rename, share, copy and retire loadouts, restore and publish versions directly, choose which roles a faction fields, and own the loadout rules.

Positions

3

Positions that currently hold this permission, and where. It can be granted: Everywhere, or on one platform. To change who holds it you need Grant permissions, and to hold this permission yourself, everywhere or for the same platform, event type or team. Unless marked, each post below holds it: Everywhere.

Settings it owns

8

Holding this permission lets you change these. All settings

  • Edit imported loadouts here

    Until this is on, loadouts copied from the current site are read here and changed there, and each hourly copy brings their changes across. Turn it on when loadouts move to this site; the copy then leaves them alone.

    Key
    operations.loadouts.edit_here
  • Who can propose a change

    Every serving member, as on the current site, or only the positions given the propose permission. Reviewers and loadout managers can always propose.

    Key
    operations.loadouts.proposals_open_to
  • A change needs review before it is published

    When off, a reviewer publishes their own change as they make it. Loadout managers always can.

    Key
    operations.loadouts.require_review
  • Reviewers can approve their own change

    When off and review is needed, someone else has to approve a reviewer's own proposal.

    Key
    operations.loadouts.allow_self_approval
  • Loadouts stop changing before a deployment

    Hours before a deployment starts when only loadout managers can publish a change to its faction's loadouts, so nobody arrives to a different kit. 0 is off.

    Key
    operations.loadouts.lock_hours_before_deployment
  • A loadout this heavy is worth a warning

    Loadouts heavier than this are marked on the faction and the loadout. 0 is off.

    Key
    operations.loadouts.weight_warning_kg
  • Unknown items stop a change being published

    When on, a change carrying an item the equipment catalogue does not know waits until someone names it.

    Key
    operations.loadouts.unresolved_blocks_publish
  • Warn on the ORBAT when a role has no loadout

    The ORBAT tells its leaders which roles have no published loadout in the deployment's faction, or are not fielded by it.

    Key
    operations.loadouts.warn_missing_on_orbat