Standard Service: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
(2 intermediate revisions by 2 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 x-small 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 12: Line 12:
#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 18: Line 18:


#'''Split Contracts:''' Customers are allowed to break a single contract up into several sub-contracts (all going from the same pick up station to the same destination station) if the number of item stacks in the contract exceeds EVE Online's item stack limit for contracts. The total combined volume of these sub-contracts cannot total more than the max size we offer for the service type. These sub-contracts could be identified by 1/3, 2/3, 3/3, etc. in the Info by Issuer field. Since the contract is split into several sub-contracts the reward and collateral will be spread across all the sub-contracts. These sub-contracts are meant and designed to be delivered together, not separately, so DO NOT take 1/2 of a contract while leaving 2/2 behind for another Pusher to complete.<br>&nbsp;
#'''Split Contracts:''' Customers are allowed to break a single contract up into several sub-contracts (all going from the same pick up station to the same destination station) if the number of item stacks in the contract exceeds EVE Online's item stack limit for contracts. The total combined volume of these sub-contracts cannot total more than the max size we offer for the service type. These sub-contracts could be identified by 1/3, 2/3, 3/3, etc. in the Info by Issuer field. Since the contract is split into several sub-contracts the reward and collateral will be spread across all the sub-contracts. These sub-contracts are meant and designed to be delivered together, not separately, so DO NOT take 1/2 of a contract while leaving 2/2 behind for another Pusher to complete.<br>&nbsp;
#'''Containers:''' For high sec service Push Industries discourages the use of containers in contracts and asks customers to avoid them when possible via usage of our Split Contract service. We will provide container service for contiguous HS to HS contracts using our Nano, X-Small, and Small services only, and our Nano Service will allow containers for low-sec and null-sec contracts.  Containers are NOT ALLOWED in Freighter and JF-class shipments. Our Quote Tool provides a warning to the customer that containers are disallowed based on the contract type they have quoted, and we require that customers identify when containers are present in an allowed contract by indicating so in the contract description. However, this does not always happen and the only way for Pushers to identify contracts with containers is after they have already accepted them. In the case where a Pusher accepts a contract with a container that freight package will have to be directly traded between the contractor and the hauler at the pick up station and again at the destination station. '''A CONTRACT CONTAINING A CONTAINER CANNOT BE RE-CONTRACTED.''' This means that the contractor and the hauler must be on different accounts to be logged in simultaneously to perform the trade.<br>&nbsp;
#'''Containers:''' For high sec service Push Industries discourages the use of containers in contracts and asks customers to avoid them when possible. We require that customers identify when containers are present in a contract by saying so in the contract description. However, this does not always happen and the only way for Pushers to identify contracts with containers is after they have already accepted them. In the case where a Pusher accepts a contract with a container that freight package will have to be directly traded between the contractor and the hauler at the pick up station and again at the destination station. '''A CONTRACT CONTAINING A CONTAINER CANNOT BE RE-CONTRACTED.''' This means that the contractor and the hauler must be on different accounts to be logged in simultaneously to perform the trade.<br>&nbsp;
#'''Low Sec (Small):''' These are contracts that are meant to be completed in a blockade runner (with a covert ops cloak).
#'''Low Sec (Small):''' These are contracts that are meant to be completed in a blockade runner (with a covert ops cloak).


Bureaucrats, push, push-admin, push-director, push-manager, push-senior, Administrators
338

edits

Navigation menu