VerliLinker SVN
Status: Beta
Brought to you by:
burek021
File | Date | Author | Commit |
---|---|---|---|
README.txt | 2009-11-29 | burek021 | [r12] |
links.lua | 2010-01-04 | burek021 | [r29] |
links_nmdc.lua.lib | 2010-01-04 | burek021 | [r28] |
utils.lua.lib | 2010-01-04 | burek021 | [r29] |
------------ INSTALLATION ------------ Copy all 3 files into your Verlihub scripts folder (most probably it is "/etc/verlihub/scripts"): - links.lua - links_nmdc.lua.lib - utils.lua.lib Edit the file "links.lua" and configure the options you want. Close the file. Type in your Verlihub: !luaload /path/to/verlihub/scripts/links.lua (for example "!luaload /etc/verlihub/scripts/links.lua") After that, type: !links to get some more help about the command usage. Also, take a look at this example configuration of hub network: http://forums.verlihub-project.org/viewtopic.php?f=102&t=4732 ----- NOTES ----- - Make sure you don't leave "classdif_kick" set to 0 because that will allow remote ops/admins to kick your ops/admins of the same class, so at least set this variable to 1, using !set classdif_kick 1 That way remote ops/admins of the same class can only kick classes lower than the class they have on their own hub. - Make sure you editted file links.lua and set the variable "links_my_prefix", otherwise you wont be able to load the script