Party Jobs

Three commands decide who plays what in a party with sims: .role for your own job, .simrole for a sim member’s, and .assist for whose target everyone kills.

“I want a player to have complete control over the role of a sim member … if the player is eligible for that role. That’s the very important part.”

— drizzlx, 2026-09-02

The four jobs are tank, healer, buffer and dps, plus auto, which means “whatever your class is.”

Which command, in which party

This is the part worth reading once. .role and .simrole look like the same command pointed at different bodies. They are not — they are honoured in different kinds of party.

Your party	.role (your own job)	.simrole (a sim’s job)	.assist
One you joined with .inviteme and have not taken over	Read	Not applicable	Read
One you formed with .invite or .party fill	Refused	Read	Refused
One you joined and then took over with .party <mode>	Refused	Read	Refused

The refusal says so in words:

[role] this party's sims already take orders from you directly — either you formed it with .invite, or you took it over with .party. Roles and main-assist are for a party you JOINED and have NOT taken over.

The reason is not arbitrary. A party you formed is already driven by you: its sims take your orders directly, so there is nothing for a declaration to tell them. A party you joined makes its own decisions and reads your declaration when it plans. Declaring into the first kind would be stored and never read, so it refuses rather than pretending.

.role — the job you are playing

Type	What happens
.role	Tells you your current job and lists the ones your class can fill
.role healer	You are the healer. The party plans around that
.role auto	Back to whatever your class is

Your class decides what you may claim. A class that cannot fill a job is refused by name:

[role] your class can't play tank. You can pick: healer, buffer, dps, or auto.

What you see: a party you joined stops treating you as generic damage and starts building its plan with your declared job in it.

.simrole — a sim member’s job

.simrole <member> <tank|healer|buffer|dps|auto>. The member is named the way you would say it, and .party lists them. Same eligibility rule: a sim can only be given a job its class can fill.

The dashboard’s Roles page is this command as a board — one row per sim member, every job that member’s class can fill side by side, the current one lit. It is reached from a chip on the Party page.

.assist — whose target dies

Type	What happens
.assist me	The party fights what is fighting you
.assist not-me	You hand it back — the party leads its own kill order
.assist <member>	That member calls the target
.assist auto	The party picks its own lead

The reply for me is worth reading closely, because it states a limit:

[assist] you're the main assist — the party fights what's fighting you, but only while you're fighting alongside them; they hold their own field if you wander off. Use .party protect for a party that follows you.

What you see: being the main assist points the kill order at you. It does not make the party follow you — that is .party protect, and it needs a party you lead.

Job and assist are two separate axes on purpose.

“a tank can be a role, but NOT the main assist”

— drizzlx

What to look out for

You see	Why it’s suspect
.role refuses in a party you are clearly in	You lead that party. Use .simrole for its members; .role is for a party you joined
A member you named is not found	Names resolve against your own party only — .party lists them
.simrole refuses a job	That sim’s class cannot fill it. The refusal lists what it can
A declared job seems ignored	Check which kind of party you are in against the table above
The party still leads its own kill order after .assist me	You wandered off. The main assist holds only while you fight alongside them

Related

Sim party mechanics · Party composition · Classes and roles · The dashboard

---

← back to l2everdream.com