Skip to content

Nameless MUCK (NMC Project)

Sections
Personal tools
You are here: Home » Development » Discussion » Internals of the New Version
« July 2008 »
Su Mo Tu We Th Fr Sa
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    
 

Internals of the New Version

Details that make no sense to normal people.

Use this section for discussions on internal details.

There is absolutely no reason this should make sense to anyone non-technical. Feel free to use all the jargon desired!

Please don't complain if you don't understand, but feel free to ask what someone means. Fair warning: developers aren't always the most politically correct people you'll find!

Created by admin
Last modified 2004-04-16 02:42 PM

Things pending

Posted by admin at 2004-04-23 02:26 PM
  1. Player and character interactive messaging
  2. process control
  3. object creation and destruction
  4. relationship establishment and disconnect
  5. registering/unregistering for events
  6. event submission
  7. property management: clearing, reading, setting and listing
  8. rich text
  9. scripting hooks
  10. remote object access
  11. remote automation access (client access MU remotely)
  12. remote service invocation (server requests remote server to run something)

Permission notes

Posted by admin at 2004-04-24 03:20 PM

Permissions are the right to do something. They can be granted to people or groups of people.

They can be specified as being in one of three modes: none, grant, revoke.

Each account has a stack of permissions. The newer entries are placed "on the top" of the stack. When an attempt to carry out something is done, the stack is searched "from the top down".

If a revoke it hit, searching stops and the request fails.

If a grant is hit, a pending success is recalled and the searching down the stack continues. If nothing revokes that grant, then the request passes.

If neither a grant nor a revoke is it, the request fails.

To disable someone from doing something, a revoke permission for it can be placed on their permission stack. If they don't have permission to update their stack, then they can't remove it.

This would even work for someone with lots of permissions. Put a revoke on everything on to their stack, and they lose all their permissions. Remove it later, and it's like it never happened. This is an alternative to trying to edit out or change what they have. It lets you undo a permission update very easily.

 
 

Powered by Plone

This site conforms to the following standards: