Baconbomb den 2 juli 2026 kl. 18.27

2026-07-02T18:27:47Z

← Äldre version		Versionen från 2 juli 2026 kl. 18.27
Rad 666:		Rad 666:


	= Registering for a Master Meet =		== Registering for a Master Meet ==

	[[File:Mastermmetregistration.png\|thumb\|caption]]Master Meet registration form showing transport fields		[[File:Mastermmetregistration.png\|thumb\|caption]]Master Meet registration form showing transport fields
Rad 672:		Rad 672:
	When registering for a Master Meet, you can provide attendance and transport information. This helps the organizers plan travel, pickups, available seats, and arrival times.		When registering for a Master Meet, you can provide attendance and transport information. This helps the organizers plan travel, pickups, available seats, and arrival times.

	== Actions ==		=== Actions ===

	=== Edit event ===		==== Edit event ====

	Opens the event edit page.		Opens the event edit page.
Rad 680:		Rad 680:
	This is only available to users who have permission to edit the event.		This is only available to users who have permission to edit the event.

	=== Register ===		==== Register ====

	Opens or shows the registration form for the event.		Opens or shows the registration form for the event.
Rad 686:		Rad 686:
	Use this to sign up and provide your participation details.		Use this to sign up and provide your participation details.

	== Registration fields ==		=== Registration fields ===

	=== Transport type ===		==== Transport type ====

	Select or describe how you plan to travel to the event.		Select or describe how you plan to travel to the event.
Rad 694:		Rad 694:
	Examples: driving, flying, train, passenger, or no transport information yet.		Examples: driving, flying, train, passenger, or no transport information yet.

	=== Departure location ===		==== Departure location ====

	Enter where you are travelling from.		Enter where you are travelling from.
Rad 700:		Rad 700:
	This can be a city, address, airport, or other relevant departure point.		This can be a city, address, airport, or other relevant departure point.

	=== Arrival location ===		==== Arrival location ====

	Only used if you are flying.		Only used if you are flying.
Rad 708:		Rad 708:
	Examples: GOT, ARN, CPH, or Copenhagen Airport.		Examples: GOT, ARN, CPH, or Copenhagen Airport.

	=== Seats available ===		==== Seats available ====

	Only used if you are driving.		Only used if you are driving.
Rad 716:		Rad 716:
	Leave empty if you are not driving or do not have seats available.		Leave empty if you are not driving or do not have seats available.

	=== Arrival time ===		==== Arrival time ====

	Enter when you expect to arrive.		Enter when you expect to arrive.
Rad 722:		Rad 722:
	This helps organizers coordinate transport, pickups, and planning around the event start.		This helps organizers coordinate transport, pickups, and planning around the event start.

	=== Comment ===		==== Comment ====

	Optional extra information.		Optional extra information.
Rad 728:		Rad 728:
	Use this for notes such as special travel details, pickup needs, delayed arrival, shared transport plans, or anything the organizers should know.		Use this for notes such as special travel details, pickup needs, delayed arrival, shared transport plans, or anything the organizers should know.

	=== Save registration ===		==== Save registration ====

	Saves your registration and transport information.		Saves your registration and transport information.

	After saving, your registration is added to the event and can be used by the organizers for planning.		After saving, your registration is added to the event and can be used by the organizers for planning.
	~~```~~

Baconbomb: Skapade sidan med 'Texten är strukturerad från din uppladdade sammanställning. = Event creation guide = This guide explains how to create and manage events on the Master Arms website. The event system supports different event types depending on what kind of activity is being planned. caption Create new event page showing the available event types == Choosing an event type == When creating a new event, first choose which type of event you w...'

2026-07-02T17:21:03Z

Skapade sidan med 'Texten är strukturerad från din uppladdade sammanställning. = Event creation guide = This guide explains how to create and manage events on the Master Arms website. The event system supports different event types depending on what kind of activity is being planned. thumb|caption Create new event page showing the available event types == Choosing an event type == When creating a new event, first choose which type of event you w...'

Ny sida

Texten är strukturerad från din uppladdade sammanställning.

= Event creation guide =

This guide explains how to create and manage events on the Master Arms website.

The event system supports different event types depending on what kind of activity is being planned.

[[File:Create new event page.png|thumb|caption]]
Create new event page showing the available event types

== Choosing an event type ==

When creating a new event, first choose which type of event you want to create. Each event type is designed for a different purpose.

=== Custom ===

A Custom event is a free-form event with basic event information.

Use this for events that do not need structured flight generation, module preferences, or detailed lineup handling. The organizer writes the title, date, organizer information, and briefing manually.

If a template is available, it can be selected from the template dropdown to pre-fill parts of the event. This is useful when creating recurring or similar events.

=== THT ===

A THT event is a structured mission event for Tally Ho Thursday.

Use this for full mission events where flights, modules, registration, lineup, mission rules, packages, waypoints, and briefing need to be handled in a structured way.

=== Training ===

A Training event is used for regular training sessions.

It is simpler than a THT event and does not use the full mission lineup system. Participants can register and select modules, but the event is mainly focused on training information rather than mission planning.

=== Master Meet ===

A Master Meet event is used for physical meetups and real-life gatherings.

It is focused on attendance, location, practical information, transport planning, and arrival details rather than aircraft modules or mission structure.

= Custom event =

[[File:Custom event.png|thumb|caption]]Create custom event page

A Custom event is a free-form event type. Use it when the event does not need structured flights, module selection, or a full THT-style lineup.

== Fields ==

=== Title ===

The name of the event.

This is shown in the event list, event page, and anywhere the event is referenced.

=== Header image ===

Optional image shown at the top of the event page.

Recommended size is 1920 x 1080 px in 16:9 format. Larger images are automatically scaled down.

=== Start time ===

The date and time when the event starts.

This is the main event time shown to users.

=== Signup deadline ===

The latest time users can sign up for the event.

Leave this empty if the signup deadline should be the same as the start time.

=== Extra event editors ===

Additional users who are allowed to edit the event.

Use this if someone other than the creator needs permission to update the event information later.

Hold Ctrl on Windows or Cmd on Mac to select multiple users.

=== Theatre ===

The map or theatre where the event takes place.

Examples: Syria, Caucasus, Persian Gulf, or another relevant theatre.

=== Max participants ===

The maximum number of people who can sign up.

Leave empty if there is no participant limit.

=== Briefing ===

Free-text event information.

Use this field for the full event description, instructions, schedule, rules, links, or any other information participants need.

=== Create event ===

Creates and saves the event.

After saving, the event becomes available on the website according to its normal visibility rules.

= THT event =

[[File:Create tht.png|thumb|caption]]Create THT event page

A THT event is a structured mission event. Use this event type for normal Tally Ho Thursday missions where registration, modules, mission information, rules, lineup, packages, and briefing need to be managed in a detailed format.

== Creating the THT event ==

=== Header image ===

Optional image shown at the top of the event page.

Recommended size is 1920 x 1080 px in 16:9 format. Larger images are automatically scaled down.

=== Title ===

The name of the event.

This is shown in the event list, event page, Discord messages, and other event references.

=== Event summary ===

A short summary of the event.

This is shown in the event list and should briefly describe what the mission is about. Keep it short and clear.

=== Date ===

The date when the event takes place.

=== Time ===

The time when the event starts.

The default time is usually 19:30, but it can be changed if needed.

=== Signup deadline ===

The latest date when users can sign up.

Use this if registration should close before the event starts. Leave empty if no separate deadline is needed.

=== Editors ===

Additional users who are allowed to edit the event.

Editors can update event details and manage registrations. Use this if someone other than the creator needs access to maintain the event.

=== Max participants ===

The maximum number of users who can register for the event.

Leave empty if there is no participant limit.

=== Activity ===

Short keywords describing the event activity.

Examples: Air combat, Ground attack, CAS, SEAD, CAP.

=== Theatre ===

The map or theatre where the mission takes place.

Examples: Syria, Caucasus, Persian Gulf, or another available theatre.

=== Module eras ===

Controls which aircraft modules are available when editing the lineup.

Select one or more eras to filter the module list.

=== Prerequisites ===

Requirements for participating in the event.

Use this for required modules, recommended training, skill level, or other participation requirements.

=== Bullseye ===

Reference point used for navigation and tactical communication.

This is usually collected from the .miz file later.

=== Ramrod ===

Authentication code used during the mission.

The default value is pre-filled, but it can be changed or generated if needed.

=== ROE ===

Rules of Engagement.

Defines when and how weapons may be used during the mission.

=== ALR ===

Acceptable Level of Risk.

Defines how much risk is acceptable during the mission.

=== Briefing ===

The main mission briefing.

This field is pre-filled with example information to help the mission creator structure the briefing. Edit the text as needed for the specific mission.

=== Cancel ===

Cancels event creation and returns without saving.

=== Create THT ===

Creates and saves the THT event.

After saving, the event becomes available on the website according to its normal visibility rules.

= THT lineup setup =

After creating the THT event, open the event and go to Edit lineup.

This page is used to prepare the available modules and create the flight structure for the event.

[[File:Create flight1.png|thumb|caption]]Edit lineup page before flights have been created

== Module selection ==

=== Modules ===

Start by selecting which modules should be available for the event.

Only the selected modules will be available when creating or editing the lineup. This makes it easier to keep the lineup limited to the aircraft that are planned for the mission.

== Creating flights ==

=== Generate Standard Lineup ===

After selecting the available modules, you can use Generate Standard Lineup.

This creates standard flights for the selected modules, for example ARCTIC, BENDER, and similar predefined flight names.

Use this if you want the system to create a basic lineup automatically.

=== Add Flight ===

Use Add Flight if you do not want to use the standard lineup, or if the selected module does not have a standard flight available.

This lets you manually create your own flight and decide how it should be used in the lineup.

== Importing mission data ==

=== Import .miz ===

Use Import .miz to upload the DCS mission file that will be used for the event.

The system will read information from the mission file, such as weather, bullseye, and waypoints.

Waypoints are imported for flights that match the flights created in the lineup. For example, if you have created a BENDER flight in the lineup and the mission file also contains BENDER, the waypoints for that flight will be imported automatically.

== Mission Commander ==

Select the Mission Commander for the event.

The Mission Commander is responsible for the overall mission planning and execution, and will be shown on the event page.

== Back to event ==

Returns to the main event page.

Use this when you are done editing the lineup or want to review how the event looks for users.

= THT participant assignment =

After the flights have been created, the next step is to assign participants and prepare the lineup.

[[File:Flightadded.png|thumb|caption]]Lineup page showing generated flights and slot assignment dropdowns

== Mission Commander ==

Select the Mission Commander for the event.

The Mission Commander is responsible for the overall mission planning and coordination. This person will be shown on the event page.

== External participants ==

Use this section to add participants who are not registered users on the website.

This can be used for guests, visiting squadrons, or people who are joining from outside the normal member list.

=== Name or call sign ===

Enter the guest’s name or call sign.

=== Group name or hosting member ===

Enter the group they belong to, or the member who is hosting or responsible for the guest.

=== Add guest ===

Adds the external participant to the event so they can be assigned to a slot in the lineup.

== Lineup ==

The lineup shows all flights that have been created for the event.

Each flight contains one or more slots. A slot represents a position in that flight, for example Arctic11, Bender21, or Crimson31.

== Assigning pilots ==

Each slot has a dropdown menu.

Use the dropdown to assign a registered user or external participant to that slot. Leave the slot as Unassigned if no pilot has been selected yet.

== Save all ==

Saves all current lineup changes.

Use this after assigning pilots or making changes to the lineup.

== Auto assign ==

Automatically assigns registered participants to available slots based on their registration and module preferences.

Use this when you want the system to fill the lineup automatically.

== Clear lineup ==

Removes all current assignments from the lineup.

Use this carefully, as it clears the selected pilots from the slots. The flights themselves remain, but the assignments are removed.

= THT flight tasking =

After the lineup has been created, the next step is to complete the flight tasking.

Flight tasking is used to define what each flight is supposed to do during the mission, what role it has, and which waypoints should be shown to the pilots.

<<Image: Flight tasking page showing role selection, waypoint settings, and imported waypoints>>

== Flight tasking ==

Each flight has its own tasking section.

Use this section to describe the purpose and instructions for that specific flight.

== Primary role ==

Select the main role for the flight.

Examples: Strike, CAP, SEAD, CAS, Reconnaissance, Transport.

This role is shown in the lineup and helps participants understand the flight’s main task.

== Secondary role ==

Select an optional secondary role for the flight.

Use this if the flight has an additional task besides its main role. Leave it as No role if the flight only has one role.

== Coordinate format ==

Select how coordinates should be displayed for this flight.

Use the default setting unless the flight needs a specific coordinate format.

== Show package waypoints for this flight ==

Controls whether package-level waypoints are shown for this flight.

Package waypoints are shared waypoints that can apply to several flights in the same package.

== Show imported flight waypoints for this flight ==

Controls whether imported waypoints from the .miz file are shown for this flight.

These waypoints are imported when the mission file contains a matching flight name.

== Flight tasking text ==

Free-text instructions for the flight.

Use this field to explain what the flight should do, such as departure, holding point, push time, target, coordination, weapons use, and RTB instructions.

== Imported flight waypoints ==

This section shows waypoints imported from the .miz file.

Each waypoint can be adjusted before it is shown in the event briefing.

=== WP ===

The waypoint number from the mission file.

=== Display name ===

The name shown to users on the event page.

This can be changed to make the waypoint easier to understand, for example CAP A, Target Alpha, or Hold Point.

=== Extra instruction ===

Optional instruction connected to that waypoint.

Use this for short notes such as altitude, timing, attack instruction, holding instruction, or coordination details.

== Delete flight ==

Removes the flight from the lineup.

Use this carefully. Deleting a flight removes that flight and its related slots from the event.

= THT packages =

After the flight tasking is complete, the final step is to set up packages.

Packages are used to group several flights together under one common plan, lead, frequency, tasking, and shared waypoints.

<<Image: Packages page showing package name, frequency, package lead, tasking, waypoints, and flights in package>>

== Packages ==

Use this section to create and manage mission packages.

A package normally contains flights that work together toward the same objective.

== Package name ==

The name of the package.

Example: WOLFPACK.

Use a short and clear name that can be referenced in the briefing and during the mission.

== Frequency ==

The radio frequency used by the package.

Example: 251.000 or another assigned package frequency.

== Add package ==

Creates a new package using the entered package name and frequency.

== Package lead ==

Select the flight or person responsible for leading the package.

The package lead is responsible for coordination between the flights in the package.

== Package tasking ==

Free-text instructions for the whole package.

Use this to describe the overall objective, coordination plan, push time, target area, or any instruction that applies to all flights in the package.

== Package waypoints ==

Waypoints that apply to the entire package.

These are shared waypoints that can be shown to selected flights in the package. Use them for common hold points, push points, target areas, ingress routes, or egress routes.

== Add waypoint ==

Adds a new package waypoint.

The waypoint can then be named and given instructions.

== Flights in package ==

Select which flights belong to the package.

Only selected flights are part of this package and will use the package information.

== Delete package ==

Removes the package from the event.

Use this carefully. Deleting a package removes the package structure and its shared package information, but the individual flights are not necessarily deleted.

= Training event =

[[File:Training event.png|thumb|caption]]Create Training Event page

A Training event is used for regular training sessions. It is simpler than a THT event and does not use the full mission lineup system.

Training events are normally created automatically for Tuesdays at 19:30, as long as no training event already exists for that date. Before creating a new training event manually, first check if one already exists. If it does, edit the existing event instead of creating a new one.

All users with the TD role can edit training events.

== Create Training Event ==

=== Back ===

Returns to the previous page without creating a new training event.

=== Date ===

The date when the training takes place.

=== Time ===

The time when the training starts.

The default time is usually 19:30, but it can be changed if needed.

=== Theatre ===

The map or theatre used for the training.

Examples: Caucasus, Syria, Persian Gulf, or another available theatre.

=== Time of day ===

Selects the general time of day for the training mission.

Use this if the mission should run during a specific preset time, such as day, night, dawn, or dusk.

=== Custom time of day ===

Free-text field for describing the time of day manually.

Use this if the normal time of day options are not specific enough.

Examples: Dawn, Dusk, Late evening.

=== Weather ===

Selects the general weather preset for the training mission.

=== Custom weather ===

Free-text field for describing the weather manually.

Use this if the normal weather options are not specific enough.

Examples: Light fog, scattered clouds, heavy crosswind.

=== Briefing ===

The main training information shown to participants.

This field is pre-filled with a basic training structure to help the creator. Edit the text as needed for the specific training session.

The briefing can include planned training areas, modules, training focus, links, instructions, and any additional notes.

=== Cancel ===

Cancels event creation and returns without saving.

=== Create Training ===

Creates and saves the training event.

After saving, the training event becomes available on the website according to its normal visibility rules.

= Master Meet =

[[File:Createmastermeet.png|thumb|caption]]Image: Create Master Meet page

A Master Meet event is used for physical meetups and real-life gatherings. It is focused on attendance, location, practical information, and planning rather than mission setup or flight lineup.

== Create Master Meet ==

=== Header image ===

Optional image shown at the top of the event page.

Recommended size is 1920 x 1080 px in 16:9 format. Larger images are automatically scaled down.

=== Title ===

The name of the Master Meet.

This is shown in the event list, event page, and other event references.

=== Event summary ===

A short summary of the event.

This is shown in the event list and should briefly describe what the meetup is about. Keep it short and clear.

=== Date ===

The date when the Master Meet takes place.

=== Time ===

The time when the event starts.

The default time is usually 19:30, but it can be changed if needed.

=== Signup deadline ===

The latest time users can sign up for the event.

Leave this empty if the signup deadline should be the same as the start time.

=== Editors ===

Additional users who are allowed to edit the event.

Editors can update event details and manage registrations. Use this if someone other than the creator needs access to maintain the event.

=== Max participants ===

The maximum number of users who can register for the event.

Leave empty if there is no participant limit.

=== Briefing ===

The main information shown to participants.

Use this field for schedule, practical details, rules, packing information, payment information, transport details, links, or other information participants need before the event.

=== Address ===

The street address or location where the Master Meet takes place.

=== Postal code ===

The postal code for the event location.

=== City ===

The city where the event takes place.

=== Country ===

The country where the event takes place.

The default value is Sweden, but it can be changed if the event is held somewhere else.

=== Latitude and longitude ===

The map coordinates for the event location.

These are fetched automatically from the address information you enter. Make sure the address, postal code, city, and country are correct so the location can be found accurately.

=== Cancel ===

Cancels event creation and returns without saving.

=== Create Master Meet ===

Creates and saves the Master Meet event.

After saving, the event becomes available on the website according to its normal visibility rules.

= Registering for a Master Meet =

[[File:Mastermmetregistration.png|thumb|caption]]Master Meet registration form showing transport fields

When registering for a Master Meet, you can provide attendance and transport information. This helps the organizers plan travel, pickups, available seats, and arrival times.

== Actions ==

=== Edit event ===

Opens the event edit page.

This is only available to users who have permission to edit the event.

=== Register ===

Opens or shows the registration form for the event.

Use this to sign up and provide your participation details.

== Registration fields ==

=== Transport type ===

Select or describe how you plan to travel to the event.

Examples: driving, flying, train, passenger, or no transport information yet.

=== Departure location ===

Enter where you are travelling from.

This can be a city, address, airport, or other relevant departure point.

=== Arrival location ===

Only used if you are flying.

Enter the airport or arrival point where you will arrive.

Examples: GOT, ARN, CPH, or Copenhagen Airport.

=== Seats available ===

Only used if you are driving.

Enter how many free seats you have available for other participants.

Leave empty if you are not driving or do not have seats available.

=== Arrival time ===

Enter when you expect to arrive.

This helps organizers coordinate transport, pickups, and planning around the event start.

=== Comment ===

Optional extra information.

Use this for notes such as special travel details, pickup needs, delayed arrival, shared transport plans, or anything the organizers should know.

=== Save registration ===

Saves your registration and transport information.

After saving, your registration is added to the event and can be used by the organizers for planning.
```

← Äldre version		Versionen från 2 juli 2026 kl. 18.19
Rad 1:		Rad 1:
	~~Texten är strukturerad från din uppladdade sammanställning.~~

	= Event creation guide =		= Event creation guide =

Webpage - Versionshistorik

Baconbomb den 2 juli 2026 kl. 18.27

Baconbomb den 2 juli 2026 kl. 18.26

Baconbomb den 2 juli 2026 kl. 18.19