Update dev docs with new action/quester/diary designs

[sammypanda]

Should be focused on needs first, and kept as simple with as much freedom as possible.

use fake blocks for NPCs, subjective things need to be client-side as much as possible.
action options need to implement their own GUIs.

It should meet complex needs of quests:

• players chosing which actions/quests/stages to play where they are stacked
  • currently it just reports "...can't be placed on another NPC's spot. Please try setting yours elsewhere."
• re-checking action conditionals, rather than once and never checked again

done:

• ~diary_entries database table (added)
• non-linear structure (solved with multiple actions playing at once)
• multiple objectives (solved with multiple actions playing at once)
• multiple endings/results/responses (i.e. consequences) (solved with multiple actions playing at once)
• conditionals/conditions (added)
• queries of the questers diary (i.e. have they completed x quest, or y, or z); a Completion condition (added)
• interactions sparkles; fx (added)

deferred:

• hidden and explicit objectives; hiding from diary display?
• optionals; maybe, rather, marking a quest as x?
• teamwork/co-op; multiple players/diaries attached to one questclient?

abandoned:

• shared NPCs (with option to lock to the original creator)

---

and needs of future maintainability:

• code flexibility to do multiple quest editors
• general decoupling of all features from each other
• i can imagine most things should be lists even if they may only contain one element (like quest owners > quest owner).

..etc..

The v0.8 plan should be updated when this system has been thought through, designed and docs have been updated (after this is done).

[sammypanda]

Should be done, just writing the methods for #112 to figure out if everything has been considered.