Too many people seem to have been confused and/or scared by the "skipped" report from the Fill task, thinking it indicated a bug or something, so I've removed it.

It was originally there mainly as debug info for my own use anyway, way back when the Fill feature was new and not thoroughly tested.
This commit is contained in:
Brettflan 2013-04-10 18:44:06 -05:00
parent 8006e1f0fd
commit e95e1b2f42
1 changed files with 1 additions and 3 deletions

View File

@ -48,7 +48,6 @@ public class WorldFillTask implements Runnable
// for reporting progress back to user occasionally
private transient long lastReport = Config.Now();
private transient int reportSkipped = 0;
private transient int reportTarget = 0;
private transient int reportTotal = 0;
private transient int reportNum = 0;
@ -178,7 +177,6 @@ public class WorldFillTask implements Runnable
// skip past any chunks which are confirmed as fully generated using our super-special isChunkFullyGenerated routine
while (worldData.isChunkFullyGenerated(x, z))
{
reportSkipped++;
insideBorder = true;
if (!moveToNext())
return;
@ -373,7 +371,7 @@ public class WorldFillTask implements Runnable
lastReport = Config.Now();
double perc = ((double)(reportTotal + reportNum) / (double)reportTarget) * 100;
if (perc > 100) perc = 100;
sendMessage(reportNum + " more chunks processed (" + (reportTotal + reportNum) + " total with " + reportSkipped + " skipped, ~" + Config.coord.format(perc) + "%" + ")");
sendMessage(reportNum + " more chunks processed (" + (reportTotal + reportNum) + " total, ~" + Config.coord.format(perc) + "%" + ")");
reportTotal += reportNum;
reportNum = 0;