JeCel reports: The mail notification for rece ... #2505
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/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/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
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#2505
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
JeCel reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
i remember there was an attempt to limit the spamminess of the "you have mail in a mailbox!" alerts, but it never seemed to work quite right.
I made it that only the first tossed item creates an email immediately, but all the items tossed after the first during the next hour are collected in one.
Reasoning is that when someone gets tossed one item, the mailbox doesn't know whether more may come. So we send out a mail right after the first, to inform the person at once. Come more items, the player still gets informed when not online or not paying attention. If he does and rushes towards the mailbox, he finds the other items anyways, mail or not.
Sure, we could make it that even after the first item, a timer waits for a second item. If that doesn't happen before the timer runs out, we send a mail. Every new item in the mail extends the timer and the mail is only sent, after the timer ran out.
one alternate is that it could wait a while (5 minutes?) to see if anything else is put in the mailbox, before sending the first email.
as it stands, at least the current system cuts down on the spam.
fixed in
7820314597
Somehow I don't get mails at all now?
how long did you wait? it takes 15 minutes, which ought to be a config option.
tested that it comes after 15 minutes on the test server:
added options to allow easy configuration:
7c1cc8ac50
Nice. This time I received the mail after the default 15 seconds :)
this is live. i think the response time is a bit low, but it'll still help w/ the spaminess.