These files contain the 'VMoo-client'-support for use 
with the JHcore MCP-implementation as it can be found at
http://www.awns.com/mcp/ .

Provided are the following files:
  README (This file)
  client.moo (client-support)
  wizme.moo (chown verbs to some wizard)
  lambdacore.moo (some basic adaptions to the core)
 
The first thing to do is to dump the information provided
in newclient.moo . Throughout the process you will find a
couple of tokens which should be replaced:
  __PACKAGE__  -> The generic MCP-package
  __CLIENT__   -> The object for client-support
  __WIZARD__   -> Should be removed at first. The verbs can
                  be chowned afterwards using wizme.moo
  __REGISTRY__ -> The MCP-registry object


After the client.moo has been dumped, the init_for_core-verb
on the newly created object should be executed. I have chosen
to corify the object OCLIENT as $client (@corify __OCLIENT__ as
client), so from now on I will refer to this object as
$client.

After dumping the object (oldclient.moo) you should use wizme.moo
to chown the verbs that need wizperms to some wizard
(In this case just one verb). Don't forget to use
@add-package __CLIENT__ to __REGISTRY__
to add the package to the registry.

------
About this package
------

-The newer versions of VMoo will include a 'auto-reconnect'-option.
 Although this can be very usefull under some circumstances it would
 make it very difficult to log off using the boot_player()-command
 and just booting an annoying player for a warning would be pointless.

 To make it clear to VMoo when it should just disconnect or when it
 should try to reconnect the $client:send_disconnect(<user>, <reason>)-
 command is provided. This command should therefore be used everywhere
 in the core just before 'boot_player()' is called to disconnect a
 logged-on player.

-The client-package will store information about the VMoo-versions
 used by the players. This information can be retrieved using the
 $client:get_client_info(<user1>, <user2>, ...)-command which will
 return lists of information about the versions used by user1, user2,
 etc (if available).


At your service,
Robbert de Haan (robbert@vmoo.com)

