Unnamed repository; edit this file 'description' to name the repository. http://git.linux-forks.de/mesecons/atom?h=origin%2Fvoxelmanip 2017-02-12T15:55:13+00:00 2017-02-12T15:55:13+00:00 Vanessa Ezekowitz vanessaezekowitz@gmail.com 2017-02-12T15:55:13+00:00 urn:sha1:50cc79ed0a6144e96d29c060102f8c168234a039 2016-08-31T06:46:11+00:00 Jeija norrepli@gmail.com 2016-08-31T06:46:11+00:00 urn:sha1:54efc64558ec21847c0b8d668bd206e88403a410 Duplicating that small piece of code seems like a better idea than putting the undo-forceloading code back into util.lua. This way, it is easier to remember to remove that unneccesary code after a couple of months / years, when people have transitioned. This also means we can make changes to the code in util.lua without breaking old code. 2016-08-30T18:54:20+00:00 Jeija norrepli@gmail.com 2016-08-30T18:54:20+00:00 urn:sha1:dfeb070a2066e9a0c7e41c6c509ec7c2b3d95f8b The change that required this compatibility layer happened in 2014, so other mods have had a lot of time to update. 2016-08-30T17:37:43+00:00 Jeija norrepli@gmail.com 2016-08-30T17:32:11+00:00 urn:sha1:6dacdaee1f942e1ba662ef017b9bde3a238f1732 2016-08-30T17:12:09+00:00 Jeija norrepli@gmail.com 2016-08-30T17:12:09+00:00 urn:sha1:e561be7fa36b6de90a759c13d745f8e54359ce3d Instead of seperately looking for onstate receptors along equipotential sections of the circuit before turning off, do that while already modifying the VoxelManip. In case an onstate receptor is found, discard the VoxelManip cache, otherwise commit it after turnoff is completed. 2016-08-30T16:24:08+00:00 Jeija norrepli@gmail.com 2016-08-30T16:24:08+00:00 urn:sha1:89153f6909558d1ba619b30a8c792c5f8493f7bc 2016-08-24T07:42:40+00:00 Christopher Head chead@chead.ca 2016-08-21T17:28:10+00:00 urn:sha1:8e6536ca2edd51175733b972fb24014b342681a8 It is no longer possible for get_node_force to return nil if the target location does, in fact, exist, because a VM will always be able to load it (whereas a forceload might not, due to exhaustion of forceload resources). So it is no longer necessary to handle get_node_force returning nil by deferring processing. 2016-08-24T07:42:40+00:00 Christopher Head chead@chead.ca 2016-08-21T04:54:15+00:00 urn:sha1:bc9d4c2d5a1d535f4abc001d527cc65c78227016 VoxelManipulator-based transactions are used to hopefully speed up scanning and replacing of networks of conductors when receptors start or stop driving signals into them. 2016-08-24T07:42:38+00:00 Christopher Head chead@chead.ca 2016-08-21T04:53:02+00:00 urn:sha1:6d79272ed4966b63e2035b19af07d13f2a0be2a3 Rather than calling out through the Lua-to-C API for each node that needs to be read or written, a group of map reads (and optionally writes) can be grouped into a transaction. Access to map data within the transaction is provided at high speed by means of VoxelManipulators. Once the reads and writes are finished, the transaction can be committed or aborted. 2016-08-24T07:41:47+00:00 Christopher Head chead@chead.ca 2016-08-21T04:48:18+00:00 urn:sha1:564cee346afcf94339472e75995394f0363a5543 A VoxelManipulator, when asked to read a mapblock, in addition to making that mapblock available to the caller, also pulls it into the server’s map cache, thus making get_node calls in the immediate future succeed. This has the dual advantages that not every mapblock containing a Mesecons circuit need remain loaded at all times (rather mapblocks can be loaded on demand as signals are sent), and that the server need not bother running ABMs and ticking entities within those mapblocks that are loaded due to Mesecons signalling.