Feature Suggestion: Introduce MCP (Model Contextual Protocol) Server for Personalized NPC Interactions
Summary:
I propose the addition of an MCP (Model Contextual Protocol) server — a backend system that models player-specific behavior and history to drive persistent, dynamic NPC interactions. This system would allow individual players to build personal relationships with named NPCs and factions across all aspects of the game: PvP, PvE, and industry — creating a living universe that remembers and responds to you.
What Makes MCP Different from Mission Arcs and Storylines?
Current mission arcs and storylines are:
- Static and pre-scripted — same path and dialogue for all players.
- Standing-triggered — not based on context or patterns of behavior.
- Non-persistent — NPCs don’t remember what you’ve done after the arc ends.
MCP is:
- Contextual and adaptive — responses depend on your actual play history, not just rep numbers.
- Player-specific — your relationship with NPCs is unique to you.
- Persistent — NPCs retain memory across time and systems.
- Integrated across systems — influencing missions, chat, spawns, trade, and events.
What This Means for the Individual Player:
PvP Example – Targeted Consequences and Recognition
If you spend months terrorizing trade routes in lowsec, you might draw the attention of Danelle Revar, a Republic Fleet captain tasked with defending Minmatar logistics. She’ll start referring to you by name, issuing system-wide warnings when you’re in local, or dispatching elite anti-pirate patrols that specifically hunt you.
Conversely, if you routinely protect convoys or push back pirates, you could be offered “Mercenary Escorts” — special missions with PvP-style escalation and rewards.
Industry Example – Context-Aware Market Reactions
An industrialist consistently building and supplying Tech II ships in a remote region might trigger interest from Ishukone tech buyers or Serpentis smugglers looking for quiet sourcing. MCP could recognize your contribution volume and offer faction contracts, reduced material costs, or limited-run blueprint deals — completely outside standard mission hubs.
On the flip side, flooding the market with cheap capital components could provoke faction cartel pressure or “dirty deal” offers from underworld NPCs asking you to back off… or collaborate.
PvE Example – Adaptive Encounters and NPC Memory
If you’re regularly farming Sansha sites, the MCP server might flag your name and cause Sansha NPCs to adapt: heavier ship comp in your next sites, bait-style spawns, or even mid-warp ambush fleets led by a named Sansha commander who calls you out directly in local.
Over time, you might earn a unique item drop or have the commander send you cryptic warnings that lead into a personalized mission chain — only available to you, based on your actions.
Technical Feasibility:
This could be modular and scalable — starting with a pilot system such as NPC agent evolution or pirate retaliation. MCP would operate on a separate server layer, tracking individualized player behavior and feeding context into existing systems.
Named NPCs, factions, and regional entities would pull personalized data from the MCP server to adjust dialogue, mission offers, ship spawns, or aggression logic. It’s a context model — not a gameplay overhaul — so integration can be gradual, targeted, and easily tuned.
TL;DR:
MCP doesn’t replace mission arcs — it adds a personalized memory system to the EVE universe. Whether you’re a pirate, hauler, ratter, or builder, the game begins to remember who you are, and responds in ways that make the universe feel alive — and like it knows your name.