Started by aik, August 31, 2015, 10:47 AM
0 Members and 1 Guest are viewing this topic.
Quote from: Marko on August 31, 2015, 10:50 AMOpen conversation with HB and type "allowsnooper" without / you were using. That should do the trick.Later, in #AG use !host commands.Does HB reply to you in any way, if not, can't help you, but other than that, solution above ^
Quote from: Marko on August 31, 2015, 11:25 AMHope someone else sorts this out as I'm out of ideas :/Good luck!
Quote from: CyberShadow on September 09, 2015, 02:51 PMI looked into this. It's caused by not using the "snooper" rank when using a snooper - this confuses HB. It will now send an appropriate error message.To fix this, just set your snooper to use the "Snooper" rank.
Quote from: CyberShadow on September 09, 2015, 10:31 PMYou would need to consult with the snooper author probably, however all rank-related code (not just in HB) assumes that if your rank is not "Unknown" or "Snooper", you are not using a snooper (i.e. you're using W:A itself).It's possible that it would be best if snoopers communicated third-party ranks via some other way than the WormNET rank field.
Quote from: aik on September 09, 2015, 10:39 PMbtw: If you whant to look into this even further - HB still doesn't reply when I send him i.e. "hello" - he used to anwer, that he's only a bot
Quote from: CyberShadow on September 09, 2015, 11:38 PMFixed, thanks. Will be applied on next restart.
Quote from: MonkeyIsland on October 18, 2015, 05:35 PMIs it fixed when you use snooper secure-logging with TUS too?
Quote from: CyberShadow on September 09, 2015, 10:31 PMYou would need to consult with the snooper author probably, however all rank-related code (not just in HB) assumes that if your rank is not "Unknown" or "Snooper", you are not using a snooper (i.e. you're using W:A itself).