| 1 |
root |
1.1 |
This guide explains how to manage quests for player. |
| 2 |
|
|
|
| 3 |
|
|
A new command, 'quests', has been added to let players see quests they are doing or have done. |
| 4 |
|
|
It is not possible (unless specially made map to remove item) to do a quest twice. |
| 5 |
|
|
Quests can have multiple paths and/or solutions. |
| 6 |
|
|
|
| 7 |
|
|
Quests are managed through items in player inventory, inserted when needed. |
| 8 |
|
|
|
| 9 |
|
|
<being rewritten> |
| 10 |
|
|
|
| 11 |
|
|
Basics: |
| 12 |
|
|
* name_pl = internal quest name |
| 13 |
|
|
* custom_name = internal task name |
| 14 |
|
|
* add a "quest_override" to npc/magic ear, set its slaying and name_pl/custom_name |
| 15 |
|
|
and fill in message with match. hp determines condition (quest not started, ..., see |
| 16 |
|
|
quest.c for details) |
| 17 |
|
|
* in that quest_override add quest_[start|end]_[quest|task] with revelant fields set |
| 18 |
|
|
* ending a quest/task removes the start marker |