Difference between revisions of "User:Lord Finnbar/Wormhole Community Etiquette"

From EVE University Wiki
Jump to: navigation, search
 
(7 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
{{Wormhole Links}}
 
{{Wormhole Links}}
  
==Being in Fleet==
+
== Rules and Feedback ==
 +
We are aware that Eve University brings together people of many backgrounds and skill levels. We all must work together to make Eve University and WHC the best they can be. Community Coordinators welcome questions on processes and fits (it’s how we learn!) as well as constructive criticism on rules. Additionally, Community Coordinators will provide instruction or correction regarding campus rules and etiquette which should be adhered to. Any concerns or issues can be raised to Community Coordinators, [[Student Advocates]], and/or Uni leadership. Excessive arguing or ranting in comms or Discord is to be avoided as there is always a better way to discuss topics and share your opinion.
 +
 
 +
== Being in Fleet ==
 
If you are in the WHC chain, always be in fleet. If there is no WHC Standing fleet, create one! See [[Standing Fleet]] for details on how to get the settings correct and [[Standing_Fleet#Community_Standing_Fleet_MOTDs|Standing Fleet MOTDs]] for the MOTD.
 
If you are in the WHC chain, always be in fleet. If there is no WHC Standing fleet, create one! See [[Standing Fleet]] for details on how to get the settings correct and [[Standing_Fleet#Community_Standing_Fleet_MOTDs|Standing Fleet MOTDs]] for the MOTD.
  
*Do not go AFK for any extended period of time while in fleet.
+
* Do not go AFK for any extended period of time while in fleet.
**If you get ninja-bossed while AFK, fleet will not be advertised. Leave fleet if you need to be AFK for an extended period of time.  
+
** If you get ninja-bossed while AFK, the fleet will not be advertised. Leave fleet if you need to be AFK for an extended period of time.  
*Do not set fleet advert to automatically update fleet advert on boss change. This can automatically swap boss to an AFK person in fleet and will cause the fleet to become unusable.
+
* Do not set fleet advert to automatically update fleet advert on boss change. This can automatically swap boss to an AFK person in fleet and will cause the fleet to become unusable.
*If you are docked but AFK, you show as present in our structures which may lead potential content to think we are able to engage with more numbers than we are actually able to field.
+
* If you are docked but AFK, you show as present in our structures which may lead potential content to think we are able to engage with more numbers than we are actually able to field.
*If you are the fleet boss and need to leave/go AFK, pass it to someone who is going to be online. Do not log off before handing off Fleet boss, as it will be given to a member of the Fleet who may not be paying attention at the time.
+
* If you are the fleet boss and need to leave/go AFK, pass it to someone who is going to be online. Do not log off before handing off Fleet boss, as it will be given to a member of the Fleet who may not be paying attention at the time.
**Passing boss gives a session change timer—surprise session change timers can get people killed. It is good practice to ask the person who says they can take fleet boss if they are ready for it.
+
** Passing boss gives a session change timer—surprise session change timers can get people killed. It is good practice to ask the person who says they can take fleet boss if they are ready for it.
**If no one is able to take boss it is best to disband the fleet.
+
** If no one is able to take boss it is best to disband the fleet.
*If for some exceptional reason, you cannot be in Fleet, let people who are in Fleet or Mumble know you are there.
+
* If for some exceptional reason, you cannot be in Fleet, let people who are in Fleet or Mumble know you are there.
  
==Being in Comms==
+
== Being in Comms ==
 
Being in Mumble is highly recommended. Talking is much faster at conveying information than typing it out in fleet. Intel is posted into fleet, but by not at least listening to Mumble can result in losing a ship when someone calls it out.
 
Being in Mumble is highly recommended. Talking is much faster at conveying information than typing it out in fleet. Intel is posted into fleet, but by not at least listening to Mumble can result in losing a ship when someone calls it out.
  
==Undocking==
+
== Undocking ==
 
Before undocking in Cake you must be in fleet. It is good practice prior to undocking to first ask if there is ongoing content. You don’t want to start jumping through the chain in your DST only to find bubble with hostiles or undock only to scare off a target someone is hunting. Contribute to content, don’t kill it!
 
Before undocking in Cake you must be in fleet. It is good practice prior to undocking to first ask if there is ongoing content. You don’t want to start jumping through the chain in your DST only to find bubble with hostiles or undock only to scare off a target someone is hunting. Contribute to content, don’t kill it!
  
==Announcing Activations==
+
== Announcing Activations ==
 
Always call out activations for Alpha, Bravo, any hole within 2 jumps of Cake, and any wormholes into or out of a system you know/suspect contain other WHC members. Wormholes make a sound and have a visual effect. We use this to determine when we need to prepare for a fight, so announcing activations lets those watching a wormhole know that the activation is friendly and not a sign of an imminent fight. It is also best practice to call out activations further down the chain as this gives others in fleet a better understanding of where people are in chain.
 
Always call out activations for Alpha, Bravo, any hole within 2 jumps of Cake, and any wormholes into or out of a system you know/suspect contain other WHC members. Wormholes make a sound and have a visual effect. We use this to determine when we need to prepare for a fight, so announcing activations lets those watching a wormhole know that the activation is friendly and not a sign of an imminent fight. It is also best practice to call out activations further down the chain as this gives others in fleet a better understanding of where people are in chain.
*If you are activating it: Call out “Friendly Alpha”, “Friendly Bravo”, “Friendly 1 Z1”, etc. in Mumble.
+
* If you are activating it: Call out “Friendly Alpha”, “Friendly Bravo”, “Friendly 1 Z1”, etc. in Mumble.
*Depending upon the circumstances, you may write it in Fleet, commonly abbreviated as “fa a”, “fa b”, “fa 1 z1”, etc.
+
* Depending upon the circumstances, you may write it in Fleet, commonly abbreviated as “fa a”, “fa b”, “fa 1 z1”, etc.
*If you did not activate it: “Unannounced Activation Alpha”, “Did someone activate Alpha?”, etc.
+
* If you did not activate it: “Unannounced Activation Alpha”, “Did someone activate Alpha?”, etc.
  
==Scanning and Updating Pathfinder==
+
== Scanning and Updating Pathfinder ==
 
Intelligence is life and death in J-space and part of this includes ensuring signatures are properly scanned, bookmarked, and updated in Pathfinder along with other important information. If everybody does a little bit, it’s not much work!
 
Intelligence is life and death in J-space and part of this includes ensuring signatures are properly scanned, bookmarked, and updated in Pathfinder along with other important information. If everybody does a little bit, it’s not much work!
  
Line 39: Line 42:
 
* Finish scanning a system and updating Pathfinder completely before running sites. Others are relying on the completion of the scanning to be able to plan content.
 
* Finish scanning a system and updating Pathfinder completely before running sites. Others are relying on the completion of the scanning to be able to plan content.
  
==PvE Content==
+
== PvP Content ==
We are a community-oriented campus. Members are encouraged (and in some cases, expected) to make an attempt to invite other members to participate. When planning content it is best to ping in the "#whc-pings" channel in Discord using the “@everyone” command to include other campus members in the content if it can be run as a group. See below for ping guidelines.
+
 
 +
=== PVP Pings ===
 +
Any ping is better than no ping at all. But if your ping contains the following others can join in much more effectively:
 +
* What you are fighting or expecting
 +
* What time you are expecting it (not needed for instant PVP)
 +
* Where you are fighting (system name, what gate/wormhole, ...)
 +
* What you need to come (Logi, DD, ECM, .....)
 +
 
 +
=== FC Commands ===
 +
When a member steps-up and is FC-ing an engagement the commands from that individual for combat related activities should be adhered to. They have the final say on what doctrine is being used, where to go, who to shoot, and all that fun stuff.
 +
* Suggestions during fleet time can be noted in fleet chat for the FC to read and to keep comms clear.
 +
* Any feedback or constructive criticism of a call the FC makes that is best left for discussion during the post-engagement debrief or commented on the AAR (if one is created).
 +
* The [https://forms.gle/3yTteJB8jBA93Fbh7 FC Feedback form] can be used to submit feedback to FCs that are part of the EVE Uni [[FC Team]].
 +
 
 +
=== Doctrines ===
 +
Doctrines exist for a reason. They allow for engagement in specific situations with fits that provide synergy with each other for performance while also keeping skill requirements in mind. As such, when a doctrine is called for in an engagement that doctrine should be adhered to unless expressly given the go-ahead by the FC to bring something else.
 +
* For example, "FC can I bring my huggin/rapier/curse/pilgrim" is likely to be met with a "yes" from inexperienced FCs, whereas "FC would bringing webs / TDs help us in this engagement?" allows a newer FC to consider whether that role is useful without having to be the FC-that-said-no. In essence, don’t just bring a Tengu to a Small Ships fight for funzies.
 +
 
 +
=== Combat Comms ===
 +
While in combat members may become excited or discouraged and offer up many ideas or suggestions. It is vital that these ideas be put into fleet chat, where they may be safely used or ignored.
 +
* Saturated voice communications cause a variety of problems.
 +
 
 +
=== Keep space clean ===
 +
Leaving wrecks, corpses, and drones in space is a dead giveaway that a system is active and dangerous. Do not give intel away for free.
 +
 
 +
== PvE Content ==
 +
We are a community-oriented campus. Members are encouraged (and in some cases, expected) to make an attempt to invite other members to participate. When planning content it is best to ping in the "#whc-pings" channel in Discord using the “@everyone” command to include other campus members in the content if it can be run as a group.
 +
 
 +
=== PVE Pings ===
 +
Any ping is better than no ping at all. But if your ping contains the following others can join in much more effectively:
 +
* Where the PVE will take place
 +
* What PVE you want to do (gas huffing, NPC shooting, mining, .....)
 +
* What time you want to do this
 +
* What you are looking for to log in with the ping
 +
 
 +
Example:
 +
{{code|@everyone Forming Harvester for 10 Sites in Bravo
 +
Undocking at 1300 (in 5 mins)}}
  
 
=== Combat Sites ===
 
=== Combat Sites ===
WHC has a few site-running doctrines for different opportunities that can be found down the wormhole chains.
+
Ask in fleet, Mumble and ping in Discord to form a doctrine fleet so that other members, especially lower SP members, can share in the fun and blue loot.
  
==== [https://auth.eveuniversity.org/fittings/doctrine/6/ Harvester] ====
+
* Hogging PvE sites for solo runs without communicating the opportunity is considered detrimental for the campus.
Harvester is our main PvE doctrine for C3 combat sites. Min comp is 2-3 Attack Battlecruisers, Solo Logi, and a Swatter ship as the minimum comp. Dual logi is taken for difficult more sites or if the logi pilots are low sp/new to logi. The idea of the doctrine is that its cheap but effective. The doctrine has a bit of a bite in case you're jumped but keep in mind its cheap so you can recover from being ganked. You want to avoid blinging it for this reason.
+
* There is nothing wrong with solo site running if the opportunity has been communicated properly and no one responded.
 
+
* WHC caters to all timezones. 'It was too late to ping' is not an excuse.
==== Wolf Rayet Doctrine ====
+
* Roll Bravo when the combat sites have been finished and there is no active content down the Bravo chain. This gives the community a brand new C3 system with more content.  
The Wolf Rayet effect in a wormhole system gives bonuses to small ship weapons and armor tank. These are ideal conditions for the spider tanked Kikimoras. To those who cannot fly the Kikimora, Retributions and Confessors can also be flown.
+
** Don't leave an empty Bravo for others.
  
How to Form for C3
+
==== How to Form ====
 
When calling for form-up for running C3 sites, call for numbers first. Depending on how many are available you can form up:
 
When calling for form-up for running C3 sites, call for numbers first. Depending on how many are available you can form up:
  
 
* If you have minimum for Harvester form up that doctrine.
 
* If you have minimum for Harvester form up that doctrine.
* If you don't have minimum for Harvester, take out Kitchen Sink PvE fits.
+
** If you don't have minimum for Harvester, take out Kitchen Sink PvE fits.
* If you have enough numbers for 2 Harvester comps, split into 2 or more groups.
+
** If you have enough numbers for 2 Harvester comps, split into 2 or more groups.
* The loot is x-ed up as a single shared op even if multiple groups are created to clear the system.
+
** The loot is considered as part of single shared effort even if multiple groups are created to clear the system.
 +
 
 +
==== Doctrines ====
 +
WHC has a few site-running doctrines for different opportunities that can be found down the wormhole chains.
  
** Ask in fleet, Mumble and ping in Discord to form a doctrine fleet so that other members, especially lower SP members, can share in the fun and blue loot.
+
===== [https://auth.eveuniversity.org/fittings/doctrine/6/ Harvester] =====
** Hogging PvE sites for solo runs without communicating the opportunity is considered detrimental for the campus.
+
Harvester is our main PvE doctrine for C3 combat sites. Min comp is 2-3 Attack Battlecruisers, Solo Logi, and a Swatter ship as the minimum comp. Dual logi is taken for difficult more sites or if the logi pilots are low sp/new to logi. The idea of the doctrine is that its cheap but effective. The doctrine has a bit of a bite in case you're jumped but keep in mind its cheap so you can recover from being ganked. You want to avoid blinging it for this reason.
** There is nothing wrong with solo site running if the opportunity has been communicated properly and no one responded.
 
** WHC caters to all timezones. 'It was too late to ping' is not an excuse.
 
** Roll Bravo when the combat sites have been finished and there is no active content down the Bravo chain. This gives the community a brand new C3 system with more content.
 
*** Don't leave an empty Bravo for others.
 
* Gas Sites
 
** Members will respond to pings for gas huffing even several jumps down chain.  
 
* Ore Sites
 
** As compression is typically utilized to reduce the need for repeated wormhole transits, most group mining activities take place in Cake or 1 jump out.
 
* Pickets
 
** For any PvE content having other members and/or alts watching holes leading into the relevant system increases the chances of successfully avoiding and escaping hostile forces.
 
** Everyone in the fleet should still be using D-scan. The more people actively checking for threats increases the chances of spotting something.
 
* Prior to departing for PvE content ensure that all signatures in Cake, the target system, and systems in-between are scanned to avoid unexpected surprises from an unscanned wormholes.
 
* Once the group content is complete, make sure any shared loot is dropped in the same numbered container in the "Donations and Loot" hangar. This allows whoever is creating the Buyback contract for the group to easily grab all the items.
 
* It is considered to be bad manners to conduct PvE in holes occupied by corps that are Blue to the Ivy League without asking for their permission first.
 
  
==PvP Content==
+
===== Wolf Rayet Doctrine =====
*FC Commands
+
The Wolf Rayet effect in a wormhole system gives bonuses to small ship weapons and armor tank. These are ideal conditions for the spider tanked Kikimoras. To those who cannot fly the Kikimora, Retributions and Confessors can also be flown.
** When a member steps-up and is FC-ing an engagement the commands from that individual for combat related activities should be adhered to. They have the final say on what doctrine is being used, where to go, who to shoot, and all that fun stuff.
 
** Suggestions during fleet time can be noted in fleet chat for the FC to read and to keep comms clear.
 
** Any feedback or constructive criticism of a call the FC makes that is best left for discussion during the post-engagement debrief or commented on the AAR (if one is created).
 
** The [https://forms.gle/3yTteJB8jBA93Fbh7 FC Feedback form] can be used to submit feedback to FCs that are part of the EVE Uni [[FC Team]].
 
** Doctrines exist for a reason. They allow for engagement in specific situations with fits that provide synergy with each other for performance while also keeping skill requirements in mind. As such, when a doctrine is called for in an engagement that doctrine should be adhered to unless expressly given the go-ahead by the FC to bring something else.
 
*** For example, "FC can I bring my huggin/rapier/curse/pilgrim'' is likely to be met with a "yes" from inexperienced FCs, whereas "FC would bringing webs / TDs help us in this engagement?" allows a newer FC to consider whether that role is useful without having to be the FC-that-said-no. In essence, don’t just bring a Tengu to a Small Ships fight for funzies.
 
* Combat Comms
 
** While in combat members may become excited or discouraged and offer up many ideas or suggestions. It is vital that these ideas be put into fleet chat, where they may be safely used or ignored. ** If voice communications are saturated with ideas, it causes a variety of problems.
 
* Keep space clean. Leaving wrecks, corpses, and drones in space is a dead giveaway that a system is active and dangerous. Do not give intel away for free.
 
  
==Rules and Feedback==
+
=== Gas Sites ===
We are aware that Eve University brings together people of many backgrounds and skill levels and we all must work together to make Eve University the best possible. Community Coordinator and Community Directors welcome questions on processes and fits (it’s how we learn!) as well as constructive criticism on rules. Concerns and issues can be raised to campus leadership and will be considered accordingly. Additionally, Community Coordinators and Community Directors will provide instruction or correction regarding campus rules and etiquette which should be adhered to. Excessive arguing or ranting / cursing in comms or Discord is to be avoided as there is always a better way to discuss topics and share your opinion.
+
* Members will respond to pings for gas huffing even several jumps down chain.  
  
== Guidelines for Discord pings ==
+
=== Ore Sites ===
=== PVP Pings ===
+
* As compression is typically utilized to reduce the need for repeated wormhole transits, most group mining activities take place in Cake or 1 jump out.
*What you are fighting or expecting
 
*What time you are expecting it (not needed for instant PVP)
 
*Where you are fighting (system name, what gate/wormhole, ...)
 
*What you need to come (Logi, DD, ECM, .....)
 
  
=== PVE Pings ===
+
=== Null Data/Relic Sites ===
*Where the PVE will take place
+
Scout(s) who were involved in scanning the sites and bookmarking them have the first claim to these sites.
*What PVE you want to do (gas huffing, NPC shooting, mining, .....)
+
* If the scout(s) passes on them, its fair game for any member of the fleet (Ask the scout before you run)
*What time you want to do this
+
* If multiple members are interested, they can come to an agreement on how to share the opportunity
*What you are looking for to log in with the ping
 
  
The PVE pings should only be posted once every 30 minutes. If they are happening in like a couple of hours it's 1 ping at your current time and an optional ping on the formup/10 minutes before. No reason to keep pinging every 5 minutes if you are missing a couple of people.
+
=== Ghost Sites ===
 +
As these highly valuable sites have a time limit, it is most efficient to take as many people as there are cans in a site (4-5). If there are not enough people who want to join in fleet, ping in Discord.
 +
* Make sure to assign everyone a specific can before warping to the site.
 +
** Enable the tactical overlay to see the colored line of north.
 +
** Cans spawn in the northeast, southeast, southwest, northwest, and (with 5 can sites) up directions.
 +
* The site timer starts as soon as an uncloaked warp is initiated, so have a squad commander initiate warp from the closest celestial.
  
PVP pings should be sent out only once. You can ping again in the following situations:
+
=== Pickets ===
*You where expecting PVP and now you have a ship count of what they are bringing
+
For any PvE content having other members and/or alts watching holes leading into the relevant system increases the chances of successfully avoiding and escaping hostile forces.
*The fight is getting escalated with more ships and you are looking for backup
+
* Everyone in the fleet should still be using D-scan. The more people actively checking for threats increases the chances of spotting something.
*The best way to avoid multiple pings is to ask a certain person in fleet or comms to make a ping or to let someone x up for making the ping so not 5 people are pinging at the same time for the same thing.
+
* Prior to departing for PvE content ensure that all signatures in Cake, the target system, and systems in-between are scanned to avoid unexpected surprises from an unscanned wormholes.  
  
Guidelines for PvE in WHC
+
==== Things to Keep in Mind ====
 +
* PvE ships are not covered under the Ship Replacement Program
 +
* PvE in wormholes is risky business. Scan all possible wormhole connections to make sure there's no activity nearby before you start. Leaving unscanned sigs is an easy way to lose ships/pods in a PvE fleet.
 +
* Expect to lose your ship to a ganks/poor target calling/latency etc. Avoid unnecessary bling in the ship or in the pod.
 +
* About loss of harvester ships: we've done this so many times before, its most likely not an issue with the doctrine fit but how you flew it. Feel free to share any suggestions though.
 +
* Social PvE is fun because of the people you take along with you. Feel free to chat on comms. Respect the call for Combat Comms.
 +
* Do not run sites in j-space systems with structures that are blue to EVE Uni or Ivy League.
  
 +
== Hangars ==
 +
WHC uses several corp hangars as part of day-to-day operations.
 +
* If the contents of a container are locked, select the items you want unlocked, right-click on locked items, and select "unlock".
 +
** If you take only part of a stack of items remember to lock it again afterward. The logs record who locked/unlocked each item so locking items after you use them show that you did not take everything.
 +
* Take only what you need and attempt to replace it if possible.
  
 +
=== General Hangar ===
  
 +
==== Ships ====
 +
Ships in the general hangar are provided as loaners by WHC and community members. They can be borrowed by those who do not have a ship for group content.
 +
* Return the ship to the General Hanger before you log off.
 +
* Replace any lost ships as soon as possible. You break it, you buy it.
 +
* Do not rename any ships you borrow from the General Hangar. The ship name is how members track the ships they are providing as loaners.
  
When/How to Communicate Site Running Opportunity
+
==== Ammo, Charges, & Drones ====
If there are just a few sites, mention on comms, throw a post (no “ping”) in #whc-pings saying you will be running the sites at X time (in Y mins). If a system has enough combat sites to run an extended PvE session (for example 10+ sites in Bacon) a ping should be sent out in #whc-pings. An ideal ping would include the location, how many sites, the doctrine and time of undock (use EVE time). The double asterisk(*) is markdown for bold in Discord by default.
+
Items in this can are provided free of charge to WHC members who might need a few more missiles or drones to complete a fit.
 +
* Remember to lock items after taking what you need.
  
Example:
+
==== PI Command Centers ====
 +
The Planetary Command Centers are free to take for WHC members for use in setting up PI.
  
Code: Select all
+
==== Used Crystals ====
 +
Dumping location for any crystals that have a high damage percentage that someone wanted to swap out for new versions. Feel free to grab any of these used crystals and recycle them.
  
''@everyone **PvE**''
+
=== Donations and Loot ===
Forming Harvester for 10 Sites in Bacon
 
**Undocking at 1300** (in 5 mins)
 
  
 +
==== Loot Cans ====
 +
These are the Numbered cans "01" to "05". These cans are for dropping off the loot from group PvP and PvE content.
 +
* Items dropped into these containers create a log to see who added or removed items.
 +
* Do not leave loot inside these containers for extended periods. Create a buyback contract as soon as all the loot has been deposited. WHC CCs regularly clean up these containers and move any abandoned items to Donations if not claimed.
  
* Null Data/Relic Sites
+
==== Donations ====
** Scout(s) who were involved in scanning the sites and bookmarking them have first dibs.
+
Items dropped into this can are donated to WHC Operations as a funding source for CAMP contracts and other WHC programs.
** If the scout(s) passes on them, its fair game for any member of the fleet (Ask the scout before you run)
+
* Consider dropping useful ammunition, drones, and modules into the "General PvP Loot" container to make them available to other WHC members.
** If multiple members are interested, they can come to an agreement on how to share the opportunity
 
** This does not usually warrant a ping unless you find a Silent Battleground or a wormhole with 10+ sites that you cannot clear safely on your own
 
** It is may be efficient to take multiple people with you and split loot for Ghost Sites to ensure easy clear of all cans
 
* Gas Sites
 
** Always ping for Instrumental Core Reservoir or Vital Core Reservoir
 
** Do not ping for any other type of Gas site. You may communicate in #whc-pings without tagging everyone.
 
** If you clear a gas site in any system, you can inform the fleet of the opportunity to huff. If you did the hard work of clearing the site, you are entitled to the blue loot that drops.
 
** Before Gas ops are started loot style should be declared: Bring Your Own Huffer or Shared Can. Any disputes should be brought up with WHC Officers.
 
  
*Things to Keep in Mind:
+
==== General PvP Loot ====
** PvE ships are not covered under the Ship Replacement Program
+
Items in this container are free for WHC members to take from to complete fits. Take only what you need.
** PvE in wormholes is risky business. Scan all possible wormhole connections to make sure there's no activity nearby before you start. Leaving unscanned sigs is an easy way to lose ships/pods in a PvE fleet.
 
** Expect to lose your ship to a ganks/poor target calling/latency etc. Avoid unnecessary bling in the ship or in the pod.
 
** About loss of harvester ships: we've done this so many times before, its most likely not an issue with the doctrine fit but how you flew it. Feel free to share any suggestions though.
 
** Social PvE is fun because of the people you take along with you. Feel free to chat on comms. Respect the call for Combat Comms.
 
** All Shared Ops should be x-ed up through the WHC Lootsheet.
 
  
 +
==== WHC Corpse Locker ====
 +
Place any unwanted corpses here.
  
*Interacting with Blues (Characters/Corporations with +5 Standing to E-UNI/IVY)
+
== Interacting with Blues ==
** Avoid running sites in systems with a Blue Structure. There may be some wiggle room if the CEO grants you explicit permission to run sites.
+
Blues are characters that have a +5 Standing to E-UNI/IVY. We avoid running sites in systems with a Blue Structure.
** Keep in mind +5 states are based on a Mutual Agreement but the agreements may get forgotten over time. There may be cases where you come across someone who appears blue to IVY but may not necessarily have E-UNI/IVY set blue.
+
* Keep in mind +5 standings are based on a Mutual Agreement but the agreements may get forgotten over time. There may be cases where you come across someone who appears blue to IVY but may not necessarily have E-UNI/IVY set blue.
** If a +5 pilot starts running sites in Innuendo:
+
* If a +5 pilot starts running sites in Cake:
*** Start a private conversation to the pilot
+
** Start a private conversation to the pilot
*** Inform them that this is E-UNI WHC home system and the sites are reserved as content generators
+
** Inform them that this is E-UNI WHC home system and the sites are reserved as content generators
*** Politely ask them not to run the sites
+
** Politely ask them not to run the sites
*** Explain that we are politely asking as they are set to +5 standings by our Diplomacy team
+
** Explain that we are politely asking as they are set to +5 standings by our Diplomacy team
*** Be graceful in your response, do not provoke a reaction. If they ask to complete a site they started, let them
+
** Be graceful in your response, do not provoke a reaction. If they ask to complete a site they started, let them.
*** If the pilot does not comply or responds negatively, copy your chat and share with the Diplomacy team and let them be
+
** If the pilot does not comply or responds negatively, copy your chat and share with the Diplomacy team and let them be.
  
 
== See Also ==
 
== See Also ==
 
[https://forum.eveuniversity.org/viewtopic.php?f=236&t=126911 Original Forum Post]
 
[https://forum.eveuniversity.org/viewtopic.php?f=236&t=126911 Original Forum Post]

Latest revision as of 22:07, 23 September 2024

E-UNI Emblem.png This page is specific to EVE University. Other corporations or groups in the game may operate differently.
For a summary of EVE University's rules and code of conduct, see EVE University Rules.



Rules and Feedback

We are aware that Eve University brings together people of many backgrounds and skill levels. We all must work together to make Eve University and WHC the best they can be. Community Coordinators welcome questions on processes and fits (it’s how we learn!) as well as constructive criticism on rules. Additionally, Community Coordinators will provide instruction or correction regarding campus rules and etiquette which should be adhered to. Any concerns or issues can be raised to Community Coordinators, Student Advocates, and/or Uni leadership. Excessive arguing or ranting in comms or Discord is to be avoided as there is always a better way to discuss topics and share your opinion.

Being in Fleet

If you are in the WHC chain, always be in fleet. If there is no WHC Standing fleet, create one! See Standing Fleet for details on how to get the settings correct and Standing Fleet MOTDs for the MOTD.

  • Do not go AFK for any extended period of time while in fleet.
    • If you get ninja-bossed while AFK, the fleet will not be advertised. Leave fleet if you need to be AFK for an extended period of time.
  • Do not set fleet advert to automatically update fleet advert on boss change. This can automatically swap boss to an AFK person in fleet and will cause the fleet to become unusable.
  • If you are docked but AFK, you show as present in our structures which may lead potential content to think we are able to engage with more numbers than we are actually able to field.
  • If you are the fleet boss and need to leave/go AFK, pass it to someone who is going to be online. Do not log off before handing off Fleet boss, as it will be given to a member of the Fleet who may not be paying attention at the time.
    • Passing boss gives a session change timer—surprise session change timers can get people killed. It is good practice to ask the person who says they can take fleet boss if they are ready for it.
    • If no one is able to take boss it is best to disband the fleet.
  • If for some exceptional reason, you cannot be in Fleet, let people who are in Fleet or Mumble know you are there.

Being in Comms

Being in Mumble is highly recommended. Talking is much faster at conveying information than typing it out in fleet. Intel is posted into fleet, but by not at least listening to Mumble can result in losing a ship when someone calls it out.

Undocking

Before undocking in Cake you must be in fleet. It is good practice prior to undocking to first ask if there is ongoing content. You don’t want to start jumping through the chain in your DST only to find bubble with hostiles or undock only to scare off a target someone is hunting. Contribute to content, don’t kill it!

Announcing Activations

Always call out activations for Alpha, Bravo, any hole within 2 jumps of Cake, and any wormholes into or out of a system you know/suspect contain other WHC members. Wormholes make a sound and have a visual effect. We use this to determine when we need to prepare for a fight, so announcing activations lets those watching a wormhole know that the activation is friendly and not a sign of an imminent fight. It is also best practice to call out activations further down the chain as this gives others in fleet a better understanding of where people are in chain.

  • If you are activating it: Call out “Friendly Alpha”, “Friendly Bravo”, “Friendly 1 Z1”, etc. in Mumble.
  • Depending upon the circumstances, you may write it in Fleet, commonly abbreviated as “fa a”, “fa b”, “fa 1 z1”, etc.
  • If you did not activate it: “Unannounced Activation Alpha”, “Did someone activate Alpha?”, etc.

Scanning and Updating Pathfinder

Intelligence is life and death in J-space and part of this includes ensuring signatures are properly scanned, bookmarked, and updated in Pathfinder along with other important information. If everybody does a little bit, it’s not much work!

  • Make sure you are keeping Pathfinder updated and cleaned up. This means properly updating new signatures, updating information on structures and POSs, deleting old sigs that aren’t there, deleting chains that have collapsed, and detaching connections that appear if someone gets podded or death clones.
  • We pay our scanners for every sig they bookmark and put in Pathfinder. In a decent week, this can be nearly 1M ISK/signature!
  • One of the first things you should do when undocking is ensuring all signatures in Cake have been updated. It is also good practice to do this while passing through the chain. See this forum post on how best to accomplish this.
  • As a general rule every signature within 2 jumps of Cake should be scanned down, bookmarked and added to Pathfinder.
    • When further down chain always bookmark all wormholes in the chain by warping to the wormhole and bookmarking it (do NOT bookmark a wormhole from your probe window).
  • Make sure you have read and understand our various guides on WHC System Naming Scheme, WHC Bookmark Naming Scheme, and WHC What To Bookmark Guide.
  • Those who scan down Null Data/Relic sites have the right to run them first. If someone has already bookmarked a site, ask them if they plan on running it.
  • Finish scanning a system and updating Pathfinder completely before running sites. Others are relying on the completion of the scanning to be able to plan content.

PvP Content

PVP Pings

Any ping is better than no ping at all. But if your ping contains the following others can join in much more effectively:

  • What you are fighting or expecting
  • What time you are expecting it (not needed for instant PVP)
  • Where you are fighting (system name, what gate/wormhole, ...)
  • What you need to come (Logi, DD, ECM, .....)

FC Commands

When a member steps-up and is FC-ing an engagement the commands from that individual for combat related activities should be adhered to. They have the final say on what doctrine is being used, where to go, who to shoot, and all that fun stuff.

  • Suggestions during fleet time can be noted in fleet chat for the FC to read and to keep comms clear.
  • Any feedback or constructive criticism of a call the FC makes that is best left for discussion during the post-engagement debrief or commented on the AAR (if one is created).
  • The FC Feedback form can be used to submit feedback to FCs that are part of the EVE Uni FC Team.

Doctrines

Doctrines exist for a reason. They allow for engagement in specific situations with fits that provide synergy with each other for performance while also keeping skill requirements in mind. As such, when a doctrine is called for in an engagement that doctrine should be adhered to unless expressly given the go-ahead by the FC to bring something else.

  • For example, "FC can I bring my huggin/rapier/curse/pilgrim" is likely to be met with a "yes" from inexperienced FCs, whereas "FC would bringing webs / TDs help us in this engagement?" allows a newer FC to consider whether that role is useful without having to be the FC-that-said-no. In essence, don’t just bring a Tengu to a Small Ships fight for funzies.

Combat Comms

While in combat members may become excited or discouraged and offer up many ideas or suggestions. It is vital that these ideas be put into fleet chat, where they may be safely used or ignored.

  • Saturated voice communications cause a variety of problems.

Keep space clean

Leaving wrecks, corpses, and drones in space is a dead giveaway that a system is active and dangerous. Do not give intel away for free.

PvE Content

We are a community-oriented campus. Members are encouraged (and in some cases, expected) to make an attempt to invite other members to participate. When planning content it is best to ping in the "#whc-pings" channel in Discord using the “@everyone” command to include other campus members in the content if it can be run as a group.

PVE Pings

Any ping is better than no ping at all. But if your ping contains the following others can join in much more effectively:

  • Where the PVE will take place
  • What PVE you want to do (gas huffing, NPC shooting, mining, .....)
  • What time you want to do this
  • What you are looking for to log in with the ping

Example:

@everyone Forming Harvester for 10 Sites in Bravo Undocking at 1300 (in 5 mins)

Combat Sites

Ask in fleet, Mumble and ping in Discord to form a doctrine fleet so that other members, especially lower SP members, can share in the fun and blue loot.

  • Hogging PvE sites for solo runs without communicating the opportunity is considered detrimental for the campus.
  • There is nothing wrong with solo site running if the opportunity has been communicated properly and no one responded.
  • WHC caters to all timezones. 'It was too late to ping' is not an excuse.
  • Roll Bravo when the combat sites have been finished and there is no active content down the Bravo chain. This gives the community a brand new C3 system with more content.
    • Don't leave an empty Bravo for others.

How to Form

When calling for form-up for running C3 sites, call for numbers first. Depending on how many are available you can form up:

  • If you have minimum for Harvester form up that doctrine.
    • If you don't have minimum for Harvester, take out Kitchen Sink PvE fits.
    • If you have enough numbers for 2 Harvester comps, split into 2 or more groups.
    • The loot is considered as part of single shared effort even if multiple groups are created to clear the system.

Doctrines

WHC has a few site-running doctrines for different opportunities that can be found down the wormhole chains.

Harvester

Harvester is our main PvE doctrine for C3 combat sites. Min comp is 2-3 Attack Battlecruisers, Solo Logi, and a Swatter ship as the minimum comp. Dual logi is taken for difficult more sites or if the logi pilots are low sp/new to logi. The idea of the doctrine is that its cheap but effective. The doctrine has a bit of a bite in case you're jumped but keep in mind its cheap so you can recover from being ganked. You want to avoid blinging it for this reason.

Wolf Rayet Doctrine

The Wolf Rayet effect in a wormhole system gives bonuses to small ship weapons and armor tank. These are ideal conditions for the spider tanked Kikimoras. To those who cannot fly the Kikimora, Retributions and Confessors can also be flown.

Gas Sites

  • Members will respond to pings for gas huffing even several jumps down chain.

Ore Sites

  • As compression is typically utilized to reduce the need for repeated wormhole transits, most group mining activities take place in Cake or 1 jump out.

Null Data/Relic Sites

Scout(s) who were involved in scanning the sites and bookmarking them have the first claim to these sites.

  • If the scout(s) passes on them, its fair game for any member of the fleet (Ask the scout before you run)
  • If multiple members are interested, they can come to an agreement on how to share the opportunity

Ghost Sites

As these highly valuable sites have a time limit, it is most efficient to take as many people as there are cans in a site (4-5). If there are not enough people who want to join in fleet, ping in Discord.

  • Make sure to assign everyone a specific can before warping to the site.
    • Enable the tactical overlay to see the colored line of north.
    • Cans spawn in the northeast, southeast, southwest, northwest, and (with 5 can sites) up directions.
  • The site timer starts as soon as an uncloaked warp is initiated, so have a squad commander initiate warp from the closest celestial.

Pickets

For any PvE content having other members and/or alts watching holes leading into the relevant system increases the chances of successfully avoiding and escaping hostile forces.

  • Everyone in the fleet should still be using D-scan. The more people actively checking for threats increases the chances of spotting something.
  • Prior to departing for PvE content ensure that all signatures in Cake, the target system, and systems in-between are scanned to avoid unexpected surprises from an unscanned wormholes.

Things to Keep in Mind

  • PvE ships are not covered under the Ship Replacement Program
  • PvE in wormholes is risky business. Scan all possible wormhole connections to make sure there's no activity nearby before you start. Leaving unscanned sigs is an easy way to lose ships/pods in a PvE fleet.
  • Expect to lose your ship to a ganks/poor target calling/latency etc. Avoid unnecessary bling in the ship or in the pod.
  • About loss of harvester ships: we've done this so many times before, its most likely not an issue with the doctrine fit but how you flew it. Feel free to share any suggestions though.
  • Social PvE is fun because of the people you take along with you. Feel free to chat on comms. Respect the call for Combat Comms.
  • Do not run sites in j-space systems with structures that are blue to EVE Uni or Ivy League.

Hangars

WHC uses several corp hangars as part of day-to-day operations.

  • If the contents of a container are locked, select the items you want unlocked, right-click on locked items, and select "unlock".
    • If you take only part of a stack of items remember to lock it again afterward. The logs record who locked/unlocked each item so locking items after you use them show that you did not take everything.
  • Take only what you need and attempt to replace it if possible.

General Hangar

Ships

Ships in the general hangar are provided as loaners by WHC and community members. They can be borrowed by those who do not have a ship for group content.

  • Return the ship to the General Hanger before you log off.
  • Replace any lost ships as soon as possible. You break it, you buy it.
  • Do not rename any ships you borrow from the General Hangar. The ship name is how members track the ships they are providing as loaners.

Ammo, Charges, & Drones

Items in this can are provided free of charge to WHC members who might need a few more missiles or drones to complete a fit.

  • Remember to lock items after taking what you need.

PI Command Centers

The Planetary Command Centers are free to take for WHC members for use in setting up PI.

Used Crystals

Dumping location for any crystals that have a high damage percentage that someone wanted to swap out for new versions. Feel free to grab any of these used crystals and recycle them.

Donations and Loot

Loot Cans

These are the Numbered cans "01" to "05". These cans are for dropping off the loot from group PvP and PvE content.

  • Items dropped into these containers create a log to see who added or removed items.
  • Do not leave loot inside these containers for extended periods. Create a buyback contract as soon as all the loot has been deposited. WHC CCs regularly clean up these containers and move any abandoned items to Donations if not claimed.

Donations

Items dropped into this can are donated to WHC Operations as a funding source for CAMP contracts and other WHC programs.

  • Consider dropping useful ammunition, drones, and modules into the "General PvP Loot" container to make them available to other WHC members.

General PvP Loot

Items in this container are free for WHC members to take from to complete fits. Take only what you need.

WHC Corpse Locker

Place any unwanted corpses here.

Interacting with Blues

Blues are characters that have a +5 Standing to E-UNI/IVY. We avoid running sites in systems with a Blue Structure.

  • Keep in mind +5 standings are based on a Mutual Agreement but the agreements may get forgotten over time. There may be cases where you come across someone who appears blue to IVY but may not necessarily have E-UNI/IVY set blue.
  • If a +5 pilot starts running sites in Cake:
    • Start a private conversation to the pilot
    • Inform them that this is E-UNI WHC home system and the sites are reserved as content generators
    • Politely ask them not to run the sites
    • Explain that we are politely asking as they are set to +5 standings by our Diplomacy team
    • Be graceful in your response, do not provoke a reaction. If they ask to complete a site they started, let them.
    • If the pilot does not comply or responds negatively, copy your chat and share with the Diplomacy team and let them be.

See Also

Original Forum Post