The mirror showed a man who had been through a war.
William studied his reflection in the bathroom's harsh light—bloodshot left eye that tracked slightly slower than the right, skin pale from fever and dehydration, the hollow look of someone who hadn't slept properly in days. Forty-eight hours since Severe escalation. The acute symptoms had faded, but the damage remained.
[COERCION STATUS: Severe (chronic)]
[PHYSICAL STATUS:]
[- Fever: 37.8°C (elevated but stable)]
[- Tremors: Occasional (1-2 per hour)]
[- Vision: Left eye 5% reduction (permanent unless compliance achieved)]
[- Stamina: Reduced approximately 15%]
[SKILL STATUS: Lethal Improvisation — RESTORED]
[SP: 1,228]
[SP GAIN RATE: −20%]
"Functional. Not optimal, but functional. I can work with this."
[ASSESSMENT: Correct. User has demonstrated above-average resistance to Coercion Protocol. Chronic symptoms will impair but not prevent operational activity.]
[NOTE: Most Users capitulate at Severe. You are an outlier.]
[ADDITIONAL NOTE: This is neither a compliment nor a criticism. It is an observation.]
William splashed cold water on his face and began the process of planning the Antwerp operation.
The decision had crystallized during the fever dreams.
Kill the Antwerp User. Generate enough SP and system satisfaction to buy a reprieve on the Olivia demand. The logic was cold but clear: if the system wanted blood, William would give it blood—just not Olivia's. A rival User was a legitimate target by any measure, a threat that needed elimination regardless of the system's demands. If eliminating that threat happened to satisfy the system's need for compliance, so much the better.
"Use one monster to avoid becoming another. Kill someone who deserves it instead of someone who doesn't."
[OBSERVATION: User is framing rival User elimination as moral alternative to Olivia elimination]
[ASSESSMENT: This framing is partially valid. Rival Users are genuine threats. However:]
[CLARIFICATION: System demands are target-specific. Eliminating the Antwerp User will generate significant rewards but will not automatically suspend the Olivia demand.]
[ADDITIONAL CONTEXT: System satisfaction is measured holistically. Demonstrating value through high-tier elimination MAY influence demand priority, but this is not guaranteed.]
"May?"
[RESPONSE: The system's demand architecture allows for priority reassessment when Users demonstrate exceptional value. Rival User elimination qualifies as exceptional value. However, the Olivia demand represents a targeted vulnerability assessment. Suspension is possible but not certain.]
"So I might kill another User and still have you demanding Olivia's death."
[ASSESSMENT: Correct. But the probability of suspension increases with the scale of the achievement. A Tier 5+ elimination would significantly influence demand priority assessment.]
[NOTE: This is more information than the system typically provides. Consider it a gesture of transparency given your demonstrated resistance.]
The system was bargaining. William recognized the tactic from his corporate days—offering partial concessions to maintain leverage while keeping the ultimate demand on the table. It wasn't a guarantee, but it was something.
It would have to be enough.
The encrypted message to Jansen went out at 9:15 AM.
Need full dossier on industrial property near Antwerp port. Shell company registered in Malta. Priority intelligence on occupants, security infrastructure, utility patterns. Payment upon delivery.
Jansen's response arrived within the hour.
Expensive request. Property is well-shielded — Maltese registration means layers of corporate obscurity. Utility analysis will require contacts I don't use for small jobs. 15,000 euros, half upfront.
William transferred the money without hesitation. Providence's retainer and contract payments had built a healthy balance, and he'd need every piece of intelligence he could get before engaging a comparable User.
[ANTWERP OPERATION: Intelligence phase initiated]
[RESOURCES COMMITTED: 15,000€ (intelligence), potential additional costs pending]
[TIMELINE: 5 days to operational readiness (estimated)]
While waiting for Jansen's dossier, William pulled up the system shop and navigated to the Scan category. His current System Scan was basic—20-meter range, surface-level assessment, easily blocked by distance or interference. Against a rival User, that wasn't enough.
[SHOP: SCAN CATEGORY]
[System Scan (Advanced): 5,000 SP]
[CAPABILITIES: 50-meter range, stat range estimation, ability count, resistance level assessment]
[PAYMENT OPTIONS: Full payment / Installment (1,000 upfront, 500 SP/week until paid)]
[NOTE: Installment carries 20% total cost increase but preserves operational flexibility]
Five thousand SP. William had 1,228, with a 20% reduction on any gains. The installment plan would put him 4,200 SP in debt—a significant commitment that would take weeks to repay. But against a Phase 3-4 User, superior intelligence could mean the difference between victory and death.
"I already owe 840 for Lethal Improvisation. This would push total debt to over 5,000. I'd be working for the system just to break even."
[ASSESSMENT: Debt accumulation is a concern. However, User elimination generates Tier 5+ rewards. A successful engagement would more than cover outstanding obligations.]
[COUNTER-ASSESSMENT: Unsuccessful engagement results in death and checkpoint activation. Debt becomes irrelevant in that scenario.]
[RECOMMENDATION: The investment is justified if it increases survival probability.]
William selected the installment option.
[PURCHASE: System Scan (Advanced)]
[PAYMENT: 1,000 SP (installment initiated)]
[CURRENT SP: 228]
[DEBT: 4,000 SP (Scan) + 840 SP (Lethal Improvisation) = 4,840 SP total]
[CAPABILITY UPGRADE: Scan range 50m, stat estimation, ability count]
The new capability integrated smoothly—his awareness expanding, the system's detection protocols becoming more sophisticated. He'd be able to assess the Antwerp User's approximate power level before engaging, identify their skill count, estimate their resistance. Not perfect intelligence, but far better than going in blind.
Jansen's dossier arrived at 4:47 PM.
William read it over scrambled eggs and toast—the first proper meal he'd managed to keep down since the Severe escalation hit. His hands shook once while he was eating, a residual tremor from the chronic Coercion, but only once.
[ANTWERP DOSSIER: Summary]
[PROPERTY: Warehouse facility, former industrial storage, retrofitted for residential/operational use]
[OWNERSHIP: Shell company (Maltese registration), traces to secondary shell (Cyprus), tertiary (Luxembourg)]
[UTILITIES: Consistent high usage for 4 months, suggests full-time occupation]
[SECURITY: Commercial-grade installation, estimated cost 50,000€+]
[VEHICLE: Black SUV registered to fourth shell company (British Virgin Islands)]
[OCCUPANTS: Unable to confirm identities, but patterns suggest 2-3 permanent residents]
The shell company architecture was sophisticated—layers of corporate obscurity that would take months to fully unravel. Whoever the Antwerp User was, they had resources and operational security training. This wasn't an amateur.
"Four months of occupation. They've been here longer than I've been in Europe. They set up before I even arrived—which means they weren't waiting for me. They have their own objectives, their own operations."
[ASSESSMENT: Antwerp User appears to be an independent operator with established infrastructure]
[IMPLICATION: They are not necessarily hostile to you specifically. Their presence in Belgium predates your awareness of them.]
[COUNTER-IMPLICATION: Rival Users are statistically likely to come into conflict. The fact that conflict hasn't occurred yet doesn't mean it won't.]
William pulled out a notebook—pen on paper, no digital trail—and began writing the operation plan.
Phase 1: Surveillance (Days 1-2)
· Advanced Scan deployment at detection range
· Confirm User phase, stat ranges, ability count
· Map daily patterns, security rotation, associate movements
· Identify vulnerable windows
Phase 2: Preparation (Days 3-4)
· Position advantages (escape routes, ambush points)
· Acquire additional consumables if needed
· Confirm checkpoint proximity (Zurich, ~600km)
· Prepare contingency plans for failed engagement
Phase 3: Engagement (Day 5)
· Execute during identified vulnerability window
· Primary approach: ambush at building exit
· Secondary approach: infiltration during low-security period
· Tertiary approach: vehicle interdiction during transit
· Objective: Eliminate rival User, absorb maximum skills
Contingency: Checkpoint activation
· If engagement fails fatally, resurrection in Zurich
· Regroup, reassess, determine if second attempt viable
· Accept that checkpoint refresh will be required regardless
The plan was solid but not foolproof. The Antwerp User was comparable in power—maybe stronger, maybe weaker, but close enough that the fight could go either way. William's advantages were limited: the Advanced Scan would give him better intelligence, the element of surprise if he timed the approach correctly, and the checkpoint insurance that meant death wasn't permanent.
His disadvantages were significant: chronic Coercion symptoms reducing his effectiveness by approximately 15%, unknown enemy capabilities, unfamiliar territory, and the very real possibility that the Antwerp User was better prepared for conflict than he was.
"Five days to prepare. Then I go hunting something that hunts like me."
[OPERATION STATUS: Planning phase complete]
[RESOURCES: System Scan (Advanced), Lethal Improvisation, Firearms Proficiency (Silver), Financial/Political Intelligence (Gold)]
[LIMITATIONS: Chronic Coercion symptoms, significant SP debt, unknown enemy capabilities]
[SURVIVAL PROBABILITY: 55-65% (estimated)]
[NOTE: These odds are better than most User-vs-User engagements. Most Users don't survive first contact.]
William closed the notebook and looked out the window at the Amsterdam canal. The evening light was fading, boats passing in the distance, the city continuing its ordinary rhythms while he planned to kill someone like himself.
"Survive. That's the only item on the list that matters."
[OBSERVATION: User has accepted the engagement as necessary]
[ASSESSMENT: This represents significant psychological commitment. There is no turning back from this decision.]
[NOTE: Good luck, William Green. You're going to need it.]
The system had never wished him luck before. William wasn't sure if that was encouraging or terrifying.
Five days. Then the hunt would begin..
Reviews and Power Stones keep the heat on!
Want to see what happens before the "heroes" do?
Secure your spot in the inner circle on Patreon. Skip the weekly wait and read ahead:
💵 Hustler [$7]: 15 Chapters ahead.
⚖️ Enforcer [$11]: 20 Chapters ahead.
👑 Kingpin [$16]: 25 Chapters ahead.
Periodic drops. Check on Patreon for the full release list.
👉 Join the Syndicate: patreon.com/Anti_hero_fanfic