The Questlog... but how?

[Jaxad0127]

The second is better for dynamic quests. The first would require character variables to store everything needed to recreate all details of the dynamic quest, which could be a lot (if the description can vary significantly). Of course, if character variables can store strings, we can just store descriptions that way.

[Ablu]

Of course, if character variables can store strings, we can just store descriptions that way.

Short note, though this is bit offtopic probably: Manaserv character variables can _only_ store strings (well you can store numbers as strings and convert them, but in the database only strings exists)

Regards,
Ablu

[atheros]

Quest Update { Quest Id, Flags [ State, Title, Description, Goal ] }

Do we need the "state" field? Since while quests arn't finished, they are active, when they gets finished for whatever reason (success, failure, cancelation, ...) they are destroyed on server side.

[Bjørn]

Quest Update { Quest Id, Flags [ State, Title, Description, Goal ] }

Do we need the "state" field? Since while quests arn't finished, they are active, when they gets finished for whatever reason (success, failure, cancelation, ...) they are destroyed on server side.

Hmm, I mainly put that there cause I thought it would be confusing to put it in the flags. Possibly values are New, Finished, Failed or Canceled. And indeed it's not something that needs to be stored server-side.