Differences

This shows you the differences between two versions of the page.

--- guides:basi_lc [2016/05/27 04:13]
nyxviliana Resebo removed
+++ guides:basi_lc [2016/11/02 11:50] (current)
nyxviliana [Building a Stable Chain]
@@ Line 1: / Line 1: @@
-=====Basilisk LC=====
+====== Basilisk LC ======
-The Basilisk LC (Basi LC), is a very important role. You have a few responsibilities and this guide will outline all of the things you have to do. You do not need any special skill points, or special assets to be the Basilisk LC however, you should be a good Basilisk pilot.
+The Basilisk LC (Basi-LC), is a very important role. You have a few responsibilities and this guide will outline all of the things you have to do. You do not need any special skill points, however it will help if you have a good level of experience as a Basi.
-====Basilisk LC Responsibilities====
+===== Responsibilities =====
-  * Keep the cap chain stable
+  * Set up and maintain a stable cap chain
-  * Maintain the number of Combat Caps the FC wants
+  * Maintain the number of "combat caps" the FC would like
-  * Keep an eye on new Basilisk pilots, give them tips.
+  * Ensure that all Basis have at least one free cap transfer
+  * Help out newbro Basis as best you can, ask the FC for help if you need it
+===== Maintaining the Cap Chain =====
+For those who don't know, the Basilisk is one of the two "cap chaining logi" of the Logistics Cruisers. Through its bonuses to cap transfer amount and your skills, it allows you to create cap seemingly out of thin air (the amount transferred is higher than the activation cost of the transfer).
-====Keeping the Cap Chain Stable====
+Your job as the Basi-LC is to set up a chain of Logi capping each other in a way that ensures they are all stable, whilst also having spare cap transfers to use for giving cap to targets under neut pressure, and Vindis who require cap intermittently due to their guns and MWD's heavy cap usage.
-The **Cap Chain** is a crucial part of our fleets. We need cap to counter [[Outuni Mesen]] and we also need capacitor to help out the Vindicators. The LC is responsible for maintaining the cap chain and make sure that it is stable at all times.  First lets go over the basics of __Combat Caps__
-==Combat Caps==
+==== Combat Caps ====
-Combat Caps refer to how many capacitor transfers are available for use in combat situations. This basically means how many capacitor transfers are available between all the Basis but not used to keep the cap chain up!
+"Combat Caps" – The number of spare cap transfers not used in the cap chain.
+  * In general, we wish to run with three combat caps. This allows us to comfortably run under neut pressure even if we have three Outunis spawn at the end of an NRF.
+  * Every Basilisk must have at least one combat cap!
-For example if there are two logi V, basilisks and they are fitted 3-3, they give each other one cap to as part of the combat chain to keep each other cap stable. Therefore if there is a total of six capacitor transfers between the two Basilisks and two are used for the cap chain there are four left over. This means there is four combat caps.
+If you run below three combat caps, please re-build the cap chain in a way that follows the above principles. If refits are required please perform them in site when anchored up at a position. For example during the 1st-3rd waves on an NRF, once anchored near the tower on the 3rd room of a TPPH, or at your anchor point on a TCRC. If you finish a site and lose combat caps please inform the FC how many you have lost, and the new total. They may ask you to refit on the next gate if necessary.
+==== Building a Stable Chain ====
+  * Level IV Basilisks will require TWO incoming transfers
+  * Level V Basilisks will require ONE incoming transfer
-==Combat Cap Requirements==
+The conventions for creating the cap chain:
-For each site we require the same number of combat caps as possible Outunis. While the technical minimum for some sites is two we prefer to have three to four combat caps at any given time. If you're unsure about having enough combat caps, ask your FC.
+  * Names are always listed in alphabetical order
+  * Normally, all Basis will cap up
+  * If necessary to keep a Level 4 stable, a Basi will also cap down
+  * If you are at the top of the list, capping up means it rolls around to the bottom
+  * If you are at the bottom of the list, capping down means it rolls around to the top
-Try to avoid your team refitting on gates, this can be done at an anchor point. If you have to refit on the gate, check with the FC.
+For example, let's say we have three pilots called **Apple**, **Banana** and **Croissant**. Croissant is Level IV, here is the stable chain:
-==How to build the cap chain==
+^ Logi Level ^ Pilot Name ^ Fit ^ Outgoing Caps ^ Incoming Caps ^ Combat Caps ^
-This is the hardest part of your job! -- Building a Cap Chain. A level V Basilisk needs one incoming cap transfer to be capstable, and a level IV Basilisk needs two incoming cap transfers.
+| LVL5 | Apple | 4/2 | Up | From Banana | 1 |
+| LVL5 | Banana | 3/3 | Up AND Down | From Croissant | 1 |
+| LVL4 | Croissant | 4/2 | Up | From Apple AND Banana | 1 |
-To coordinate this typically we get people to cap based on alphabetical order. The person at the bottom of the channel list caps the person above him and so on, with the person at the top capping the person at the bottom. This is called "Capping UP." However we some times have level IV Basilisks in the cap chain so to deal with this we get the person above them to cap the person below them (cap down). To make this easier for pilots we give them instructions in the MOTD. Part of your job is to manage the MOTD, not just cap chain but the roles as well.
+As you can see, Croissant receives 2 incoming transfers, and each pilot has one combat cap, giving a total of three combat caps.
-==How to maintain the cap chain==
-As people leave and join the fleet, you will need to update the cap chain so keep an eye on who the logis are in your fleet keep the cap chain stable according to the info above.
-==Ensuring the cap chain is stable==
+==== Performing Stability Checks ====
-It is often a good idea to preform stability checks every once in a while, such as when a new Basilisk joins or one leaves, and at the start of the fleet. This can be done over coms by telling your Basilisks to "Basi confirm stability in basi love" but can also be done in channel, information in the channel MOTD gives you some advice on acronyms to use. <wrap em>If at any point the FC wants to take a gate and you feel the cap chain is not stable or the Basilisks are not ready LET THE FC KNOW.</wrap>
+Sometimes you may wish to perform a stability check to ensure all Basis are capping the correct person. You will normally always perform a stability check if it is the fleet's first site after undocking. To perform a stability check:
-Be careful how you do this, going into a site when the Basilisks are not ready has caused pilots to die in the past, but they dont have to be running perfect until Outunis are on grid! Don't tell the FC your not safe if you feel you can get stable and safe before an Outuni wave as this may cause the fleet to sit outside a gate.
+  * Get the cap chain running
+  * Get all Basis to run all their modules (Cap Transfers, Shield Boosters, RESEBOs, Afterburner) on a non-Logi player, the FC is usually a good choice
+  * Ask Basis to confirm that they are all stable
+If at any time you believe the chain is not stable please inform the FC and attempt to restore stability as soon as you can.
-====Basilove MOTD====
+===== Basilove MOTD =====
-Almost all parts of your job including maintaining the CAP chain require you to edit the MOTD. To do this, you need operator rights in the channel. If you do not have them when you are taking over as LC ask the active FC or the LC who is leaving fleet to give them to you!
+You will need to update the MOTD as part of your job, this will require operator rights. If you do not have them please ask the FC to grant them.
-Basilove MOTD can be broken into two sections.
+The Basilove MOTD can be broken into two sections.
-  - Logi Information such as standard procedure for roles, the cap chain etc.
+  - General Information, such as standard procedure for entering sites, repping, the cap chain etc.
-  - Fleet Information, this includes who the FC is, DDD, AAA and other roles important to the Basilisk team and the cap chain.
+  - Fleet Information, this includes who the FC, DDD and AAA are due to their importance to the Basi team, along with the current cap chain details.
 <WRAP group>
-<WRAP half column  >
+<WRAP half column>
-This section (the fleet information section) is the only part you edit EVER.
+==== Fleet Information Section ====
+This is the only section you should edit, EVER! If you feel the other information is incorrect you must ask an FC to correct it, it is not your place to change!
-Always keep the roles up to date with the active pilots who are flying them, please also link them in the channel it is faster for you and it means other logi can right click > add to watch list.
+Always keep the roles up to date with the active pilots who are flying them.
-Please also keep the cap chain up to date. As you can see here it includes from left to right, the pilot logi level (L5), their fit (3/3 or 4/2) and their name. For more information on formatting the cap chain please read the MOTD! Please also include the number of combat caps down the bottom for easy reference.
+Please keep the cap chain up to date at all times. As you can see here it includes from left to right, the pilot logi level (L5), their fit (3/3 or 4/2) and their name. Please also include the number of combat caps down the bottom for easy reference.
 </WRAP>
@@ Line 58: / Line 72: @@
 </WRAP>
-====How to deal with someone who is in channel but not in fleet====
+===== Managing the Pilots in Channel =====
-It is a requirement that only people in fleet are in the channel, all though occasionally an FC may pop in, for the most part if a pilot is in the channel but not in fleet you are within your rights to tell them to leave. If they do not, you may kick them from the channel. If you can not kick them because they have operator rights, please remove their operator rights, kick them and then add their rights back. When kicking someone set duration to be between 1-5 minutes with reason "not in fleet." Please do not ban anyone indefinitely.
+To prevent confusion, only pilots in fleet should be in the channel. If someone leaves fleet and forgets to leave the channel, please feel free to kick them by right clicking and going to Channel --> Kick. Set the duration 1 minute and the reason to "Not in Fleet".
+If you are unable to kick someone due to their operator rights, please remove their operator rights, kick them, and then add their operator rights back. Do not forget the last part!
-====New Bro Basilisks====
+===== Player Conflicts in the Channel =====
-Occasionally you will get a new bro Basilisk. When you do, as the LC you should be keeping an extra eye on this pilot making sure he/she is safe, working properly. Don't be afraid to give him/her information he needs via basilove and/or coms.
+If there is a conflict in the channel due to bad behaviour, or a disagreement between pilots, do not under any circumstances attempt to resolve the conflict yourself. Immediately inform the FC and provide them with logs of the channel up to that point. Don't get involved yourself, it is not your place to do so.

The Valhalla Project

User Tools

Site Tools

Differences

Page Tools