Fill process should run a bit more safely now if you have a really high frequency specified; it would previously drop out of the current fill loop if the process had been manually paused, but not if it had been automatically paused for low memory, which was an oversight
This commit is contained in:
parent
4620b0eac0
commit
2ed580556b
|
@ -132,7 +132,7 @@ public class WorldFillTask implements Runnable
|
|||
for (int loop = 0; loop < chunksPerRun; loop++)
|
||||
{
|
||||
// in case the task has been paused while we're repeating...
|
||||
if (paused)
|
||||
if (paused || pausedForMemory)
|
||||
return;
|
||||
|
||||
// every 5 seconds or so, give basic progress report to let user know how it's going
|
||||
|
|
Loading…
Reference in New Issue