Hint domain
Posted: 05 Oct 2011, 19:01
There are many obscure features, like where openkore just silently does nothing until you configure it (silently doing nothing on Auto Spell skill cast when autoSpell option wasn't configured), or where additional configuration may be useful, or where response is expected (party join request). We may add some hints where the user most likely would want (need) to do further configuration or do some actions. Also, group all those under some message domain (for example, "hint"), maybe even designate individual console color for it (for example, "darkcyan", isn't used in default configuration).
Hints may be easily disabled (squelchDomains). If there would be too many hints, a hint about how to disable hints may be added.
Hints may be somehow extracted by the interface and displayed separately (GUI may want that).
Example hints: http://openkore.svn.sourceforge.net/vie ... threv=7848
Also, that idea may just be applied to new/changing code for start, without much effort to apply it everywhere in the existing stuff.
Hints may be easily disabled (squelchDomains). If there would be too many hints, a hint about how to disable hints may be added.
Hints may be somehow extracted by the interface and displayed separately (GUI may want that).
Example hints: http://openkore.svn.sourceforge.net/vie ... threv=7848
Also, that idea may just be applied to new/changing code for start, without much effort to apply it everywhere in the existing stuff.