*** General information ***
Before you start writing a guild you should write down all the powers
that you think you will have and all the drawbacks. There should
also be an explanation of how they fit in the guild.
It is also good if you add some information about the general
feeling of the guild.
Then you give this document to the guild coordinatior.
He/She will then tell you if it is ok to start coding or if
something has to be changed. This is because you shouldnt
have to code things that the guild coordinator not will approve later.

Then you write your guild. (See instructions below.)

When you are finished you have to add information to your document
about exactly how the powers/drawbacks works. After that the guild
has to be finally approven by the guild coordinator.
The document is then put in /open/GUILDS/GUILD_your-guild-name.
****************************


If you are a wizard and want to make a guild of your own, then you
should do this:

Copy the file /room/adv_guild.c, and make your own titles. It is 
important that your new guild has the same costs for advancement.
This is done by the call "room/adv_guild"->query_cost_for_level(l, e),
where 'l' is the current level of the player, and 'e' is the current
experience of the player. This function should return the cost in 
gold to advance for that player. Put this function call in
cost_for_level().

Why this extra call ? Because the file room/tune.h might get changed,
and the adv_guild.c reloaded with new costs. The cost to advance must
be the same in all guilds, as it should not be used for competition.

Don't forget to remove the lines for cloning of bboard, orc_slayer-quest
and the book in extra_reset().

Next step is to make an autoload object, that players will carry that
shows that they are a member of your guild. The object does not have
to be visible to the player, but it must have an id == "guild_mark".
You must also check that the player is not member of another guild,
by the call: present("guild_mark",this_player()).
It can happen that a player can lose his autoload object.

It is a requirement that all guilds must document all their features
in /open/GUILD_xxx, so that all wizards can see what they do. Not how
the features are implemented, but what features are implemented.

A normal thing with guilds are that they give some nice feature to the
player, like special "emotes", extra spells, and other fancy things.

It must be possible to leave the guild.

Players in your guild must also solve enough quests before becomming
wizard.


Things that are allowed:
Basically are all abilities that aren't too powerful allowed.

Limits:
Basically all guildpowers must cost sp or hp. (Exceptions from this 
can be made if the power has other great limitations.)
There has to be a logical connection between the guild and the abilities.

Teleporting to the guild from many different places in the game have to
cost at least 30 sp.
Healing may not be better then heal one hp per sp cost (in average).

The total abilities (including disadvantages) in a guild may not make 
the guild more powerful then mageguild.

The powers should be in proportion to the players level. That can be made by
not allowing abilities until a certain level or make them work less powerful
for low-level players.


Disadvantages (examples):
  The guild members may not use party object.
  The guild members may not use armours.
  The guild members may not have magobj.

Examples of things NOT counted as disadvantages:
  Playerkilling/Non playerkilling (That is only an attitude.)
  Hard to join the guild.
  Long or hard way to the guild.
  Certain alignment to advance level/stats.


Guildline/clubline:
===================
All guilds may have a guildline. It doesn't have to cost anything
to chat over a guildline, however there is a minimum cost for
clublines of 15 sp/chat.

The following 4 files in the /open/line library should be used when
  making a line:
1. /open/line/line.c         All functions needed for handling the line.
2. /open/line/send_player.c  A statue of the player that automatically will
                             be placed in the send_room.
3. send_room.c               The room for keeping statues for the line.
                             (Just make a copy of /open/line/send_room.c)
4. send.h                    All constants needed for specifying your own line.
                             (Make a copy of /open/line/send.h and make
                             your own adjustments)


Here is an example of how to write in your guild-object:
(OBS Do NOT change the order of these includefiles.)

#include "/players/your-name/send.h"
#include "/open/line/line.c"

init(arg) {
  init_line();
}
  


