Why is the map limit not 31000, but 30927??? Searching through the code brought nothing that would suggest this (in fact, the opposite), unless there is somthing I missed.
The great mystery...
FOSS gamedev and creative worlds
This is a mostly frozen copy of the Minetest forums through 2017. If you know phpBB3 and would like to host any G-rated forum here, you can email: me@minetest.org If the email doesn't work, find out who's taken over Final Minetest from OldCoder and email them to get write access or an admin account.
I should have set this up years ago. But it's no tale of woe.
Whether the temperature is high or low, regardless of cold winds blow,
away we go like Edgar Allan Poe, on now with the show. BTW rhymes are welcome.
Map limits
5 posts
• Page 1 of 1
-
LorenzoVulcan - Member
- Posts: 437
- Joined: Mon Mar 12, 2012 06:46
I think it's for pairing chunk dimension,for not make 1/3 or 1/4 of chunk spawning.
Developer of the BlockForge 2# Project!
Official thread: http://minetest.net/forum/viewtopic.php?pid=54290#p54290
Official thread: http://minetest.net/forum/viewtopic.php?pid=54290#p54290
It used to be ±30976 -- since the new map generation was introduced (march 2012), it is ±30912. The theorical map limit is 32768, but it was intentionally reduced to prevent crashes related to high view distances (as far as I know).
- celeron55
- Member
- Posts: 430
- Joined: Tue Apr 19, 2011 10:10
Calinou wrote:It used to be ±30976 -- since the new map generation was introduced (march 2012), it is ±30912. The theorical map limit is 32768, but it was intentionally reduced to prevent crashes related to high view distances (as far as I know).
It is limited in order to not have to implement performance-eating and bug-prone boundary checks in lighting code and other algorithms.
-
0gb.us - Member
- Posts: 841
- Joined: Sun Sep 16, 2012 01:55
Calinou wrote:It used to be ±30976 -- since the new map generation was introduced (march 2012), it is ±30912. The theorical map limit is 32768, but it was intentionally reduced to prevent crashes related to high view distances (as far as I know).
It's not ±30912. It's +30927 to -30912. The high and low boundaries do not match. That keeps the map divisible into a number of whole chunks though.
5 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 18 guests