Samki Licui
Eternal Beings
RUST415
7
   |
Posted - 2015.10.27 00:31:00 -
[1] - Quote
Introduction: I am Samki Licui (a.k.a. Kodaw Kuori, Balta Katei). I have participated in Dust 514 and EVE Online for over a year now. I regularly provide EVE support for a Dust 514 corporation, Eternal Beings, in which I am a director. I am familiar with Planetary Interaction. I have also posted this proposal to the EVE Online forums here.
Summary: My idea is how to extend Planetary Conquest gameplay to potentially all lowsec and nullsec regions. The implementation includes an expanded EVE-Dust interaction mechanism to permit transport of Dust clones by EVE players (see 1.a, 1.d). This new clone transport mechanic (see 1), which requires EVE player participation, is required to reach the farthest reachest of null security space. I suggest implementation of other submechanics to inhibit stagnant no-risk-high-profit situations (see 4) and to promote meaningful and satisfying conflict around the new districts (see 1.j, 2, 3).
1). New transport mechanic: Clone Pack deployable
1.a) Allow planetary districts to launch clones into EVE
space as a Clone Pack deployable which can be
hauled by EVE players. This will be the only method
for transferring clones into and out of nullsec
systems.
1.b) Clone Pack deployable can be deployed within
10km of any district satellite (like a mobile depot).
Deployment time required is:
1.b.I) 3 minutes for Clone Pack S (150 clones)
1.b.II) 10 minutes for Clone Pack M (400 clones)
1.b.III) 20 minutes for Clone Pack L (1600 clones)
1.b.IV) 40 minutes for Clone Pack XL (6400
clones)
1.c) Deployment time can only occur within the
planetary district's selected reinforcement period
(ex: XL deployment will fail unless started in first
20 minutes of reinforcement period).
1.d) If successfully deployed, Clone Pack descends to
planet surface and a new PC battle is scheduled
1.e) Clone Pack deployable can be seen on D-scan
and type displays in space how large a clone
transfer is being made (S: 100, M: 400, L: 1600
XL: 6400).
1.f) The size of the Clone Pack launched into space
will be the minimum size required to hold the
number of clones being removed from the district.
1.g) Clones can be removed from the launched
Clone Pack (since it is just a deployable with a
cargo bay) and handled like any other EVE item.
As such, clones can be placed into Clone Packs
of smaller or larger sizes (S, M, L, XL).
1.h) Clone Packs deployables (not the clones they
may contain) can be built and traded on the market.
1.i) Clones may be bought/sold on the market.
1.j) Objective: The purpose of requiring Clone Packs
to be deployable at the district satellite only during
district reinforcement timers is to ensure the
defending district owner has a well-defined time
and place in which they can mobilize their EVE
assets to defend themselves.
2) New submechanic 1: clone sales for PI production
bonus.
2.a) Mechanism: District holders can choose to sell
clones to NPC planetary governments for a
temporary bonus in resource extraction rates.
3.b) Alternate mechanism: District holders can
choose to sell clones in exchange for certain
amounts of planetary commodities (bypassing
legacy code changes involved in PI resource
extraction rates).
2.c) Objective: Incentivize occupiers of nullsec systems
to populate planets districts with clones that may
be attacked by other nullsec corporations.
3) New submechanic 2: clone transfer through highsec
3.a) Mechanism: Clone loss rate when transferring
clones from one lowsec system to another via
highsec jumps is minimal (0.1% per highsec jump).
3.b) Objective: Reduce the effective distance
between otherwise isolated/far-flung lowsec
systems to increase the amount of potential
conflict between district-holders.
3.c) Note: If Clone Pack transfer is not implemented,
this submechanic may still permit increase in
number of planetary districts.
4) New submechanic 3: district clone attrition
4.a) Mechanism: District clone count reduced by
10% of maximum district clone capacity at the start
of every reinforcement period if the holding
corporation's daily Command Point income is
less than 1000.
4.b) Objective: Prevent corporations from farming
planetary districts without risk or effort.
My proposal doesn't address potential POS / Citadel bonuses in order to keep this proposal simple. Obviously, all the numbers I have proposed are only proposals. I searched this subforum for Dust clone transfer mechanics and I did not see any relevant threads in the past two years (the closest in relevance were threads about items enabling clone soldier boarding parties).
|