Sunday, November 15, 2009

Commandeering (part 1)

At the core of Exegesis sovereignty mechanics sits FoF Tuning, a non-destructive PvP system that enables players to seize control of enemy assets, as opposed to ka-blooing them.

FoF Tuning applications aren't limited to sovereignty contests, however: much like a TacMap would, they come in to fill ancient holes in the feature set of EVE, and today's "I could do that last century" segment is about:

Commandeering.
At heart, Commandeering is self-explanatory: it gives players the ability you hijack third-party ships and space assets for the benefit of their faction, corporation or self.

The basic gameplay is straightforward, too: find a suitable target, apply FoF Tuner modules to it for a while, and the coveted thingy is yours. That's if nobody tries to stop you, of course.

From a game mechanics standpoint, here's how it works:
FoF Tuners are high-slot utility modules. They emit FoF Tuning signal to the specific frequency of a Faction, Corporation or Pilot. When aimed at an applicable target, this signal is either added to the target current tuning charge (if the emitter and target frequencies match) or subtracted from it (if they differ).
Which of three possible frequencies a FoF Tuner is emitting can be selected automatically (default) or manually (with Scripts). [More on FoF Tuners]
Most things found in space that belong to players (and some NPC stuff) are susceptible to Commandeering/FoF Tuning. That includes ships, anchorables and deployables, various can types, POS towers and modules, outposts, stargates… pretty much anything save corpses can potentially be snatched away or repossessed through Commandeering.


Tuning states:

The status of any space asset is decided over two key attributes: Ownership and Control.

The process of Commandeering amounts to modifying a space asset's Tuning charge and frequency in such a way as to shift it it to a new Controller (and possibly Owner).

• Ownership can be Owned or Abandoned.
  • If Owned, an Owner is defined. The Owner can be a Faction, Corporation or Pilot (usually the Controller).
• Control can be Controlled, Neutralized, Challenged.
  • If Controlled, a Controller is defined. The Controller is the a Faction, Corporation or Pilot (in many cases the same as the Owner) that last brought the target to its Nominal Tuning Charge.

  • If Neutralized, a Contender may be defined. The Contender is a Faction, Corporation or Pilot in favor of which the target is currently holding a positive FoF Tuning charge, after the object has been brought to 0.0 Ts, and while it hasn't yet been tuned back up to its NTC.

  • If Challenged, a Challenger is defined. The Challenger is the Faction, Corporation or Pilot in favor of which the target is currently holding a positive (yet insufficient to gain Control) FoF Tuning charge, after the object has been tuned back up to its NTC from a Neutralized state by the  Contender.
• Commandeering a target requires to feed it enough FoF Tuning signal to first bring its Tuning charge down to 0.00 Ts, at which point its Control flips to Neutralized ; then push some more signal to pump it to a positive charge in your favor, which switches its Control to Challenged, and makes you the Challenger. With another healthy helping of your FoF frequency signal, the tuning charge in your favor can be brought up to the target's Nominal Tuning Charge (NTC) threshold, which will gain you Controller status over the target — in many cases this will also grant Ownership to the Controller.
  • Reducing the Tuning Charge of a target by feeding it a different FoF Frequency (than its current Challenger/Controller's) is known as Neutralizing.

  • Increasing the Tuning Charge of a target by feeding it the same FoF Frequency as its current Contender/Challenger/Controller is known as Tuning Up.

  • Successfully tuning a target up to its NTC and gaining Control over it is known as Commandeering.
The typical states a target goes through in the course of Commandeering are as follows:
  1. Owned/Controlled: Tuning charge remains positive for the Controller ever since it reached NTC.
  2. Owned/Neutralized: Attackers have brought the object Tuning charge down to 0.00 Ts.
  3. Owned/Challenged: the Contender FoF frequency has successfully charged the object up to its NTC, switching its state to Challenged (and resetting its tuning charge to 25% NTC), and is now tuning it positively again, but still below NTC.
  4. Owned/Controlled: the target Tuning charge has hit NTC from a Challenged state, granting Control  to the Challenger, thus making it the (new ?) Owner.
This sequence is the most commonplace and applies to ships and the majority of non-sovereignty-bound objects under usual circumstances.
Some special targets may become Abandoned immediately around phase 3, when they become Challenged (ex: Dungeons Control Centers, POS), while others will see their Ownership remain unaffected by a change of Controller in phase 4 (ex: 'rescued' ships, or Dungeon Mass Drivers).
[It is worth noting that reaching phase 2 or moving to phase 3-4 against Sovereignty Structures may present significantly different challenges, but since this article focuses primarily on Commandeering ships, we'll get back to that later.]



Tuning Charge:

All space assets susceptible of being Commandeered can hold a positive Tuning charge of a single FoF frequency at any one time. A few important factors in the level of this charge are worth knowing.

  • Nominal Tuning Charge (NTC): This is the required level an item must be charged up to, in order to Commandeer it.
    Its base value is set by the item TypeID, and can be increased  by Sovereignty modifiers, Tuning Amplifiers Rigs (for ships only), Tuning Amplifiers Arrays (POS and Outposts) to compute the ETC.

  • Effective Tuning Capacity (ETC): the maximum charge the item can currently hold, based on NTC plus modifiers such as FoF Tuning skill level (on ships), sovereignty benefits, etc.
    ETC is almost always higher than NTC, and increases the asset's defensive buffer against Neutralization attempts (but not Commandeering proper, which is based on NTC).

  • Passive Tuning Recharge (PTR): The ability for a space asset to regenerate lost Tuning charge over time,  up to its ETC. Many space assets can enjoy this benefit, although it may be dependent on sovereignty modifiers/prerequisites to work properly.
    Ships have a built-in PTR that's always on as long as there's a pilot aboard, and which can be boosted by the FoF Tuning skill and by sovereignty  modifiers.
    Outposts, POS, Stargates, deployable defenses, DMD and DCC also have a PTR (subject to sovereignty conditions/modifiers).
    Cans, secure cans, anchorable bubbles, construction platforms don't benefit from PTR.





    • Of note: ships left floating in space Abandoned (even inside a friendly forcefield) will suffer a 'negative PTR' of sorts, as their Tuning charge will slowly start to decay toward Neutralized.



Who can Commandeer what, and in whose name ?

Any pilot with the skills and FoF Modules fitted can attempt Commandeering, but some targets such as POS and sovereignty-bound structures can only be Commandeered in the name of a Player Corporation or Faction, and as such are off-limits for players in NPC 'noob' corps.

Player-controlled ships and drones are always fair targets for everyone (although Commandeering a Capital ship with a single cruiser may prove impractical), and select NPC ships can also fall prey to FoF tuners (mostly in the context of epic/special missions).

• Pilots in NPC corps can only use Tuners set to their personal frequency, and can't Commandeer for Corp or Faction. Likewise their ships are always Owned in personal name. [Doesn't apply to FW militias/corps, see below.]

• FW militias, both NPC corporations and enlisted player corps are not considered NPC and are treated like 'real' corporations for the purposes of Commandeering rules.


Commandeering Ships.


• Manned Ships:

Can technically be Neutralized, Tuned Up and Commandeered anywhere, but doing so can be an Aggression/Criminal Act, with potentially ka-bloo-ey consequences in lawful space.
  • Manned ships are immune to FoF Tuning while their structural integrity is not compromised. They become vulnerable while their structure is damaged to 95% or below, provided their shields and armor remain under 15%.

  • While its Control is in a Challenged state, a ship is largely disabled: the pilot retains control of steering and the ability to warp, dock, or jump/accelerate through a gate/portal, but can't activate modules or drive-jump under her ship's own power.
    Ejecting and activating self-destruction of the ship both remain possible at any time.

  • If the Challenger(s) manage(s) to gain Control over the ship and the ship's Owner changes as a result, the pilot is forcibly ejected, leaving the ship vulnerable to boarding by the new Owner(s).
• Unmanned ships: 


Unmanned ships floating in space (in or out of forcefields) retain their tuning charge and Controller for at least a while if left alone, but their Ownership status changes to Abandoned after three minutes without a Pilot aboard.
A Pilot member of a Faction can board any ship Owned or Controlled by her Corporation, Faction, or self, but not a ship Owned by another Corporation in same Faction (unless her Faction is the Controller).
 
• Boarding a ship that is Abandoned requires its Control to be either Neutral, or Challenged/Controlled in favor of the boarding Pilot personal/Corp/Faction FoF frequency.

• On boarding, an Abandoned ship's Owner attribute will automatically change to its new Pilot (if Control was Neutral before), or match the current Challenger/Controller.

• Abandonned ships can be Neutralized or Tuned up without the requirement to first bring them down into structure — if nobody's home, the boat is up for grabs and won't resist on its own.

• Unmanned-yet-still-Owned ships can only be boarded by the ship's Owner(s) or Controllers:
  • A ship Owned by a Faction can be boarded by any member of said Faction, or a member of the Controller entity.

  • A ship Owned by a Corporation can only be boarded by a member of said Corporation, or a member of the Controller entity.

  • A ship Owned privately by a pilot can only be boarded by its Owner, or by a member of the Controller entity.

The fine print:

Generally, Commandeering a foreign ship results in the Controller change triggering an Owner change to match, but Owner and Controller of a ship don't always have to be the same inside a Corporation or Faction, with amusing ramifications.
  • Commandeering a Corp-Owned ship within an alliance using the Faction's FoF Frequency will not change the Owner to Faction.
    Thus, a Neutralized/Challenged ship, while Owned by an allied Faction/Corporation can be 'rescued' by  members of a different Corporation in same Faction, provided they tune the ship to the Faction's FoF frequency. Control in this case will be gained by the Faction, but the Ownership will be retained by the same Owner (Corp or Faction), leaving the pilot in the cockpit (unless the ship was previously Owned in Pilot's name, who would then be ejected by the Ownership change).

  • A Neutralized/Challenged ship, while Owned in personal name by a Pilot can be 'carjacked' by  members of her Corporation or Faction, provided they tune the ship to the Corporation/Faction's FoF frequency. Control in this case will be gained by the Corporation/Faction, triggering an Ownership change (to Corp or Faction) that will forcibly eject the Pilot. [Note that the ejected pilot may still end up with proper rights to board the ship again… right after the session change delay.]

  • Commandeering a Faction or Corp-Owned ship using a (different) Corporation FoF frequency (even if belonging to the same Faction) will trigger an Ownership change (to Corp) that will forcibly eject the Pilot (if any).

Tuning ship settings:

• Pilots can manually change the Ownership and Control settings of their active ship, either in station (requires access to the Fitting service) or in space (near a Carrier/Ship Maintenance Bay).

• Corporation officers can edit the O/C settings of assembled ships directly from the Corporate Hangars (requires access to the Fitting Service, or a Maintenance Bay in range if on a POS). 

• Carrier/Motherships/Titans pilots can modify Owner/Controller settings on the ships stored in their Maintenance Bay if they so choose, which will otherwise remain as they were when they got loaded in.
  • Player-Corporation members have a choice of setting their ship Owner and/or Controller to either 'me' or 'Corporation'.

  • Alliance (and FW) pilots have a choice of setting their ship Owner and/or Controller to either 'me', 'Corporation', or 'Faction'.
Ownership/Control settings don't have to always match, within limits ('me' as Owner is not compatible with 'Faction' as Controller, for ex).

As a player corp pilot, setting your ship to 'Corp'/'Corp' is usually the way to go: it gives you maximum flexibility by allowing you to easily swap ships in space with corpmates, and to defend each other against Commandeering attempts while preserving a possible corp-subscribed insurance on your ship.

If you're member of an alliance 'Corp/Faction' grants you the same level of flexibility without voiding a possible corp insurance on your ship.

The only sensible reason to fly a ship with Controller/Owner set to 'me' is if you just took advantage of Kill Rights to 'repossess' a ship in space, or if you have to leave your empty ship floating in a POS and don't trust your alliance/corp mates to leave it alone (note that it could still be scooped or easily ejected from the POS after if becomes Abandoned).
  • Packaged ships have no Owner/Controller attributes set, being generic item types and all, while newly-assembled ships will default to Owner: 'PilotName' Controller: 'PilotName' (if assembled in personal hangar), or Owner: 'CorpName' Controller: 'CorpName' if assembled in a Corporate hangar (POS or station).

  • Ships you take from Corporate hangars (including Deliveries), or that are dropped in your personal hangar from/by corporation officers will come with default settings of 'Corp'/'Corp' unless they have been set otherwise by corp officers.

  • Assembled ships received through direct trade or corp/alliance contracts keep their O/C attributes until you board them, at which point you can manually change them.

  • If you're in a NPC corporation, your ship comes pre-set to Owner: you, Controller: you, and you can't change those yourself (except by ejecting, which will reset the Owner to Abandoned after 3 minutes).

Commandeering and Insurance.

Contrary to what happens when you contract or repackage your ship, losing it to Commandeering doesn't void your policy, but the beancounters tend to look cross at such claims, and as a rule of thumb you'll get only about 25% of the payout you'd be entitled to on a 'clean' loss.

Warning: changing the Owner on a ship will void any active Insurance contract previously taken by the former Owner of the ship — keep it in mind when receiving 'corp ships' that may already be insured.


Commandeering and Kill stats.

Simply put, being forcibly ejected from your ship in the process of a Commandeering qualifies as a ship loss. Even though the insurance people won't like it, when it comes to Kill Rights, Kill Stats, Kill Boards, Kill Whatever, it counts as such.
People participating in a successful Commandeering will get credit for any target whose Controller changes as a result of FoF tuning, which means the same ship will ding twice before it (doesn't) change hands in a FoF Tuning contest: once when it becomes Challenged, and once when Control is (re)taken.
This is intended so rescuers of a distressed ship can get credit for their bloodless achivement.


Commandeering, as seen by the Space Police:

Tuning up (or Neutralizing) a target using the exact same FoF frequency as its current Owner is not considered Aggression, but Assist, and falls under the same applicable rules a remote-boost would.
Neutralizing or Tuning up a target using a different Pilot/Corp/Faction FoF frequency from its current Controller's is always an aggression, but not a Criminal Act if the FoF Frequency used on the target is that of the Owner's Corporation or Faction (or if the Tuner(s) and target are at war, benefit from Kill Rights, etc).
Members of NPC corporations (except FW Militias against valid FW/war targets) will always be 'perps' when Commandeering a target: NPC corp membership doesn't allow one to Commandeer a 'corpmate' boat more than it makes legal to shoot them.

Beyond CONCORD, Commandeering can also get you in trouble with NPC Navies and FW Militias, if by chance you're attempting to hijack a stargate in NPC-controlled space

***

[In part 2 of this series, we'll have a look at other potential targets for Commandeering, besides ships]

Saturday, November 14, 2009

FoF Tuner Modules


Overview:

FoF Tuners are high-slot utility modules that emit FoF Tuning signal to the specific frequency of a Faction, Corporation or Pilot, directed at a locked target.
When activated against an applicable target, this signal is either added to the target current tuning charge (if the emitter and target frequencies match) or subtracted from it (if they differ).

The effect of FoF Tuners signal is applied to the target at the end of the module cycle, not as it starts — long-cycled FoF Tuners will see a significant delay before the target's tuning charge starts changing as a result of the module's first activation.


FoF Frequencies:

• Each Pilot, Corporation or Alliance FoF frequency is unique and tied to its ID.

• Which frequency a FoF Tuner is emitting can be selected automatically (default) or manually (with Scripts).
  • In Auto mode they will select the first applicable frequency in this order: Faction, Corporation, Pilot.
  • Two scripts allow to force the frequency to either Corporation or Pilot as default, but the FoF Tuner will revert to Auto if the selected frequency is not applicable to the designated target, starting the cycle from the Script-selected step. 

FoF Tuners:
  • Come in Micro, Small, Medium, Heavy and Capital sizes, with versions ranging from Meta 1 to 15.

  • Like other similar emitters, FoF Tuners use capacitor power to output a proportional amount of effect per cycle: much like 'normal' damage, it can be quantified in per-second output, in this case Ts/sec.

  • The efficiency of FoF tuners doesn't follow a strict 'bigger is better' code. Larger versions of FoF Tuners don't necessarily make the best use of capacitor and charges compared to smaller types.
    Notably, Medium (cruiser-sized) Tuners display a higher efficiency and proportionally longer range (before skills/ship modifiers) compared to most other types — this is intentional, to allow T1/T2 cruisers to prove viable choices in territorial warfare and POS Commandeering.
In addition to capacitor power, FoF tuners burn Cooling Pellets to prevent overheating.
  • Cooling Pellets come in only one size and flavor, various FoF Tuner models will simply burn more or less per cycle, depending on their model and applicable modifiers.

  • A FoF Tuner can run without cooling pellets, but will start heating up and spreading heat damage through high slots soon afterwards.

  • Overloading a FoF Tuner increases it's Ts/sec output by about 40%, at the expense of doubled cooling pellets consumption (which still won't be enough to stop it from overheating).

  • Running an overloaded FoF Tuner without cooling pellets is possible, but will result in 2x the usual heat buildup …expect some of your high slots to go offline shortly if you go there for more than a cycle or two.
Numbers:

The actual stats of FoF Tuners are yet tba, but should be comparable with Energy Transfer / Neutralizer modules of equivalent size.

Accounting for lvl4 in Frequency Modulation and FoF Tuning skills, stats should scale as follows from T1 to T2 (without ship-specific bonus):
Size:          Range(km)  Ts/sec  CapEff    Cycle  Pellets/Cycle
Micro:          6.5-8     10       x1.2       5s     6-9
Small:           10-12    12.5     x1.1      10s    12-18
Medium:        22.5-27    20       x1.25     10s    20-30
Heavy:           32-38.5  30       x1        15s    40-60
Capital(Sieged): 40-48    50(312)  x0.15(x1) 30s   180-250

• Ts/sec values are for non-named T1 Tuners. T2 variants should output about 20% more for an average increase of 50% in Cooling Pellets consumption, with a constant capacitor efficiency.
 

• Actual capacitor use and base values are tbd, but the Cap Efficiency values above reflect what should be the proportional Ts units emitted for a set capacitor drain.
 

• Ship modifiers (Assault Frigates, Marauders) to the base Cooling Pellets consumption of various FoF Tuners types are rounded up to the unit on each cycle.


Applicable skills :
  • FoF Tuning: allows usage of FoF Tuners. Rank 4 Science skill, Intelligence/Willpower.

    • Prereqs: Electronics lvl 4.

    FoF Tuning grants a 5% per skill level to the Tuning Signal output of FoF Tuners and to the passive tuning recharge rate and tuning capacity of one's ship (Tuning Strength modifiers).
    Tech 1 Micro, Small, Medium, Heavy and Capital FoF Tuners require the FoF Tuning Skill at lvl 1 through 5 respectively. T2 FoF Tuners require +2 lvls over their T1 counterparts (up to lvl5).


  • Electronic Warfare, for 5% reduction in capacitor usage per skill level (not applicable to capital FoF Tuners).

  • Frequency Modulation, for 10% increase in range per skill level.

Specialist Ships — The following ship classes have special bonus for FoF Tuner modules:
  • Assault Frigates, Marauders: all races.

    • Per Ship skill level: 10% to FoF Tuner efficiency (reduces capacitor and cooling pellets usage) and 15% RoF boost.
    • Ship role bonus: 250% FoF Tuner range multiplier.

    A typical AF pilot with lvl4 Assault Ships skill will burn 8 Cooling Pellets per cycle on T1 Small FoF Tuners, and 11 on a T2 small FoF Tuner — lvl 5 Assault Ships will reduce the consumption of a Small FoF Tuner II to 9 pellets/cycle.
    Marauders follow the same profile: level 4 in ship-specific skill will burn 24u/cycle and 36u/cycle on Heavy T1 and T2 Tuners, respectively, reduced to 20u/cycle and 30u/cycle at lvl5.


  • Dreadnoughts: all races

    • Per Racial Dreadnought skill level: 10% to FoF Tuner efficiency (reduces capacitor and cooling pellets usage) and 10% RoF boost.
    • Ship role bonus: 300% FoF Tuner range multiplier.
    • Siege mode affects FoF Tuners like other siege weapons, with a 625% multiplier to Ts/cycle, but incurs a 20 seconds activation delay on a new target (ignored on following cycles in autorepeat mode).


  • T3 Cruisers/others: Undecided yet, but likely.

Cooling Pellets:

Those are produced (by players only) from a mix of Coolant, Heavy Water and Nanite Paste. They require BPO or BPC sold by various NPC corporations through their LP stores.
  • While many NPC corporations will offer Cooling Pellets BPC, only the NPC Factional Warfare Militias will offer BPO, at a substantial cost and only to pilots in high standings with them (and Faction).

  • Each Pellet is 0.005 m3 in size, and weighs 0.01 kg

  • The recipe for Cooling Pellets is 1x Nanite Repair Paste, 10 Coolant, 20 Heavy Water — for 1000 units per run and a price estimate of about 80 ISK/pellet (blueprint costs ignored).

***


[See Commandeering for more information on FoF Tuning applications.]

Friday, November 13, 2009

DevBlog #709 — Dominion Sov. Warfare

[Update on Dominion, by way of DevBlog.]


The good (yes, there is some):
It's a well-written one, much more didactic and less confusing than average. In fairness, if it could make sense, despite the material at hand, it would.
Read it, it even has a nice flowchart — Seleene Mark Abathur seems really fond of those.

The bad:
Well, the mechanics are still an open-invite for blobfest, with zero restrictions on the number of factions, ship classes or total head count that can pile up over hard-timed singular hotspots tackled in succession.
Not that I expected it to change for the better, despite well-meaning and cringe-inducing statements like:
"Most importantly, we delayed finalizing this part of the design because we wanted to maximize our interactions with the EVE community. By reading your forum feedback, speaking with the CSM and listening to you at FanFest, it is reasonable to say that this feature of Dominion has had more influence from the players than any other we've done."
I've been there before, so I'll just sum it up:
It is still a death sentence for the small/medium alliances, there's still no potential (even limited) immunity for critical infrastructure like Capital Assembly Arrays on POS (since the removal of Constellation Capital Immunity), and that's just the pure warfare side of things, no going back to the larger territorial dynamics.

The ugly:
Wether CCP is unsure about that bit and puffing smoke to dodge the issue, or they've made a decision and it's just a fumble in the writeup… anyhow, that part is confusing:
Offensive structures (SBUs)
Vulnerability states
SBU(s) are vulnerable while being anchored and onlining.
Once an Outpost and/or Infrastructure Hub is reinforced, the SBU(s) enter a parallel reinforcement cycle. That means that the SBU(s) are invulnerable as long as there are no vulnerable structures in system.
  • If the Outpost and Infrastructure Hub are vulnerable, so is the SBU(s). 
  • If the Infrastructure Hub is vulnerable and the outpost is not, then the SBU(s) are vulnerable.
  • If the Outpost and Infrastructure Hub are vulnerable, so is the SBU(s).
I reckon • 1 and • 3 above are not supposed to read the same, but there's no way to make a safe guess on what line 3 should be. Most likely it should start like this, to cover all three positions:
  • If the Outpost is vulnerable and the Infrastructure Hub is not, then the SBU(s) are…
    • vulnerable ?
    • invulnerable ?
…your guess is as good as mine. Considering the two descriptive sentences before this breakdown are contradicting each other, it could go either way.

No worries,  though: just ram everything in sight with 800 ships and you'll have plenty of time to check during the reinforced timers if the SBUs feel ticklish or not.

Damn, and I almost wrote a real post on Commandeering. Next time, I suppose.

Thursday, November 12, 2009

Training and Learning


Training in general, and learning skills in particular have been a subject of contention ever since EVE implemented them.
Despite most users generally agreeing the overall concept of background training is a healthy, liberating one compared to the traditional model of treadmill grind prevalent in most MMO, its balancing and impact on player experience and behaviour are complex and touchy issues.

Some people argue for the pure and simple removal of Learning skills, while on the opposite end of the spectrum, some are still foaming at the mouth over the reduction in prerequisites for Advanced Learning skills (from lvl5 down to lvl4 in respective basic skills).
I, for once, sit firmly somewhere in the middle.

I like that people get a chance to specialize their toons sooner if they so choose, by training Adv. Learning skills early, and pumping select attributes to +8 without putting essential skills on hold for weeks, and I like that the current system allows compulsive optimizers to remap their toons' attributes once a year to align them to a finely-tuned long term training plan — and of course, the recent addition of Queueing, although long overdue, is more than welcome.
Finally, the early-training speed boost granted to characters under 1.6 million SP (exact figure ?) is a boon of n00bie goodness which I heartedly approve.

All these changes are Good™ in my view, as they improve playability and accessibility, and grant players more flexibility and freedom, while not detracting from one of my personal favorite characteristics in a 'sandbox' design: player choices should be meaningful.

Conversely, removing ghost training was stupid and misguided beyond belief, but I covered that at length in the past, so I won't go there again today.

Specialization is Good™ (as long as you can change course if you want to):

Remapping attributes only makes sense because you can't do it every week, or you might as well get rid of attributes entirely and set a fixed learning speed applicable to every character and skill type in game.
Similarly, Learning skills allow you to make meaningful choices about which attributes you want to prioritize, and to support specialized skill sets, which contribute to the flavor and strategic depth of the game.

Which is why, as much of a n00b-lover as I am, I'm not favorable to the idea of removing training skills entirely and just toss a blanket +9 boost to all new toons attributes.
The fact is, that bonus would not make any difference to the usual scapegoats for that sort of proposal: the 50+ million SP vets, but would be a huge slap in the face of the mid-range (10-25m SP) toon owners who wouldn't benefit from it.

Honestly, when you're past the 40-50m SP mark, odds are your toon is already both fairly specialized and enjoys +8 to +9 across all attributes, save maybe your single less-favored one. Furthermore, you're reached a point where the majority of the skills in your plan are level 5s with Rank 6+, thus you're already looking at training from a multi-weeks scale perspective, which makes the investment in long Learning skills both comparatively painless and sensible. Oh and you have +4 to +5 implants on all but your combat clones

Between 10 and 30 million SP, you may not be able to afford multiple custom tailored sets of clones, and you probably make do with a single mixed +3/+4 set, with maybe a +5 tossed in the mix if you've spent the time on Cybernetics lvl5 (a week or so).
At this stage, your choices in skill sets are significant: you can be a decent Battleship pilot or a well-honed frigate specialist, or you could be starting to look good in a T2 cruiser, but hardly all three.
If you spread yourself across fields, say between drones and Leadership, or Trade and Industry, you can do stuff, but there will definitely be a wide gap between you and a specialist in the field, which can play a significant part in deciding the roles you can successfully fill.

…and this is not necessarily a bad thing.

In a small group of players, or among n00b-to-midrange toons, specialization is a factor of differentiation and can be valued and rewarded by the recognition of your peers, or get you entrusted with the jobs you can do best, etc: it is part of who you are in the group, and why you have a unique, identifiable place in it.

To sum up: in the first three years of your pod pilot career, what you decide to train should already mean something, and learning skills should both help you get there faster and set your skill set apart from those who have chosen another path.

That said, accessibility is also important, and I support the notion that having to put on hold essential skills early in your spacenerd life until you reach +8 across the board of your attributes is an uncalled-for pain.

A possible fix 

…would be to grant new characters a freebie of all Basic Learning skills (attributes boosters and Learning itself) injected and trained to level 1 at creation, and to allow Learning skills to be trained in a parallel queue, at 50% speed (without penalty to the main queue).

Combined with the current speed boost to training awarded to n00b toons, this offers a wealth of interesting choices to make:
  • parallel-train Learning Skills early and you get better attributes sooner, but you also hit the training speed-boost barrier before those who don't (your Learning skill points still count against the upper limit on 2x training speed bonus) ;

  • focus on the essentials and you're mission-ready earlier, but it will take you the little bit of extra time to get really good at it, as your Learning skills catch up on the side (which should also give you — the player — some time to learn how to fly that ship properly and avoid the overly expensive lessons of upgrading to T2 or bigger ships too soon).
Adv. Learning skills in this context don't need further tweaking, or minimal, like drop the prerequisites to lvl 3 of respective Attribute skill, add Learning lvl5 as a prerequisite for all, and maybe slightly adjust their rank so +7 on any attribute can be managed fairly fast, while +8, 9, 10 require more serious commitment.


[Caveat: I'm unsure whether one should be allowed to train Learning skills in the main Queue, too, either while the Learning-only queue is idle, or in parallel… I'm leaning toward 'yes', as it would allow players who want it to focus hard on learning for a while at any point in their plan, but it could also result in people feeling compelled to do nothing but Learning until it's done, which is the main criticism I hear about the current Apocrypha system.]

On a semi-separate note, I wonder how good or bad it would be if it was possible to trade-back skill points put in skills one no longer uses to acquire new skills faster ?
Maybe with a 50% points 'waste' penalty, and a capped usage: no more than once every 3 months, no more than X skills/levels at a time…

Food for thought.

Wednesday, November 11, 2009

Logoff/Downtime Grace period.


With the removal of timer-based obstacles in sovereignty contests, and because the main battlegrounds of territorial warfare would then be deadspace dungeons, metagaming the daily downtime could become even more imbalancing under Exegesis than before, if left unchecked.
To address this issue (and a few other of lesser impact), Exegesis should introduce a Relog Grace Period on logoff/logon, and around downtimes.


Downtime Grace Period:

[Intended to prevent pre-DT zerg rushes on Dungeons]
  • From 15' before downtime, and during the 15' following restart of TQ, it is not possible to tune/neutralize sovereignty structures:
    Sovereignty Structures, be they Occupancy Tokens, Sovereignty Flagpoles or sovereignty-affected POS (and modules) gain a temporary invulnerability to FoF Tuning for 15' pre and post downtime: FoF Tuner modules aimed at them will complete their cycle, but will auto-deactivate after that, and the current FoF Tuner cycle will be 'wasted' (the effect of FoF Tuners applies to their target as the end of a cycle, not as it starts).
    [Note: Tuning equipment remains functional against ships and anchorables during the Grace Period, as a provision for the Commandeering feature to work as intended. FW Sovereignty Tokens are subject to the Grace period just as any player-conquerable structure.]

[Intended to prevent long downtimes from overly helping Defenders.]
  • Sovereignty Structures for which a Passive Tuning Recharge may apply still benefit from it during the grace period, but never during downtime. Changes in the state of sovereignty that require a downtime to be reflected in game will be decided based on a snapshot of the gamestate at the time the server goes offline.

[Intended to prevent the Defenders of a Dungeon to leverage the downtime as a way to force Challengers back to the Entrance level of the Dungeon]
  • Ships logging off inside any Planetary/Solar Dungeon's room in the last 15' before a downtime/reboot will auto-warp back to the same room (instead of the Dungeon's Entrance deadspace pocket) if they log back in within the first 15' following server restart.

Relog Grace Period:

[Intended to protect players from too severe a penalty in case of accidental disconnect]
  • Ships logging off inside a Planetary/Solar Dungeon at any time (outside of the 15' pre-Downtime Grace Period) enjoy a 15' Relog Grace Period, during which they will auto-warp-back to the coordinates where they lost link inside the Dungeon. Normal emergency-warpoff to 1 million KM applies inside a Dungeon, but during the first 15' after lost-link is detected, a ship will enjoy a special pass to warp back right into the Dungeon deadspace pocket they left from — past that delay, they will auto-warp back to the Dungeon's entrance beacon.
    [Note: regular timers are not canceled by the Relog Grace Period in Dungeons: losing link with aggro will see your ship try to auto-warpoff to 1 million KM then stand defenseless there for the duration of the aggro timer before you vanish, but if you relog before 15' past losing link, you'll auto-warp right back inside the dungeon where you lost link in first place, not to the Dungeon's entrance pocket — unless that's where you logged off, ofc.]



Tuesday, November 10, 2009

Cooking tips during recess.


No headache-inducing wall of text for you today, due to my being busy cooking and doing non-spacenerd stuff. Instead, I'm going to do what it is I do here when I'm not busy killing bazillions of electrons with design games: I'm going to pretend I can read CCP's hivemind, and mock their assumed dorkiness based solely on my more or less well-informed assumptions.

Here goes:

Most of the ideas suggested here in the daily downtime filler  (and then some) have been looked into by the current crop of devs@CCP at one point or another, and in many cases, the consensus seems to be "Cool, but impossible".
Translated, that usually means they have no clue how some of the old code works, and they believe it would blow up in their face in spectacular and interesting ways, were they to poke its black magic with their trembling fingers.

Going back to its inception, EVE is over 10 years old now, and at its core rots a collection of haphazard hacks that CCP used to think they could/would fix later.
From the perspective of the people burdened with maintaining and improving them, most huge, old codebases are largely made of black boxes, and as far as EVE is concerned, it is a fact many of the original coders have left the building, leaving behind an undocumented and ancient beast in Tranquility.

Now it's Windows 98: you patch, you add services around the bank of the code swamp, but you don't want to risk yourself anywhere near the deep end.
…I've had this discussion with some of EVE devs in the past, who usually agreed it'd make more sense altogether to start working on EVE 2.0 with a separate team, to reproduce the gameplay of the original while it is still live, but on a codebase that actually works and scales up.

With EVE euro server more than paying for itself and the China franchise turning out what amounts to money for (almost) nothing, you'd think it should be possible to do just that: keep a live team on EVE 1.0, seed a new team to actually design shit ahead of time (for a change), in view of EVE 2.0 but with EVE-as-we-know-it in mind, and then start coding anew, retrofitting what can be into live-EVE as you progress, to meet and fill the semester expansion deadlines.

Why is that not happening ? 

Inertia is a powerful thing, and maintaining compatibility with an old codebase is a good way to ensure people will keep coding as usual and not move on to the new methods as long as they can help it. Unless you split your teams entirely to allow the new breed to breathe their own brand of oxygen, this stuff is happening later than Soon™.

Entirely insulating development teams is a suicidal HR and productivity move, however: who in their right mind would be driven to give their best to old-EVE, knowing a 2.0 is in preproduction and their own project is therefore sitting on the death row ?

Count'em… nobody, except those rare grognards willing to take one for the company (who would be better used on the new-and-better EVE team), and the terrible losers who can't find the testicular fortitude to send out their resumes and find a gig where what they do matters (and those, you can feel sorry to have on the payroll to begin with).

You'd be left trying to motivate a flock of people, most of them in the lower 5% percentile of talent in house and/or already looking for a way out, and the usual BS about 'we're la creme de la creme of awesome hardcore MMO nerds' won't cut it anymore at this point. Prepare to raise pay across the board, or hemorrhage staff and customers very soon (no ™ here).

In short, starting a new and sexier project, staffed with the best talent you can muster would amount to shooting your cash-cow in the gut a few times with a 12-gauge gun, on the off-chance the 2.0 version will be worth the extra years and millions of dollars in development.
Ergo: not happening.

Thus, EVE will carry on, it will keep getting milked for cash as long as the tremors of elderly dementia remain manageable, and hopefully (for CCP) they'll have another successful game or two  ready to take over by the time the once gold-spewing tits go up…

On a separate note, a Pot-au-Feu can benefit from a cup of fresh pineapple juice added after the first grease-skimming. It's a nice cheerful dish, well-suited for the cold season we're entering.


Monday, November 9, 2009

IntelligenceServices


Ever got a mail from a POS whining it's under attack ? IntelligenceServices is that, if the POS had a cell-phone instead, and knew to call someone who cares…

The assumption behind IntelligenceServices is that ships, stargates, stations, even POS control towers act as surveillance cameras (in space !), and the information resulting from their monitoring can be shared with whoever meets certain criteria.
Conversely, pilots can select with whom they share the tactical data available to them, within certain limits.

In highsec empire, NPC factions broadcast information about the local situation as a public service, freely available to all but wanted criminals and terrorists. Once you leave the well-controlled areas of Empire, however, you're dependent on of the local spacelords goodwill and less-than-perfect surveillance network for your situational awareness needs.
…or are you ?

It all depends on the resources available to you.

Worst case scenario, you're flying solo across hostile and highly-secured 0.0 sovereign space, and odds are the local patrols will see you coming from a constellation away if they bother polling the stargates stats, while you fly in a fog with zero clue about who's in local until they get into visual range, or unless you run some manual scans.

Best case scenario, you're a trusted member of a rather large and well-coordinated fleet, in your own high-sovereignty alliance space (or a very friendly ally's), and nearly every ship, stargate, outpost or POS is acting as a searchlight-mounted camera for your benefit, relaying to you intel about everything in range of their sensors, in real-time.

Most of the time, as you're prowling around the wild lands on the edge of sovereign space, hunting for juicy NPCs or rival faction pilots, you'll get only the occasional chirp from a lone TacticalRelay, and mostly rely on your fleet's advanced scouts to scry through the fog of war.

IntelligenceServices overview:
The general principle is simple: stuff with sensor senses, transmits TacticalDataStreams to its Controller/Pilot, and the Controller decides (within limits) who to share the intel with.
Whatever TacticalDataStreams reach you, they fill your TacMap, SitAW and Overview (or browser window) with the up-to-date, accurate intel you need to make the informed decisions that will help yourself or your underlings die in a blaze of glory.
Excited yet ?

TacticalDataStreams explained:
Any entity that acts as a TacticalDataSource (TacDS) can report on its own internal state (type, name, location, damages, engaged, etc) and, if it has the sensors for it, about what it can see in the grid it's in by sending out a TacticalDataStream.
  • Each TacticalDataStream is directed to a single, specific UserGroup, which can be preset or left up for the player to pick.

  • Recipients of TacticalDataStreams can use IntelNodes to filter and merge them, and redirect the resulting composite TacticalDataStream to a different UserGroup.

  • Factors such as sovereignty modifiers, the type of the TacDS, or presence of friendlies nearby can affect the ability and range a TacDS can send out its TacticalDataStreams.

  • Each TacticalDataStream is a one-way transmission, you need at least two to enable a full exchange of TacticalData between entities.

  • Ships can only 'listen' until they join a fleet, at which point they become TacticalVessels (TacVes) and can stream the tactical data they receive from their own sensors and other TacDS to any recipient of their choice.

  • Some space structures act as TacticalRelays, permanent TacDS for their Controller alliance/corp, to which they transmit the data they gather, after which it is up to the Controller entity to relay that intel to whoever they want.

  • Pods and POS-gunners are 'listen-only' regardless of whether the pilot is in a fleet.

So… what can I see ?
Beyond publicly available data (easily out-of-date in 0.0), and what your ship sensors and scanner probes gather, your TacMap (and Overview in some cases) will show you all the information that is shared with and relayed to you by a variety of sources.

If you're not in a fleet, you will see:
  • all the Tactical Data that your alliance and corporation IntelligenceServices have decided to share with all their respective members ;

  • all the data that is made available to select UserGroups you belong to by Outpost-bound IntelNodes ;

  • all the Tactical Data that is made available to you as member of a select PrivateUserGroup you have been invited to by his creator/manager, which can feed you up to as much data as is available to his TacticalVessel in first place (yes, that's where spies everywhere rejoice !).

If you are in a fleet, you will see (in addition to the above):
  • all the Tactical Data your peers (Squadmates if you're a Squad member, Squad Commanders in your Wing if you're a Squad Commander, Wing Commanders in your Fleet if you're one) choose to share horizontally ;

  • all the Tactical Data your Commander chooses to share with you (see below) ;

  • all the Tactical Data that is made available to you as member of a select FleetUserGroup you have been invited to by his creator/manager, which can feed you up to as much data as is available to him in first place.
A Fleet Commander typically forwards some/all of his available Tactical Data to each (or all) Wing Commander(s), who decide to relay all or part of what they receive to each (or all) of the Squad Commander(s) under them, etc.

You can selectively filter out some data inputs to 'listen' only to select sources for clarity's sake, although it is usually better to use the TacMap display options to fine-tune what you need to see.

Who can I share my TacticalDataStreams with ?
If you're not in a fleet:
Nobody, unless you're an IntelligenceOfficer with proper authorization sitting in an Outpost: your ship is not a functional TacticalVessel until you join a fleet.

If you're in a fleet:
As long as you're in a ship (and not POS gunning), you can transmit to at least one UserGroup of your choice using you onboard comms, and possibly more if you have been entrusted with extra IntelNodes as part of your fleet duties.
The default target for your TacticalDataStream transmission when in a fleet is your direct commanding officer, with a quick-select option to switch transmission to your peers (your direct CO still receives your stream when you share in peers mode).
Going for peers sharing is your best option in most cases to maintain some level of tactical awareness if your commander goes down, but you can perfectly direct your TacticalDatstream transmission to a different destination… if you don't stray away from the grid your teammates are in, odds are nobody will notice your ship is not reporting any intel to the fleet.

***

[Better massage your temples and get a cold drink, we're not done yet…]

Sunday, November 8, 2009

Tactical Maps v1


Welcome to EVE-online: the wargame.

The tactical map is available to any pilot, and lays out for the player the combined intelligence gathered by her own ship, what she receives from her fleet, and whatever local territorial surveillance networks are willing to share.

This information is presented in two modes: the HUD Situational Awareness window (SitAW), which can be arranged anywhere on the overview and provides a limited-resolution synthetic view on the tactical situation, and the TacMap proper, a full-screen mode similar to the system/stellar map, which offers a much finer-grained selection of data, polled in real-time from the server.
The real-time TacMap is full-screen-only, in part to discourage players from keeping it on all the time, as it could cause excessive server load and client lag, and partly because displaying so much information in anything smaller than 1024*768 would only result in visual clutter.
A third mode of the TacMap is available through in-game Chromium and out of game browser (via New Eden) which will allow strategists not present in the fleet to monitor the tactical situation from the comfort of their ebil overlord lairs outpost basements.

Under the best of circumstances, the TacMap will show you much more information than what is currently available in-game, and which today is typically relayed mostly by voice comms, despite the worthy attempts of fleet broadcasts to be helpful. In order to reduce clutter and make sure your screen shows you what you need to see, SitAW and TacMap can be adjusted to 6 different 'views':
  • Fleet (TacMap Default)
  • Wing
  • Squad
  • World
  • Constellation
  • Solar (SitAW default)
  • Grid (really cool, yet maybe unpractical for technical reasons)
Fleet, Wing and Squad views 'auto zoom' to display a portion of the stellar map or solar system encompassing the locations of respective groups in your fleet that currently feed data available to you (within transmission range limits).
If that area spans beyond a single system, the systems where fleet members or active tactical relays are present will be highlighted and can be selected to switch to Solar mode. Similarly, if the selected view extends across several constellations, it is possible to select a constellation to switch to Constellation mode.
If all members of the selected view are in the same system or grid, the display will automatically switch to Solar or Grid view respectively, and will auto-zoom in to frame the group if possible.

World view shows the entire stellar map, with color-coded highlights on every system where you benefit from Tactical feeds.

Constellation view zooms to frame the entire constellation you're currently in (default), or which you selected from the TacMap.

Solar shows only the solar system you're currently in (or selected from the TacMap), much like the current system map, but will also reflect the status of connecting stargates in neighbor systems (if available).

Grid view shows the grid as seen by your ship sensors (default), or the sensors of any ship or Tactical Relay available to you, showing more or less the same kind of information you'd get from your main overview's brackets if zoomed out, albeit in a stylized fashion.

TacMap (fullscreen) mode:
In TacMap mode, you can zoom in on a Solar system or Constellation by selecting them, or on any arbitrary portion of the stellar map, either by using a 'alt-click'n'drag' rectangular selection, or by shift-clicking several systems and/or constellations to create a selection. Multiple items selection sets (rectangle or shift-click) can be saved and exported for later reuse.

In World, Constellation and multi-system set views,  the TacMap also reflects which systems are within coverage of your alliance's IntelligenceServices network by surrounding them in a greenish halo.

When zoomed out to show more than a single system at once, the TacMap defaults to a 2D view that won't accurately reflect distances between solar systems but makes for potentially better legibility ; it can be switched to 3D mode for player convenience.

Solar and Grid views (or any views that auto-zoom to such scales) are 3D-only and freely rotatable by mouse-drag, and default to a bird's eye perspective close to a top-down 2D view.
  • The finest granularity of TacMap in Solar mode is grid-wide, which means you'll see all items of interest present in the same grid synthesized as a composite object, even when zoomed all the way in. Hovering on the composite grid object will provide you with a sorted breakdown of items in grid, while double clicking the composite object will switch the TacMap to a Grid view of that grid.

  • Ships are not fully rendered in Solar and Grid views, and use simplified 3D icons on a broad per-class basis (all ships of a same class share the same icon, regardless of race or model, using the same distinctions available in overview setting). Drones, fighters/fighter-bombers may not be shown in Solar and Grid views.

  • Similarly, ships and items 3D icons are color-coded according to your overview settings, with hostiles/war targets typically showing in red, fleet members in purple, alliance mates in dark blue, etc. Cloaked ships that you can see by virtue of them sharing their tactical information with you (directly or not) appear translucent, while the 3D icons of ships presently engaged in combat blink.

  • Fully zoomed out, Solar view reverts to a simple 5-colors one-bubble-per-grid display model, similar to the SitAW mode, but with fully detailed information available on hovering/selecting (see SitAW mode below).
Grid view details:
For most purposes, Grid view is an easier to read schematic version of the 3D overview, centered on a select ship/tactical relay instead of your ship PoV.
Grid view is freely rotatable and zoomable down to a 10km-wide cube. When zoomed out beyond the finer-grain resolution, overlapping objects are merged into a single slightly oversized icon that cycles through the list of 3D icons of objects it presently stands for.
Much like the directional scanner, Grid view can be set to either show every visible item, or use your current Overview Settings (independently of the personal settings of the ship/structure whose PoV is used).

[Caveat: To reduce server load and client lag, it is likely that remote Grid view will only be practical for ships and structures that are located in the same solar system as yours. This is due to the requirement for Grid view to display reasonably accurate positional data for each object, while Solar view needs at most to list the visible contents of a grid.

Depending on how the server really handles grid, especially memory-wise, implementing remote grid view may prove to be impossibly complicated or resource-hungry. If that were to be the case, having to drop Grid view should not be a show stopper for Tactical Maps altogether: a suitably detailed Solar view would already go a long way toward making things much more interesting.]

SitAW mode:
The HUD window mode presents a limited subset of useful tactical information in a compact form.
World and Grid modes are not available in SitAW, nor can arbitrary selections of systems be created (but they can be recalled from a saved set). Selecting the Fleet/Wing/Squad mode will bring SitAW to Solar view if all reporting members of the selection are presently in the same system.

SitAW Constellation/saved set view is 2D only, using the same synthetic, scale-inaccurate rendering used in the 2D TacMap mode.

SitAW default view is Solar, and in this mode will only display a single color-coded bubble for each monitored grid-wide 'grain', in one of 5 colors:
  • Red: war targets, (potentially) members of a fleet flagged as hostile by SharedIntel, or -standings
  • Blue: alliance members/assets and +standings
  • Green: fleet members
  • White: neutral/unknown/space stuff.
  • Orange: any mix of the above present in the same grid.
Hovering the mouse on a bubble will provide a simple 1-4 lines breakdown of what it represents, without much details beyond the count of entities (drones are ignored) for each of the main categories (Red, Blue, Green, White).
Solar mode in SitAW is freely rotatable but not zoomable: clicking on a bubble will zoom x8 to display an area centered on the bubble/grid at the time of the click, a second click anywhere in the SitAW display will restore the view to full-size Solar mode.

Browser mode:
Both in-game and out, via either EVE-Chromium or your browser of choice, tactical maps should be able to provide much of the essential information to monitor a battle from a strategist perspective, yet only in 2D, and less real-timey.

The browser version can zoom anywhere from World to Solar, displays detailed data about selected objects via schematic flag panels, and generally speaking feeds from the same sources TacMap and SitAW do, only rendering it in a slightly more 'corporate' style, and at a slower refresh rate of roughly every 30 to 60 secs.

It should prove invaluable to monitor the health and Control/Ownership status of your alliance's stargates, outposts and other Sovereignty Tokens, and could tie-in with community-made tools that provide nicely arranged views of statistical data.

Now that we have shiny maps, what intel exactly can we see on them ?
Well, that would depend on IntelligenceServices (see next post).


Tactical Maps: a true WTF? moment.


When I started typing what would grow into the first episode of The DOLT Chronicles, I expected to churn out a couple quick illustrative examples of Exegesis new mechanics, each no longer than a paragraph or two…
How I got carried away probably says a lot about my own tendency to contextualize and think in a systemic way, but it also has to do with the intrinsic magic of Design by Tales, that pretty much requires you flesh out concepts until they grow legs and start walking while you try to explain about a piece of design through a story.

A cool example of how storytelling can lead to 'emergent' design of sorts can be found no farther than in the very first sentence of this short tale:
Marz El Duchamp, The Poutine Pie Clan CEO and newly-founded DoubleOreganoLimeToast [DOLT] alliance's grand poo-bah took another long look at the tactical map of the CL4M-1T system in SH-3LF constellation, for what seemed like the thousandth time of the night.
Believe it or not, this reference to a tactical map was not meant by me as a segue for a new feature I had in mind for Exegesis. It just happened because it was an obvious tool of the trade you'd expect any strategist in a spacewar-themed world to have at his disposal, and because a guy peering over the master plan for what his group is about to jump into is a classic way to start the exposition.

I retrospectively bang my head on desk at the notion it never occurred to me how critical a TacMap would be to make non-blob fleets a viable feature of EVE, and it's quite frightening to consider CCP and the players have been seemingly OK with EVE lacking such an invaluable tool for the past 6 years — short of the various in and out of game 'sovereignty' maps, which are strategic at best, but certainly neither tactically nor sub-tactically usable.


For Pete's sake, X-Wing had a TacMap… in 1992 !

There is a lot of cool stuff old games had that EVE doesn't and should — and I'm not talking about joystick controls — but I'll try to stick to one problem for the moment: situational awareness of the map kind.

A clear picture of your and the enemy's troops whereabouts on the battlefield is not mere eyecandy for a combat group leader: to a large extent the tactical map is the reality of the battle, seen from a strategist perspective.

In a strategic or tactical game you can even expect the map to largely become the territory, and to directly order units to go after a given objective directly from the TacMap, using it as a Commander interface.
I personally would love to see that idea developed in EVE, but even as a strictly informative tool (as opposed to an input interface), TacMaps would seriously change the life of EVE players at large, not just Commanders'.
…and because this is EVE, it would not be all good news, ofc: the candy comes with razor blades fillings.

Because I have no idea how hard it would be to make tactical maps truly interactive and a two-way communication/command interface, I'll split this feature description in two versions: TacMap v1, which only shows you what's happening on the battlefield, and TacMap v2 (Combat Leader edition) which allows to use the TacMap as a control surface to transmit orders and assign objectives to units directly from the TacMap interface.

TacMap v2 being an extension of TacMap v1, it is recommended to read the v1 article before v2 to fully understand what TacMap Combat Leader edition is about.

Friday, November 6, 2009

Please speak after the beep…



This is an automated message: It's off the grid Day for me, see you tomorrow.


Thursday, November 5, 2009

The DOLT chronicles — ep. 1


[Editors's note
: before you rightfully go all WTF? about this following on Exegesis Introduction, there's a half-decent explanation for it (and today's filler being late), right there.]


***


05:48 — Somewhere in lowsec Matari space.

Marz El Duchamp, The Poutine Pie Clan CEO and newly-founded DoubleOreganoLimeToast [DOLT] alliance's grand poo-bah took another long look at the tactical map of the CL4M-1T system in SH-3LF constellation, for what seemed like the thousandth time of the night. His best scout was over there by his lone self, reporting in real-time from this deep-red, out of the way system.
CL4M-1T lay fallow and free from any formal sovereignty claim, along with most of its constellation, by mutual agreement of the two neighborhood alliances, the Elder Sons of Piko [ESPIK] and Tromatile Endeavours [TRENDS], and it was for Marz's fleet to take advantage of this wild lands intel fogginess.



For their first full-scale operation as a true nullsec alliance, DOLT's objective was to insert a seeding party near planet 6 without anyone noticing, and to lay claim on the planet before the night was through. Marz knew full well his alliance plan was daring, maybe overly so, but DOLT had nothing to offer to endear itself to ESPIK or TRENDS unless they first moved into the area, and moving time was due for the Poutine Clan and their alliance partner, the Purple Matarixes. The alliance war chest had been grown to slightly over fifty billions ISK in the last few months to provide for their first colonization foray in nullsec, twenty of which had already been converted into hardware, now waiting to be deployed at his command.

On the tacmap, set to reflect his scouts' situational reports about the SH-3LF constellation, LU-5T1, CL4M-1T and H1-1P0 where still glowing green, meaning no sign of intruders in either system had been detected at this point. Only spotty intel was available about RFC-748, the next system after LU-5T1, as it had been deemed too risky to keep a permanent presence in a sovereign system that could more easily be monitored by ESPIK, whose first sovereign constellation started right after RFC-748 and extended westward. A single Phobos-class heavy interdictor cruiser, flying under civilian colors, was playing the relog dance on request to check for any activity near the LU-5T1 gate. HK-477, the last system in constellation was a dead-end connected solely to LU-5T1, with an average of 6 jumps a day for the past week, and the mostly Euro-timezoned ESPIK were unlikely to raid it at what was nearing 7AM for them, on a Tuesday.

"It's always a Tuesday…" Marz thought with a nervous smile, as his Nidhoggur-class carrier, The Squeamishly Reckless sled out of the Krusual Tribe station into the reddish dawn of a nearly-asleep lowsec system.


***

05:50 — CL4M-1T

DOLT colonization fleet most advanced scout, the Rapier-class recon cruiser Designated Driver III, idled under cloak about 200 klicks from the LU-5T1 gate in CL4M-1T while her captain, Beliot Montcourdi monitored the second and last gate in system (to H1-1P0) on his directional scanner.

Beliot didn't bother with localspotting, which he knew to be largely pointless in a wild lands system. Without the proper scanning equipment on a lunar POS nor the ability to listen in on nearby stargates traffic reports, foreign pilots wouldn't show up in one's local list until they first got in visual range of one of his fleet members, and he was the only DOLT pilot in CL4M-1T, at least for the next couple minutes.

Belio flipped the display of his tacmap to check on the rest of his squad: The Striking Lemurs, which were holding on the other side of this gate, just a few seconds and a jump away. He could now see the six stealth bombers in LU-5T1, maybe half an AU off the CL4M-1T gate, presumably aligned and at speed, invisible and 'deadly to all, and first ourselves' as they liked to say.
He couldn't spot the two Broadswords heavy interdictors at first, but after a few seconds they blinked on his screen, as they dropped to STL speed for a few instants, in the constant warp routine that kept them reasonably safe despite their lack of cloak. The other Lemur scout, a Rapier-class cruiser like Belio's was currently hawking the gate to RFC-477, but he would soon have to break cloak and put his clone on the line for the greater good of DOLTs everywhere…

Voicecomms abruptly broke the silence, Erik's unmistakable Bawlmorese accent sparing him the trouble to identify himself — not that he would ever care to stick to protocol, anyway.
— Hey fat ma-ma, sweady yet ?

— Kinda yeah, I've been looking everywhere, but I can't seem to find any high-slots on this thing… you're sure this is the right boat you gave me ?

— I feel you, bab'boy… ain'a thang I can do, tha…

— …please clear comms, we're up in five, guys ! — there was no confusing this last voice, either: despite her mastery of internet anglospeak, Claudia was leading her Wing from downtown Turin, and she was no foreign student.

***

05:53 — On the edge of highsec Metropolis.

Duke of Tankard, today's freighter pilot, felt he had every reason to be nervous: the Charon freighter — which having the proper skills to fly earned Duke much heckling, despite his claim about this specific proficiency being accidental and none of his fault — had been acquired on alliance funds just a few days earlier, just in time to pick up and convoy to this last highsec stop the three pieces of architecture that now filled almost entirely the monstrous cargo ship.

Despite his being presently stuck in a humongous Caldari boat shaped like a poorly finished paving slab, he was as true a Matari pilot as any DOLT, and one of the few among them with any actual experience of nullsec wars. Most of his escort group, except for Claudia and a couple others, had never seen zero-zero closer than as tourists on a hunting trip, and their practical skills in fleet combat were limited to Empire Factional Warfare.
As much as he personally wished he was flying a combat-ready ship, he hoped they wouldn't get to find out today how different 'true' territorial warfare could be from the Empire paintball games they'd trained in.

He checked his mission brief for the umpteenth time, knowing to be one of the very few pilots in this entire fleet with a nearly complete picture of the plan. …So many things could go wrong that he could see in there, but there was no way around it, and he had to admit Marz and the rest of the DOLT brass had been thorough in prepping this run, about as practical as you'd expect from a bunch of carebears with veneer fangs, but they certainly did their homework.
The titan part, especially, made him feel queasy: the spy paranoia he learned from his former life as a big-alliance FC had become second nature, and the idea that the security of the entire plan depended on a for-hire titan pilot, even a Ragnarok one, was heresy to him.
Live with it, he told himself. There was a good reason he was flying with the Matarixes now, and he did know what he was getting into when he signed up. With a sigh, Duke reached for the push-to-talk key to report his status on the Command channel.

— Duke for Command: all set. Over.

— Copy that, Duke, stand by for go.

— Copy Command, Duke out.

***

05:57 — Somewhere in lowsec Matari space.

Marz scrolled down the fleet list once more, looking for any major gaps or missing names, and it was hard for him to believe how few he could find. That 3/4 of the DOLT had turned out on a monday night was more than comforting: it was energizing to the point he suddenly started feeling confident about their chances of success, maybe for he first time since they started working on the colony project. You spend so much time looking for what can go pear-shaped, you end up forgetting it could actually work out alright, he thought. At this point, he spotted a green dot next to Almar's name in local, and that was all he needed for a wire to go loose in in brain.
Marz opened comms and only realized he had started speaking when the sound of his own voice reached his ears.

DOLTs, this is Marz… If you're not asleep at your keyboard by now, or otherwise afk, I count 164 people in Fleet at the moment. Check it out, this is not a joke… assuming we don't have too many alts on, and even if we do, that's about eighty percent of us accounted for on this op', and I feel for those who're about to miss this party, because today is the first day of our life on the frontier.

For the next couple weeks, we will live in huts, eating rodents and probably fighting off the local warlords for our right to live out in 0.0, and it will hurt, a lot… I'm sure you're ecstatic now that you fully grasp what it is you've voted for three months ago…
Seriously though, this is a big step we're taking today, and within a month or two at most, I'm sure we'll be a very different bunch of people, all of us. We're headed where there are no cozy NPC stations, no market to shop, no agents to hand you your oregano toasts, but you'll find that living day in an out in the same few systems, all together, makes it feel home in no time, like never before.…We will grow trimmer, stronger, maybe not meaner because we're fluffy that way, but hopefully we'll lose some lard, at least in game…
Before we know it, we'll be building our very first outpost and get ourselves our very own constellation. That's the program, and how good we do, starting tonight, will decide how many weeks before we get there…

A few seconds' pause to catch his breath. Here we go. Marz flicked his mike back on:
…In right about now, the main fleet will start moving, you're just a few jumps from some serious eyecandy, and Erik will lead you there.
After that, there's no turning back except by getting podded to empire — make sure your clones are up-to-date, and then assemble with your squad, you have about… well, three minutes before this train leaves the station, and I want it to be a one-way ticket for all of us.
For great justice and toasty glory, let's get busy people ! Marz out.
Not wanting to stay around to hear which it was of either cheering or stunned silence, Marz switched comms to command-channel-only as he typed out a quick line to Almar. His voicecomms were already crackling back to life on the command channel.

— For command, Marz, that was corny.

— Thank you Claudia, I was shooting for unprepared, corny is good by me. Erik, how's your fleet ?

— Hoe dawn… coul'be beddar, m'shure. We'll be good, tha.

— OK, you know where to go… get going, and hold for stragglers at the sun one jump out. First one ready pokes the other.

— Rie-do.

— Claudia for command, are we go ?

— Yup, unleash the frigate fury, dottoressa. I'm bringing the gate in a minute. Duke ?

— Aye.

— Get that sweet Caldari trailer of yours underway, please ?

— Roger. Moving now to align safe, Duke out.

— Lemurs ?

— Belio for command, all clear. Waiting for go on cyno.

— I'll let you know… All get to positions and report. Marz out.

On the private text chat, Almar was getting back to him:

Almar > I'm ready, did you check your POS settings ?
Marz El Duchamp > Double checking… yes.
Almar > See the scout ? <- Fixeret Doze.
Marz El Duchamp > yup. Should I invite him ?
Almar > Her. Just invite me in a separate squad, we're ganged already.
Marz El Duchamp > Coming up.

Seconds later, a new squad appeared in Marz's Wing: Drilling-Zone, with only Almar and Fixeret Doze in it. This part seemed to work as planned… unless that guy was about to catapult the entire DOLT fleet into a logon trap, that is, but Almar's agent had a solid name going for him, which he should be eager to maintain, and unless the highly-rated escrow company that secured the deal was in on it too, Marz reassured himself in the thought there was no profit for anyone in screwing DOLT over. Besides, those people were big leagues players with reputations worth much more than the measly thirty billions ISK Marz had managed to negotiate as collateral…
He sure hoped he wasn't about to lose his alliance's entire cash reserve on a scam.

***
[To be continued]

Wednesday, November 4, 2009

Exegesis


Welcome to Exegesis, ex-Sovereignty 2.0.

In this series of articles, you'll find working bits and ideas mostly lifted from a design document I toyed with from mid-2008 to early 2009, and which I've picked back up and started posting here around the time Dominion was announced.

Exegesis roams wide and far, but at core is focused on re-writing the sovereignty system to make sovereignty building more accessible and attractive, territorial warfare more exciting and tactically deeper, and generally 0.0 life worth your time.
To get there, I focused on two essential things: try to make every role meaningful and interesting (not just for top brass and elite units), and ensure that smarts and dedication can trump raw numbers (of ISK, of grunts, of GiantDicks™).

The end goal is to give a fighting chance to small/medium alliances who want to live and claim space in 0.0, to reward teamwork and creative problem solving, and to support a more diverse, more lively ecosystem of sovereign entities and playstyles  in nullsec.

This post will be updated as I go to reflect new entries in the series.

Here be the list:

Exegesis: all the entries tagged so, to date.

***


Can code, will travel.

If you have read this stuff, think it would be less terrible than Dominion, can code (preferably Java, Flash or anything reasonably platform-agnostic and web-friendly), and have a few hours to spare on BeerWare, I'd like it if you got in touch with me, either in comments or by email.

The idea is to create an interactive demo of Exegesis sovereignty mechanics, or maybe make it a simple 2D webgame, if you feel up to it.

I may be prompt to fill downtime mocking SCRUM bigots, but I'm not averse to rapid prototyping — I just don't like it when the half-baked results of early design brainstorming sessions end up plaguing TQ for years, at the expense of 300k paying customers.

The hopes CCP will reconsider the announced trainwreck that is Dominion solely because of a WebApp demo are slim at best, but there's no harm in trying… necessary triumph, ebil good men, do nothing, you know the song.


Exegesis — Introduction.

[Continued from Dicing the blob (part 1)]


A few days ago I outlined a sovereignty model that I think would give us a more diverse and exciting nullsec map, where alliances of various styles and sizes could prove viable. The core concepts aren't exactly new, at least to me and some other spacenerds who have long been advocating a revamp of 0.0, but with Dominion around the corner, it sounds like it's the last opportunity we'll have to hope for a better nullsec before another 5 years (average cycle length of CCP's iterations on sovereignty).

Sovereignty mechanics that encourage alliances to preserve the wilderness around their colonized space would go a long way toward reducing sovereignty sprawl, and would create plenty of opportunities for skirmishes on the wild lands hunting grounds…which solves about 1/3 of the compound problem that stops so many people from punching their ticket into the frontier life.

The rest can be easily summed in one sentence:
Territorial warfare sucks, especially if you're the defender against a giant blob.
Beyond making you wish you were killing sewers bats to level up in Everquest instead, blob-centric territorial warfare has a nasty habit of making 0.0 colonization a near-suicidal project for any alliance under 2000 members, or without a direct line to the executor of one such, plus a solid set of filthy pictures thereof — believe it or not, that's a luxury many otherwise perfectly good and enterprising alliances lack, and which, in my n00b-lover heart I believe shouldn't be a requirement to get to play the end-game of EVE… paint me pink and call me a carebear now, please.

Thus, dicing the blob is not just about making territorial battles (more?) fun for a greater proportion of 0.0 players, it's also about giving small to medium alliances a fair fighting chance by allowing smart tactics to beat the numerical odds.

Hence, behold… Sovereignty 2.0, a.k.a Exodus-at-last, a.k.a Dominion-my-tushie, a.k.a:

Exegesis

[Fair warning: past this point, the easy mode ends, Exegesis model is a tad more involved than Dominion, and although the resulting in-game experience should have a fairly smooth flow to it, there are quite a few moving pieces underneath to make this possible.]

First, let me introduce my s33krit weapon to you: Commandeering !
Ouchie… yeah, it's a bit cold, sorry. It'll hurt but for a minute.

Commandeering (a.k.a FoF Tuning) is a non-destructive PvP mechanic, which allows you to capture enemy ships and space assets such as secure containers and other anchorables, POS control towers and Outposts, and seize control of stargates, acceleration gates and other Sovereignty Structures.
Not only does it open a wealth of opportunities for cool PvP such as convoy escort/attack, it is the pivotal element of a new, better sovereignty warfare system.

Gameplay-wise, it falls somewhere between EW jamming and capacitor neutralization/transfer: high-slots utility modules (FoF Tuners) allow you to project signal on a target, precisely tuned to your Alliance/Corp/Personal frequency.
  • As you pump out megawatts of tuning power into your poor victim's electronics, it drains the target's current tuning charge, assuming your FoF frequency and theirs differ… and if they match, it's still pretty much like cap/shield transferring mechanics: you boost them up to their maximum possible charge.

  • After you manage to suck your target dry (Neutralize it), your tuning signal starts charging them back up, only now it's on your FoF frequency instead of theirs.

  • The end result, if you push enough signal through to bring the target back up to its 'nominal charge level' is you hijack its controls, and Commandeer it.

  • Of course, the target doesn't have to be an entirely hapless victim: most potential targets enjoy some kind of passive recharge to their tuning, and it is possible for other players to counter your Neutralization/Commandeering attempts by boosting or Neutralizing your target with their own FoF Tuners.
It gets more brainy, but that's the gist of it, and it can do for the purpose of this article, so we'll leave it at that for now.

Why do we need yet another type of weapon/warfare ?

Glad you asked: because it's non-destructive, and that makes a big difference for sovereignty warfare. I also personally am all giddy at the prospect of commandeering enemy ships by forcibly ejecting their pilots after bringing them into structure — something I feel has been sorely missing from EVE like, forevah — but that's for a separate discussion.

Non-destructive PvP creates tactical/strategic parameters one can't just wish away through the simple invocation of obscene firepower, which is about the only thing a blob knows how to do. If you can't gank your way, every step of the way, to a railed victory, and you actually have to keep your eyes on many different goals at once, you soon realize you'll need more than a few brains to do the job(s), brains that should be granted some autonomy in how to play the ball… see where I'm going with that ?

FoF Tuning is straightforward and intuitive enough to entail almost no learning curve for pilots, yet brings an all-new dimension to how you think about seizing territory: because the goal is to affirm your superiority over multiple hotspots that can't simply be erased one after another with DPS (as is the case with POSes, or HUBs, or Disruptor Fields), you actually have to occupy those landmarks, and if you're in the habit of not going anywhere without your 800 blobmates, you'll find that the lot of you always ends up covering only a fraction of the playground you should.

Summarily, you'll now have to shoot hostile ships where they are messing with your stuff, instead of blowing up barns while the enemy's asleep on the other side of the Date Line.


Territorial warfare, Exegesis-style.
Besides the introduction of FoF Tuning, the three most significant new factors in Exegesis tactics, compared to Apocrypha or Dominion are the introduction of Planetary Sovereignty, real-time Occupancy, and dynamic, progressive sovereignty modifiers.

Planetary Sovereignty:

Where System Sovereignty is the standard unit of deep-space nation building, Planetary Sovereignty constitutes the finer level of territorial granularity that brings a new dimension to battles for solar-scale control: more than one faction/alliance can now benefit from active sovereignty (and associated defensive perks) simultaneously, inside a single solar system.
This simple (?) change allows to significantly boost the defensive benefits attached to each sovereignty level, making initially harder to gain a foothold in a well-defended system, but rewarding committed Challengers with a defensible staging point from which to take their next move.
The requirement to consolidate gained ground during an invasion also opens the Challengers to counter-strikes, making this much harder to rely on traditional scorched-earth strategies that overly favored those Challengers who could bring the most numbers to the battlefield without committing to defense.

Real-time Occupancy:

The ability to maintain, challenge or seize sovereignty in Exegesis is tied to one's ability to assert Occupancy over the coveted space by Controlling Sovereignty Tokens (through FoF Tuning).
There are no hard-timers restrictions on how fast one can seize or lose Tokens to meet of fail Occupancy requirements, but speedbumps exist to mitigate timezone and initiative advantage, in the form of nested Occupancy requirements that limit the capacity of a party to beeline for the heart of the enemy's sovereignty (see below).
Because most Sovereignty Structures (Tokens and Flagpoles) can passively recharge as long as sovereignty benefits are in effect, it is generally unpractical to simply pwn and move on when attempting to seize sovereignty — building Occupancy really entails occupation.

The most pedestrian Sovereignty Tokens are stargates, a number of which must be seized (or at least denied to other contenders) via FoF Tuning to gain access to a Sovereignty Flagpole of interest.
Stargate conquest comes with a twist in that one often has to work both sides of a jump simultaneously to gain Control of stargates — it is not possible to attempt Commandeering of a stargate while its sister (on the other side of the jump) is under the Control of a different faction.

Balance between Challengers and Defenders is achieved in large part thanks to asymmetric Occupancy requirements for any given goal, depending on each contender status relative to the coveted Sovereignty Flagpole (Owner/Defender, Controller or not, etc.) — this grants the model extra flexibility for easy tweaks to the balance during testing and after release.

Dynamic, progressive sovereignty modifiers:

Starting at Planetary Sovereignty level and going up from there, sovereignty benefits act both as boosters to the Defender(s) fighting abilities and as filters that help break the onrush of the enemy.

Most Sovereignty Flagpoles are now found in player-colonized deadspace complexes (Planetary and Solar Dungeons), which must be explored to reach the Dungeon Control Center (DCC) chamber before the DCC can be Neutralized or Commandeered.

Travel from a Dungeon room to the next is done via player-built acceleration gates known as Dungeon Mass Drivers (DMD) which are hardly destructible, yet can be used by pilots of any faction who manage to seize Control of the DMD (or enjoy a Defender right-of-way perk), provided their ship class is not restricted by applicable Sovereignty Immunities.

Basic sovereignty benefits, from Planetary level and up include:
  • boosts to your faction's ships Sensor Resolution (faster lock) and FoF Tuners' efficiency,
  • a blanket boost to all your space assets' (ships, structures, anchorables, Outposts) FoF Tuning strength (how much maximum Tuning charge they can hold),
  • …and to their Passive Tuning Recharge rate (where applicable).
Various levels of sovereignty benefits combine in beautiful an intricate ways.

Sovereignty and Occupancy not only affect your faction's ships and Sovereignty Structures attack/defense in FoF Tuning, or determine how many hotspots your group must cover at once to achieve its objectives, but they also inform which ship classes can reach any given Sovereignty Flagpole, and (to some extent), what kind of trouble they could run into on the way.

Other notable stuff:

4-tiered Sovereignty: Planetary, Solar, Constellar, Regional.
  • Planetary Sovereignty enables to control an existing outpost around the planet, and builds up Occupancy for Solar sovereignty, in addition to other Planetary Defender benefits.

  • Solar Sovereignty allows to build an outpost per system (on a Controlled Planet), and enables forcefield charge on outpost(s) owned by the Solar Defender. It also comes with Solar Defender benefits and contributes to build Occupancy for Constellation Sovereignty purposes.

  • Constellar Sovereignty allows the construction of a second outpost in the Constellation Capital solar system after all systems in Constellation are doted with one Outpost (not mandatory, and can be gamed by design by rotating capitals).
    Constellation Sovereignty also triggers Neighborhood rules in addition to Constellar Defender benefits, and contributes to Occupancy towards Regional Sovereignty.

  • Regional Sovereignty allows the Regional Defender to deploy an extra outpost in every system under its sovereignty (up to 3 in Constellar Capital Systems), and triggers Heartland Takeover Immunity in addition to other Regional Defender Benefits.
    Regional Defender's sovereign constellation connected to nothing but same-faction sovereign Constellations can still be lost, but the Challenger won't be able to claim Constellation Sovereignty over it until at least one connecting constellation is lost to the Regional Defender.

Outposts:
  • Can behave either/both as Sovereignty Flagpoles (when they're Constellation or Regional Capital) and Sovereignty Tokens (as they contribute to protect their respective planet from capture).

  • Can now raise a forcefield (with system sovereignty) and operate defensive modules, both of which cost fuel (besides applicable ammo supplies) to remain active.

  • Now with a self-destruct button ! Sounds crazy, but there could be real reasons to want to get rid of an outpost in Exegesis (due to the impact on Effective Security Status). No worries though, this one has a couple (long) hard-timers, and can be cancelled before it goes boom.

Dynamic Environment:

Effective Security Status is but a (big) part of the environmental changes introduced in Exegesis. Building up sovereignty and infrastructure may screw up with the local PvE resources, but it has the weird side effect of favoring the presence of more domestic species of NPCs, notably in Dungeons (see below).
Among the few PvE benefits of a high sovereignty modifier are the increased odds of Agents from NPC corporations setting up shop in your local outposts (if you allow them to), and higher-than-average chances to stumble on long-range wormholes (typically exiting far away, and deep in the red).
On the flipside, the odds of a long-range wormhole 'coming' from remote, very low Effective Sec Status and exiting into your cozy core systems are proportional to your own local Effective Sec Status modifier — expect many unannounced visitors of the non-NPC kind.

Dungeons:

Starting as a beacon in a Cosmic Anomaly found within 4 AU of their respective celestial body, Planetary and Solar Dungeons can be colonized by player alliances by deploying Dungeon Mass Drivers (DMD) to explore their successive rooms before a Dungeon Control Center (DCC) can be erected in the deepest chamber of the mini-complex.
DMDs and DCCs are permanent structures that become virtually indestructible while a Dungeon is Owned by any faction — they can be Neutralized and/or Commandeered by any faction's pilots who meet Occupancy requirements.
  • DMDs will activate for their Owner faction pilots at any time, regardless of their Control state, while foreign ships must force their way through by Commandeering (or alternatively Hacking) them. Neutralizing and Commandeering DMDs is subject to Occupancy requirements. Seizing control of a DMD allows a foreign faction to activate it, but doesn't grant Ownership, which is inherited from the local DCC. Depending on applicable sovereignty modifiers, DMDs may restrict passage to certain classes of foreign ships, even if properly Commandeered.

  • DCCs are Sovereignty Flagpoles, and grant Planetary or Solar Ownership and Sovereignty to their Controlling faction. They burn special fuel pellets (manufactured from ice products and trade goods), and will revert to a Neutral state (but not Abandoned) if they run dry.

  • Planetary Dungeons are 3 rooms deep, including the entrance Space Anomaly and the DCC chamber. It takes two DMD warps to reach the DCC chamber from open space.

  • Solar Dungeons comprise a potential of 4 to 9 rooms (depending on planet count in system), not necessarily arranged in a chain, some of which can be left out (unconnected) at the colonizers' discretion.
    • Any direct path from the entrance deadspace pocket to the DCC chamber must range between 3 and 5 DMD warps.
    • Rooms can be set up as dead-ends, but no two rooms can be connected together both ways by DMDs (no 2-warps round trips).
    • Any room can fit up to 3 'exit' DMDs, and be reached from no more than 2 rooms.
  • Dungeons are home to a local fauna of drone-type NPCs, which can adopt a variable stance towards visitors, depending on applicable sovereignty modifiers, ranging from hostile to neutral or even friendly.
    The quantity and type of Dungeons drones scale dynamically depending on the pilots entering their room.
    Solar Dungeons, in addition to drones, may sport player-deployed sentry turrets and EW around their DMD(s), fueled from the local DCC CPU/Grid and fuel (requires Constellation and Solar sovereignty combined). These defenses inherit Ownership from the DCC, but can potentially be Neutralized or Commandeered by third-parties to be turned away/against the Dungeon Defenders.
Neighborhood rules: Cosmology matters in Exegesis ! …sorta.

Neighborhood rules (Nr) simply mean the sovereignty status of your surroundings have an impact on local conditions.

In their simplest form, Nr dictate that you can't Commandeer a stargate while its sister (on the other side of the jump) is Controlled or otherwise Tuned positively for another faction ; thus you must first Neutralize both, and only then can try and Commandeer the stargate you want, while making sure to keep at least some FoF Tuning going on the other gate to 'plug the tub'.
Fun fact: Nr apply to border zones of NPC space, too, so you may have to hijack lowsec/nullsec gates under the nose of the local Navy, which certainly won't mind… certainly.

On a broader scale, Constellation Sovereignty gives the Constellar Defender a boost to the tuning strength of all its assets in the constellation, even in systems that are Abandoned or under third-party sovereignty.
Sovereignty Tokens and Flagpoles belonging to the Constellar Defender also enjoy a bonus to their passive recharge rate, including every stargate in the constellation that connects to a system (in or out of constellation) belonging to the Constellar Defender (stargate ownership in Abandoned systems defaults to the Constellation Defender's if available).

The BigMap™ expression of Nr is Heartland Takeover Immunity, which requires Regional Sovereignty (rather tricky to claim and maintain), and prevents a Challenger from establishing a Constellation Capital in any constellation entirely surrounded by Sovereign Constellations belonging to the Regional Defender (that doesn't stop a Challenger from lifting the Regional Defender's Constellation Sovereignty, only from re-claiming it right away).

***

OK, I can see you're all dizzy already, so we'll take a short recess, and I'll see you after the break for some examples.