Guide
OGameX Inactive Player Farming
Inactive Farming discovers eligible inactive-only players, spies their planets, evaluates reports, and attacks targets that meet your resource and safety filters. It uses a selected origin, probes, cargo ships, fleet-slot reserves, ignored galaxies, and repeat intervals.
Overview
The feature considers players marked inactive or long inactive while excluding vacation, banned, protected, stronger, or new-player statuses. Eligibility comes from the latest completed universe scan, while current resources, fleets, defense, and storage information come from espionage reports.
Complete Universe Scan before enabling farming. Use strict filters and supervise the first spy and attack sequence. Player status and planet conditions can change, so no stored target should be treated as permanently safe.
Select the Farm Origin
Choose a detected planet, moon, or the shared Main Fleet option as Farm origin celestial. The origin needs probes, selected cargo ships, fuel, and free fleet slots.
If using Main Fleet, verify its current coordinates. A deploy-style Pause Fleet Save can update the shared location. A missing origin warning means the feature cannot send spy or attack actions until a valid selection is made.
Start from one stable location. Farming from a distant or poorly supplied origin can increase fuel use and waiting states.
Spy and Fleet Configuration
Probes per spy controls the number sent for each espionage attempt. Choose an amount appropriate for obtaining the report detail needed by your filters.
Cargo ship type selects the cargo used for attacks. Confirm that enough of that ship type is available at the origin. Attack speed changes the selected flight speed. Faster is not always better when fuel and pause timing matter.
Fleet slots to keep free reserves capacity for Defender, Bank, Pause Fleet Save, expeditions, and ordinary account actions. Use a nonzero reserve rather than allowing farming to occupy every slot.
Delay between spy and attack actions spaces repeated actions. Keep a practical delay and do not use the smallest value simply to process the list faster.
Resource Filters
Minimum lootable resources to attack prevents attacks when the report’s estimated loot is below your basic threshold.
Auto-add to attack list above identifies high-value targets that can be promoted automatically into the priority attack list. Set it at or above the ordinary minimum so the priority list remains selective.
Prioritize attack list lets saved priority targets be considered before ordinary eligible planets. Priority does not override current inactivity, threat, report, fleet-slot, or interval checks.
Storage-Level Filter
Minimum combined storage level can skip automatic spying for planets whose Metal Storage, Crystal Storage, and Deuterium Tank levels sum below the configured threshold.
This filter helps avoid spending probes on very small targets before a current report exists. Set it conservatively because old or incomplete information can reduce the candidate list. A target filtered by storage can be rechecked manually when needed.
Attack Intervals
Default attack interval sets the repeat period for ordinary targets from one to five days. Each saved target can later receive its own interval.
The interval is a minimum wait between attacks, not a promise that the target will be attacked exactly on schedule. It still needs current eligibility, a safe report, enough loot, ships, slots, fuel, and an active non-pause period.
Use longer intervals while testing. Repeatedly attacking on the shortest possible cycle can create concentrated activity and may be inappropriate for the changing target.
Ignored Galaxies
Select galaxies that should never be used for automatic farming. This is useful for distance, fuel, strategic, or account-management reasons.
Ignored targets remain visible with an ignored-galaxy state where relevant but are not ready for normal automated actions. Review this list after changing the origin or moving Main Fleet.
Espionage Reports and Threat Checks
After spying, the feature evaluates known resources, loot percentage, ships, defense, and storage levels. A target with detected fleet or defense is blocked. A target without enough known detail remains waiting rather than being treated as clear.
Delete processed reports can remove inactive-farm espionage messages after the feature has handled them. Leave it off during initial testing so reports remain available for comparison. Enable it only after the target status and report viewer are understood.
See Targets and Reports for card states, priority controls, per-target intervals, and report review.
Coordination with Other Fleet Features
Farming competes for probes, cargo ships, fuel, and fleet slots. Defender and Pause Fleet Save should retain priority for protection. Expeditions can also consume a large number of slots across selected celestials.
Schedule farming during active periods with room before the next pause. Keep automated activity below 14 hours per day. Target intervals, action delays, and pauses reduce repetitive patterns but cannot guarantee account safety.
Recommended Setup
- Complete the universe scan.
- Select one well-supplied origin.
- Reserve fleet slots for protection.
- Set a modest probe count and choose an available cargo type.
- Use high minimum loot and storage thresholds.
- Ignore distant galaxies for the first test.
- Keep report deletion off.
- Watch one spy report become ready, blocked, or low-resource.
- Allow one supervised attack before expanding the list.
Troubleshooting
- No targets are found: complete the scan and review inactivity, galaxy, and storage filters.
- Spy actions wait: confirm probes, origin, fuel, fleet slots, and pause state.
- Reports remain blocked: fleet or defense is detected or threat detail is incomplete.
- Ready targets are not attacked: check cargo ships, attack interval, loot threshold, slots, speed, and origin.
- Too many reports disappear: disable processed-report deletion during investigation.
- Main Fleet origin is wrong: review the shared selection after deploy-style fleet movement.
FAQ
Does inactive farming attack every inactive player?
No. It filters player status, galaxies, storage, current reports, resources, threats, intervals, and fleet availability.
Does priority bypass safety filters?
No. Priority changes ordering but does not override current eligibility, report, threat, or fleet checks.
Can I keep fleet slots free?
Yes. Configure the number that farming must leave available for other routines.
Why is a planet storage filtered?
Its known combined storage levels are below the minimum configured for automatic spying.
Should processed reports be deleted immediately?
Keep deletion off during initial testing so you can compare reports with target states, then enable it only if desired.
FAQ
What is OGameX Inactive Player Farming?
The feature considers players marked inactive or long inactive while excluding vacation, banned, protected, stronger, or new-player statuses. Eligibility comes from the latest completed universe scan, while current resources, fleets, defense, and storage information come from espionage reports.