Improve Reloading Quests and Improve SetObjectives

[Pychnight]

IF you add a invalid quest to the database it will prevent the quest list command from listing other valid quests, also ensure that default starting quests field is actually applied during reload.

Other Task

Improve Set Status to support multi-message objectives with multi-color (1 color per message)
Format

this should be maybe turned into a objectives list? where we can freely add and free objectives at will and have 5 objectives per page

• Previously known as set status
  party:setObjectives("string", index, color)

so party:setObjectives("test", 0, red) will override the objective in index 0 of the objective list
it will add the strings in order from 0 to whatever number.

[tbarela]

WIP:

If I'm following you on the first point, its much better now. As you've seen, it wasn't that hard to cause things not to reload. I've gone over it a bunch, and at least the obvious cases I was seeing are fixed. Much easier to edit things, /reload, and move on now.

I also completely revamped the status and saving code. SetQuestStatus has been updated to take indexes, so you can have multiple status's set. Also, its considered a per PartyMember thing now. Theres enumerable extensions for SetQuestState, so you can do something like party.SetQuestStatus(1,"Status #1",Color.Purple), which will give each PartyMember a quest status in their #1 slot that text and color. Theres no need to order the status's, or keep them tightly packed. /quest status will order them for you... but the paging display is not in yet.

Temporarily disabling quest status saving due to bug, and out of time for today.

[Pychnight]

progress update on this?

[Pychnight]

Confirmed as implemented and working as intended, closing issue