Its been a long time comming, but now it is that time again,
This time almost every file in the hubsoft has been edited one way or another so please be aware that there might be new issues/problems.
One thing that has changed is that during startup the command line is checked and it will abort straight away if there is something
it does not understand on the command line, this I guess will mostly effect linux users, but Windows users that runs the hub without the
gui console is also effected.
This means that on update and the following restart the hub might fail to restart IF the start-up parameters are incorrect, you have been warned!Another new thing is that we have added a few options and done som changes to better support the use of external bots with FlexHub.
While I personally prefer GBot (version 0.292 does now support nmdcs:// and some other new things and works well with FlexHub), there are other bots
(like the old Chimera) that also works with FlexHub. Due to that many of the bots are old (some are very old) and developed for Ynhub not everything will
work ofcourse.
Here is short introduction as to how you might set-up a bot to work together with FlexHub:
1. create a new profile for the bot
!addprofile Bots 6 Operator (create a new profile of level 6 using the existing profile Operator as a source. i.e it will be created with the same settings as the Operator profile)
(I prefer to make the bot one level higher than the normal Ops so they cant mess with it, but thats just me
, you can choose any level you want)
The profile should be operator and have a key, this will work best with FlexHub.
2. edit the profile
Do
!showprofile Bots to see what commands it is allowed to use, then do
!allow Bots command-name false to remove the right to use all the commands that the bot does not need (it usually do not need any at all).
Then do
!allow Bots command-name (or comma separated list of commands) to add the commands that you want it to be able to use
If you run the bot only from the same computer as the hub you can do
!override all to make it pass all the rule checks,
else its better to just add the overrides it actually needs, the override
checkmyinfo to allow it in even if its myinfo
and tag is 'weird' and not conforming to normal practice is almost always needed, plus some of the security overrides like
securitypm and
securitymc which makes it override the spam warnings/checks so it can send as much as it needs in main and PM.
3. add the bot user
!ar MyBot secretpassword Bots This should be enough to allow the bot to login successfully.
(It might be a good idea to also use bindip on the bot account, but that is for you to decide how you want to use it).
Then there is a couple of settings that you can use to change the interaction between FlexHub and the bot.
First there is the setting
!set ignore_unknown , what it does is make FlexHub ignore any unknown command and just display it in main like a normal
message instead of replying with the standard "Unknown command: xxxx". This setting can be used independent of other settings.
Second there is a group of settings that can be used to hide the commands from everyone but the one typing the command
the ordinary setting for cmd prefix (or trigger) is
!set cmd_prefixes and its default value is !+ which means that any hub command can be triggered
either with ! or +.
We have added a new setting:
!set cmd_prefixes_ext where you can set another command prefix (or trigger), if you for example set it to @, then
the hub can filter those command and only send them to the bot (this way they wont be displayed in main for everyone to see).
To do this you must also edit the profile for the bot like this :
!modprofile Bots extbot true to tell FlexHub that the user in that profile is an
external bot
For this update a restart of the hub is needed.
Use '!update now' in your hub or download it from the download section linked above.
Changelog for this release:
svn 1303
+ added : %[user_comment] for textcommands
+ added : Active Port protocol and Search Port UDP to !userinfo
+ added : The hub external IP is stored in settings so it is available directly after a restart (it can also be set manually with !set hubip)
+ added : attackstats reset added to help
+ added : new hub command !showautobans, similar to !showipbans but only lists the current autobans
+ added : new hub setting (!set advanced) : cmd_prefixes_ext, to define which command prefix the external bots listens to (to make the hub ignore them)
+ added : new hub setting (!set advanced) : ignore_unknown, to make the hub ignore unknown commands (useful toghether with external bots)
+ added : new profile setting : extbot, for use with external bots. Set this to true to make it possible to filter mc chat to and from the bot
+ added : showlog also show file date and size
* changed : !bindip can now be used with multiple IPs/ranges, use commas to separate, no spaces and there is no need to use * either
* changed : ADC DMSG rewritten
* changed : Yet another attempt at getting this right : #890996 adcs link not listed on reg https://bugs.launchpad.net/flexhub/+bug/890996, the default message has been improved and should now work better, you will need to do !set reg_msg -default to reset it. Also re-added the BindIP info that went missing in the last update.
Note that the %[address] variable does not contain the protocol ( it does not start with dchub:// or adc://) you must add that yourself, or change to use the other address variables %[address_nmdc], %[address_nmdcs], %[address_adc] or %[address_adcs] which does include the protocol part.
* changed : autoprotection of hubowner function rewritten
* changed : moved extra portinfo from !hubinfo to !corestats #964699 Hide open ports from public https://bugs.launchpad.net/flexhub/+bug/964699
- fixed : !resettimeout freezes the hub https://bugs.launchpad.net/flexhub/+bug/945476
- fixed : !say command can be used on hubowner https://bugs.launchpad.net/flexhub/+bug/944376
- fixed : !set hub_address would accept invalid addys
- fixed : !showlog now correctly handles reading from large log files
- fixed : !shownickbans didnt work with offset numbers (always showed only the first 50 bans)
- fixed : #924346 error on double bindip addings https://bugs.launchpad.net/flexhub/+bug/924346, bindip now properly support multiple IPs and/or ranges to be added
- fixed : #938071 Password shown on new master account from cmd line https://bugs.launchpad.net/flexhub/+bug/938071
- fixed : #941027 just another error https://bugs.launchpad.net/flexhub/+bug/941027 [FI] [-2] [ERROR] [NMDC_DataArrival] FlexHub/./protocols/Hub-ALL.lua:401: attempt to index field '?' (a nil value)
- fixed : #962308 !cmdhistory to show recent commands https://bugs.launchpad.net/flexhub/+bug/962308
- fixed : ADC feature broadcasts, reducing approx. 50% of ADC search traffic
- fixed : AccountManager:Check() now fixes some missing account info in ADCH imported accounts.
- fixed : Hub address on !set reg_msg https://bugs.launchpad.net/flexhub/+bug/941930
- fixed : added file exists check to AddHubFiles
- fixed : blocked too much client info when set show_tag was set to false
- fixed : changed default deflood settings to allow more connections
- fixed : changed parsing of PM's so GBot bug doesnt cause it to be disconnected
- fixed : default reg_msg changed to include line feeds before and after the message
- fixed : fixed so unknown/unsupported ADC supports dont show up in !ui
- fixed : import was missing some account information
- fixed : manual shutdown messages did not get sent to main
- fixed : minor fix to GetSVN function
- fixed : modcmd error on mixed case names for commands
- fixed : modcmd reporting nothing changed if only the helt text was modified
- fixed : references to tFuncs in Hub-Start.lua before Hub-Funcs is loaded fixed
- fixed : renamecmd and delcmd didnt handle mixed case names too well either
- fixed : return messages on error on !setprofile changed to something more usable
- fixed : settings that had a table of valid options wasnt correctly checked
- fixed : several fixes related to account generation, iLevel was missing, added nick == sNick validation to check (#902879 Account problems after !changereg command https://bugs.launchpad.net/flexhub/+bug/902879 )
- fixed : several of the set commands was missing right clicks, they should now all(almost) be available in the right click menu at FlexHub Menu/Settings, thanks Massi for reminding me 
- fixed : sorting textpatterns now on startup and reload, should fix all pattern priority problems
- fixed : the !set parser did not always pick the correct setting name
- fixed : topic echoed the new setting one extra time to the one setting the new topic. topic now also reports what the old topic was after changing it
NOTE: For !restart to work when running multiple FlexHubs, you'll have to make sure that the files you start the hub with, have a unique name. For Windows this means renaming both FlexHub.lua and FlexHub.exe (both the .exe and the .lua need to have the same name though), for Linux this means renaming FlexHub.lua only. So for example in Windows: rename FlexHub.lua to FlexHub1.lua and FlexHub.exe to FlexHub1.exe.
NOTE: Linux --nogui version needs the file: bit.so in the FlexHub lib-folder, available in the Linux archive in download section if you don't already have it. The FlexHub team currently does not support or supply Linux x64 versions.
NOTE: After '!update now' the hub will tell you if it needs a !restart or if you can just use !rs (reload scripts) instead. If the path to FlexHub.exe contains spaces the hub will have to be started once manually if it was running svn 1108 or earlier before updating, a correct restart script (for use with !restart) will only be created on manual startup.
Keep giving feedback!
Regards, the FlexHub team
5 Replies
10693 Views