Jump Freight Service: Difference between revisions

Jump to navigation Jump to search
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 11: Line 11:
# Standard contracts with less than 12 hours remaining
# Standard contracts with less than 12 hours remaining
# JF Rush contracts
# JF Rush contracts
# Standard contracts with less than 24 hours remaining


===JF Queue Priority Exceptions===
===JF Queue Priority Exceptions===
Line 38: Line 37:
#*Do not gate between LS systems, gate between NS systems, or warp in NS systems to deliver JF contracts.
#*Do not gate between LS systems, gate between NS systems, or warp in NS systems to deliver JF contracts.
#Upon delivering the package send a delivery mail to the customer (see [[Delivery_Mails|Delivery Mails]] for more information).
#Upon delivering the package send a delivery mail to the customer (see [[Delivery_Mails|Delivery Mails]] for more information).
== Special Cases ==
#'''Split JF Contracts:''' Customers are allowed to break a single JF contract up into several sub-JF 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, which is currently 500 unique items/stacks of items. PushX provides the Split JF service to avoid the usage of containers in JF Contracts and reduce overall costs for customers.
#*The total combined volume of these sub-JF contracts cannot exceed the volume limit for jump freight couriers.
#*The split JF contracts will be identified by 1/3, 2/3, 3/3, etc. in the contract description. Since the JF contract is split into several sub-JF contracts the reward and collateral will be spread across all the sub-JF contracts.
#*'''Split JF contracts must be picked up from the same station. Split-JF contracts CANNOT come from multiple stations in the same system.'''
#*Split JF Contracts from different customers forming one total JF contract are allowed, in the event members of the same corporation or organization wish to share the cost of a full JF trip but keep their assets separated into contracts.
#*The split JF contracts are meant to be delivered together, not separately, so DO NOT take 1/2 of a JF contract while leaving 2/2 behind for another JF Pilot to complete.
#'''Containers and Double Wraps''' Containers and double wraps are not allowed in JF contracts. It is often too difficult or time-consuming for a contractor to reach these dangerous and remote locations to station-trade a courier with an assembled container or double wrap. PushX provides the Split Contract service as an alternative to using containers in JF contracts.
#* JF Pilots are also allowed, at their discretion, to make special arrangements with the customer to pick up and deliver a JF contract containing containers provided the '''JF Pilot making the arrangements with the customer is the one who actually completes the JF contract'''.


== Erroneous JF Contracts ==
== Erroneous JF Contracts ==
Line 68: Line 56:


== Losing JF Permissions Due to Inactivity ==
== Losing JF Permissions Due to Inactivity ==
*After 30 days without completing a JF Contract, JF Pushers will lose their JF Team Permissions in PIR
*After 21 days without completing a JF Contract, JF Pushers will lose their JF Team Permissions in PIR
*When JF Team Permissions in PIR are lost, JF Pushers will be removed from the JF Team and lose their JF Team Permissions - this includes PushX SOV ACL access and JF Team communication channels.
*When JF Team Permissions in PIR are lost, JF Pushers will be removed from the JF Team and lose their JF Team Permissions - this includes PushX SOV ACL access and JF Team communication channels.
*In order to rejoin the JF Team, Pushers must reapply and wait in the same Applicant Queue as other applicants. This may not require retaking the JF Team Application Interview.
*In order to rejoin the JF Team, Pushers must reapply and wait in the same Applicant Queue as other applicants. This may not require retaking the JF Team Application Interview.
Bureaucrats, push, push-admin, push-director, push-manager, push-senior, Administrators
340

edits

Navigation menu