Difference between revisions of "Organised Events"

Latest revision as of 20:37, 11 October 2025

Organized Events	Community-run battles across NA, EU, AU, and AS — formats, participation, hosting, and expectations.

Guide to Organized Events

What are organized events?

Large-scale, community-run battles bringing regiments and public players together across global regions (NA, EU, AU, AS).

Public event announcements are posted on the Event Noticeboard in the Official Holdfast Discord.

What type of events are there?

Line Battle 🪖: Massive engagements with infantry, cavalry, and artillery focusing on volleys and tactical movement.
Naval Battle ⚓: Ship-versus-ship combat where players crew vessels to fire broadsides.
Siege 🏰: Attackers storm a fortified position held by defenders.
Skirmisher Only 🎯: Light infantry battles emphasizing ranged fire and fast movement.
Artillery Only 💥: Events focused entirely on cannons, mortars, and rockets to dominate the battlefield.
Cavalry Only 🐎: Fast-paced, horse-based combat with dragoons and hussars, emphasis on cavalry charges.
Naval Siege ⚓🏰: A hybrid mode where ships assault fortified coastal positions, combining naval gunnery with land defenses.
Frontlines ⚔️: Territory-control mode where teams fight over sequential objectives.

How do I participate?

Join a regiment: Private events allocate slots by regiment and generally don't allow non-regimental players. Regiments handle their own rosters, sign-ups, and rule enforcement.
Public events: Anyone can join public events by checking the Event Noticeboard in the Official Holdfast Discord.
- Players are not required to sign up individually, but large regiments are encouraged to do so to help admins with balancing and special allocations.
- Regiment leaders may request the "Events Enjoyer – Regiment" tag in the Holdfast Official Discord. See: Enlistment.
Be on time and ready: Arrive early and load the server when announced.

Public vs Private Events

Public Events: Run by developer-approved server admins under the official developer rules. Mods are not used in public events.
Private Events: Organized by regiments or communities with their own admins, rules, and optional mod use. These can vary widely in style and format.

What is required to host an event?

Communities can host official or unofficial events. Hosts need to plan for a minimum of:

Server – Dedicated and stable with the correct configuration.
Staff – Admins; clear escalation for rule breaches.
Ruleset – Brief, readable, and clearly posted.
Sign-ups – Regiment headcounts and special unit requests (e.g., Artillery).
Comms & Briefs – Clearly communicating server details, start time, and mod requirements.
After-Action – Screenshots, results, feedback form.

Player Expectations

Follow host rules and your officer's commands.
Keep communications clear (no "ear-spam").
Do not grief, teamkill, or deliberately exploit rules.
Report issues to admins after the current round is over.

Are mods or custom maps used?

Yes, but only in Private Events.
Players must ensure they are subscribed to and have downloaded all required Workshop content before the start time.
Hosts must publish a list of mods and their build IDs in advance.

Tools

@@ Line 1: / Line 1: @@
-{{TOC right}}
+{{ContentTemplateModernInline
-=Organized Events=
+ | welcome = Organized Events
-Organized events are community-run battles that bring regiments and public players together across multiple regions (NA, EU, AU, AS).
+ | blurb   = Community-run battles across NA, EU, AU, and AS — formats, participation, hosting, and expectations.
-For public event announcements see: [https://discord.com/channels/306195621373542400/613794041850626049 Event Noticeboard].
+ | sections_title   = On this page
-==Event Formats==
+ | sections_content =
-;Line Battle 🪖
+* [[#Guide|Events Guide]]
-:Infantry, cavalry, and artillery fight in lines, emphasizing teamwork, volleys, and tactical movement.
+* [[#Event Formats|Event Formats]]
-;Naval Battle ⚓
+* [[#How to Participate|How to Participate]]
-:Ship-versus-ship engagements. Players crew vessels together, firing broadsides, managing sails, and boarding opponents.
+* [[#Public vs Private Events|Public vs Private Events]]
-:
+* [[#Hosting an Event|Hosting an Event]]
-;Skirmish 🎯
+* [[#Player Expectations|Player Expectations]]
-:Smaller, faster rounds prioritizing maneuver, shooting, and light-infantry play.
+* [[#Mods & Custom Maps|Mods & Custom Maps]]
-;Campaign 📜
+* [[#See Also|See Also]]
-:Multi-week, narrative or map-driven wars where outcomes influence subsequent battles.
-;Special / Themed ⭐
-:Sieges, historical recreations, training events, tournaments, or one-off modded scenarios.
-==Typical Weekly Rhythm (Example)==
-''Times vary by host; always confirm in announcements.''
-==How to Participate==
-*'''Join a regiment''': Private events allocate slots by regiment and generally don't allow non-regimental players.
-*'''Public sign-ups''': Players are not required to sign-up for public events, though it's highly encouraged that large regiments do so to help admins with balance and special allocation. Regiment leaders may get the "Events Enjoyer - Regiment" tag in the Holdfast Official Discord. See: [https://discord.com/channels/306195621373542400/613784269713834034 Enlistment]
-*'''Be on time and ready''': Arrive early and load the server when announced.
+ | featured_title   = Guide to Organized Events
-==Hosting an Event==
+ | featured_content =
-Communities can host official or unofficial events. At minimum, plan for:
-*'''Server''' – Dedicated server with stable performance and correct config (map rotation, max players, pings/regions).
+== What are organized events? ==
-*'''Staff''' – Admins; clear escalation for rule breaches.
-*'''Ruleset''' – Brief, readable, and pinned (formations, firing rules, ship limits, round/time caps).
+Large-scale, community-run battles bringing regiments and public players together across global regions (NA, EU, AU, AS).
-*'''Sign-ups''' – Regiment headcounts, special requests (Artillery, Skirmishers, Cavalry)
-*'''Comms & Briefs''' – Start-time, server/password, map list, faction balance, and any mod requirements.
+Public event announcements are posted on the Event Noticeboard in the Official Holdfast Discord.
-*'''After-Action''' – Screenshots, results, feedback form.
-==Player Expectations==
+== What type of events are there? ==
-*Follow host rules and your officer’s commands.
+; Line Battle 🪖
-*Keep comms clear during volleys/boarding; no ear-spam.
+: Massive engagements with infantry, cavalry, and artillery focusing on volleys and tactical movement.
-*No griefing, teamkilling, or deliberate rule lawyering.
+; Naval Battle ⚓
-*Bring issues to admins after the round.
+: Ship-versus-ship combat where players crew vessels to fire broadsides.
-==Mods & Custom Maps==
+; Siege 🏰
-Some events use Workshop content or SDK-built maps.
+: Attackers storm a fortified position held by defenders.
-*Ensure you’re subscribed/downloaded before start.
+; Skirmisher Only 🎯
-*Hosts should publish a mod list and build IDs in advance.
+: Light infantry battles emphasizing ranged fire and fast movement.
-==See Also==
+; Artillery Only 💥
-*[[Regiments]]
+: Events focused entirely on cannons, mortars, and rockets to dominate the battlefield.
-*[[Server_Hosting_Guide]]
+; Cavalry Only 🐎
-*[[Event_Admin_Tools]]
+: Fast-paced, horse-based combat with dragoons and hussars, emphasis on cavalry charges.
-*[[Official Holdfast Discord]]
+; Naval Siege ⚓🏰
+: A hybrid mode where ships assault fortified coastal positions, combining naval gunnery with land defenses.
+; Frontlines ⚔️
+: Territory-control mode where teams fight over sequential objectives.
+== How do I participate? ==
+* '''Join a regiment''': Private events allocate slots by regiment and generally don't allow non-regimental players. Regiments handle their own rosters, sign-ups, and rule enforcement.
+* '''Public events''': Anyone can join public events by checking the Event Noticeboard in the Official Holdfast Discord.
+** Players are not required to sign up individually, but large regiments are encouraged to do so to help admins with balancing and special allocations.
+** Regiment leaders may request the "Events Enjoyer – Regiment" tag in the Holdfast Official Discord. See: [https://discord.com/channels/306195621373542400/613784269713834034 Enlistment].
+* '''Be on time and ready''': Arrive early and load the server when announced.
+== Public vs Private Events ==
+; Public Events
+: Run by developer-approved server admins under the official developer rules. Mods are not used in public events.
+; Private Events
+: Organized by regiments or communities with their own admins, rules, and optional mod use. These can vary widely in style and format.
+== What is required to host an event? ==
+Communities can host official or unofficial events. Hosts need to plan for a minimum of:
+* '''Server''' – Dedicated and stable with the correct configuration.
+* '''Staff''' – Admins; clear escalation for rule breaches.
+* '''Ruleset''' – Brief, readable, and clearly posted.
+* '''Sign-ups''' – Regiment headcounts and special unit requests (e.g., Artillery).
+* '''Comms & Briefs''' – Clearly communicating server details, start time, and mod requirements.
+* '''After-Action''' – Screenshots, results, feedback form.
+== Player Expectations ==
+* Follow host rules and your officer's commands.
+* Keep communications clear (no "ear-spam").
+* Do not grief, teamkill, or deliberately exploit rules.
+* Report issues to admins after the current round is over.
+== Are mods or custom maps used? ==
+* Yes, but only in Private Events.
+* Players must ensure they are subscribed to and have downloaded all required Workshop content before the start time.
+* Hosts must publish a list of mods and their build IDs in advance.
+== See Also ==
+* [[Server_Hosting]]
+* [https://discord.gg/holdfastgame Official Holdfast Discord]
+ | image_content   =
+ <!-- Optional right column content; leave blank to hide the aside -->
+ | layout          = auto
+ | two_col         = no
+ | left_width      = 320px
+ | aside_width     = 320px
+ | gap             = 1rem
+ | show_toc        = no
+ | show_section_edit = no
+}}