Difference between revisions of "User:Alto deraqwar"

From EVE University Wiki
Jump to: navigation, search
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=WORK ON GRAVITY WELL WIKI PAGE=
+
=WORK ON CITADEL VULNERABILITY PAGE=
  
<div style="float: right; clear:right; margin-left: 1em; margin-bottom:1em; font-size:90%">__TOC__</div>
 
Gravity Well is a free-port Fortizar Class citadel in [http://evemaps.dotlan.net/system/Boystin Boystin] which was built by members of Project Solitude for use by Eve University members and residents of the Solitude region.
 
  
As a free-port Gravity Well provides market, reprocessing, and cloning facilities to the Solitude region along with corporation hangers for Eve University members. Being in Boystin Gravity Well has easy access to the current market hub house in the NPC station of [http://evemaps.dotlan.net/station/Boystin_V_-_Moon_6_-_Federal_Intelligence_Office_Assembly_Plant Boystin V - Moon 6 - Federal Intelligence Office Assembly Plant]; along with this the Low-Sec system of [http://evemaps.dotlan.net/system/Pertnineere Pertnineere] next door allows easy access for Jump Freighters.
+
{{structures}}
 +
'''Vulnerability''' is a game mechanic used by most deployable structures to encourage large, planned fleet engagements and enable both attacking and defending groups to more effectively and fairly engage in structure warfare.  
  
Gravity Well finished anchoring at 00:15 on August 16 YC 118 and was the second citadel built and anchored by Eve University after [[Azmo's Large Innuendo]]. Due to restrictions around control permissions, access rights and to keep better track of tax income Gravity Well is currently held by the [[Ivy League Hall of Residence]] rather than the University directly.
+
== Vulnerability hours ==
== Services ==
+
In the case of Citadels and Engineering Complexes the structure owner schedules a set of vulnerability windows over the week for each of their structures. This schedule is set for the first time when the Structure is deployed and will be it's schedule for @@@@@NEED TO CHECK; CAN I SCHEDULE HOURS OUTSIDE OF CURRENT WEEK FOR FIRST WEEK OF DEPLOYMENT@@@@@  Each window is a minimum of 1 hour in length and must be scheduled to start at a whole hour on the EVE clock. The number of hours which must be scheduled for each week depends on the size and type of structure.
=== Market ===
 
Gravity Well has a market module installed; this allows the purchase and sale of items from the citadel. Brooker fees for this market are kept deliberately low to encourage market activity. Uni members are strongly encouraged to make use of this market to help establish and maintain Gravity Well.
 
=== Cloning Services ===
 
Gravity Well has a cloning module installed; this allows capsuleers to install [[jump clone|jump clones]] and [[medical clone|medical clones]] in the citadel. Members of Eve Uni can install clones for free.
 
=== Reprocessing ===
 
Gravity Well currently has [[reprocessing]] facilities. It is expected that these will be removed once Industrial Arrays take over this functionality.
 
=== Corporate Offices ===
 
Eve University has corporate offices in Gravity Well; this allows corporate hangers for University members. Unfortunately current Eve mechanics do not allow corp members to [[Medical_clone#Remote_installing_clones|remote install a medical clone]] to a citadel.
 
  
== History ==
+
{| class="wikitable" border=0 align=center
Gravity Well was built by the members of the Project Solitude campus as both an experiment to investigate the construction; use and function of citadels and as a uniting project for members.
+
! Type !! Name !! Size !! Required number of vulnerability slots per week
 +
|-
 +
| Citadel || Astrahus || Medium || 3
 +
|-
 +
| Citadel  || Fortizar || Large || 6
 +
|-
 +
| Citadel || Keepstar|| X-Large || 21
 +
|-
 +
| Engineering Complex || Raitaru || Medium || 9
 +
|-
 +
| Engineering Complex || Azbel || Large || 18
 +
|-
 +
| Engineering Complex|| Sotiyo || X-Large || 36
 +
|}
  
=== Origins ===
+
== Vulnerability states ==
Late in 2015 The idea of a uniting project for the members of Project Solitude was one of the outcomes of discussions inspired by [[Aaric Novigrad|Aaric Novigrad's]] [http://forum.eveuniversity.org/viewtopic.php?f=218&t=92715 "Solitude State of the Union"] post. Leading on from this [[Sally Digital]] noted that the the idea of a communal [[Player_Owned_Starbase|POS]] had often been kicked around by members of Project Solitude but quickly discarded due to the complexity and restrictions of POSes. However the announced introduction of citadels by CCP presented "the opportunity for a massive communal project to build, deploy and maintain one of these structures for ourselves, for the benefit of our fellow Solibro’s and, possibly, the wider Solitude community." At the same time the name "Gravity Well" was coined as a title for the proposed project.  
+
During their scheduled vulnerability windows structures can be attacked and pushed into reinforce if sufficient damage is applied. However damage to these structures have a cap on the maximum DPS allowed. Therefore there is always a minimum amount of time required to reinforce them.
  
The following discussions agreed that the construction of a citadel in Solitude by members of Project Solitude was desirable. However a number of factors had to be considered including feasibility; location; type and function of the citadel. Along with this a major point of discussion was who would end up "holding" the Citadel. At the time little information had been released on citadels so most discussion went into a hiatus. However the idea that Project Solitude should and would establish a Citadel in Solitude had been agreed and that once more information was released the campus would undertake the project.
+
{| class="wikitable" border=0 align=center
 +
! Type !! Name !! Size !! DPS Cap !! Minimum time to reinforce
 +
|-
 +
| Citadel || Astrahus || Medium || 5000 || 24 Minutes
 +
|-
 +
| Citadel || Fortizar || Large || 15000 || 24 Minutes
 +
|-
 +
| Citadel || Keepstar|| X-Large || 75000 || 24 Minutes
 +
|-
 +
| Engineering Complex || Raitaru || Medium || 5000 || 16 Minutes
 +
|-
 +
| Engineering Complex || Azbel || Large || 15000 || 16 Minutes
 +
|-
 +
| Engineering Complex|| Sotiyo || X-Large || 75000 || 16 Minutes
 +
|}
 +
NB - While similar sized Citadels and Engineering Complexes have the same damage cap; Engineering Complexes have lower HP per layer therefore take less time to reinforce.
  
=== Planning ===
+
== Vulnerability hours ==
Early in 2016 with the majority of citadel information having been released and the announcement that citadels would go live with the April release actual planning for the construction of the citadel begun. While the location; name and holding corp were still to be determined these would not prevent construction as under citadel mechanics the citadel itself could be constructed and later [[Anchoring Objects in Space|anchored]]. What had to be confirmed though was the type/function of the proposed citadel. Internal discussion lead to the conclusion that to allow the greatest functionality at a cost which was both affordable and defend-able by members of Project Solitude a Fortizar class citadel should be constructed. 
+
'''Vulnerability hours''' are the periods that the structure can be attacked with each slot representing one hour. The amount of hours needed differ between each size of citadels and are managed in the [[Structure Browser]] window.
  
=== Construction ===
 
In the mid period from April 2016 till July 2016 resource gathering activities were undertaken by the members of Project Solitude. These included shared can mining fleets to gather minerals; weekly missioning fleets for required salvage and many members of the campus turning their [[Planetary_Interaction|Planetary Interaction]] chains over to produced the needed PI products. Isk over-flow from these activities was used to fill up any shortfalls in materials.
 
  
Also during this period the University firmed up it position on citadels including the introduction of a Director of Structure and Structure Officers to oversee and coordinate all structures across the University. This lead to the appointment of [[Talman Drak]] as the first Structure Officer for Project Solitude. Along with him Project Officer Exorcist Wraith, Pemluan Katelo and Tek Sharax and Project Member Angella Montjoie were instrumental in coordinating the fleets and construction of the citadel.
 
  
=== Anchoring ===
 
[[Image:4fd830c710a183a52e7cd2a845da241a.jpg|thumb|left|128px]]
 
One of the riskiest points of launching a citadel is the dangerous final 15 minute vulnerability window at the end of the anchoring. Due to this anchoring of Gravity Well was started with very little fanfare by a safe alt corp at 00:15 August 15th 2016 with anchoring completing 24 hours later at 00:15 August 16th 2016.
 
  
At then end of anchoring Gravity Well was then transferred to the Ivy League Hall of Residence for future safe keeping.
+
Upon entering a predefined Vulnerability slot the citadel will now be attackable. Citadels cannot be affected by any form of Electronic Warfare and will limit the amount of damage it can take per second as defined by its size. This damage cap cannot be exceeded and will result in decreased damage or zero damage dependent on attacking force.
  
{{Solitude_Navbar}}
+
Once damage has been taken the Citadel will begin a 15 minute repair timer that upon completion will fully repair the Citadel this timer however is paused while taken sufficient damage and should the Citadel reach 0% Shield or Armor (dependent on current stage) it will enter a Reinforcement state.
 +
 
 +
Reinforcement ends at different times dependent on what stage the siege is at. When Shields are reduced to 0% a 24 Hour reinforcement cycle takes place during which the Citadel will be invulnerable. Should Armor be reduced to 0% a 6 Day Reinforcement occurs (The exception to this however are all Citadels located in a Wormhole. These timers will end after 24 hours)
 +
 
 +
Once the reinforcement state ends a new repair timer will begin where if successful will fully repair the Citadel and will no longer be attackable until the next vulnerability slot. Additionally a Citadel that has been forced into a reinforcement state will not follow the vulnerability timers until it has been successfully defended and a repair cycle completes.
 +
 
 +
*To pause the repair timer the Citadel must receive damage that is at least 10% of the damage cap.<br />
 +
*Standup Warp Scrambler can only function while a citadel is vulnerable.<br />
 +
 
 +
While vulnerable the current status of the Citadel is shown on the damage indicator.
 +
<gallery>
 +
File:Citadel3.jpg|Citadel damage indicator
 +
</gallery>
 +
 
 +
The outer grey/red circle shows the current damage. It has one section for shield (top), armor (lower left) and hull (lower right). In each section a dot represents 1/12th of full health. A grey dot means intact, a red dot means damaged. So in our example there are only 2 grey dots left on the lower right section, which means the Citadel has only about 17% (2 x 1/12 x 100%) hull left.
 +
 
 +
The inner yellow circle shows the repair timer. In our example it has about 2/3 of the 15 mins left. One can hover with the mouse over the Citadel damage indicator and it will display how much time is left on the repair timer and whether it is running or paused.

Latest revision as of 01:35, 1 May 2017

WORK ON CITADEL VULNERABILITY PAGE

Vulnerability is a game mechanic used by most deployable structures to encourage large, planned fleet engagements and enable both attacking and defending groups to more effectively and fairly engage in structure warfare.

Vulnerability hours

In the case of Citadels and Engineering Complexes the structure owner schedules a set of vulnerability windows over the week for each of their structures. This schedule is set for the first time when the Structure is deployed and will be it's schedule for @@@@@NEED TO CHECK; CAN I SCHEDULE HOURS OUTSIDE OF CURRENT WEEK FOR FIRST WEEK OF DEPLOYMENT@@@@@ Each window is a minimum of 1 hour in length and must be scheduled to start at a whole hour on the EVE clock. The number of hours which must be scheduled for each week depends on the size and type of structure.

Type Name Size Required number of vulnerability slots per week
Citadel Astrahus Medium 3
Citadel Fortizar Large 6
Citadel Keepstar X-Large 21
Engineering Complex Raitaru Medium 9
Engineering Complex Azbel Large 18
Engineering Complex Sotiyo X-Large 36

Vulnerability states

During their scheduled vulnerability windows structures can be attacked and pushed into reinforce if sufficient damage is applied. However damage to these structures have a cap on the maximum DPS allowed. Therefore there is always a minimum amount of time required to reinforce them.

Type Name Size DPS Cap Minimum time to reinforce
Citadel Astrahus Medium 5000 24 Minutes
Citadel Fortizar Large 15000 24 Minutes
Citadel Keepstar X-Large 75000 24 Minutes
Engineering Complex Raitaru Medium 5000 16 Minutes
Engineering Complex Azbel Large 15000 16 Minutes
Engineering Complex Sotiyo X-Large 75000 16 Minutes

NB - While similar sized Citadels and Engineering Complexes have the same damage cap; Engineering Complexes have lower HP per layer therefore take less time to reinforce.

Vulnerability hours

Vulnerability hours are the periods that the structure can be attacked with each slot representing one hour. The amount of hours needed differ between each size of citadels and are managed in the Structure Browser window.



Upon entering a predefined Vulnerability slot the citadel will now be attackable. Citadels cannot be affected by any form of Electronic Warfare and will limit the amount of damage it can take per second as defined by its size. This damage cap cannot be exceeded and will result in decreased damage or zero damage dependent on attacking force.

Once damage has been taken the Citadel will begin a 15 minute repair timer that upon completion will fully repair the Citadel this timer however is paused while taken sufficient damage and should the Citadel reach 0% Shield or Armor (dependent on current stage) it will enter a Reinforcement state.

Reinforcement ends at different times dependent on what stage the siege is at. When Shields are reduced to 0% a 24 Hour reinforcement cycle takes place during which the Citadel will be invulnerable. Should Armor be reduced to 0% a 6 Day Reinforcement occurs (The exception to this however are all Citadels located in a Wormhole. These timers will end after 24 hours)

Once the reinforcement state ends a new repair timer will begin where if successful will fully repair the Citadel and will no longer be attackable until the next vulnerability slot. Additionally a Citadel that has been forced into a reinforcement state will not follow the vulnerability timers until it has been successfully defended and a repair cycle completes.

  • To pause the repair timer the Citadel must receive damage that is at least 10% of the damage cap.
  • Standup Warp Scrambler can only function while a citadel is vulnerable.

While vulnerable the current status of the Citadel is shown on the damage indicator.

The outer grey/red circle shows the current damage. It has one section for shield (top), armor (lower left) and hull (lower right). In each section a dot represents 1/12th of full health. A grey dot means intact, a red dot means damaged. So in our example there are only 2 grey dots left on the lower right section, which means the Citadel has only about 17% (2 x 1/12 x 100%) hull left.

The inner yellow circle shows the repair timer. In our example it has about 2/3 of the 15 mins left. One can hover with the mouse over the Citadel damage indicator and it will display how much time is left on the repair timer and whether it is running or paused.