Package atavism.server.events

Contains classes to parse and generate client messages/events.

See:
Description

Class Summary

AcquireEvent	an object is attemping to acquire another object
AcquireResponseEvent
ActivateItemEvent
AmbientLightEvent	this event contains information about the ambient light.
AttachEvent
AuthorizedLoginEvent	this client is logging into the server (proxy usually)
AuthorizedLoginResponseEvent
AutoAttackEvent
ClientParameterEvent
ComEvent
CommandEvent
ConResetEvent	the server is being told that the connection has been reset for a particular user.
DetachEvent
DirectedEvent	use this event when you want to send a particular event to multiple recipients on a single connection.
DirLocOrientEvent
DropEvent
ExtensionMessageEvent
FragmentedMessage	fragmented message sometimes the an event is split up into seperate subevents, stored in this fragmentedmessage.
FreeTerrainDecalEvent
IslandManifestEvent	this event contains information about the worldfile the server usually sends this event to the user when they log in in the loginhandler.
JScriptEvent	execute the passed in script
LoadingStateEvent	tells the client when we start and stop loading a new scene
LoginEvent	this client is logging into the server (proxy usually)
LoginResponseEvent
LogoutEvent	the user is logging out
LogoutResponseEvent
ModelInfoEvent	send out what meshes to draw for the given object it is a full update, so if you unequip a rigged attachment, a full update is sent out
MultiEvent	an object is attemping to acquire another object
NewLightEvent	new light information when receiving this event, please note that the loc information for the point light is not set in the light.
NewObjectEvent	the world server is telling a different server about a new object without serializing the obj - we dont serialize to the entitymgr because it doesnt need the full object
NewTerrainDecalEvent
NotifyFreeObjectEvent
NotifyNewObjectEvent	this event is saying notifyObj needs to know about a new object the event handler should send it a newobj message
NotifyPlayAnimationEvent	object *IS* playing an animation - this event says other need to know about this obj's animation - we have the list as part of the event because this event may be serialized and the other server/client wont know what the list should be
PortalEvent	signals that a mob is portaling - this shouldnt come from the client because we dont check if its allowed or anything.
RegionConfiguration	this event contains information about the regions in the world and what goes inside of them, like forests
RegisterEntityEvent	the server is receiving a serialized entity in this event the proxy server sends the approp world server the serialized entity.
RegisterEntityResponseEvent	we are responding a registerentity event we use the data stored rather than the getEntity.toBytes() when we call toBytes() because its what the server tells us that is the correct information.
RoadEvent	sends the client information about a road
SaveEvent	tells the server to save all persistent objects
SceneLoadedEvent	this event contains information about the worldfile (scene) the server usually sends this event to the user when they log in in the loginhandler.
ScriptEvent	send the target object/mob an event so that it can do something
SkyboxEvent	this event contains information about the skybox the server usually sends this event to the user when they log in in the loginhandler.
StateEvent	sends the client state information
TerrainEvent	this event contains information about the terrain the server usually sends this event to the user when they log in in the loginhandler.
TimerEvent
UITheme
UnregisterEntityEvent
UnregisterEntityResponseEvent	we are responding to a unregisterentity event
WorldFileEvent	this event contains information about the worldfile (scene) the server usually sends this event to the user when they log in in the loginhandler.

Package atavism.server.events Description

Contains classes to parse and generate client messages/events.

The client API uses the term "message" for all communication with the server. The server uses the term "event" for messages to/from the client and "message" for messages betweeen server plugins.