MetzNet
/
dfhack
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

remove outdated info for persistence API

develop
Myk Taylor 2023-10-07 00:46:42 -07:00
parent a3cd847181
commit c4b31176a9
No known key found for this signature in database
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/dev/Lua API.rst
Unescape Escape View File

@ -684,7 +684,7 @@ Persistent configuration storage
-------------------------------- --------------------------------
This api is intended for storing configuration options in the world itself. This api is intended for storing configuration options in the world itself.
It probably should be restricted to data that is world-dependent. It is intended for data that is world-dependent.
Entries are identified by a string ``key``, but it is also possible to manage Entries are identified by a string ``key``, but it is also possible to manage
multiple entries with the same key; their identity is determined by ``entry_id``. multiple entries with the same key; their identity is determined by ``entry_id``.
@ -717,10 +717,8 @@ Every entry has a mutable string ``value``, and an array of 7 mutable ``ints``.
otherwise the existing one is simply updated. otherwise the existing one is simply updated.
Returns *entry, did_create_new* Returns *entry, did_create_new*
Since the data is hidden in data structures owned by the DF world, The data is kept in memory, so no I/O occurs when getting or saving keys. It is
and automatically stored in the save game, these save and retrieval all written to a json file in the game save directory when the game is saved.
functions can just copy values in memory without doing any actual I/O.
However, currently every entry has a 180+-byte dead-weight overhead.
It is also possible to associate one bit per map tile with an entry, It is also possible to associate one bit per map tile with an entry,
using these two methods: using these two methods: