Mined x16r for 36+ hours, balance has not moved. Should be at least 2 mBTC. What's up with that?

Edit: nvm, 4 weeks to find one block with full pool speed. LOL. I don't need a pool for that.

This whole pool is a shitshow. Been mining for 8 hours on it today to give it another chance. While 3 coins dropped, only 2 were credited. So yah, that's scammy.
And doesn't even include the huge incompetence at work here regarding missing splits, not protecting against basic hacks that are know for decades, or any DoS protection, fucking up payouts, not even changing the payout rules on the main page or constantly speaking of oneself in plural... and that's not half of it.
This is a business, act like it.

We should not use 24 hour actuals in our profit switching script, that makes sense.
But current estimate has a high fluctuation.

Does anyone see a reason why we should not just use the average of both values? (as long as current estimate is not zero)
Or we could just check if current estimate is not zero and still use 24 hour actuals?

I was using pool current estimate, due to the frequent splits. This results in a lot of algo changes, but I only update every 15 min.
I'm done with zergpool for now, maybe others had more luck. Because when it was up, profit was about +40%, at least until the orphans reduced profit of 20 hours to 0.

zergpool: 0.00247307 BTC
ahashpool: 0.00628855 BTC
This includes mutiple chain splits on both pools, ahashpool reacted quite fast (not fast enough, but more than 10x faster than zergpool). This plus the recent hack of zergpool, the coming .5% fee on it despite late chain split detection and a lot of down times, this does not look good for zergpool in any regard.

Download the file, fix line 13 to say $zergpool_Host = "zergpool.com" and create a new start file (e.g. copy from zpool) or change existing to -PoolName ahashpool,zergpool and choose your algos. Runs fine. A lot of switching however, the statistics are not reliable enough with this small miner base.