There are some problems with the help file supplied with MUSHclient these days. The help file itself is basically sound, but it uses a format that is no longer supported by Windows XP, Vista, Windows 7 etc.
As a work-around, version 4.76 onwards of MUSHclient will have the entire "raw" help database supplied as a SQLite3 database called help.db in the main MUSHclient directory.
Since SQLite3 supports FTS (full text search) then you can make a plugin that does sophisticated boolean searches of the help files (eg. "alias NEAR trigger", "alias NOT trigger" or "alias AND trigger AND add").
The help database is a little idiosyncratic in design, for historical reasons, however an example plugin will be shipped that shows how you might extract usable data from it.
The example plugin (currently) just outputs help information to the main output window, however it could be amended to use a miniwindow, or maybe generate HTML files for use in your web browser.
You can use the "snippet" feature of the FTS search to generate snippets of the help to show the context. For example, searching for "alias NEAR trigger":
One possible way of displaying the help would be to combine the FTS searches with the utils.filterpicker function. This lets you filter output dynamically at runtime based on what is typed into the filter box. Thus you could refresh the help topics shown based on what is typed into the filter.
As a work-around, version 4.76 onwards of MUSHclient will have the entire "raw" help database supplied as a SQLite3 database called help.db in the main MUSHclient directory.
Since SQLite3 supports FTS (full text search) then you can make a plugin that does sophisticated boolean searches of the help files (eg. "alias NEAR trigger", "alias NOT trigger" or "alias AND trigger AND add").
The help database is a little idiosyncratic in design, for historical reasons, however an example plugin will be shipped that shows how you might extract usable data from it.
The example plugin (currently) just outputs help information to the main output window, however it could be amended to use a miniwindow, or maybe generate HTML files for use in your web browser.
You can use the "snippet" feature of the FTS search to generate snippets of the help to show the context. For example, searching for "alias NEAR trigger":
Functions
BroadcastPlugin - Broadcasts a message to all installed plugins
... of message (eg. trigger has fired = 1, alias matched = 2 ...
DeleteLines - Clears some recent lines from the output window.
... call DeleteLines from a trigger, alias or timer using send ...
ExportXML - Exports a world item in XML format
... lets you export one trigger, timer, alias, macro, keypad item ...
One possible way of displaying the help would be to combine the FTS searches with the utils.filterpicker function. This lets you filter output dynamically at runtime based on what is typed into the filter box. Thus you could refresh the help topics shown based on what is typed into the filter.


