@Bladerunner I suppose. I know exactly what you are asking. Problem with wunderground. They don't have an 'error' line. So I am going to have to make something up. Something that looks at the variable and if $null, will reply to the user that the location is wrong.
I will look at that when I get the chance.
@Bladerunner I am not sure what you might be doing wrong. PM me your version of the code and I will review over it.
As I had mentioned before, You should only need to do the following:
@chachin , @Phil_FW version add's in code that will also ignore a user that signs off and signs back on a server with a new nick. My code at the top works just fine. But you are more than welcomed to use @Phil_FW's code if you have that issue.
@chachin You can use my botabuse script [url] http://www.hawkee.com/snippet/7858/[/url]
Just remove the semi-colon on line 56 and load the bot abuse script. This will limit the amount of requests before the bot will then ignore the user/ spam bot.
@chachin
Modify the sockclose area like a so:
Line 302: Remove the or !forecast5 from the if statement. This will keep it from spitting out the long info.
Code
Lines 324 thru 330. Change the bot from messaging the %wu_nick, to message the channel %wu_chan
@ryan7461035 !twitter v1.6 released. It includes the on/off function.
My bad for giving you bad direction. It needed to be placed in the "if (%t_2 != $null)" Section. I had copied/pasted from my wunderground script and didn't test it.
The v1.6 should work. It is set up for each individual channel of each network. (Aka you can be on irc.hawkee.net with twitter off on #bestchanever. But still have twitter on and working on irc.efnet.net's #bestchanever)
Hope this helps.
@ryan7461035 In the top area in the ;;; Network line. you could add a simular line for the chan and network. and have the line say simply t_cleanup | halt.
as for a switch function, who would you want to be able to control it? ops only of said chan? I will follow up next week when i am back near a computer. cant edit well on a smart phone :p
wu_cleanup is the alias at the bottom of the script right above the version history. Its used to clean up all the variables. Are you by chance missing it?
@RicJames No offense intended. I just look towards the obvious problems before diving deep in.
If I understand your first problem correctly. The !w is not working with registered users? I believe this stems back to the starting on:TEXT: line. I was having problems with the weather script responding to any command that started with a !w. ( Say !work, !whois, !wasted, etc) So I put a space after it. I will need to look at that more.
I am unclear as to the issue you are having with the WHILE inside the !alertinfo response. Could you elaborate further?
@RicJames The !w only works if the person/$nick is already registered with the BOT hosting the script and not the NickServ of that network. Have you !w REGISTER 90210 <-- to the $nick you are testing with?
@DragonHeart I did once in the past. And I am not sure where it is at the moment. (Gonna have to dig through my files) Thou I do recall, it uses the admin.cgi data page which requires a server user name and password.
Do you operate the server you want the song history for, or is it someone elses? If its some one elses, I will have try and create one for the public song history page, which may be a few as my schedule is busy.
@Yawhatnever Line 68 is ment to be commented out. It is a detailed 'status' giving you all the stats on the station. vs line 67 which only tells you if the station is online or offline.
and yes, on line 33, it has been corrected to %np_nick. I have had made this script years ago, but finally got around to posting it. So I may of messed up a few areas. Let me know if you find anything else.
@KilllerX I have a secondary script that works to prevent it.
The second line in the main alias code shows ;botabuse. Just remove the semi-collan and add the following script alias. This limits how many times someone can activate the bot before it will ignore the user.
That code is here: http://www.hawkee.com/snippet/7858/
If that won't work, let me know and I can adjust.
Updated script to v4.0
Added some changes to the script to allow the Local hosting client to also be able to activate the scripts.
Ex. Billy is hosting the script, and Kyle is also in the chan. Before, only Kyle could use the script. Now both Billy and Kyle can use the script.
V3.3
!alert has been corrected. Line 238 is looking in the code for a <alert count, and when it is found, is supost to remove all other text from said line. Well wunderground.com had changed that line, So I have corrected the script to reflect the new TOS text.
