In a message dated 7/19/00 6:46:37 PM Central Daylight Time,
> Maybe there's some middle ground: Perhaps you let players write whatever
> code they want, but you place restrictions on what API's they're allowed
> to call and what arguments they're allowed to pass. Like a system of
> permissions: root can call anything he wants, but if sword wants to call
> wound(), then the parameter it passes must be in the range allowed by the
> server-side 'wound-permissions' database. Permissions cost money - it
> costs you N credits to load an object and give it wound(0..M) permissions
> - so you create a market for conjoured/contructed swords, or anything else
> (magic portals, flying carpets) that does something not allowed by the
> defaults. Idk - just a thought.
Isn't this basically what Mark Miller's been working on for the last few
years with Electric Communities?
Greg Burch <GBurch1@aol.com>----<firstname.lastname@example.org>
Attorney ::: Vice President, Extropy Institute ::: Wilderness Guide
http://users.aol.com/gburch1 -or- http://members.aol.com/gburch1
ICQ # 61112550
"We never stop investigating. We are never satisfied that we know
enough to get by. Every question we answer leads on to another
question. This has become the greatest survival trick of our species."
-- Desmond Morris
This archive was generated by hypermail 2b29 : Mon Oct 02 2000 - 17:34:54 MDT