Guild Missions are quests created by a Guild's Guildmaster. You must be in a Guild in order to receive credit for a Guild Mission, though any player may party up with a guild member while they do their mission. A Mission may be comprised of one or more Mission Pieces. While you may have a plethora of Mission Pieces (MPs), a guild will only ever have one Mission. This mission is the sum of its active MPs. In order to allow for changing the mission, a Guild may have numerous inactive MPs.

There are three types of Guild Missions Pieces: Fetch, Kill, and Visit.

• Fetch Missions require a player to obtain an item and return it to a specific Guild NPC. The item will be destroyed when it is given to the Guild NPC while the mission is active. The GM must supply the item during the setup process so there can be no false positives/negatives in fulfilling the mission. Custom objects may be used but as the mission is dependent on the item's glance, name, and physical file name (thus an iron key from one dungeon cannot be replaced with an iron key from another), some custom items may not be feasible. For example, a forged sword would have the player's name as part of the glance and thus it would not make an appropriate template. A non-finished forge sword, or a forged ring which do not contain a player name, would be more appropriate.
• Kill Missions require a player to kill an NPC. In order to set up a Kill Mission, the GM will use the same interface for finding NPCs as the Scoreboard and, previously, Guildap.
• Visit Missions require a player to visit a place or NPC. These missions may only be performed for credit once per uptime given that they are (typically) so easy to complete.

Each Mission is comprised of separate Mission Pieces. For example, a mission might be to kill 25 ugly orcs AND return 25 short swords to a Guild NPC. When a player (of the appropriate guild) performs one of those actions, they will receive partial credit for doing so.

Credit is automatically calculated for a Mission Piece based on the following criteria:

• Fetch Mission Pieces: Credit shall be assigned based on the item's shop value and if the item may be stolen rather than requiring combat to obtain. The GM must supply whether or not the item requires combat during the setup process.
• Kill Mission Pieces: Credit shall be automatically assigned based on the difficulty of the NPC based on its level and battle ferocity.
• Visit Mission Pieces: Credit shall be a flat amount (very little) relative to other Mission types.

To review rewards, see "help mission rewards"

Ultimately, a Guild may have an infinite number of Mission Pieces from which to build their Missions. Mission Pieces are truly modular which may be 'activated' to form a cohesive Mission. That said, there are limits to the number of Missions that may be approved at a time and to the number of Mission Pieces that may be active during a given time.

1 Piece may be reviewed at a time, similar to GMEdit. Only 5 Mission Pieces may be made active each uptime. You will receive a one-hour window in which to disable a mission piece so that it will not count against you.

Mission Limits may be withheld during initial release.

You sure can! Only the person who completes the MP will receive credit, however. If a MP is to kill 20 orcs and you have a party of 5 players, 20 orcs must still die!

Yes, absolutely. But a Mission must reset before you can repeat it. For example, if a Mission consists of killing 100 orcs and fetching a sword, your guild will not receive repeat credit for the sword until 100 orcs have died; similarly, your guild will not receive repeat credit for killing orcs until the sword has been delivered.

Visit mission pieces are handled a bit differently. You do not need to complete them in order for the whole mission to reset, however resetting the mission (by completing its kill and fetch pieces) will also reset its visit parts. Additionally, due to being very easy to complete, visit pieces have an additional limit - any given player can earn credits for visiting each place/NPC only once per 24h (real time).