Newcomer / Intro I don't get core mining... a bit...

If your getting more than 4 chunks at braking a rock you never went over charged...
Every core rock has prefixed numbers, 1 for normal cracking, 1 for Failure...
Every core rock can be repeated every 6 days for the exact same fragments every time...
Core mapped mining is done every 6 days but nobody shares their routes as every core rock is globaly shared on every platform and after a rock is cracked every instance of that ring will announce that there was a core rock there with a new dust cloud as other players pass by...
But every core rock in the same location in the ring is generated the same every time, every 6 days, so the miner get the same exact amount from the same rock...
If you get 14 with FULL crack, every 6 days you can get another 14 chunks... untill you crack a rock the chunks remain a random unknown number only after cracking do you know the number, just like laser mining rocks are exactly the same every 3 hours after 6 days every core rock generates the same chunks in the same location in the ring...
You can then repeat the rocks and get the exact same chunk count, every time, 9, 14, 12, 11, 15 and do this 5 core run every 6 days...
 
Last edited:
Oh, so you're saying that exceeding yield should give me like 4 chunks? Well I've certainly never seen that happen.

k, cool info, thanks man!
 
Oh, so you're saying that exceeding yield should give me like 4 chunks? Well I've certainly never seen that happen.
.........

... because, as I tried to explain (and obviously failed miserably) - the "...yield exceeded" message and the red boxes that appear above the blue ones on detonation is a known bug. You can see this in my videos - as soon as the actual detonation occurs the red boxes appear above the blue ones and the yield exceeded message appears even though the detonation successful message also appears.

I didn't do it but if you set your charges such that you have a load of red boxes BEFORE detonation - that is the yield exceeded range.

I have never detonated with charges set too low (no blue boxes) - I assume that too results in an unsuccessful detonation.
 
... because, as I tried to explain (and obviously failed miserably) - the "...yield exceeded" message and the red boxes that appear above the blue ones on detonation is a known bug. You can see this in my videos - as soon as the actual detonation occurs the red boxes appear above the blue ones and the yield exceeded message appears even though the detonation successful message also appears.
Yeah, and in case you want to know (from an epistemological standpoint) why you didn't convince me, see below ;)

The reason you didn't convince me was because of my presupposition of random yield on detonation, which you didn't dispute, and that you just said it's a known bug and you posted two screenshots where you got 14 yields.
My reaction to your claim was:
  • sample of two is garbage evidence, particularly that I have personal experience that contradicts this AND (more importantly) can present an order of magnitude more data on the spot that seemed to support my claim
  • existence of a known bug doesn't negate the possibility that there's something else going on. For example, refraction can be considered a bug of spherical earth model in that it allows you to take a picture over curved surface that makes it look flat (search "black swan flat earth" in google images), but that doesn't mean that there are no truly flat regions of earth.
  • frankly, you... riled me up by saying "no [I won't bother to back it up], others can testify I don't lie". That's two logical fallacies in one, argument from authority and appeal to popularity, that I found borderline insulting (at the time when you posted them) ;) . When you posted your screenshots later I was already midway through my testing ;)

On the other hand, what made Graphite's comment convince me is:
  • he told me that chunk yield is not a random on detonation, which is what I presupposed, but said that all cores have two preset values, one for optimal yield and one for failed yield. This is consistent with what I know about the game in general, i.e. I know that the game is mostly procedurally generated to the utmost detail, asteroid yields for laser and subsurface mining are fixed and mapped mining is a thing for laser and subsurface mining (e.g. the Egg exists), so it's logical this would work the same.
  • he said that "failed yield" is in the order of 4 chunks. I wasn't aware of it and I never got that kind of result, but anyone who did more mining than I did (so pretty much anyone) would immediately call him out on that if it was false; nobody did, so I'm willing to accept that.

Long story short, the needlessly long argument was rooted in a presupposition I had that was wrong and therefore your arguments didn't sound convincing to me, despite being obviously correct to you.

And that's a cool moral to this story for anyone, cause most arguments (particularly IRL) revolve around misaligned presuppositions.
Find the root of the issue and the rest will likely fall in place, unless it's down to personal taste, in which case it's a dead end anyway ;)
 
Last edited:
Really? Can you post a screenshot of that? (exceeded yield, 15 chunks freed)? I will do another run tonight perhaps and take screenshots of my results to compare. It's baffling.
.......

I remembered to press F10 today before heading back from the Painite hotspot I was checking for you (an alt account had to bring home before server downtime):

So "Optimum yield range exceeded..." message but successful detonation producing 15 chunks:

Umastae (20210518-174543).jpg
 
Thanks for coming back to that, although this subject was closed since Graphite's post ;)

Since in the post above mine you stated : "... frankly, you... riled me up by saying "no [I won't bother to back it up], others can testify I don't lie". Which misconstrued my no - I meant I had none available and you have decided to label that as "[I won't bother to back it up]". So basically you got up my nose with those words and I enjoyed remembering to actually produce a screen-shot of the 15 chunks with error message for your edification.

A subject is only closed when all participants feel it is closed (or T.J. closes it ;) ).

Have a nice day...
 
Last edited:
Since in the post above mine you stated : "... frankly, you... riled me up by saying "no [I won't bother to back it up], others can testify I don't lie". Which misconstrued my no - I meant I had none available and you have decided to label that as "[I won't bother to back it up]". So basically you got up my nose with those words and I enjoyed remembering to actually produce a screen-shot of the 15 chunks with error message for your edification.

A subject is only closed when all participants feel it is closed (or T.J. closes it ;) ).

Have a nice day...
Ok so I misunderstood you then. If you didn't have any at hand but intended to post later, I would've expected sth like "no, but I'll post one later when I can". Instead you delegated me to others vouching for you, which indicated you cba ;)

Never mind though, Graphite explained it to me pointing at a misconception I had that you didn't mention, which resolved the conundrum. You were right, the subject of "poor yields" is and was closed.
There seems to be another subject of your hurt feelings though ;) I hope that is closed now as well, given that it was just a misunderstanding on my part.
 
......

Never mind though, Graphite explained it to me pointing at a misconception I had that you didn't mention, ... .

The actual figures were news to me too - I thought there was some sort of graduated output - now I don't feel so bad if the yield only gives 13 chunks. :ROFLMAO:

All good - enjoy yourself. (y)
 
Back
Top Bottom