When set on people will see changes to the field for everyone in their buddy list regardless of whether they are currently sharing any rooms.
Example:
/as field set buddy on
This is similar to FIELD SET WATCH except it works for the buddy list.
Defines the maximum length the specified field can be.
Example:
/as field Comment set limit 256
Once set the field cannot be changed during that chat session. Network operators will still be able to change their fields as often as they would like.
Example:
/as field Comment set once on
This can be used to encourage people to use fields for descriptive purposes and not to just play with them. In theory someone could try to flood people with their field changes, but set once would prevent this. It does, however, force people to settle for fields with any mistakes they may have made upon initial setting.
When set on people will see the field whenever they share a room and the field value changes.
Example:
/as field Comment set onchange on
By automatically seeing the field when it changes people do not need to check the field value to know what it is. They can look at the initial value and then know they will be informed if it changes.
People will see the field whenever they both share a room. So upon entering a room you will see this field for all the users and they will see yours.
Example:
/as field Comment set onjoin on
This is often a good setting for fields that provide descriptive material. It allows you to learn a little bit about each person in the room.
This setting limits the field to network operators.
Example:
/as field Comment set oper on
Many fields are nice to allow to all users, such as a space for them to put their age or job. But fields that are restricted to network operators make them easier for normal users to identify and harder for normal users to trick other people into thinking they are an operator.
When private is set on then only network operators can set or view the field.
Example:
/as field Comment set private on
This command creates fields that will work normally except be completely invisible to normal users.
This setting allows a field to be viewable from anywhere on the network. When it is off then fields are only shared between people on the same server.
Example:
/as field Comment set remote on
Whether you wish fields to be local or global will depend primarily on the nature of your network.
Allows you to define the data type that will go into this field.
Example:
/as field Comment set type text
When set on people will see changes to the field for everyone in their watch lists regardless of whether they are currently sharing any rooms.
Example:
/as field Comment set watch on
This can be used to send messages to people you are friends with. For example, you could create an away field that would notify everyone on your watch list when you switch it to away or back to here.
This setting causes the field information to show in a /whois command.
Example:
/as field Comment set whois on
This is a very good way to allow users to describe themselves without making the fields become overly annoying through constant updates. A few additional fields in the whois would allow for a full description that is only sent to users who ask for it.