Standard Service: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
#Avoid using the autopilot while carrying contracts. | #Avoid using the autopilot while carrying contracts. | ||
#Check the Push Internal MOTD for any warnings about high sec systems. | #Check the Push Internal MOTD for any warnings about high sec systems. | ||
#Upon delivering the package send a delivery mail using the evemail generator to the customer. | #Upon delivering the package send a delivery mail using the evemail generator to the customer. | ||
== Special Cases == | == Special Cases == | ||
| Line 19: | Line 20: | ||
#'''Containers:''' For high sec service Push Industries discourages the use of containers in contracts and asks customers to avoid them when possible, but we do allow customers to place containers in contracts for several reasons: 1) when the number of item stacks is very high (200+) but the volume is low, 2) for allowing customers to organize a large number of items, and 3) to separate items from their own in the contract that might belong to a 3rd party. 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> | #'''Containers:''' For high sec service Push Industries discourages the use of containers in contracts and asks customers to avoid them when possible, but we do allow customers to place containers in contracts for several reasons: 1) when the number of item stacks is very high (200+) but the volume is low, 2) for allowing customers to organize a large number of items, and 3) to separate items from their own in the contract that might belong to a 3rd party. 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> | ||
#'''Low Sec (Small) Contracts:''' These are contracts that are meant to be completed in a blockade runner (with a covert ops cloak) or a deep space transport (with a MWD and a normal cloak). | #'''Low Sec (Small) Contracts:''' These are contracts that are meant to be completed in a blockade runner (with a covert ops cloak) or a deep space transport (with a MWD and a normal cloak). | ||
== Wrongly Priced Contracts == | == Wrongly Priced Contracts == | ||