mtcontrib/mtsatellite
1
0
Fork 0
mirror of https://bitbucket.org/s_l_teichmann/mtsatellite synced 2024-12-24 09:10:17 +01:00
Code Issues Projects Releases Wiki Activity

SETUP: Wrote paragraph how to convert world databases into interleaved format.

Browse Source
This commit is contained in:
Sascha L. Teichmann 2014-10-05 08:59:11 +02:00
parent 549955bf6d
commit 1838b837d6
1 changed files with 18 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
SETUP.md
View File

@ -14,7 +14,24 @@ Setting up MTSatellite takes six steps:
6. [Start the Minetest server](#markdown-header-start-the-minetest-server)
## Convert world database into interleaved format
**TODO: Write me!**
MTSatellite operates best if the block data of the world is stored in a LevelDB database with
a key scheme called interleaved. With this key scheme you can pick up sets of neighbored blocks a
lot quicker than with a plain database.
See [Z-order curve](http://en.wikipedia.org/wiki/Z-order_curve) at Wikipedia for grasping the core ideas.
MTSatellite can run on plain LevelDB or SQlite3 world databases but this reduces the performance significantly.
This is also not tested very well and will likely break your database. So do not use it! Stay with the
interleaved format!
To convert your original plain SQLite3 or LevelDB database (Redis is not supported atm) to the interleaved
LevelDB format you have to use `mtdbconverter`:
mtdbconverter -source-backend=sqlite /path/to/your/world/map.sqlite /path/to/your/world/map.db
Depending on the size of your world and the speed this conversion will take some time.
Change `-source-backend=sqlite` to `-source-backend=leveldb` if your world is stored as a LevelDB.
`mtdbconverter` can also be used to convert your world back to the plain key scheme.
See `mtdbconverter --help` for all options.
## Configure the Minetest server
**TODO: Write me!**