ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/deliantra/server/pod/events.pod
(Generate patch)

Comparing deliantra/server/pod/events.pod (file contents):
Revision 1.37 by root, Tue Apr 6 23:34:57 2010 UTC vs.
Revision 1.41 by root, Mon Oct 1 01:43:39 2012 UTC

226 226
227=head3 inscribe_note (book pl message skill -- ) 227=head3 inscribe_note (book pl message skill -- )
228 228
229Used whenever a book gets inscribed with a message. 229Used whenever a book gets inscribed with a message.
230 230
231=head3 infect (victim disease_type disease -- )
232
233Invoked whenever an object is diseased. The disease object is already
234inserted in object (the template disease object is C<disease_type>),
235but no messages have been generated. If overriden, no messages will be
236generated.
237
231=head3 trigger (object who -- ) 238=head3 trigger (object who -- )
232 239
233Invoked whenever a lever-like B<object> has been activated/triggered in some 240Invoked whenever a lever-like B<object> has been activated/triggered in some
234(manual) way. 241(manual) way.
235 242
384=head3 shout (player message --) 391=head3 shout (player message --)
385 392
386Invoked whenever the player uses the B<say>, B<chat> or B<shout> command, 393Invoked whenever the player uses the B<say>, B<chat> or B<shout> command,
387before it gets processed. 394before it gets processed.
388 395
389=head3 build (player builder map x y --) 396=head3 build (player builder map x y checkok --)
390 397
391Players tries to build using C<builder> at (map+x+y). Is invoked after the 398Players tries to build using C<builder> at (map+x+y). Is invoked after
392usual sanity checks, so the coordinates are valid. 399the usual map sanity checks, so the coordinates are valid. The boolean
400C<checkok> is true only if the build code thinks it is "ok" to build at
401that space, and normally you should only build when it is true.
393 402
394 403
395=head2 MAP EVENTS 404=head2 MAP EVENTS
396 405
397These events are generally dependent on a map and thus all have a map 406These events are generally dependent on a map and thus all have a map
441handled asynchronously as soon as the command reaches the server, even when 450handled asynchronously as soon as the command reaches the server, even when
442the player hasn't logged in yet (meaning there is no player yet). 451the player hasn't logged in yet (meaning there is no player yet).
443 452
444=head3 connect (client -- ) 453=head3 connect (client -- )
445 454
446Called as soon as a new connection to the server is established. Should 455Called as soon as a new connection to the server is established and the
447not be overriden. 456socket has been configured.
457
458=head3 version (client string -- )
459
460Called as soon as the version command from the client is received
461(normally the very first command sent).
448 462
449=head3 setup (client string -- ) 463=head3 setup (client string -- )
450 464
451Client sent the setup command to negotiate parameters. Handling is 465Client sent the setup command to negotiate parameters. Handling is
452mandatory and done by F<login.ext>. 466mandatory and done by F<login.ext>.

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines