Dylan K. Taylor a62ce64fdd
Revert "Chunk: added modification counter"
This reverts commit a5418a019dc2a83210084632130db8ce06f529ea.

The more I assessed this, the more I realized that this implementation
doesn't actually offer any value. Since modcounters don't persist after
chunk unload + reload, they can't be reliably used to detect changes in
chunks without additional event subscriptions.
For the purpose I actually intended to use them for (population task
cancellation) there's a) another solution, and b) modcounts are
unreliable for that too, because of the aforementioned potential for
chunks to get unloaded and reloaded.
For the case of detecting dirty chunks within PopulationTask itself,
they are also unnecessary, since the dirty flags are sufficient within
there, since FastChunkSerializer doesn't copy dirty flags.

In conclusion, this was a misbegotten addition with little real value,
but does impact performance in hot paths.
2021-10-28 21:02:04 +01:00
..
...
2021-10-23 23:57:28 +01:00
2021-09-03 21:25:06 +01:00
2021-10-23 23:54:49 +01:00
2020-01-22 11:55:03 +00:00
2021-10-13 20:31:24 +01:00
2021-10-26 23:02:50 +01:00
2021-10-26 00:50:43 +01:00
2021-10-07 20:16:54 +01:00
2021-10-28 17:28:53 +01:00