1) The basics: what to write

A campaign request is easiest if you include:

• Goal: what you want pilots to do.
• Where: one or more systems, constellations, or regions.
• Who: who can participate and who the targets are.
• Stop condition: stage / percentage / kill target, if needed.
• Contribution cap: max sites, plexes, kills, or contributions per pilot, if needed.
• RP flavour: a line or two for atmosphere.

Write it however you like

You can write one sentence, a paragraph, or a list. PANDAX reads intent from your wording.

What matters most

The wording that defines the objective is the most important part. If you mention multiple objectives, PANDAX prioritises the most strategic one. For example: saying “capture the system” will override “plexing” or “combat roam”.

2) Campaign types and the wording that triggers them

Below are common campaign types and example phrases PANDAX reliably understands. You can copy-paste these, remix them, or use them as templates.

System capture / iHub objectives (highest priority)

• “Capture the system.”
• “Take the system.”
• “Flip the system.”
• “Destroy the iHub.”
• “iHub bash in <system>.”
• “System capture operation in <system>.”

FW plexing campaigns

Plexing language indicates a FW plexing campaign unless you explicitly asked for capture.

• “FW plexing in <system>.”
• “Run plexes.”
• “Offensive plexing only.”
• “Defensive plexing.”
• “Plexing across <system1> and <system2>.”

IMPORTANT: If no specified systems are mentioned, then this campaign will run until the end date/time and end in success.

IMPORTANT: If any system changes hands during this campaign period, then plexing for that system may no longer be recognised.

IMPORTANT: If your campaign specifies systems and any of those systems becomes occupied by the opposing faction, then the campaign will end in failure - system lost.

IMPORTANT: If the campaign only specifies enemy held systems and they all change hands before the end date/time, then the campaign will end in success immediately - all systems won.

IMPORTANT: You really DO NOT WANT to set FW plexing campaigns to be everywhere without specifying systems of focus, or this campaign will count offensive and defensive plexing in all systems.

Pirate insurgency: corruption / suppression

Any mention of corruption or suppression creates an insurgency campaign. You don’t need to say “pirate plexing” — corruption/suppression is enough.

• “Increase corruption in <system>.”
• “Push corruption.”
• “Raise suppression.”
• “Reduce corruption.”
• “Increase suppression to stage 4.”
• “Corruption to 5.”

IMPORTANT: If no specified systems are mentioned, then this campaign will run until the end date/time and end in success. If all target systems reach stage 5 corruption against a suppression campaign, or stage 5 suppression against a corruption campaign, then the campaign can fail.

IMPORTANT: If the campaign specifies multiple systems and a specified stage for them to reach, each system will no longer count plexing once it reaches that stage, and the campaign will end in success if all systems reach the specified target stage.

Advantage push campaigns

Use these when you want strategic advantage activity such as depots, caches, rendezvous points, or propaganda.

• “Push advantage in <system>.”
• “Destroy supply depots.”
• “Clear depots and caches.”
• “Run rendezvous points.”
• “Deploy propaganda structures.”
• “Propaganda beacons in <system>.”

IMPORTANT: If no specified systems are mentioned, then this campaign will run until the end date/time and end in success.

IMPORTANT: If any system changes hands during this campaign period, then pushing advantage for that system will no longer be recognised.

IMPORTANT: If your campaign specifies systems for pushing advantage and any of those systems becomes occupied by the opposing faction, then the campaign will end in failure - system lost.

IMPORTANT: You really DO NOT WANT to set advantage campaigns to be everywhere without specifying systems of focus, or this campaign will count advantage pushing in systems that do not have any importance.

Note: At the moment, the system cannot tell whether an individual action was specifically a Supply Depot, a Rendezvous Point, or a Propaganda Beacon. Advantage campaigns will therefore pick up any of these activity types under the same umbrella.

Combat operations

If you don’t mention capture, plexing, advantage, corruption, or suppression, it becomes a combat campaign.

• “Combat roam.”
• “Looking for fights.”
• “Gatecamp and skirmish.”
• “Hunt targets in <system>.”
• “PvP patrol.”

3) Importing campaigns from EVE Freelance Jobs

REQUIRED: Freelance Job tracking must be enabled in your PANDORA settings for your corporation. If this is not configured, PANDORA will not import any Freelance Jobs from EVE.

Combat campaigns and FW plexing campaigns can also be imported directly from EVE Freelance Jobs instead of being created manually on this page.

When Freelance Job tracking is enabled, PANDORA will automatically import corporation Freelance Jobs created in EVE and convert them into PANDORA content.

If a Freelance Job is a combat or FW plexing job and is set to:

• 50 or more kills / plexes: it is imported as a campaign.
• Below 50: it is imported as a mission.

• PANDAX enriches the Freelance Job description you wrote in EVE.
• The imported PANDORA campaign lists participants like a normal campaign.
• Progress is tracked against the Freelance Job goal.
• You can add extra rewards to the generated PANDORA version after import.

Tip: Use this create-campaign page for custom campaigns, RP-heavy campaigns, special restrictions, or operations that are not already represented by an EVE Freelance Job. Use Freelance Jobs when you want the in-game job itself to drive the campaign or mission automatically.

4) Systems, regions, constellations, and location targeting

Systems

• “In Evati.”
• “Across Auga and Vard.”
• “Operate around Kamela.”

Constellations and regions

• “Across the <constellation> constellation.”
• “Throughout <region>.”
• “Operate in the warzone region.”

Specific locations inside a system

• “Kills must be on the Evati gate.”
• “Fight only at stations.”
• “Engage in asteroid belts.”
• “Hold the undock.”
• “Camp the <station name> station.”

5) Who can take part and who the targets are

Who can take part

• “Only for members of the Amarr Empire.”
• “Minmatar-only.”
• “Caldari militia only.”
• “Gallente only.”
• “Only for members of <alliance name>.”
• “Ushra’Khan only.”
• “Corp members only.”
• “Only for PIE.”

Important note for insurgency campaigns:
If the campaign is about corruption or suppression, faction eligibility is determined automatically based on which empire controls the system(s). When that rule applies, it overrides any faction you manually state.

Who the targets are

• “Kill members of the Amarr Empire.”
• “Primary targets: Minmatar militia.”
• “Hunt Caldari fleets.”
• “Kill members of the Ushra’Khan alliance.”
• “Primary targets: <alliance name>.”
• “Kill members of PIE.”

6) Optional restrictions (with who, ship rules, item/structure objectives)

“With who” rules

• “Kills must be with <pilot name>.”
• “<pilot name> must be on the kills.”
• “Only kills alongside <pilot name> count.”
• “Only kills with PIE on the kills count.”

Ship restrictions

• “Kills must be in Punishers.”
• “Only kills while flying Thrashers count.”
• “Frigates only.”
• “Cruisers only.”
• “Assault Frigates only.”
• “Amarr hulls only.”

Target ship restrictions

• “Kills must be against Ventures.”
• “Only kills against frigates count.”
• “Target Assault Frigates.”
• “Kills must be against Amarr ships.”

Item objectives

• “Destroy Mobile Warp Disruptors.”
• “Destroy cynosural beacons.”
• “Loot tags from wrecks.”
• “Recover <item name> from wrecks.”

Structure objectives

• “Destroy the Astrahus.”
• “Kill the Ansiblex.”
• “Remove hostile mobile depots.”
• “Structure bashing operation.”

7) How campaigns end (targets, stages, kills, failure on expiry)

Campaigns can end in three ways:

• Automatically when a target you specified is reached.
• At the scheduled end date/time if no automatic target was specified.
• Manually if the creator ends the campaign early.

Most important rule

If you do not set a stage, percent, or kill target, the campaign runs until the end date/time or until the creator manually ends it.

Critical: end-condition campaigns can fail

If you do set an end condition, that target is considered paramount.

• If the end date/time is reached before the target is achieved, the campaign is treated as failed.
• If the target is achieved before the end date/time, the campaign completes successfully and ends early.

Insurgency stages

• “Increase corruption to stage 4.”
• “Suppression to 5.”
• “Reach corruption level 3.”

FW plexing contested targets

• “Push contested to 75.”
• “Reach 100%.”
• “Hold at 60.”

Advantage targets

• “Push advantage to 80.”
• “Cap advantage at 100.”
• “Advantage to 60.”

Combat kill targets

• “End after 50 kills.”
• “First to 100 kills wins.”
• “Stop once we hit 75 kills.”
• “Kill target 40.”

8) Per-participant caps / maximum counted contributions

You can limit how many times each participant can be credited during a campaign. This is useful when you want to reward broad participation rather than allowing one pilot to claim unlimited credit.

• “Up to a max of 5 sites per person.”
• “Maximum 5 plexes per pilot.”
• “Cap rewards at 10 kills per participant.”
• “Only count 3 sites per character.”
• “Limit each capsuleer to 5 contributions.”

How this works

• FW plexing, pirate plexing, and advantage campaigns: each pilot can only have up to that many accepted plexing / site / advantage entries counted.
• Combat campaigns: each pilot can only be credited on up to that many accepted killmails. After reaching the cap, that pilot is removed from further credited attacker lists.

IMPORTANT: A per-participant cap is not the same as a campaign end condition. For example, “max 5 sites per person” limits each pilot’s counted contributions, but it does not automatically end the campaign after 5 sites.

9) Enlistment requirement (opt-in tracking)

By default, campaigns automatically track all eligible participants. If you want only opted-in pilots to be tracked, require enlistment.

• “Enlistment required.”
• “Participants must enlist.”
• “Only enlisted pilots count.”
• “You must enlist to take part.”
• “Participants should enrol/enroll to take part.”

10) Solo / alone / 1v1 requirement

If your campaign requires kills to be made solo or strictly 1v1, state that directly.

• “Solo only.”
• “Kills must be solo.”
• “1v1 only.”
• “One-on-one duels only.”
• “Go it alone.”
• “Each encounter will stand alone.”
• “No fleets.” / “No gangs.”
• “No logi.” / “No remote reps.”

IMPORTANT: If you also mention fleets or group participation, Solo mode will not be used unless you explicitly say “solo only” or “1v1 only”.

11) Adding RP flavour and ambience

• “Quiet comms. Fast strikes. Leave only wrecks.”
• “The gates burn tonight — hold the line.”
• “We squeeze until the system breaks.”
• “No broadcasts. No mercy.”

12) Copy-paste example prompts

Pirate insurgency

Increase corruption in Evati to stage 4.
Enlistment required.
Targets: enemy farmers and response fleets.
RP: The noose tightens, one gate at a time.

Pirate plexing with a per-person cap

Capture Angel complexes in Siseide.
Amarr and Minmatar can join this.
Pay 10 million ISK per site.
Up to a max of 5 sites per person.

FW plexing

FW plexing across Auga and Vard.
Push contested to 80.
Targets: enemy plexers and roaming response fleets.

Advantage push

Push advantage across Kamela and Kourmonen.
Reach advantage 75.
Propaganda beacons and caches only.

Combat campaign

Combat roam in Evati.
End after 50 kills.
Frigates only.
Kill members of the Ushra'Khan alliance.
RP: No blues. No mercy.

Combat campaign with a per-pilot cap

Combat roam in Evati.
End after 100 kills.
Pay rewards for up to a max of 5 kills per pilot.
Targets: enemy roamers and plex hunters.

Solo combat campaign

Combat roam in Evati.
End after 25 kills.
Solo only. No fleets. No logi.
Targets: enemy roamers and plex hunters.

Imported Freelance Job campaign example

Create the combat or FW plexing Freelance Job in EVE.
Set the goal to 50 or more kills / plexes.
PANDORA will import it as a campaign if Freelance Job tracking is enabled for your corporation.

13) Tips and common mistakes

Be careful with the word “capture”

If you say “capture” or “flip”, you are creating a system capture style campaign. If you only wanted plexing, say “FW plexing” instead.

If you want early completion, include a number

• Insurgency: stage 1–5
• FW plexing: contested 1–100
• Advantage: advantage 1–100
• Combat: kills

Use Freelance Jobs for imported corporation objectives

If your corporation already creates combat or FW plexing Freelance Jobs in EVE, enable Freelance Job tracking in PANDORA settings. Jobs with 50 or more kills / plexes are imported as campaigns; smaller jobs are imported as missions.

Use enlistment when participation must be controlled

Enlistment prevents huge numbers of incidental participants being tracked automatically.

Keep restrictions reasonable

The more restrictions you add, the stricter the campaign becomes. That can be good — just remember it may reduce counted activity if your fleet can’t meet the conditions.