Set up recruitment
/lfc and /lfp: a free-agent board and a job board, both built from questions you write.
Let players without a clan advertise themselves on /lfc, and let clans advertise open spots on /lfp, both built from questions you write.
| 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 |
Before you start#
- The
lfcandlfpmodules must be on. They run independently. - To post on
/lfpa member needs theMANAGE_LFPrank permission, which the shipped leader and officer ranks have: see Ranks.
Steps#
Post a profile as a player without a clan
Run /lfc, click Create ▸ Application, answer the categories, then click the submit button.
Post an opening as a clan
A member with MANAGE_LFP runs /lfp, clicks Create ▸ Recruitment, ticks the requirements, optionally sets Recruitment ▸ Description, then submits.
Answer a posting
A clan browsing /lfc invites straight from the profile (it needs INVITE). A player browsing /lfp picks a clan, writes a message and applies; the clan reads it under Applications and accepts or rejects.
Check that it works#
With one account that has no clan, post on /lfc: /lfc now shows Profile ▸ My application at the top, and everyone sees the post in the list (broadcast-on-post announces it server-wide). With a clan leader, post on /lfp and apply from a second account. The clan gets the application and the applicant sees it under Applications ▸ Sent by me.
Write your own questions#
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.
lfc.yml ships Main Role with Attacker, Support, Gatherer and Explorer — their ids are still
Atacante, Soporte, Recolector and Explorador, which players never see. Both files are translated
with the rest of the language folder; rename the examples 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 in lfc.yml / lfp.yml
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 | A member who is not the leader is offered to leave first (lfc.leave-first-prompt): on yes they leave and carry on in one go. A leader is refused with 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 in lfc.yml / lfp.yml
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 |
| Applying while in a clan | A member who is not the leader is offered to leave first (lfp.leave-first-prompt); a leader is refused with lfp.error-player-in-clan |
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 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.
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