Packages

p

net.psforever

services

package services

Ordering
  1. Alphabetic
Visibility
  1. Public
  2. Protected

Package Members

  1. package account
  2. package avatar
  3. package chat
  4. package galaxy
  5. package hart
  6. package local
  7. package properties
  8. package support
  9. package teamwork
  10. package vehicle

Type Members

  1. class CavernRotationService extends AnyRef

    A service that assists routine access to a series of game zones through the manipulation of connections between transmit point structures.

    The caverns were a group of game zones that were intended to be situated underground.

    A service that assists routine access to a series of game zones through the manipulation of connections between transmit point structures.

    The caverns were a group of game zones that were intended to be situated underground. Access to the caverns was only sometimes possible through the use of special above-ground warp gates called geowarps (geowarp gates) and those geowarps were not always functional. Usually, two caverns were available at a time and connections to these caverns were fixed to specific active geowarp gates. The changing availability of the caverns through the change of geowarp gate activity was colloquially referred to as a "rotation" since it followed a predictable cycle. The cycle was not just one of time but one of route as one specific geowarp gates would open to the same destination cavern.

    The client controls warp gate destinations. The server can only confirm those destinations. The connectivity of a geowarp gate to a cavern warp gate had to have been determined by opening the cavern with an appropriate packet and checking the map description of the cavern gates. The description text explains which of the geowarp gates in whichever zone has been connected; and, where usually static and inanimate, that geowarp gate will bubble online and begin to rotate and have a complementary destination map description. Opening different combinations of caverns changes the destination these warp gate pairs will connect and not always being connected at all. The warp gate pairs for the cavern connections must be re-evaluated for each combination and with each rotation and all relevant pairings must be defined in advance.

    See also

    ActorContext

    Building

    ChatMsg

    Config.app.game.cavernRotation

    GalaxyService

    GalaxyAction.LockedZoneUpdate

    GalaxyResponse.UnlockedZoneUpdate

    InterstellarClusterService

    org.log4s.getLogger

    resources/zonemaps/lattice.json

    SessionActor

    SessionActor.SendResponse

    StashBuffer

    WarpGate

    Zone

    ZoneForcedCavernConnectionsMessage

    ZoneInfoMessage

  2. class GenericEventBus[A <: GenericEventBusMsg] extends ActorEventBus with SubchannelClassification
  3. trait GenericEventBusMsg extends AnyRef
  4. class InterstellarClusterService extends AbstractBehavior[Command]
  5. abstract class RemoverActor extends SupportActor[Entry]

    The base class for a type of "destruction Actor" intended to be used for delaying object cleanup activity.

    The base class for a type of "destruction Actor" intended to be used for delaying object cleanup activity. Objects submitted to this process should be registered to a global unique identified system for a given region as is specified in their submission.

    Two waiting lists are used to pool the objects being removed. The first list is a basic pooling list that precludes any proper removal actions and is almost expressly for delaying the process. Previously-submitted tasks can be removed from this list so long as a matching object can be found. Tasks in this list can also be expedited into the second list without having to consider delays. After being migrated to the secondary list, the object is considered beyond the point of no return. Followup activity will lead to its inevitable unregistering and removal.

    Functions have been provided for override in order to interject the appropriate cleanup operations. The activity itself is typically removing the object in question from a certain list, dismissing it with a mass distribution of ObjectDeleteMessage packets, and finally unregistering it. Some types of object have (de-)implementation variations which should be made explicit through the overrides.

  6. class ServiceManager extends Actor

Ungrouped