your-land/bugtracker
your-land
/
bugtracker
44
20
Code Issues 2.4k Projects 2 Wiki

daydream reports: I died here colliding with som ... #2812

New Issue
Closed
opened 2022-10-04 20:46:24 +00:00 by yourland-report · 23 comments
yourland-report commented 2022-10-04 20:46:24 +00:00
Member
Copy Link

daydream reports a bug:

I died here colliding with something and lost 5677 xp it was NOT a ghost or a monster, IDK what it was but I don't think this death was fair at all

Player position:

{
	x = 2000.0061035156,
	y = -3004.4990234375,
	z = 1500.8850097656
}

Player look:

{
	x = -0.0050101159140468,
	y = -0.97992467880249,
	z = -0.19930498301983
}

Player information:

{
	avg_jitter = 0,
	connection_uptime = 81818,
	serialization_version = 29,
	patch = 0,
	protocol_version = 40,
	formspec_version = 6,
	major = 5,
	minor = 6,
	version_string = "5.6.0",
	state = "Active",
	min_rtt = 0.17200000584126,
	ip_version = 6,
	lang_code = "",
	max_rtt = 2.3840000629425,
	avg_rtt = 0.18099999427795,
	min_jitter = 0,
	max_jitter = 2.2019999027252
}

Player meta:

{
	fields = {
		inflicted_damage = "572432",
		xp_redo_hud_color = "0xFFC001",
		["signslib:pos"] = "(2302,-2755,1790)",
		["petz:werewolf_clan_idx"] = "2",
		["3d_armor_inventory"] = "return {\"\", \"\", \"\", \"\", \"\", \"\"}",
		crafted = "1378",
		["ocean_build.ocean_built"] = "8",
		xp = "826321",
		hud_state = "on",
		["stamina:exhaustion"] = "101",
		["unified_inventory:bags"] = "return {\"water_life:croc_bag\", \"water_life:croc_bag\", \"water_life:croc_bag\", \"water_life:croc_bag\"}",
		["ocean_build.last_warning"] = "1.65235e+09",
		yl_church = "return {[\"last_death\"] = {[\"x\"] = 2000, [\"y\"] = -2878, [\"z\"] = 1500}, [\"last_death_portal\"] = 1664916277}",
		placed_nodes = "137958",
		["petz:werewolf"] = "0",
		["petz:lycanthropy"] = "0",
		jointime = "1650064821",
		repellant = "0",
		partychat = "party",
		bitten = "0",
		yl_commons_player_created = "1650064821",
		played_time = "6153569",
		digged_nodes = "938961",
		punch_count = "29052",
		died = "96",
		arenalib_infobox_arenaID = "0",
		yl_commons_thankyou = "77",
		["petz:old_override_table"] = "return {[\"new_move\"] = true, [\"sneak\"] = true, [\"sneak_glitch\"] = false, [\"jump\"] = 1.5, [\"speed\"] = 2, [\"gravity\"] = 1}",
		["stamina:poisoned"] = "no",
		["stamina:level"] = "19",
		["petz:werewolf_vignette_id"] = "5",
		yl_commons_player_joined = "1664834661"
	}
}

Log identifier


[MOD] yl_report log identifier = LSRTFxOfQOMzzqq2dPoCKN0lMgrgmgnm

Profiler save:

profile-20221004T204624.json_prettyEE

Status:

# Server: version: 5.5.1-yl | game: Minetest Game | uptime: 10d 2h 26min 23s | max lag: 2.61s | clients: SirLondoCat, test1234, Bla, Chache, Kalek, Parrish, Bill88, Lucien_II, Therottenpotato, hatti, Squawk, the_chosen_one, Road, rabenkind, drgn, Service, AliasAlreadyTaken, niceride, Momma, daydream, Bailiff

Teleport command:

/teleport xyz 2000 -3004 1501

Compass command:

/give_compass Construction LSRTFxOfQOMzzqq2dPoCKN0lMgrgmgnm D2691E 2000 -3004 1501
daydream reports a bug: > I died here colliding with something and lost 5677 xp it was NOT a ghost or a monster, IDK what it was but I don't think this death was fair at all Player position: ``` { x = 2000.0061035156, y = -3004.4990234375, z = 1500.8850097656 } ``` Player look: ``` { x = -0.0050101159140468, y = -0.97992467880249, z = -0.19930498301983 } ``` Player information: ``` { avg_jitter = 0, connection_uptime = 81818, serialization_version = 29, patch = 0, protocol_version = 40, formspec_version = 6, major = 5, minor = 6, version_string = "5.6.0", state = "Active", min_rtt = 0.17200000584126, ip_version = 6, lang_code = "", max_rtt = 2.3840000629425, avg_rtt = 0.18099999427795, min_jitter = 0, max_jitter = 2.2019999027252 } ``` Player meta: ``` { fields = { inflicted_damage = "572432", xp_redo_hud_color = "0xFFC001", ["signslib:pos"] = "(2302,-2755,1790)", ["petz:werewolf_clan_idx"] = "2", ["3d_armor_inventory"] = "return {\"\", \"\", \"\", \"\", \"\", \"\"}", crafted = "1378", ["ocean_build.ocean_built"] = "8", xp = "826321", hud_state = "on", ["stamina:exhaustion"] = "101", ["unified_inventory:bags"] = "return {\"water_life:croc_bag\", \"water_life:croc_bag\", \"water_life:croc_bag\", \"water_life:croc_bag\"}", ["ocean_build.last_warning"] = "1.65235e+09", yl_church = "return {[\"last_death\"] = {[\"x\"] = 2000, [\"y\"] = -2878, [\"z\"] = 1500}, [\"last_death_portal\"] = 1664916277}", placed_nodes = "137958", ["petz:werewolf"] = "0", ["petz:lycanthropy"] = "0", jointime = "1650064821", repellant = "0", partychat = "party", bitten = "0", yl_commons_player_created = "1650064821", played_time = "6153569", digged_nodes = "938961", punch_count = "29052", died = "96", arenalib_infobox_arenaID = "0", yl_commons_thankyou = "77", ["petz:old_override_table"] = "return {[\"new_move\"] = true, [\"sneak\"] = true, [\"sneak_glitch\"] = false, [\"jump\"] = 1.5, [\"speed\"] = 2, [\"gravity\"] = 1}", ["stamina:poisoned"] = "no", ["stamina:level"] = "19", ["petz:werewolf_vignette_id"] = "5", yl_commons_player_joined = "1664834661" } } ``` Log identifier ``` [MOD] yl_report log identifier = LSRTFxOfQOMzzqq2dPoCKN0lMgrgmgnm ``` Profiler save: ``` profile-20221004T204624.json_prettyEE ``` Status: ``` # Server: version: 5.5.1-yl | game: Minetest Game | uptime: 10d 2h 26min 23s | max lag: 2.61s | clients: SirLondoCat, test1234, Bla, Chache, Kalek, Parrish, Bill88, Lucien_II, Therottenpotato, hatti, Squawk, the_chosen_one, Road, rabenkind, drgn, Service, AliasAlreadyTaken, niceride, Momma, daydream, Bailiff ``` Teleport command: ``` /teleport xyz 2000 -3004 1501 ``` Compass command: ``` /give_compass Construction LSRTFxOfQOMzzqq2dPoCKN0lMgrgmgnm D2691E 2000 -3004 1501 ```
AliasAlreadyTaken was assigned by yourland-report 2022-10-04 20:46:24 +00:00
flux added the
1. kind/balancing
 label 2022-10-04 21:21:33 +00:00
flux commented 2022-10-04 21:22:08 +00:00
Member
Copy Link

probably a bat. cf. #2760, #2761

probably a bat. cf. #2760, #2761
daydream commented 2022-10-05 00:14:53 +00:00
Member
Copy Link

I saw the color of it, it wasn't dark brown... it was tan color if that helps... was this death justified?

I saw the color of it, it wasn't dark brown... it was tan color if that helps... was this death justified?
flux commented 2022-10-05 01:06:11 +00:00
Member
Copy Link

I saw the color of it, it wasn't dark brown... it was tan color if that helps... was this death justified?

in my view, hellevators are a bit of an exploit, and i've certainly died in them due to collision glitches (no entity involved at all). but getting rid of their worst behavior would require changes to the client and engine, and none of the core devs seem interested in changing the status quo.

alias may have a different view, and may refund your XP.

> I saw the color of it, it wasn't dark brown... it was tan color if that helps... was this death justified? in my view, hellevators are a bit of an exploit, and i've certainly died in them due to collision glitches (no entity involved at all). but getting rid of their worst behavior would require changes to the client and engine, and none of the core devs seem interested in changing the status quo. alias may have a different view, and may refund your XP.
daydream commented 2022-10-05 01:32:01 +00:00
Member
Copy Link

there was very much something there, tan color (light light brown) but it all happens so fast, there's just no way for me to guess what it was. It wasn't a case of colliding with the mineshaft or a door or something like that tho...

there was very much something there, tan color (light light brown) but it all happens so fast, there's just no way for me to guess what it was. It wasn't a case of colliding with the mineshaft or a door or something like that tho...
death 4 oct.jpg
452 KiB
death 4 oct.jpg
AliasAlreadyTaken commented 2022-10-13 04:15:53 +00:00
Owner
Copy Link

2022-10-04 20:43:17: ACTION[Server]: daydream damaged by 49 hp at (2000.05,-2877.55,1500.47)
2022-10-04 20:43:17: ACTION[Server]: [bones] daydream dies at (2000,-3005,1500) and their inventory goes to bones.
2022-10-04 20:43:17: ACTION[Server]: [MOD] xp_redo: daydream lost 5677 XP!
2022-10-04 20:43:17: ACTION[Server]: [MOD] xp_redo: Reason of death of daydream: return {["from"] = "engine", ["type"] = "fall"}

2022-10-04 20:43:17: ACTION[Server]: daydream damaged by 49 hp at (2000.05,-2877.55,1500.47) 2022-10-04 20:43:17: ACTION[Server]: [bones] daydream dies at (2000,-3005,1500) and their inventory goes to bones. 2022-10-04 20:43:17: ACTION[Server]: [MOD] xp_redo: daydream lost 5677 XP! 2022-10-04 20:43:17: ACTION[Server]: [MOD] xp_redo: Reason of death of daydream: return {["from"] = "engine", ["type"] = "fall"}
flux commented 2022-10-13 16:06:01 +00:00
Member
Copy Link

there was very much something there, tan color (light light brown) but it all happens so fast, there's just no way for me to guess what it was. It wasn't a case of colliding with the mineshaft or a door or something like that tho...

oh i absolutely believe you died from falling on a mob, and we don't know what it was. could have been a glitched mese monster (tiny and textureless e.g. random color), or who knows.

cf. #2760, #2761

ugh firefox has gone kakapupu and i need to reboot

> there was very much something there, tan color (light light brown) but it all happens so fast, there's just no way for me to guess what it was. It wasn't a case of colliding with the mineshaft or a door or something like that tho... oh i absolutely believe you died from falling on a mob, and we don't know what it was. could have been a glitched mese monster (tiny and textureless e.g. random color), or who knows. cf. #2760, #2761 ugh firefox has gone kakapupu and i need to reboot
flux added the
2. prio/elevated
4. step/discussion
2. prio/controversial
 labels 2022-11-07 19:31:10 +00:00
AliasAlreadyTaken commented 2023-01-05 10:51:03 +00:00
Owner
Copy Link

Sounds like we also want to log what entities are close to a death position or what block the player hit when falldamage was applied

Sounds like we also want to log what entities are close to a death position or what block the player hit when falldamage was applied
flux commented 2023-01-05 18:28:07 +00:00
Member
Copy Link

what block the player hit when falldamage was applied

since fall damage is calculated by the client, and collision data isn't relayed to the server, this is impossible to do perfectly, though i suppose we can do some crude checks.

> what block the player hit when falldamage was applied since fall damage is calculated by the client, and collision data isn't relayed to the server, this is impossible to do perfectly, though i suppose we can do some crude checks.
AliasAlreadyTaken commented 2023-01-06 01:22:34 +00:00
Owner
Copy Link

what block the player hit when falldamage was applied

since fall damage is calculated by the client, and collision data isn't relayed to the server, this is impossible to do perfectly, though i suppose we can do some crude checks.

So it could happen, on the server is an entity at position x,y,z while the client smashes into it in position a,b,c ?

> > what block the player hit when falldamage was applied > > since fall damage is calculated by the client, and collision data isn't relayed to the server, this is impossible to do perfectly, though i suppose we can do some crude checks. So it could happen, on the server is an entity at position x,y,z while the client smashes into it in position a,b,c ?
flux commented 2023-01-06 23:29:37 +00:00
Member
Copy Link

So it could happen, on the server is an entity at position x,y,z while the client smashes into it in position a,b,c ?

correct

> So it could happen, on the server is an entity at position x,y,z while the client smashes into it in position a,b,c ? correct
flux commented 2023-12-26 01:30:05 +00:00
Member
Copy Link

something similar happened again. at the very least, we should do some logging about the environment around the player when they die due to fall damage. additionally, perhaps small flying mobs should be made to not collide with other entities.

something similar happened again. at the very least, we should do some logging about the environment around the player when they die due to fall damage. additionally, perhaps small flying mobs should be made to not collide with other entities.
👍 1
flux added this to the flux's TODO list project 2023-12-26 01:30:19 +00:00
flux added the
4. step/at work
 label 2023-12-26 01:30:25 +00:00
flux self-assigned this 2023-12-26 01:30:30 +00:00
flux commented 2023-12-27 22:56:31 +00:00
Member
Copy Link

implemented the logging: 341ab1cd20

now we will get these:

2023-12-27 14:52:56: ACTION[Server]: [yl_commons] [falling death] flux2 @ (2042.1630859375,16.611999511719,1167.1080322266) {"from":"engine","type":"fall"} in=air below=air objects=gauges:hp_bar@(2042.1630859375,16.611999511719,1167.1080322266) physical=false collide_with_objects=true;petz:moth@(2042.8775634766,15.000950813293,1167.2010498047) physical=true collide_with_objects=true
implemented the logging: https://gitea.your-land.de/your-land/yl_commons/commit/341ab1cd2068fdc743b382946d911e031d257cf3 now we will get these: ``` 2023-12-27 14:52:56: ACTION[Server]: [yl_commons] [falling death] flux2 @ (2042.1630859375,16.611999511719,1167.1080322266) {"from":"engine","type":"fall"} in=air below=air objects=gauges:hp_bar@(2042.1630859375,16.611999511719,1167.1080322266) physical=false collide_with_objects=true;petz:moth@(2042.8775634766,15.000950813293,1167.2010498047) physical=true collide_with_objects=true ```
👍 1
flux commented 2023-12-27 23:22:01 +00:00
Member
Copy Link

not sure if the thumbs up was just for the logging or also for making bats not collide_with_objects

not sure if the thumbs up was just for the logging or also for making bats not `collide_with_objects`
AliasAlreadyTaken added this to the 1.1.123 milestone 2023-12-27 23:22:16 +00:00
AliasAlreadyTaken commented 2024-01-25 23:30:48 +00:00
Owner
Copy Link

not sure if the thumbs up was just for the logging or also for making bats not collide_with_objects

Let's discuss not-colliding in a different issue. Question is what happens in reality when you jump 500 meters downwards in a shaft and hit a tiny object like a bat or a mouse. I would assume it may still hurt a lot? If we want to do that, please open another issue. This one deals with logging.

> not sure if the thumbs up was just for the logging or also for making bats not `collide_with_objects` Let's discuss not-colliding in a different issue. Question is what happens in reality when you jump 500 meters downwards in a shaft and hit a tiny object like a bat or a mouse. I would assume it may still hurt a lot? If we want to do that, please open another issue. This one deals with logging.
AliasAlreadyTaken added the
4. step/ready to QA test
 label 2024-01-25 23:33:27 +00:00
rewired_X commented 2024-01-26 00:08:05 +00:00
Copy Link

obviously the object would get brutally crushed and your pain would be from hitting the ground

obviously the object would get brutally crushed and your pain would be from hitting the ground
AliasAlreadyTaken commented 2024-01-28 15:20:38 +00:00
Owner
Copy Link

QA

I tried killing Boris by throwing him down the Hellevator. I placed bats at around -4000 and -5000 and Boris died somewhere nearby:

2024-01-28 15:08:18: ACTION[Server]: [bones] Boris dies at (2000,-4127,1500) and their inventory goes to bones.
2024-01-28 15:08:18: ACTION[Server]: [MOD] xp_redo: Reason of death of Boris: return {["from"] = "engine", ["type"] = "fall"}
2024-01-28 15:08:18: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4000,1500) {"from":"engine","type":"fall"} in=air below=air objects=gauges:hp_bar@(2000,-4000,1500) physical=false collide_with_objects=true

2024-01-28 15:15:10: ACTION[Server]: [bones] Boris dies at (2000,-5092,1500) and doesn't have any inventory to be dropped.
2024-01-28 15:15:10: ACTION[Server]: [MOD] xp_redo: Reason of death of Boris: return {["from"] = "engine", ["type"] = "fall"}
2024-01-28 15:15:10: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4965.203125,1500) {"from":"engine","type":"fall"} in=air below=air objects=gauges:hp_bar@(2000,-4965.203125,1500) physical=false collide_with_objects=true

Unfortunately the bat wasn't mentioned. The gauges:hp_bar is always with the character, please exclude it from the detection or gather a list of objects nearby instead of only the closest. If that already is the case, then maybe they are too far away? Collision should have happened around -4000 and -5000, death occurred ~127 or ~100 blocks below

QA I tried killing Boris by throwing him down the Hellevator. I placed bats at around -4000 and -5000 and Boris died somewhere nearby: 2024-01-28 15:08:18: ACTION[Server]: [bones] Boris dies at (2000,-4127,1500) and their inventory goes to bones. 2024-01-28 15:08:18: ACTION[Server]: [MOD] xp_redo: Reason of death of Boris: return {["from"] = "engine", ["type"] = "fall"} 2024-01-28 15:08:18: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4000,1500) {"from":"engine","type":"fall"} in=air below=air objects=gauges:hp_bar@(2000,-4000,1500) physical=false collide_with_objects=true 2024-01-28 15:15:10: ACTION[Server]: [bones] Boris dies at (2000,-5092,1500) and doesn't have any inventory to be dropped. 2024-01-28 15:15:10: ACTION[Server]: [MOD] xp_redo: Reason of death of Boris: return {["from"] = "engine", ["type"] = "fall"} 2024-01-28 15:15:10: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4965.203125,1500) {"from":"engine","type":"fall"} in=air below=air objects=gauges:hp_bar@(2000,-4965.203125,1500) physical=false collide_with_objects=true Unfortunately the bat wasn't mentioned. The gauges:hp_bar is always with the character, please exclude it from the detection or gather a list of objects nearby instead of only the closest. If that already is the case, then maybe they are too far away? Collision should have happened around -4000 and -5000, death occurred ~127 or ~100 blocks below
AliasAlreadyTaken added
4. step/question
ugh/QA NOK
 and removed
4. step/discussion
 labels 2024-01-28 15:20:58 +00:00
whosit commented 2024-01-29 08:15:15 +00:00
Member
Copy Link

objects=gauges:hp_bar collide_with_objects=true

O_o

> objects=gauges:hp_bar collide_with_objects=true O_o
flux commented 2024-01-30 00:52:57 +00:00
Member
Copy Link

obviously the object would get brutally crushed and your pain would be from hitting the ground

after scouring the internet, i've managed to uncover only a single story of a bird strike with a skydiver:
https://www.skyxtreme.com/archive/july2000/safety.html#bird

so certainly enough to hurt, probably not enough to kill you.

gauges:hp_bar is always with the character, please exclude it from the detection

done: 9ca80ac40a

Collision should have happened around -4000 and -5000, death occurred ~127 or ~100 blocks below

the reported death position is where the bones were placed. if the player is in the air, the bones mod attempts to place the bones on the ground, so that the priest doesn't teleport them to some random position in the middle of the air and also so that they're just easier to find in general. i think 127 is the limit of positions to look at.

objects=gauges:hp_bar collide_with_objects=true

collide_with_objects is meaningless if physical=false

as for why the bats weren't recorded, i don't know. i've increased the radius of the search slightly:

d82f2c819f

> obviously the object would get brutally crushed and your pain would be from hitting the ground after scouring the internet, i've managed to uncover only a single story of a bird strike with a skydiver: https://www.skyxtreme.com/archive/july2000/safety.html#bird so certainly enough to hurt, probably not enough to kill you. > gauges:hp_bar is always with the character, please exclude it from the detection done: https://gitea.your-land.de/your-land/yl_commons/commit/9ca80ac40ac5bc5bc3c4a8978351fdd0e1fac1be > Collision should have happened around -4000 and -5000, death occurred ~127 or ~100 blocks below the reported death position is where the bones were placed. if the player is in the air, the bones mod attempts to place the bones on the ground, so that the priest doesn't teleport them to some random position in the middle of the air and also so that they're just easier to find in general. i think 127 is the limit of positions to look at. > objects=gauges:hp_bar collide_with_objects=true `collide_with_objects` is meaningless if `physical=false` ------------------- as for why the bats weren't recorded, i don't know. i've increased the radius of the search slightly: https://gitea.your-land.de/your-land/yl_commons/commit/d82f2c819f4b81484e95fe8a2d7c12eea39d5fd5
AliasAlreadyTaken commented 2024-01-30 00:54:29 +00:00
Owner
Copy Link

obviously the object would get brutally crushed and your pain would be from hitting the ground

after scouring the internet, i've managed to uncover only a single story of a bird strike with a skydiver:
https://www.skyxtreme.com/archive/july2000/safety.html#bird

so certainly enough to hurt, probably not enough to kill you.

NERD!

Rest: Will retest :D

> > obviously the object would get brutally crushed and your pain would be from hitting the ground > > after scouring the internet, i've managed to uncover only a single story of a bird strike with a skydiver: > https://www.skyxtreme.com/archive/july2000/safety.html#bird > > so certainly enough to hurt, probably not enough to kill you. NERD! Rest: Will retest :D
AliasAlreadyTaken commented 2024-01-30 04:50:59 +00:00
Owner
Copy Link
2024-01-30 04:45:56: ACTION[Server]: Boris damaged by 269 hp at (2000,-4009.91,1500)
2024-01-30 04:45:56: ACTION[Server]: [bones] Boris dies at (2000,-4137,1500) and keeps their inventory.
2024-01-30 04:45:56: ACTION[Server]: [MOD] xp_redo: Boris lost 0 XP!
2024-01-30 04:45:56: ACTION[Server]: [MOD] xp_redo: Reason of death of Boris: return {["from"] = "engine", ["type"] = "fall"}
2024-01-30 04:45:56: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4009.9128417969,1500) {"from":"engine","type":"fall"} in=air below=air objects=petz:bat@(2000.3118896484,-4012.5905761719,1501.3742675781) physical=true collide_with_objects=true

Second attempt:

2024-01-30 04:47:39: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-3972.3500976563,1500) {"from":"engine","type":"fall"} in=air below=air objects=mobs_monster:oerkki@(1997.9010009766,-3971.4995117188,1500.0526123047) physical=true collide_with_objects=true

Not sure, did we really collide with an oerkki? The x coordinate looks like its far enough? Should have been a bat again.

2024-01-30 04:49:25: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-3976.5219726563,1500) {"from":"engine","type":"fall"} in=air below=air objects=petz:bat@(2000.3118896484,-3979,1499.6474609375) physical=true collide_with_objects=true;petz:bat@(1999.7507324219,-3978.92578125,1499.4422607422) physical=true collide_with_objects=true

2024-01-30 04:52:33: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4028.3139648438,1500) {"from":"engine","type":"fall"} in=air below=air objects=

2024-01-30 04:55:22: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4032.0122070313,1500) {"from":"engine","type":"fall"} in=air below=air objects=petz:bat@(2000.3121337891,-4033.7043457031,1499.8848876953) physical=true collide_with_objects=true

2024-01-30 04:56:22: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-3972.3620605469,1500) {"from":"engine","type":"fall"} in=air below=air objects=mobs_monster:oerkki@(1997.9001464844,-3971.4992675781,1500.0998535156) physical=true collide_with_objects=true

2024-01-30 04:57:39: ACTION[Server]: [yl_commons] [falling death] Boris @ (2002,15,1154) {"from":"engine","type":"fall"} in=air below=air objects=yl_npc:npc@(2000,14.500500679016,1157) physical=true collide_with_objects=true;signs:display_text@(2001,16.34375,1157.466796875) physical=false collide_with_objects=false

2024-01-30 04:58:23: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4029.5268554688,1500) {"from":"engine","type":"fall"} in=air below=air objects=

2024-01-30 04:59:55: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-3978.9262695313,1500) {"from":"engine","type":"fall"} in=air below=air objects=petz:bat@(2000.3115234375,-3978.8508300781,1501.3747558594) physical=true collide_with_objects=true;petz:bat@(1999.7506103516,-3979.818359375,1500.0549316406) physical=true collide_with_objects=true

2024-01-30 05:00:36: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4004.8840332031,1500) {"from":"engine","type":"fall"} in=air below=air objects=

Boris should have died from a collision with a bat in all of those 10 cases.

It detected correctly in 4 cases
It detected nothing in 3 cases
It detected "wrong" in 2 cases
It detected wrong position, but correctly NPC nearby in 1 case

Since this tool only gathers the objects nearby, it can't know whether the "wrongly" detected entities might have been responsible for the death. Maybe we could increase the range by a bit more, but so far its good enough. Since it is not 100%, it only may give us a rough idea and cannot be relied on 100%

To be noted: If someone dies by a punch, nothing is logged, this is purely against "falling on someone's head"

``` 2024-01-30 04:45:56: ACTION[Server]: Boris damaged by 269 hp at (2000,-4009.91,1500) 2024-01-30 04:45:56: ACTION[Server]: [bones] Boris dies at (2000,-4137,1500) and keeps their inventory. 2024-01-30 04:45:56: ACTION[Server]: [MOD] xp_redo: Boris lost 0 XP! 2024-01-30 04:45:56: ACTION[Server]: [MOD] xp_redo: Reason of death of Boris: return {["from"] = "engine", ["type"] = "fall"} 2024-01-30 04:45:56: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4009.9128417969,1500) {"from":"engine","type":"fall"} in=air below=air objects=petz:bat@(2000.3118896484,-4012.5905761719,1501.3742675781) physical=true collide_with_objects=true ``` Second attempt: ``` 2024-01-30 04:47:39: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-3972.3500976563,1500) {"from":"engine","type":"fall"} in=air below=air objects=mobs_monster:oerkki@(1997.9010009766,-3971.4995117188,1500.0526123047) physical=true collide_with_objects=true ``` Not sure, did we really collide with an oerkki? The x coordinate looks like its far enough? Should have been a bat again. ``` 2024-01-30 04:49:25: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-3976.5219726563,1500) {"from":"engine","type":"fall"} in=air below=air objects=petz:bat@(2000.3118896484,-3979,1499.6474609375) physical=true collide_with_objects=true;petz:bat@(1999.7507324219,-3978.92578125,1499.4422607422) physical=true collide_with_objects=true ``` ``` 2024-01-30 04:52:33: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4028.3139648438,1500) {"from":"engine","type":"fall"} in=air below=air objects= ``` ``` 2024-01-30 04:55:22: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4032.0122070313,1500) {"from":"engine","type":"fall"} in=air below=air objects=petz:bat@(2000.3121337891,-4033.7043457031,1499.8848876953) physical=true collide_with_objects=true ``` ``` 2024-01-30 04:56:22: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-3972.3620605469,1500) {"from":"engine","type":"fall"} in=air below=air objects=mobs_monster:oerkki@(1997.9001464844,-3971.4992675781,1500.0998535156) physical=true collide_with_objects=true ``` ``` 2024-01-30 04:57:39: ACTION[Server]: [yl_commons] [falling death] Boris @ (2002,15,1154) {"from":"engine","type":"fall"} in=air below=air objects=yl_npc:npc@(2000,14.500500679016,1157) physical=true collide_with_objects=true;signs:display_text@(2001,16.34375,1157.466796875) physical=false collide_with_objects=false ``` ``` 2024-01-30 04:58:23: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4029.5268554688,1500) {"from":"engine","type":"fall"} in=air below=air objects= ``` ``` 2024-01-30 04:59:55: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-3978.9262695313,1500) {"from":"engine","type":"fall"} in=air below=air objects=petz:bat@(2000.3115234375,-3978.8508300781,1501.3747558594) physical=true collide_with_objects=true;petz:bat@(1999.7506103516,-3979.818359375,1500.0549316406) physical=true collide_with_objects=true ``` ``` 2024-01-30 05:00:36: ACTION[Server]: [yl_commons] [falling death] Boris @ (2000,-4004.8840332031,1500) {"from":"engine","type":"fall"} in=air below=air objects= ``` Boris should have died from a collision with a bat in all of those 10 cases. It detected correctly in 4 cases It detected nothing in 3 cases It detected "wrong" in 2 cases It detected wrong position, but correctly NPC nearby in 1 case Since this tool only gathers the objects nearby, it can't know whether the "wrongly" detected entities might have been responsible for the death. Maybe we could increase the range by a bit more, but so far its good enough. Since it is not 100%, it only may give us a rough idea and cannot be relied on 100% To be noted: If someone dies by a punch, nothing is logged, this is purely against "falling on someone's head"
AliasAlreadyTaken added
ugh/QA OK
 and removed
ugh/QA NOK
 labels 2024-01-30 05:13:06 +00:00
flux commented 2024-03-27 02:14:02 +00:00
Member
Copy Link

because it's culturally important, noting that fabio once got hit in the face by a bird killed a bird with his face while riding a roller coaster https://www.youtube.com/watch?v=OjAYxpXUklc

because it's culturally important, noting that fabio once ~~got hit in the face by a bird~~ killed a bird with his face while riding a roller coaster https://www.youtube.com/watch?v=OjAYxpXUklc
flux commented 2024-03-27 02:15:02 +00:00
Member
Copy Link

i can't verify that the logging code is present on the main server, nor whether its working well enough to close this.

i can't verify that the logging code is present on the main server, nor whether its working well enough to close this.
flux removed the
4. step/at work
4. step/question
 labels 2024-04-03 19:40:10 +00:00
AliasAlreadyTaken commented 2024-04-20 05:08:58 +00:00
Owner
Copy Link

The logging works, but cases were rare lately.

I'll close until this becomes a problem again.

The logging works, but cases were rare lately. I'll close until this becomes a problem again.
AliasAlreadyTaken added
5. result/fixed
 and removed
4. step/ready to QA test
 labels 2024-04-20 05:09:13 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
1. kind/balancing

Depends on balancing

  
1. kind/breaking

something that alters or disables an existing game mechanic

  
1. kind/bug

Something is not working

  
1. kind/construction

A build needs fixing

  
1. kind/documentation

Needs proper documentation

  
1. kind/enhancement

New feature

  
1. kind/griefing

players despoiling builds or nature

  
1. kind/invalid

Not a valid report, e.g. created by mistake with no content.

  
1. kind/meme

issue is mostly a joke

  
1. kind/node limit

something which works for or against the node limit

  
1. kind/other

Something not within the other kinds

  
1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other

  
2. prio/controversial

not likely to happen w/out a lot of discussion

  
2. prio/critical

Very important

  
2. prio/elevated

something players are eager to have fixed

  
2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem

  
2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.

  
2. prio/low

Not so important

  
3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.

  
3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup

  
3. source/engine

Issue is due to a bug or feature of the minetest engine

  
3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation

  
3. source/integration

Two or more nonbuggy mechanics conflict, or our attempts to rectify conflicting mechanics have created a new bug

  
3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues

  
3. source/license

A licensing problem is involved

  
3. source/mod upstream

Problem is upstream (not engine/client)

  
3. source/unknown

   
3. source/website

Affects the website

  
4. step/approved

Alias has approved this feature, someone should implement it

  
4. step/at work

Being worked on

  
4. step/blocked

we plan to do this, but other work has to be finished first

  
4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon

  
4. step/help wanted

Need some help

  
4. step/needs confirmation

   
4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done

  
4. step/question

More information is needed

  
4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing

  
4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.

  
4. step/want approval

Someone can quickly implement this if Alias approves the change/feature

  
5. result/cannot reproduce

   
5. result/duplicate

This issue or pull request already exists

  
5. result/fixed

problem is fixed

  
5. result/maybe

not planned currently, but maybe some day

  
5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

  
ugh/petz

yet another petz bugz.

  
ugh/QA main

That's something we can only wait and see whether it hapens again: On the main server

  
ugh/QA NOK

Fix didn't yield the expected results

  
ugh/QA OK

tested

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
Milestone
Clear milestone
No items
No Milestone
1.1.123
Projects
Clear projects
No project
flux's TODO list
Assignees
Clear assignees
No Assignees
AliasAlreadyTaken
flux
6 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#2812
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?