qlog

[Kinni]

Suggestion Type: Command

Suggestion 1

Code: Select all

Sytax: qlog <keyword>
  Example: qlog spider 

I think it would be nice to search keywords from your qlog. Many times I've thought, "Hey, self. You have some quest having to do with a spider or some such. What was it you have to do again?" Being able to search the massive qlog for a keyword(s) would be super helpful!

Suggestion 2

Code: Select all

Syntax: qlog <location>
  Example: qlog Waterdeep

Many quests begin in one area but require journey to another. This command could function very much like the current 'qlog local' option, but an alternate location from which you currently standing could be reviewed. This way when So-and-So sends me from Waterdeep to Tantras, only or me to get there and go "What did I need?", I can easily type 'qlog Waterdeep' to review a list of what quests might have been assigned to me while I was in Waterdeep.

[Hrosskell]

For the first function I just use ctrl+f. It works on Windows w/ zMUD but not sure of other applications it'd catch in. As for the second, I believe local typically* shows up both in the zone it's coming from and going to.

*this probably depends on who wrote it and all that jazz, so your mileage may vary.

[Mele]

Qlog local is coded, FYI. :)

[Beskytter]

I really like the idea of having a searchable qlog. Both Besky and Eyo have long qlogs.
If not a searchable qlog, then perhaps a secondary one that only shows active quests?

So, qlog current (qlog cur) would display those quests from the full qlog that are still active.

[Timaeus]

Qlog Progress does show active quests only.

[Mohana]

Qlog Progress does show active quests only.

Good to know. I, like many others have a four plus page of Qlogs, and using the ctrl+f or Qlog local isn't always the best option. But even with Qlog Progress I still have a 3 page list. It would be nice to narrow it down a bit more.

[Raona]

I like this idea, but the translation from IC to code would be tricky and require constant refinement for the location option. That is, area filenames would be needed to filter, but they don't often overlap with IC names, and unless someone was constantly adding keywords to them (as with helpfiles) this would be of limited use. Even the breakdown by area can be confusing. (For example, the City of the Dead is its own area, and QLOG LOCAL only shows quests in that area when you are in it, not in Waterdeep more generally. QLOG <location> would require cityofthedead to search for the "right" thing, unless there was a lookup table to equate the IC City of the Dead to cityofthedead.)

The QLOG <keyword> idea is more workable, but perhaps not worth the effort to code if most clients have their own search function.

QLOG PROGRESS is an existing solution to the (fine!) QLOG current suggestion.

I touched up the QLOG helpfile to flesh these out a bit.

[Rhangalas]

Maybe qbits related to knowledge or reputation could be on a separate 'page'. That way, you don't have a page or three of "You are familiar with X region" or "You learned about so-and-so. Your knowledge of religion has increased."

[Raona]

Maybe qbits related to knowledge or reputation could be on a separate 'page'. That way, you don't have a page or three of "You are familiar with X region" or "You learned about so-and-so. Your knowledge of religion has increased."

Fair to put this more concretely as a request for additional options, like
QLOG KNOWLEDGE
and/or
QLOG GEOGRAPHY
QLOG RELIGION
perhaps making QLOG default to giving just QLOG QUESTS or somesuch?

[Hrosskell]

I like the QLOG QUESTS idea as default, with the others brought up only on specific request.

[Rhangalas]

Fair to put this more concretely as a request for additional options, like
QLOG KNOWLEDGE
and/or
QLOG GEOGRAPHY
QLOG RELIGION
perhaps making QLOG default to giving just QLOG QUESTS or somesuch?

Exactly. It would make it a lot easier (faster to look up in the middle of an RP) to RP what your character knows and not what you know as a player. Say my character saw a PC wearing the symbol of some obscure, lesser/minor deity or something, I could 'QLOG RELIGION' and it would output something similar to:

[Knowledge-Religion] Adept

You learned about X. Your knowledge of religion has been increased.
...

And so on. Same goes with the other knowledges... say a PC asked my character the location of something, I would QLOG GEOGRAPHY. If my PC doesn't know it offhand, maybe they would pull out some maps if they have them. Barring that, he would RP being unable to tell them.

That's just me though. I know the knowledges were meant for prestige, but since they are there... might as well use them for something.