daydream reports: wonder if it's possible to mak ... #3508

Open
opened 2023-01-13 22:35:31 +00:00 by yourland-report · 4 comments

daydream reports a bug:

wonder if it's possible to make the please vote message RED if you haven't voted yet instead of blue to draw your attention to which vote you didn't do yet - so it would be a separate message for each vote opportunity obviously but sometimes I don't realize another thing has been added and I think I've done it already cuz things are added in a random way instead of "this month's votes are x" do all of them or whatever

Player position:

{
	z = 1563.8000488281,
	x = 2112.3168945313,
	y = 7.5
}

Player look:

{
	z = 0.99029016494751,
	x = 0.014002013020217,
	y = 0.13830886781216
}

Player information:

{
	minor = 6,
	ip_version = 6,
	min_rtt = 0.15700000524521,
	avg_rtt = 0.16599999368191,
	min_jitter = 0,
	max_jitter = 1.9900000095367,
	avg_jitter = 0,
	connection_uptime = 2125,
	serialization_version = 29,
	patch = 1,
	version_string = "5.6.1",
	lang_code = "",
	protocol_version = 41,
	state = "Active",
	max_rtt = 2.1640000343323,
	major = 5,
	formspec_version = 6
}

Player meta:

{
	fields = {
		xp = "1055196",
		["stamina:exhaustion"] = "108.5",
		repellant = "0",
		["petz:werewolf_clan_idx"] = "2",
		["petz:werewolf"] = "0",
		["unified_inventory:bags"] = "return {\"water_life:croc_bag\", \"water_life:croc_bag\", \"water_life:croc_bag\", \"water_life:croc_bag\"}",
		placed_nodes = "192085",
		["3d_armor_inventory"] = "return {\"3d_armor:helmet_crystal 1 1160\", \"shields:shield_crystal 1 1160\", \"3d_armor:chestplate_crystal 1 1160\", \"3d_armor:leggings_crystal 1 1160\", \"3d_armor:boots_crystal 1 1160\", \"\"}",
		digged_nodes = "1312063",
		punch_count = "64416",
		partychat = "party",
		["signslib:pos"] = "(2006,18,1643)",
		hud_state = "on",
		arenalib_infobox_arenaID = "0",
		["ocean_build.last_warning"] = "1.65235e+09",
		played_time = "12956147",
		["ocean_build.ocean_built"] = "8",
		yl_commons_thankyou = "206",
		died = "194",
		yl_church = "return {[\"last_death\"] = {[\"z\"] = 1997, [\"x\"] = 2460, [\"y\"] = 7}, [\"last_death_portal\"] = 1673600980}",
		yl_commons_player_created = "1650064821",
		yl_commons_player_joined = "1673647237",
		xp_redo_hud_color = "0xFFC001",
		jointime = "1650064821",
		bitten = "0",
		["petz:lycanthropy"] = "0",
		crafted = "2403",
		["petz:old_override_table"] = "return {[\"new_move\"] = true, [\"sneak\"] = true, [\"sneak_glitch\"] = false, [\"jump\"] = 1.5, [\"speed\"] = 2, [\"gravity\"] = 1}",
		inflicted_damage = "1290516",
		["stamina:level"] = "11",
		["petz:werewolf_vignette_id"] = "5",
		["stamina:poisoned"] = "no"
	}
}

Log identifier


[MOD] yl_report log identifier = Q8mcg82tB1WUI0gjm6Vive4PU3Cnlmam

Profiler save:

profile-20230113T223531.json_prettyEE

Status:

# Server: version: 5.6.1-yl | game: Minetest Game | uptime: 2d 9h 28min 38s | max lag: 3.52s | clients (26/42): AliasAlreadyTaken, Bailiff, Boot, Chache, Chazz, daydream, do_ob, DragonWrangler1, Elias, Ernesto, flux, itaca94, johanlegend, labrat, Lucien_II, micaias, niceride, Parrish, Pocrom, Queenfire234312, rabenkind, rewired_X, Service, shanish2, Therottenpotato, yoneda

Teleport command:

/teleport xyz 2112 8 1564

Compass command:

/give_compass Construction Q8mcg82tB1WUI0gjm6Vive4PU3Cnlmam D2691E 2112 8 1564
daydream reports a bug: > wonder if it's possible to make the please vote message RED if you haven't voted yet instead of blue to draw your attention to which vote you didn't do yet - so it would be a separate message for each vote opportunity obviously but sometimes I don't realize another thing has been added and I think I've done it already cuz things are added in a random way instead of "this month's votes are x" do all of them or whatever Player position: ``` { z = 1563.8000488281, x = 2112.3168945313, y = 7.5 } ``` Player look: ``` { z = 0.99029016494751, x = 0.014002013020217, y = 0.13830886781216 } ``` Player information: ``` { minor = 6, ip_version = 6, min_rtt = 0.15700000524521, avg_rtt = 0.16599999368191, min_jitter = 0, max_jitter = 1.9900000095367, avg_jitter = 0, connection_uptime = 2125, serialization_version = 29, patch = 1, version_string = "5.6.1", lang_code = "", protocol_version = 41, state = "Active", max_rtt = 2.1640000343323, major = 5, formspec_version = 6 } ``` Player meta: ``` { fields = { xp = "1055196", ["stamina:exhaustion"] = "108.5", repellant = "0", ["petz:werewolf_clan_idx"] = "2", ["petz:werewolf"] = "0", ["unified_inventory:bags"] = "return {\"water_life:croc_bag\", \"water_life:croc_bag\", \"water_life:croc_bag\", \"water_life:croc_bag\"}", placed_nodes = "192085", ["3d_armor_inventory"] = "return {\"3d_armor:helmet_crystal 1 1160\", \"shields:shield_crystal 1 1160\", \"3d_armor:chestplate_crystal 1 1160\", \"3d_armor:leggings_crystal 1 1160\", \"3d_armor:boots_crystal 1 1160\", \"\"}", digged_nodes = "1312063", punch_count = "64416", partychat = "party", ["signslib:pos"] = "(2006,18,1643)", hud_state = "on", arenalib_infobox_arenaID = "0", ["ocean_build.last_warning"] = "1.65235e+09", played_time = "12956147", ["ocean_build.ocean_built"] = "8", yl_commons_thankyou = "206", died = "194", yl_church = "return {[\"last_death\"] = {[\"z\"] = 1997, [\"x\"] = 2460, [\"y\"] = 7}, [\"last_death_portal\"] = 1673600980}", yl_commons_player_created = "1650064821", yl_commons_player_joined = "1673647237", xp_redo_hud_color = "0xFFC001", jointime = "1650064821", bitten = "0", ["petz:lycanthropy"] = "0", crafted = "2403", ["petz:old_override_table"] = "return {[\"new_move\"] = true, [\"sneak\"] = true, [\"sneak_glitch\"] = false, [\"jump\"] = 1.5, [\"speed\"] = 2, [\"gravity\"] = 1}", inflicted_damage = "1290516", ["stamina:level"] = "11", ["petz:werewolf_vignette_id"] = "5", ["stamina:poisoned"] = "no" } } ``` Log identifier ``` [MOD] yl_report log identifier = Q8mcg82tB1WUI0gjm6Vive4PU3Cnlmam ``` Profiler save: ``` profile-20230113T223531.json_prettyEE ``` Status: ``` # Server: version: 5.6.1-yl | game: Minetest Game | uptime: 2d 9h 28min 38s | max lag: 3.52s | clients (26/42): AliasAlreadyTaken, Bailiff, Boot, Chache, Chazz, daydream, do_ob, DragonWrangler1, Elias, Ernesto, flux, itaca94, johanlegend, labrat, Lucien_II, micaias, niceride, Parrish, Pocrom, Queenfire234312, rabenkind, rewired_X, Service, shanish2, Therottenpotato, yoneda ``` Teleport command: ``` /teleport xyz 2112 8 1564 ``` Compass command: ``` /give_compass Construction Q8mcg82tB1WUI0gjm6Vive4PU3Cnlmam D2691E 2112 8 1564 ```
AliasAlreadyTaken was assigned by yourland-report 2023-01-13 22:35:31 +00:00
flux added the
1. kind/enhancement
label 2023-01-14 00:01:05 +00:00
Member

i guess this is technically possible but i don't know where that data is to be queried.

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.

  1. Let's make it that there's a chatcommand to display the announcements in a formspec.

  2. Let's make it that when the announcement changes, those changes go to the discord.

  3. 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.

  4. 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.

This also means that adding and removing announcements must follow a stricter regime. We cannot simply "set all announcements at once", then forget about them for a while.

  1. 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.

  2. /announcement_list should display them all and also provide IDs, which are needed to address them in the delete command.

  3. /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.

  4. /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.

Does this solve the problem of people not knowing what they already voted on? No.

  1. Should there be a "I voted for X sticker" ? Could this be in any way used against the voter, like a mayor demanding all their citizens to show their voting sticker, else they will be kicked from the city or similar?

Does THIS solve the problem of people not knowing what they already voted on? No, people still need to take notes or similar. Adding a "if you voted, thing becomes red" is technically possible, but not generic. That's why I'd wait until yl_quest and a proper quest log.

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. 1. Let's make it that there's a chatcommand to display the announcements in a formspec. 2. Let's make it that when the announcement changes, those changes go to the discord. 3. 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. 4. 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. > This also means that adding and removing announcements must follow a stricter regime. We cannot simply "set all announcements at once", then forget about them for a while. 5. 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. 6. `/announcement_list` should display them all and also provide IDs, which are needed to address them in the delete command. 7. `/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. 8. `/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. > Does this solve the problem of people not knowing what they already voted on? No. 9. Should there be a "I voted for X sticker" ? Could this be in any way used against the voter, like a mayor demanding all their citizens to show their voting sticker, else they will be kicked from the city or similar? > Does THIS solve the problem of people not knowing what they already voted on? No, people still need to take notes or similar. Adding a "if you voted, thing becomes red" is technically possible, but not generic. That's why I'd wait until yl_quest and a proper quest log.
  1. 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.

Add them to the news formspec?

> 4. 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. Add them to the news formspec?
Member

Alias wrote:

Should there be a "I voted for X sticker" ? Could this be in any way used against the voter, like a mayor demanding all their citizens to show their voting sticker, else they will be kicked from the city or similar?

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.

Alias wrote: > Should there be a "I voted for X sticker" ? Could this be in any way used against the voter, like a mayor demanding all their citizens to show their voting sticker, else they will be kicked from the city or similar? 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.
Sign in to join this conversation.
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#3508
No description provided.