Administrator reports: ticker terminates too early, most likely utc VS local time problem ... #8473
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/petz
3. source/testserver
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/possible close
4. step/QA main
4. step/QA NOK
4. step/QA OK
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
kind/standalone
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#8473
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Administrator reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
It's still kinda weird... I guess "frequency" is aligned with the moment you run the command, not with the "end time".
Just to demonstrate what I mean:
If the ticker has frequency 1 hour, but runs only for 1 minute, I would expect it to say message once after one minute.
Instead, it says it once when you run it and never again.
If you have an event planned, and want people to remind about it every 1 hour, until 15 min before the event starts, you'd have to caculate frequency and starting time just right, instead of specitying
msg$1h$<15-min-before-event>True - the ticker is tied to the send-time, not the "finish" time. We could try to make that happen. So far, when an event requires more frequent ticker messages the closer it gets, I'd probably use the yl_scheduler to create those tickers. Or one could make a yl_ticker_addon. Most reasonable would be ofc to have the feature in the ticker itself.
The reaosn why tickers in general do not have guaranteed "showtime" is that we put them into buckets, to spread them over the chosen interval. Like when you have one ticker that is meant to run every hour, is displays once per hour. If you have three tickers that are intended to be displayed once per hour, they are spread out and one of them is displayed every 20 min. If we had guaranteed ticker showing connected to the "finish" time, we could satisfy only one of the conditions, either the spread or the guarantee.