Systems

Recruitment

/lfc and /lfp: a free-agent board and a job board, both built from questions you write.

Two boards, pointing in opposite directions, built from the same three question types.

Command	Who posts	Who reads
`/lfc`	A player with no clan, advertising what they play	Clans, browsing and inviting
`/lfp`	A clan, advertising what it is looking for	Players, browsing and applying

Both are modules and can run independently. Their question sets live in lfc.yml and lfp.yml.

Question types

A category is one question. There are three kinds:

`type`	What the player does	Uses
`TOGGLE`	Ticks it on or off	`answers` and `selections` are ignored
`SINGLE_SELECT`	Picks one answer	`answers`
`MULTI_ANSWER`	Picks answers, then a tier for each	`answers` and `selections`

categories:
  pvp:
    display-name: "&cPvP"
    icon: DIAMOND_SWORD
    type: MULTI_ANSWER
    answers:
      PotPvP:     { name: PotPvP,     icon: SPLASH_POTION }
      CrystalPvP: { name: CrystalPvP, icon: END_CRYSTAL }
      MacePvP:    { name: MacePvP,    icon: MACE }
    selections:
      HT1: { name: HT1, color: "&4", icon: NETHERITE_SWORD }
      LT1: { name: LT1, color: "&a", icon: NETHERITE_INGOT }
      HT2: { name: HT2, color: "&c", icon: DIAMOND_SWORD }
  farmer:
    display-name: "&aFarmer"
    icon: DIAMOND_HOE
    type: TOGGLE
  role:
    display-name: "&eMain role"
    icon: SHIELD
    type: SINGLE_SELECT
    answers:
      Attacker: { name: Attacker, icon: IRON_SWORD }
      Support:  { name: Support,  icon: SHIELD }

The category ids, the answer ids and the tier ids are all yours. Nothing inside categories is pruned, and an entry you delete stays deleted. icon takes a material name or a head reference.

The shipped `lfc.yml` categories are in Spanish

lfp.yml ships English examples; lfc.yml ships Rol Principal with Atacante, Soporte, Recolector and Explorador. They are examples, so rename them to whatever your server asks players.

MULTI_ANSWER is what turns a flat list into a profile that says something: a player does not just tick PotPvP, they tick it at HT2. Both files ship with the same ten-tier ladder as an example.

Looking for clan

settings:
  cooldown-seconds: 300
  expiry-days: 7
  broadcast-on-post: true
  expiry-check-interval-minutes: 10

/lfc opens the browser. A player with no profile builds one from the categories, submits, and appears in the list. A player who already has one sees it at the top and can edit, renew or cancel it.

Rule	Detail
Only players without a clan may post	`lfc.error-in-clan`
One profile per player	The player's UUID is the row id
Cooldown	`cooldown-seconds` between posting and renewing, 300 s
Expiry	`expiry-days` after the last post or renewal, 7 days
Expiry sweep	Every `expiry-check-interval-minutes`, 10 min
Broadcast	`broadcast-on-post` announces posts and renewals server-wide

A profile is removed automatically the moment its owner joins a clan, and the player is told.

A clan browsing the list invites straight from the profile — the button is a normal clan invite, so it still needs INVITE.

Looking for players

settings:
  cooldown-seconds: 300
  expiry-days: 7
  broadcast-on-post: true
  expiry-check-interval-minutes: 10
  description-max-length: 200
  application-message-max-length: 200
  application-cooldown-seconds: 120
  max-applications-per-player: 3

/lfp opens the browser. A clan member with MANAGE_LFP can post, edit, renew or cancel the clan's posting, and read its applications; anybody else sees the board and applies.

A posting carries the categories and a free-text description, capped at description-max-length.

Applying

A player picks a posting, writes a message capped at application-message-max-length, and submits.

Rule	Setting
Pending applications at once, across every clan	`max-applications-per-player`, 3
Wait before applying to the same clan again after a rejection or withdrawal	`application-cooldown-seconds`, 120 s
One application per player per clan	the row id is `playerUuid:clanId`

Applications are PENDING, ACCEPTED, REJECTED or WITHDRAWN. The applicant is notified either way, and can withdraw a pending one from My applications.

Accepting joins the player to the clan there and then, so all the ordinary join rules still apply — the clan being full, the player being banned from it, or the player having joined somewhere else in the meantime.

Joining clears pending applications — unless you founded the clan

Joining a clan marks every pending application of that player WITHDRAWN; accepted and rejected rows are left alone, and nothing is deleted. Creating a clan with /clan create clears the founder's LFC profile but not their applications, so a founder keeps every pending one and it keeps counting against max-applications-per-player. Withdraw them from My applications.

An accepted application is written to the clan log, along with the posting being created, edited, renewed or cancelled.

The menus

Both boards ship with the same shape: a browser, a create/edit screen, a mode picker, an option picker and a tier picker — five files for /lfc. /lfp adds the applications list, the application detail screen and my applications, for eight. They are ordinary menu files — see Menus.

Start with fewer questions

Every category is another click between a player and a posted profile. Three or four questions that actually sort players — a mode, a tier, a role — beat ten that everybody ticks the same way.

Something missing on this page? Tell us on Discord