After going through that part of code things look to be behaving as they should, even with your settings. If you pull the latest commit from git and set tvrage(debug) to DEBUG it may reveal what the problem is. It'll be quite verbose, though, so best to not leave it enabled constantly.
Thank you for looking into this. I compiled the latest Eggdrop 1.8 from CSV (the december 2012 build, wanted to do that anyway) and added only your script with my previous settings and now it works. Strange! Something must have been conflicting.
# Number of hours to adjust calculations for announcements by.
# For example, if the eggdrop runs on a computer set to CST
# and your announce country is US then you should set this to 1.
# If PST then this should be set to 0.
set tvrage(offsetHours) -5
The announcements are displayed at the right time for the US shows (EST). When people from the US use the schedule triggers however, yesterday/today/tomorrow, the script acts like UTC time and not EST.
When I'm writing this it's Sat Jan 4 00:29:20 GMT 2014. People from the US where it's still january 3rd get to see the saturday schedule when using !tonight. How can I solve this? Because most of my users are American, I would like it to follow the offsethours for schedule triggers as well.
As tvrage website is offline since 1 month and probably will never come back, does someone know an another eggdrop script with same command ? ( i just need !last and !next )
As tvrage website is offline since 1 month and probably will never come back, does someone know an another eggdrop script with same command ? ( i just need !last and !next )
As tvrage website is offline since 1 month and probably will never come back, does someone know an another eggdrop script with same command ? ( i just need !last and !next )