sm-discuss AT lists.ibiblio.org
Subject: Public SourceMage Discussion List
List archive
Sorcery Consistency (WAS: Re: [SM-Discuss] devel sorcery & gaze new functionality)
- From: Paul Mahon <dufflebunk AT dufflebunk.homeip.net>
- To: sm-discuss <sm-discuss AT lists.ibiblio.org>
- Subject: Sorcery Consistency (WAS: Re: [SM-Discuss] devel sorcery & gaze new functionality)
- Date: Tue, 25 Jan 2005 18:36:28 -0500
gaze prune was moved into cleanse as --sweep, along with cast --fix
specifically to keep what scripts did consistent. This is how I break
things down:
* gaze is only used for looking at spell info/state,
* cast is only used for installing spells,
* dispel is only used to remove installed spells,
* scribe is only used to manage grimoires,
* cleanse is used only to test and fix system problems,
* sorcery is used to modify system wide state and updates, and
* summon for downloading stuff.
I believe this accurately reflects reality too.
On Tue, 2005-25-01 at 17:40 -0500, Sergey A. Lipnevich wrote:
> How about "gaze prune" then :-)? And how would one know that sorcery
> doesn't do what cast does? They both change the system. These are
> rhetorical questions, just to set people thinking.
> Cheers,
>
> Sergey.
>
> Seth Alan Woolley wrote:
>
> >I think the distinction between sorcery and gaze is that sorcery allows
> >you to do and set things, and gaze allows you to view things in a
> >read-only manner.
> >
> >Sorcery is an action with side-effects. Gazing is merely observing
> >(ignore the minor perturbations of quantum mechanics).
> >
> >Perhaps scribe should be used to set stuff with sorcery remaining as the
> >menu/gui tool.
> >
> >
> >
>
> --------------------------------------------------------
> The information contained in this message is intended only for the
> recipient, and may be a confidential attorney-client communication or may
> otherwise be privileged and confidential and protected from disclosure. If
> the reader of this message is not the intended recipient, or an employee or
> agent responsible for delivering this message to the intended recipient,
> please be aware that any dissemination or copying of this communication is
> strictly prohibited. If you have received this communication in error,
> please immediately notify us by replying to the message and deleting it
> from your computer.
>
> --------------------------------------------------------
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
>
Attachment:
signature.asc
Description: This is a digitally signed message part
-
Re: [SM-Discuss] devel sorcery & gaze new functionality
, (continued)
-
Re: [SM-Discuss] devel sorcery & gaze new functionality,
Sergey A. Lipnevich, 01/25/2005
-
Re: [SM-Discuss] devel sorcery & gaze new functionality,
Andrew, 01/25/2005
- Re: [SM-Discuss] devel sorcery & gaze new functionality, Duane Malcolm, 01/25/2005
- Re: [SM-Discuss] devel sorcery & gaze new functionality, Andrew, 01/25/2005
-
Re: [SM-Discuss] devel sorcery & gaze new functionality,
Andrew, 01/25/2005
-
Re: [SM-Discuss] devel sorcery & gaze new functionality,
Seth Alan Woolley, 01/25/2005
- Re: [SM-Discuss] devel sorcery & gaze new functionality, Sergey A. Lipnevich, 01/25/2005
- Re: [SM-Discuss] devel sorcery & gaze new functionality, Andrew, 01/25/2005
- Re: [SM-Discuss] devel sorcery & gaze new functionality, Seth Alan Woolley, 01/25/2005
- Re: [SM-Discuss] devel sorcery & gaze new functionality, Sergey A. Lipnevich, 01/25/2005
- Re: [SM-Discuss] devel sorcery & gaze new functionality, Arwed von Merkatz, 01/25/2005
- Sorcery Consistency (WAS: Re: [SM-Discuss] devel sorcery & gaze new functionality), Paul Mahon, 01/25/2005
- Re: Sorcery Consistency (WAS: Re: [SM-Discuss] devel sorcery & gaze new functionality), Seth Alan Woolley, 01/25/2005
-
Re: [SM-Discuss] devel sorcery & gaze new functionality,
Sergey A. Lipnevich, 01/25/2005
- Re: [SM-Discuss] devel sorcery & gaze new functionality, David Kowis, 01/25/2005
Archive powered by MHonArc 2.6.24.