It looks as if tvrage has changed the URL's need to pull the data. I've put out a new version with the corrected URL's in the default config, and one other bug fix. Alternatively you can add to tvrage.conf the following to fix the problem.Keksz wrote:hello,
I have a problem since today:
11:27 <@k3ksz> !tv Lost
11:27 <@Anno> {%%show_name%%} - URL: {%%show_url%%}
11:27 <@Anno> Last Episode: N/A
11:27 <@Anno> Next Episode: N/A
+tvquiet? I have no idea where you got this flag from but it's not one of the flags in my script. Is it perhaps something from rosc's updates?Keksz wrote: edit:
+tvquiet is not working, because of me or because the new version?
I had earlier an older version, 1.0 RC2 and now it's now working...
The bot announcing in public would be caused by the theme. Nothing related to this has changed in the script. Truth be told its been so many years since I've touched those particular pieces I had to look it up myself.Keksz wrote: edit2:
changed everything to msg, at the tvrage.conf, but I get still pub announce on the channel (whatever channel is set to tvquiet or not)
# Set triggers to pub(1) or msg(2).
set tvrage(pubTriggers) 2
You shouldn't have had to change back anything to get things working. No actual code has been removed and as you can see from the changelog the only thing at all that has been removed is some already commented out debug statements.Keksz wrote: edit3:
Changed back my version to 1.0 RC2 with the new URLs
There I have
# Set triggers to pub(1) or msg(2) or both (3)
set tvrage(pubTriggers) 3
in the config, which is working, some of the channels are set to PUB and some only to MSG
Which is good for me. It's working
But is there a way to add !last and !next commands to the script?GaveUp wrote:This can already be accomplished using the existing commands by modifying the theme file.
No, it was not possible to add your own triggers without making your own customizations to the script. This isn't the case any longer, though. I've just put up v2.0b1 that adds preliminary support for custom triggers. I'm not completely set on how it's done so it may change, but it does seem to be solid enough to be used. Any feedback or suggestions on this feature are welcome.sadnem wrote:But is there a way to add !last and !next commands to the script?GaveUp wrote:This can already be accomplished using the existing commands by modifying the theme file.
I mean, for what i read you say that we can edit the default theme to make !showinfo work as a !next, !last or whatever trigger, right? Or is it actually posible to add triggers only by modifyng the theme?
Thanks for the release but im triying to add a custom trigger and it allways displays the !showinfo results instead of the ones i want, for example i have in tvrage.conf:GaveUp wrote: No, it was not possible to add your own triggers without making your own customizations to the script. This isn't the case any longer, though. I've just put up v2.0b1 that adds preliminary support for custom triggers. I'm not completely set on how it's done so it may change, but it does seem to be solid enough to be used. Any feedback or suggestions on this feature are welcome.
Grab 2.0b1 here.
Code: Select all
#Custom1
set tvrage(cTriggerCustom1) "!sig"
set tvrage(cFlagsCustom1) "-"
Code: Select all
set tvrage(cTemplateCustom1) "PRIVMSG {%%chan%%} :{%%show_name%%}"