When you first install Argo, the entire MUCK is treated as a single RP environment: system parameters and database entries are the same everywhere on the world. This may or may not be the way you want things to be set up. Some MUCKs have distinct areas with different themes: skills and objects that would be appropriate in one part of the MUCK might not be in others. Or, you might want to set aside a portion of the MUCK as a development or test area. The tool for dealing with these issues is the +realm command, which lets you designate a branch of the environment tree as a separate Argo environment.

The +realm command relies heavily on MUCK's `envirionment tree' structure. If you're not familiar with the idea, it might be useful to peruse the relevant pages of The MUCK Manual before reading further.

A `realm' is an area of the MUCK — that is, a branch of the environment tree — that is treated as an independent installation of Argo. When Argo is first installed, room #0 is designated as the parent of the `global' realm: all definitions and system settings are stored as properties on room #0, and are valid throughout the global realm. To add additional realms, or subrealms, go to the environment room that will be the parent of the realm, and type +realm #add, and follow prompts. When you create a new realm, it inherits all definitions and settings from the global realm, but is treated as an independent installation of Argo from this point onward. That is, any database entries you define (new object, abilities, NPC's, etc.) apply only within the new realm. You may delete material that was inherited from the global realm but is not appropriate to the newly created subrealm.

A related issue is that of IC and OOC areas. The coded effects of a number of skills, spells, and psionic abilities `break the rules' of normal MUCK security, allowing players to use exits that are locked against them, take objects from other players, and, indirectly, modify properties on other players. The distinction between IC areas and OOC areas provides a way of managing these `rule breaking' abilities, and prevent them from being used inappropriately. Some Argo commands and abilities — those which modify MUCK security — may only be used in areas (that is, branches of the environment tree) that you designate as 'in character'. Use the +icroom command to do this. The syntax is +icroom <#dbref of room>, which toggles the IC status of the designated room (i.e., if it wasn't an IC room, it becomes one; if it already was an IC room, it becomes an OOC room). The room argument defaults to `here', so you can also go to the environment room(s) in question and type +icroom without arguments.