In-Game Faction HQ

A faction headquarters for territory games: war planning, intel on rivals, logistics and a hidden operations room.

  • 7 categories
  • 24 channels
  • 9 roles
  • Medium
Download Discord JSON

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

HQ

  • hq-lobby

    General faction chat.

  • rules-of-engagement

    When members may open fire, and when they may not. Not optional.

  • faction-orders

    Standing orders and anything the whole faction must read.

WAR ROOM

  • war-planning

    The next push, in outline. Timing lives in Operations.

  • target-list

    What the faction wants, and the reason it is worth taking.

  • defense-alerts

    Enemy at the wall. Post first, explain after.

  • after-action

    What happened and what it cost.

INTEL

  • rival-factions

    One post per rival, kept current: strength, holdings, habits.

  • scouting-reports

    Raw sightings. Time and place, even if it turns out to be nothing.

  • diplomacy-notes

    Who is neutral, who is friendly, and for how long.

LOGISTICS

  • resources

    What the faction holds and what it is short of.

  • base-building

    Construction plans and who is building what.

  • crafting-requests

    Ask the Quartermaster. One request per post.

  • supply-status

    Current stock, written by the Quartermaster.

TERRITORY

  • claimed-territory

    What we hold.

  • contested-zones

    What is being fought over right now.

  • map-and-borders

    The current map. Officers keep it accurate.

OPERATIONS

  • operation-timing

    When we move. The one thing recruits do not see.

  • officer-chatHidden from @everyone

    Officers only.

  • Command

VOICE

  • Muster Hall
  • Squad One
  • Squad Two
  • AFK

Roles

  • Faction LeaderAdministrator
  • OfficerAdministrator
  • QuartermasterModerator
  • Veteran
  • Member
  • Recruit
  • Ally
  • Muted

Overview

Built for sandbox and territory games where a faction holds ground and fights other factions for it. The layout follows the loop those games run on. War Room is the planning floor: #war-planning for the next push, #target-list for what the faction wants and why, #defense-alerts where anyone can raise an alarm without asking first, and #rules-of-engagement, a read-only statement of when members may open fire, which stops one impulsive member starting a war the faction cannot fight. Intel is deliberately separate: #rival-factions holds one post per rival kept current, #scouting-reports takes raw sightings, and #diplomacy-notes records who is neutral this week. Logistics covers the half that decides most sandbox conflicts: #resources, #base-building, #crafting-requests and a read-only #supply-status. Territory holds #claimed-territory, #contested-zones and #map-and-borders. Operations is hidden from everyone below Officer, because the plan for a surprise raid cannot sit in a channel a spy can read; recruits are trusted with everything except the timing. Voice has a small Command room, two squad rooms and a Muster hall. Recruit, Member, Veteran and Officer are the ladder; Ally is a limited role for a friendly faction, reaching #diplomacy-notes and the muster hall only.

When to use it

Territory games are lost in logistics and intelligence far more often than in combat, but most clan servers give both one channel and put the war plan in general chat where a rival's alt can read it. This layout separates planning from intel from supply, keeps the operational timing behind an Officer wall, and writes rules of engagement down so a single member cannot commit the faction to a war by accident.

What makes it different

  • Rules of engagement are read-only, so one member cannot start a war on impulse.
  • Operational timing sits behind an Officer wall while everything else stays open.
  • Intel is split from planning, so scouting reports do not bury the actual decisions.
  • Logistics gets four channels, because supply decides more sandbox wars than aim does.

Recommended Vetox setup

  • Auto Roles

    Assign Recruit automatically on join so the Operations category stays hidden without an Officer acting first.

  • Reminders

    Set Reminders in #war-planning for muster times so a scheduled push does not depend on someone being awake to ping.

  • Temp Voice

    Enable Temp Voice beside the squad rooms so a raid can split into extra channels and clean them up afterwards.

  • Logs

    Enable Logs into the Officer area so role changes and channel edits are visible if the faction is infiltrated.

Questions

Why hide operations from recruits specifically?

Because infiltration is a normal tactic in territory games and a recruit is the cheapest account to burn. Recruits can see the target list, the rules, the map and the supply status, which is everything they need to play. What they cannot see is when the faction moves. That single restriction removes most of the value of infiltrating without making a recruit feel excluded from the faction.

Should #defense-alerts really be open to everyone?

Yes. An alert that needs permission is an alert that arrives late. The channel exists so any member who sees an enemy at the wall can say so immediately, and it is worth the occasional false alarm. Keep it out of the Officer area, give it a ping role, and accept that some alerts will be nothing.

Common mistakes

  • Planning a timed operation in a channel every recruit can read, which is how surprise raids stop being surprises.
  • Treating resources as an afterthought, then losing a siege because nobody tracked what the faction had.
  • Leaving rules of engagement unwritten, so a single member's grudge becomes the faction's war.

Consider instead

  • Survival Tribe Alliance Your group is cooperative and social rather than fighting other factions for territory.
  • MilSim Unit You run structured military simulation with ranks and training rather than sandbox territory control.

Do you have any doubts?

Our team is there for you

0.0k

Servers

0+

Commands

0

Users

0

Languages