jackofthebean000 reports: -30911 90 -29542 nothing loadi ... #4621

New Issue

yourland-report · 2023-05-28T20:48:38Z

yourland-report commented

2023-05-28 20:48:38 +00:00

jackofthebean000 reports a bug:

-30911 90 -29542 nothing loading to the west

Player position:

{
	z = -29542.203125,
	x = -30911.41796875,
	y = 89.5
}

Player look:

{
	z = -0.0086648063734174,
	x = -0.84146618843079,
	y = -0.54024034738541
}

Player information:

{
	connection_uptime = 386,
	serialization_version = 29,
	patch = 0,
	minor = 7,
	state = "Active",
	lang_code = "",
	major = 5,
	version_string = "5.7.0",
	formspec_version = 6,
	max_rtt = 1.9650000333786,
	protocol_version = 41,
	ip_version = 6,
	min_rtt = 0.1870000064373,
	avg_rtt = 0.20000000298023,
	min_jitter = 0,
	max_jitter = 1.7620000839233,
	avg_jitter = 0
}

Player meta:

{
	fields = {
		repellant = "0",
		["stamina:poisoned"] = "no",
		["stamina:exhaustion"] = "16",
		xp = "2193505",
		played_time = "6830085",
		digged_nodes = "2760407",
		placed_nodes = "823877",
		died = "233",
		["ocean_build.forbidden"] = "true",
		["ocean_build.ocean_built"] = "12",
		["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"water_life:croc_bag\", \"unified_inventory:bag_large\"}",
		yl_commons_thankyou = "87",
		arenalib_infobox_arenaID = "0",
		["3d_armor_inventory"] = "return {\"shields:shield_crystal 1 7055\", \"3d_armor:chestplate_crystal 1 7055\", \"3d_armor:boots_crystal 1 6800\", \"3d_armor:helmet_crystal 1 7055\", \"3d_armor:leggings_crystal 1 7075\", \"\"}",
		jointime = "1628815524",
		bitten = "0",
		["ocean_build.last_warning"] = "1.66259e+09",
		hud_state = "on",
		punch_count = "58320",
		["ethereal:fly_timer"] = "-99",
		inflicted_damage = "1044118",
		crafted = "158877",
		partychat = "main",
		yl_commons_player_created = "1628815524",
		yl_commons_player_joined = "1685306584",
		yl_church = "return {[\"last_heal\"] = 1677536522, [\"last_death_portal\"] = 1684699514, [\"last_death\"] = {[\"z\"] = 211, [\"x\"] = 2925, [\"y\"] = 62}}",
		["signslib:pos"] = "(3072,76,277)",
		["stamina:level"] = "8"
	}
}

Log identifier


[MOD] yl_report log identifier = iET0puuUJBquKC5VlXHqnSXD0vXKjf2C

Profiler save:

profile-20230528T204838.json_prettyEE

Status:

# Server: version: 5.6.1-yl | game: Minetest Game | uptime: 6d 3h 44min 54s | max lag: 1.15s | clients (32/52): AliasAlreadyTaken, Aliza, Bailiff, bizon, BobaCat, Boot, Chameleon, daydream, Diaeresis, Dirac, Empempires, flux, FullmetalBOI, jackofthebean000, JeCel, labrat, laira, melone, mrminer, Oblivion12, Papi, Qualia, Rattrap, Sense, Service, shanish2, Sokomine, Sysmatic, Therottenpotato, tour, Transformers, whosit

Teleport command:

/teleport xyz -30911 90 -29542

Compass command:

/give_compass Construction iET0puuUJBquKC5VlXHqnSXD0vXKjf2C D2691E -30911 90 -29542

jackofthebean000 reports a bug: > -30911 90 -29542 nothing loading to the west Player position: ``` { z = -29542.203125, x = -30911.41796875, y = 89.5 } ``` Player look: ``` { z = -0.0086648063734174, x = -0.84146618843079, y = -0.54024034738541 } ``` Player information: ``` { connection_uptime = 386, serialization_version = 29, patch = 0, minor = 7, state = "Active", lang_code = "", major = 5, version_string = "5.7.0", formspec_version = 6, max_rtt = 1.9650000333786, protocol_version = 41, ip_version = 6, min_rtt = 0.1870000064373, avg_rtt = 0.20000000298023, min_jitter = 0, max_jitter = 1.7620000839233, avg_jitter = 0 } ``` Player meta: ``` { fields = { repellant = "0", ["stamina:poisoned"] = "no", ["stamina:exhaustion"] = "16", xp = "2193505", played_time = "6830085", digged_nodes = "2760407", placed_nodes = "823877", died = "233", ["ocean_build.forbidden"] = "true", ["ocean_build.ocean_built"] = "12", ["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"water_life:croc_bag\", \"unified_inventory:bag_large\"}", yl_commons_thankyou = "87", arenalib_infobox_arenaID = "0", ["3d_armor_inventory"] = "return {\"shields:shield_crystal 1 7055\", \"3d_armor:chestplate_crystal 1 7055\", \"3d_armor:boots_crystal 1 6800\", \"3d_armor:helmet_crystal 1 7055\", \"3d_armor:leggings_crystal 1 7075\", \"\"}", jointime = "1628815524", bitten = "0", ["ocean_build.last_warning"] = "1.66259e+09", hud_state = "on", punch_count = "58320", ["ethereal:fly_timer"] = "-99", inflicted_damage = "1044118", crafted = "158877", partychat = "main", yl_commons_player_created = "1628815524", yl_commons_player_joined = "1685306584", yl_church = "return {[\"last_heal\"] = 1677536522, [\"last_death_portal\"] = 1684699514, [\"last_death\"] = {[\"z\"] = 211, [\"x\"] = 2925, [\"y\"] = 62}}", ["signslib:pos"] = "(3072,76,277)", ["stamina:level"] = "8" } } ``` Log identifier ``` [MOD] yl_report log identifier = iET0puuUJBquKC5VlXHqnSXD0vXKjf2C ``` Profiler save: ``` profile-20230528T204838.json_prettyEE ``` Status: ``` # Server: version: 5.6.1-yl | game: Minetest Game | uptime: 6d 3h 44min 54s | max lag: 1.15s | clients (32/52): AliasAlreadyTaken, Aliza, Bailiff, bizon, BobaCat, Boot, Chameleon, daydream, Diaeresis, Dirac, Empempires, flux, FullmetalBOI, jackofthebean000, JeCel, labrat, laira, melone, mrminer, Oblivion12, Papi, Qualia, Rattrap, Sense, Service, shanish2, Sokomine, Sysmatic, Therottenpotato, tour, Transformers, whosit ``` Teleport command: ``` /teleport xyz -30911 90 -29542 ``` Compass command: ``` /give_compass Construction iET0puuUJBquKC5VlXHqnSXD0vXKjf2C D2691E -30911 90 -29542 ```

AliasAlreadyTaken was assigned by yourland-report

2023-05-28 20:48:38 +00:00

AliasAlreadyTaken commented

2023-05-28 22:03:21 +00:00

Isn't that a world border?

whosit commented

2023-05-28 22:36:38 +00:00

Offtopic: how hard it is to make MT world loop? So at that border it could just give mapblocks from the opposite side of the world :P

sixer commented

2023-05-29 08:08:00 +00:00

the coords overflow at -32768 / 32767 ... far from current boundary. I think there is a mod that does this world loop, but most code like monster pathfinding, etc woud be unable to handle this without modification

👍 1

AliasAlreadyTaken commented

2023-05-29 20:09:54 +00:00

There are attempts to have a much larger worldsize, but so far MT devs are not willing to go forward on the PR.

https://forum.minetest.net/viewtopic.php?f=5&t=9183

There are attempts to have a much larger worldsize, but so far MT devs are not willing to go forward on the PR. https://forum.minetest.net/viewtopic.php?f=5&t=9183

AliasAlreadyTaken added the

4. step/discussion

label 2023-05-29 20:10:04 +00:00

flux commented

2023-05-30 17:15:10 +00:00

the size of the world can't be changed w/out major architectural changes to the game, and providing backwards compatibility is the major hurdle.

the reason why the world border is at -30912/30927: the mapgen bound is 31007 in both the - and the + direction. the resulting boundaries aligned to mapchunks are -30992, 31007. subtracting a full mapchunk from that, not just another mapblock, you get -30912, 30927. 31007 is a fairly arbitrary limit. the main reason of having the limit is to keep mapgen and other things from crashing at the edge.

there is a mod that teleports you from one side of the world to the other, but it's pretty jarring to use in practice, in part because mapgen doesn't match https://content.minetest.net/packages/Don/worldedge/

here's an upstream engine issue discussing adding proper support for wrapping the map at the edge of the world: https://github.com/minetest/minetest/issues/12655

the size of the world can't be changed w/out major architectural changes to the game, and providing backwards compatibility is the major hurdle. the reason why the world border is at -30912/30927: the mapgen bound is 31007 in both the - and the + direction. the resulting boundaries aligned to mapchunks are -30992, 31007. subtracting a full mapchunk from that, not just another mapblock, you get -30912, 30927. 31007 is a fairly arbitrary limit. the main reason of having the limit is to keep mapgen and other things from crashing at the edge. there is a mod that *teleports* you from one side of the world to the other, but it's pretty jarring to use in practice, in part because mapgen doesn't match https://content.minetest.net/packages/Don/worldedge/ here's an upstream engine issue discussing adding proper support for wrapping the map at the edge of the world: https://github.com/minetest/minetest/issues/12655

whosit commented

2023-05-30 17:47:25 +00:00

Kinda sad that "world wrapping" issue is so focused on seamless mapgen, because I think having strange looking terrain is not a problem. Especially for YL, because YLanders would probably just fix it all by hand :D

flux commented

2023-05-30 21:23:15 +00:00

Kinda sad that "world wrapping" issue is so focused on seamless mapgen, because I think having strange looking terrain is not a problem. Especially for YL, because YLanders would probably just fix it all by hand :D

it doesn't look "strange" so much as you end up w/ giant flat cliffs and biome mismatches:

> Kinda sad that "world wrapping" issue is so focused on seamless mapgen, because I think having strange looking terrain is not a problem. Especially for YL, because YLanders would probably just fix it all by hand :D it doesn't look "strange" so much as you end up w/ giant flat cliffs and biome mismatches: ![image](/attachments/07c33043-34bb-4f00-a40a-a850526dd8ec)

image.png

702 KiB

whosit commented

2023-05-30 21:40:18 +00:00

IMO being able to go there and wrap around vs just being stopped by emptiness is a big deal. Finding a cliff like this is not a big deal.

JeCel commented

2023-06-01 11:17:53 +00:00

Seems like a nice terraforming project :b

AliasAlreadyTaken commented

2023-06-01 12:26:35 +00:00

Since noone can go "outside" the worldborder, noone will ever see the cliff. Also, I'd like to keep the border area and especailly the "outside" clear, just in case MT devs adopt the "larger worldsize" PR

sixer commented

2023-06-01 13:00:32 +00:00

Since noone can go "outside" the worldborder, noone will ever see the cliff.

not sure if staff with noclip would be able to. But it is off-limit to normal players and server would not send "outside" blocks even if they would actually exist in block db.

Also, I'd like to keep the border area and especailly the "outside" clear, just in case MT devs adopt the "larger worldsize" PR

This limit is set in world metadata. Increasing the limit in minetest by PR would allow defining bigger limits (by editing world.mt), but will not auto-enlarge existing worlds. 31000 is very conservative limit, I think it probably could be increased to around 32600 without any technical trouble

> Since noone can go "outside" the worldborder, noone will ever see the cliff. not sure if staff with noclip would be able to. But it is off-limit to normal players and server would not send "outside" blocks even if they would actually exist in block db. > Also, I'd like to keep the border area and especailly the "outside" clear, just in case MT devs adopt the "larger worldsize" PR This limit is set in world metadata. Increasing the limit in minetest by PR would allow defining bigger limits (by editing world.mt), but will not auto-enlarge existing worlds. 31000 is very conservative limit, I think it probably could be increased to around 32600 without any technical trouble

flux commented

2023-06-01 16:25:17 +00:00

This limit is set in world metadata. Increasing the limit in minetest by PR would allow defining bigger limits (by editing world.mt), but will not auto-enlarge existing worlds. 31000 is very conservative limit, I think it probably could be increased to around 32600 without any technical trouble

this is wrong. 31007 is a hard-coded constant in the c++ code - increasing the mapgen_limit (in map_meta.txt, not world.mt) beyond 31007 does not change anything. i highly discourage changing the c++ code to change this w/out doing very thorough testing, and i don't think it's worth the hassle. (side note: you can change mapgen_limit for existing worlds - it only affects map generation, not anything else. if you shrink the limit, any existing mapblocks outside the limit will still load normally.)

you can increase the size of the world slightly by shrinking the mapchunk size to 1, but the new boundaries would then only be -30976, 30991, and doing so would make map generation much less efficient, would result in far more issues like #850 but between any mapblock boundaries, would result in a much greater density of structures like dungeons, and probably other similar issues.

> This limit is set in world metadata. Increasing the limit in minetest by PR would allow defining bigger limits (by editing world.mt), but will not auto-enlarge existing worlds. 31000 is very conservative limit, I think it probably could be increased to around 32600 without any technical trouble this is wrong. 31007 is a hard-coded constant in the c++ code - increasing the mapgen_limit (in map_meta.txt, not world.mt) beyond 31007 does not change anything. i *highly* discourage changing the c++ code to change this w/out doing very thorough testing, and i don't think it's worth the hassle. (side note: you can change mapgen_limit for existing worlds - it only affects map generation, not anything else. if you shrink the limit, any existing mapblocks outside the limit will still load normally.) you *can* increase the size of the world slightly by shrinking the mapchunk size to 1, but the new boundaries would then only be -30976, 30991, and doing so would make map generation much less efficient, would result in far more issues like #850 but between *any* mapblock boundaries, would result in a much greater density of structures like dungeons, and probably other similar issues.

flux commented

2023-06-01 16:27:47 +00:00

Since noone can go "outside" the worldborder, noone will ever see the cliff. Also, I'd like to keep the border area and especailly the "outside" clear, just in case MT devs adopt the "larger worldsize" PR

the context here was coding the client/server to seamlessly connect the far sides of the world. but you point out something important - implementing that would make it even harder to expand the size of the world at a future date.

> Since noone can go "outside" the worldborder, noone will ever see the cliff. Also, I'd like to keep the border area and especailly the "outside" clear, just in case MT devs adopt the "larger worldsize" PR > the context here was coding the client/server to seamlessly connect the far sides of the world. but you point out something important - implementing that would make it even harder to expand the size of the world at a future date.

Boot commented

2023-06-01 16:53:56 +00:00

However, you should also keep an eye on the size of the database. Regular backups are more important to me than an even bigger world.

However, if Minetest really wants to enlarge the world in area, then it would at least make sense to do without the absurd depth (and height) of 30 km. The deepest mines in the real world are just 4 km deep and down there the rock is already 66°C hot.

However, you should also keep an eye on the size of the database. Regular backups are more important to me than an even bigger world. However, if Minetest really wants to enlarge the world in area, then it would at least make sense to do without the absurd depth (and height) of 30 km. The deepest mines in the real world are just 4 km deep and down there the rock is already 66°C hot.

AliasAlreadyTaken commented

2023-06-02 02:27:45 +00:00

In case of such large decisions, YL will "go with the flow" and if upstream minetest decides to integrate the PR, we'll make use of it. If not, we'll not add it ourselves - unless we want to fork.

We'll also not change the mapchunk size, it sounds like high risk, little gain.

Database size is also a consideration, we need to be able to afford making backups :D So far, we're doing backups every 3 days, beginning with the first day of the month. Currently the backup is 150 GB, that's 1.5 TB per month - of which only the first backup of the month go to permanent storage, the others are deleted over time because we lack storage space to keep all of the month. This will only get worse when the world size is extended.

In case of such large decisions, YL will "go with the flow" and if upstream minetest decides to integrate the PR, we'll make use of it. If not, we'll not add it ourselves - unless we want to fork. We'll also not change the mapchunk size, it sounds like high risk, little gain. Database size is also a consideration, we need to be able to afford making backups :D So far, we're doing backups every 3 days, beginning with the first day of the month. Currently the backup is 150 GB, that's 1.5 TB per month - of which only the first backup of the month go to permanent storage, the others are deleted over time because we lack storage space to keep all of the month. This will only get worse when the world size is extended.

AliasAlreadyTaken added the

3. source/engine

label 2023-06-02 02:28:03 +00:00

sixer commented

2023-06-02 04:39:18 +00:00

This limit is set in world metadata. Increasing the limit in minetest by PR would allow defining bigger limits (by editing world.mt), but will not auto-enlarge existing worlds. 31000 is very conservative limit, I think it probably could be increased to around 32600 without any technical trouble

this is wrong. 31007 is a hard-coded constant in the c++ code

I meant that hardcoded constant increasing first (and then the world limit)

> > This limit is set in world metadata. Increasing the limit in minetest by PR would allow defining bigger limits (by editing world.mt), but will not auto-enlarge existing worlds. 31000 is very conservative limit, I think it probably could be increased to around 32600 without any technical trouble > > this is wrong. 31007 is a hard-coded constant in the c++ code I meant that hardcoded constant increasing first (and then the world limit)

flux referenced this issue

2023-06-03 17:39:09 +00:00

mrminer reports: indestructable wall ... #4670

mrdeveloper referenced this issue

2023-06-06 18:16:20 +00:00

mrminer reports: indestructable wall ... #4670

Sign in to join this conversation.