[ViewVC] Diff of: cvs/deliantra/server/pod/events.pod

Comparing deliantra/server/pod/events.pod (file contents):
Revision 1.37 by root, Tue Apr 6 23:34:57 2010 UTC vs.
Revision 1.40 by root, Tue Apr 13 18:57:06 2010 UTC

 =head3 shout (player message --)
 Invoked whenever the player uses the B<say>, B<chat> or B<shout> command,
 before it gets processed.
-=head3 build (player builder map x y --)
+=head3 build (player builder map x y checkok --)
-Players tries to build using C<builder> at (map+x+y). Is invoked after the
+Players tries to build using C<builder> at (map+x+y). Is invoked after
-usual sanity checks, so the coordinates are valid.
+the usual map sanity checks, so the coordinates are valid. The boolean
+C<checkok> is true only if the build code thinks it is "ok" to build at
+that space, and normally you should only build when it is true.
 =head2 MAP EVENTS
 These events are generally dependent on a map and thus all have a map
 handled asynchronously as soon as the command reaches the server, even when
 the player hasn't logged in yet (meaning there is no player yet).
 =head3 connect (client -- )
-Called as soon as a new connection to the server is established. Should
+Called as soon as a new connection to the server is established and the
-not be overriden.
+socket has been configured.
+=head3 version (client string -- )
+Called as soon as the version command from the client is received
+(normally the very first command sent).
 =head3 setup (client string -- )
 Client sent the setup command to negotiate parameters. Handling is
 mandatory and done by F<login.ext>.

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines