Core 2652

Coder Rules for Core 2652

Last Updated: June 3, 2002


This document describes the "wizard" rules that are specific to The Core. These rules will always take precedence over the rules and documentation that is standard with the Nightmare mudlib release. However, if a topic is not covered in this document, then the generic rules that came with the mudlib will apply. These rules are maintained and enforced by the head administrator of the game: Vice President Grey.

 

CODER POWERS

Coders are normal mortals. They cannot turn invisible, force players to do things, snoop players, or magically transport themselves or other players. The standard commands that allow coders to do these things have been removed from the game. For the purposes of maintaining game and site security, the "snoop" command is available for admins and members of the Enforcement group only. Coders may not write any object that duplicates or mimics the functions of the removed commands.

 

CODER BODIES

Coders are normal mortals, and improve their bodies through the normal means that are accessible to players. Do not write programs or use the "eval" or "call" commands to artificially change your stats, skills, hit points, age, credits, etc....

 

SUICIDING

If you suicide your character after you've obtained Codership, you will not be offered Codership again.

 

CLONING AND DESTING

The "clone" and "dest" commands may be used inside your own area for object testing purposes. Use of these commands outside of your area is considered magical (because you shouldn't be testing stuff outside of your area), and therefore illegal.

 

MAGIC

There is no such thing as magic here. Period.

 

TECHNOLOGY

Technology may be used by player and Coder alike, provided they do not conflict with the CODER POWERS paragraph above. Specifically:

  1. There shall not be any "cloaking" devices.
  2. There shall not be any "transporter" or matter transference devices. The Mass-transit system is an exception to this rule.
  3. There shall not be any monitoring devices (snoopers) that can either be placed in a player's inventory, or made to follow the player undetected.
  4. Stationary monitoring devices (room snoopers) are permitted. However, they must adhere to certain technological standards. If a room is "bugged", it must be detectable by some other device. You may "bug" your own area as you see fit. Be warned: if you "bug" another Coder's area, be prepared for the consequences if he/she finds out! Coders do not take kindly to the invasion of their privacy.
  5. The "tell" and "shout" commands are magical in nature, and therefore are not a part of this mud. Technological communication devices (such as the comm system) are permitted, provided that they adhere to certain technological standards. (Note: The "tell" command does work for tells to other muds).

 

TOYS

Coders can make personal technological devices (called "wizard toys" on other muds). These devices must use gerks for power. If you make a toy, you must put certain provisions in it so it won't function if it falls into the hands of players.

 

GADGET-TO-ROOM RATIO

Coders should concentrate on rooms and not on making "gadgets." These gadgets include "toys" and technological devices. To keep Coders focused, a ratio has been made.

Definitions:

 

TECHNOLOGICAL STANDARDS

Every technological device (computer, machine, or whatever) must adhere to certain standards:

  1. Technology requires energy. The exception to this rule would be a simple machine that can be powered by a human being (prime example: the lever). Every device that is considered to require energy must be given a "gerks" rating. 1 gerk is the lowest measurable amount of energy on The Core. The device must either have a gerk-per-use cost, or a gerk-per-reset() cost.
  2. So where do the gerks come from, then? Gerks come from either batteries or generators (steam generators, windmills, solar power, nuclear fusion, or whatever). Handheld devices should be either powered by replaceable batteries that can be purchased at shops, or they must interface with the player's prosthetic implant that is a power generator.
  3. Every device that comes into being must come from SOMEWHERE. In other words, you just don't pull a laptop computer out of your hip pocket and suddenly it just came into being. Devices either come from replicators (which must drain your energy allotment), or from being constructed out of mined natural resources.

 

PLAYING THE GAME

When you become a Coder, the game is not over. In fact, it changes dramatically. If you wish not to play, you can stay inside your area with a minimal energy allotment and write LPC code. This is perfectly acceptable. In fact, you don't even need a area if you don't want one. The City can arrange for private quarters for you within the confines of the City.

 

CODER CONDUCT

As a matter of pride, Coders do not directly help the Players. (this is a subtle way of saying DO NOT DIRECTLY HELP THE PLAYERS!!!!) Such "help" might consist of:

 

When in the City, or anywhere else, a Coder is not automatically the world's policeman. It is up to Enforcement to see that justice is done, so ordinary Coders should never take it upon themselves to become a game admin and "resolve a problem".

 

CODER SECRETS

Information that is available only to Coders should not be made available to players. This would include giving away stat information about monsters/players/Coders to players, quest information as mentioned above, and coding details (such as combat formulas, healing rates, etc.).

 

However, from time to time, the game administrator(s) may publish information about coding details if it is deemed appropriate.

 

EXCEPTION - THE U.S. CONGRESS CLAUSE

The single exception to the CODER CONDUCT rules applies when the Coder is within the confines of his/her own area. The Coder reigns supreme within his own area, and may run things however he wants. Even when other Coders are present, the Coder who owns the area always retains the upper hand. This means that Coders may administer "justice" (in a role-playing sense ONLY) within the confines of their own area.

 

This does NOT mean that you may kidnap a player and bring him inside your area so you can do whatever you want! Just like in the case of Dracula, the player (or Coder!) must enter your area under their own free will.

 

HARASSMENT

REGARDLESS of the above exception clause, harassment will not be tolerated anywhere in The Core... even within a Coder's own area. The Core defines "harassment" as the following:

  1. the continuance of unwanted sexual advances after the recipient has said no.
  2. verbal profanity directed at another player
  3. ANY form of a "curse" object. If you have created an object that you feel should be an exception to this rule, consult an admin.
  4. using your coder powers to modify or hinder a player in any way. This includes, but is not limited to: teleporting a player, changing a player's title skills or stats, forcing an NPC monster to attack or harass a player, echoing messages that impersonate a player, etc.

 

CODE OWNERSHIP

If you move, or request to be moved, your code out of the /ftp or /open directories, then that code becomes property of The Core. If you leave The Core, you may take copies of the code you wrote with you, but you may not erase the copies which reside on The Core.

You are not authorized to take copies of any code from The Core that was not written by you.

 

FTP SERVER

The Core runs an ftp server which allows Coders to upload and download files. As suggested in the CODE OWNERSHIP section above, the ftp server may not be used to get copies of files in the /std directory.

 

The location of the sever is:

ftp core.aa.net 5000

The ftp server will require you to sign in with your Coder character's name and password. People who aren't Coders will not be able to use the ftp server.

 

PROGRAMMING GUIDELINES

Please use meaningful variable names, and provide comments with your code. If I see anyone writing code with variables called "foo", I will throw a fit!

 

Do not attempt to circumvent any security features created by the game admin. This might include things like writing your own "summon" command, because the admin removed the pre-existing summon command.

 

Every "area" coded MUST BE MAPPABLE. The Senators will periodically commission a player to go through new areas with a piece of graph paper. No area may overlap another area, and no room may overlap another room. (You may, however, create additional floors. Even so, the "z" value must always be an increment of 10).

 

INACTIVITY

If you know you are going to be inactive for a long period of time (not logging on for 2 months or more), please notify Grey ahead of time. Also, please notify Grey if you do not intend to participate in the game any more, except for logging on every few days to chat.

 

If a Coder doesn't logon for 2 months or more, without having made prior arrangements, that Coder will be demoted.

 

If a Coder stops contributing to the game, their area space could be better used by an active contributing person. The inactive Coder can be demoted, and either have their area either moved to a less desirable location, or removed from the game entirely.

___________________________________________________

This page may be viewed from any browser, not just one from Redmond.
Last Modified: June 3, 2002
Page written by Dave Shay (
how to contact me).
Page content copyright ©1998,1999 by Dave Shay. Do not copy without express permission.