daydream reports: wonder if it's possible to mak ... #3508
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3508
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?
daydream reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
i guess this is technically possible but i don't know where that data is to be queried.
The messages are already three lines long when there are three things going on. One of which is the bailiff vote for more than 14 days. 7 days application phase, 7 days voting phase, then 3 to 7 day congratulations to the new bailiffs (depending on when Alias remembers to remove them).
Then there is usually at least one event going on and one vote.
Means, the whole screen is cluttered in blue, mobile users sometimes even can't read the first line, coz the third line moved it up.
Wall of text. Bad UI.
Let's make it that there's a chatcommand to display the announcements in a formspec.
Let's make it that when the announcement changes, those changes go to the discord.
Let's make it that not all announcements happen at the same time. Let's only display ONE at a time, but cycle them by the hour. So if we have 4 messages, message1 gets displayed immediately, message2 gets displayed after 15 minutes, message3 after 30 and message4 after 45 minutes. 60 minutes after, the first message gets displayed again.
Maybe we can also make it that persons who recently joined get those messages in a shorter interval, so that after 10 minutes or so they're up2date.
We need a way to add, remove and list the singular announcements.
/announcement_add
,/announcement_remove
and/announcement_list
sound straight forward./announcement
could be the command to display the formspec./announcement_list
should display them all and also provide IDs, which are needed to address them in the delete command./announcement_remove
would take an ID as a parameter and only remove this specific announcement. Then the order and interval must be rearranged to not skip any./announcement_add
takes a message. we could make it take a duration or a date when it autoremoves itself, but that's more than a bonus goal.Add them to the news formspec?
Alias wrote:
Er. If a major tries that, empty your chests, cut your losses and move to a better place. That city has no future unless the major is replaced or receives a brain update.