Standard Service: Difference between revisions

Jump to navigation Jump to search
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Below are the procedures for delivering contracts from the standard queue. '''Please note that all Pushers working in high sec are expected to have at least their own freighter and 1 billion ISK in collateral.''' Owning a deep space transport and a blockade runner is highly recommended for the small high sec and low sec contracts.
Below are the procedures for delivering contracts from the standard queue. '''Please note that all Pushers working in high sec are expected to have at least their own freighter and 1.5 billion ISK in collateral.''' Owning a deep space transport and a blockade runner is highly recommended for the small high sec and x-small low sec contracts.


== Procedures ==
== Procedures ==
Line 8: Line 8:
#*If you see a newer contract (or newer contracts) that you can complete while doing an older contract or a rush contract it is alright to accept and deliver the newer contract(s) as well.
#*If you see a newer contract (or newer contracts) that you can complete while doing an older contract or a rush contract it is alright to accept and deliver the newer contract(s) as well.
#*If doing an older contract or rush contract that would put you in a position to easily do other newer contracts once you reach the initial destination you may take those newer contracts and complete them as well.  
#*If doing an older contract or rush contract that would put you in a position to easily do other newer contracts once you reach the initial destination you may take those newer contracts and complete them as well.  
#*Low sec (small) contracts are considered to be part of the standard queue.
#Read the entire contract twice before accepting it.
#Read the entire contract twice before accepting it.
#Read the Info By Issuer field for special notes.
#Read the Info By Issuer field for special notes.
#DO NOT use autopilot.
#DO NOT use autopilot.
#DO NOT use lower security space as a shortcut if the contract does not require it.
#DO NOT use lower security space as a shortcut if the contract does not require it.
#Check the Push Internal MOTD for any warnings about high sec systems.
#Check the Push Internal MOTD and PushX Discord #gank-intel channel for any warnings about high sec systems.
#Upon delivering the package send a delivery mail to the customer using the Queue's mail feature.
#Upon delivering the package send a delivery mail to the customer using the Queue's mail feature.


Line 28: Line 27:
== Pusher Etiquette ==
== Pusher Etiquette ==


Not all, but some of our customers plan their game time around when you make a delivery. After you accept a contract please be prompt with your delivery. Accepting a contract because you plan to do it in 2 days is '''NOT ALLOWED'''. Also, neglecting low reward or long distance contracts in favour of high reward and short distance contracts is '''NOT ALLOWED'''. '''Pushers who break these rules will be contacted directly by a Push Director or a Senior Pusher and possibly removed from the corporation if such behaviour continues.'''
Not all, but some of our customers plan their game time around when you make a delivery. After you accept a contract please be prompt with your delivery. Accepting a contract because you plan to do it in 2 days is '''NOT ALLOWED'''. Also, neglecting low reward or long distance contracts in favour of high reward and short distance contracts is '''NOT ALLOWED'''. '''Pushers who break these rules will be contacted directly by a PushX Director, Manager, or a Senior Pusher and possibly removed from the corporation if such behavior continues.'''
Bureaucrats, push, push-admin, push-director, push-manager, push-senior, Administrators
338

edits

Navigation menu